In short, prototyping is the innovation hub that builds out Salesforce prototypes to show the “art of the possible”
This can be broken down into three main components:
1. User flow
It’s important that user’s know and understand how they will be using Salesforce. Which screens will they need to navigate to, which buttons they need to click, and what happens when actions are assigned to other teams.
This can be accomplished with a “swim-lane” style of user flow diagram. This type of diagram works well when there are multiple swim-lanes, that is, multiple personas collaborating. It should also show important decision points along the way.
2. System flow
Similar to the user flow, it’s important to know how data will flow during processes. This includes both within Salesforce and all connected systems.
In addition, as automation becomes more complex, it’s important to know which triggers cause which automation to execute, which may in turn cause subsequent triggers to fire. This
3. User Interface/User Experience (UI/UX)
When building more complex interfaces, using a mockup tool with a Salesforce extension can help users understand what the application will look like. Think visualforce pages and lightning web components (LWC). It also helps the develop build according to the design.
The takeaway
Prototyping isn’t necessary for small to medium implementations, but it’s critical for large scale ones. Once complete, everyone will understand what the general flow and UI will look like. Also, making changes at this phase is really simple.