When you’re implementing a project or feature for a client, there are some important considerations.
Here are a few to keep in mind.
1. Ease of understanding
As a consultant, you spend countless hours looking at Salesforce. You understand how it works, how to find things, and what to do when things go wrong.
More often than not, your clients don’t have this understanding. So while building, occasionally place yourself in their mindset. The more you understand their green perspective, the better solution you will build
2. Modular
Should business logic be in 1 mega-flow, or multiple subflows? While it’s rare to build version 1 of a flow as a megaflow, there definitely needs to be a time in which it makes sense to keep things modular.
This is especially true when business logic can be used across multiple flows. But often it’s just a matter of splitting logic into logic groups.
3. Data-driven architecture
Not hardcoding text, easily updating parameters that may change over time, and building for scalability. Three great reasons why data-driven architecture is preferrable.
While it takes more time upfront to build them, your client will be happy. They will be able to update some things on their own, and not have to depend on you for every minor change.
To be continued tomorrow…
The takeaway
Make sure you’re building for your client, not for yourself.