In a conversation with a Salesforce colleague last week, he mentioned something quite surprising.

For his FSL project, he wrote a design document. No surprise there. However, his team is part of a larger project across multiple clouds, and he was the only one that wrote one. The other team members didn’t feel the need to have a design.

Um, what?

How do you know what to do without a design? It’s like trying to build a building without a blueprint. Where would the doors and windows go?

So let’s consider a few objectives for a design:

  1. It provides project clarity.
  2. It sets a functional goal(s).
  3. It aligns the team around these goals.

Keep in mind that every minute spent writing a design could potentially save hours of development and testing.

The takeaway
Before this conversation, I didn’t believe it was possible to start any project without a design. Even a quick enhancement benefits from spending a moment to consider options and then pick one.

Friends don’t let friends implement Salesforce without a design.

Category:
Salesforce