Choosing the first process to map
Key Takeaway
Map a small, low-risk, high-impact process first, such as onboarding (Recruit to Day One), not the organization's core process, such as Lead to Revenue.
Business process mapping shows a process visually, from the input that starts it to the outcome that ends it, so a team can see the process and improve it. Teams often resist mapping, so your first map has to prove its value quickly. Salesforce recommends starting with a smaller process that is low risk and high impact, not the organization's core process.
Define a process by input and outcome
Define a business process by its input, the thing that starts it, and its outcome, the result that ends it. Don't define a process by the application it runs in. Processes often span several applications and manual activities, so Salesforce screens rarely cover the whole process.
Your goal is a better business outcome, not just a better application. So always consider the broader end-to-end process.
Here are three processes defined by input and outcome:
| Process | Input | Outcome |
|---|---|---|
| Lead to Revenue | A lead qualified by marketing | Revenue booked into accounts receivable |
| Hire to Retire | An open role | An employee's last day |
| Recruit to Day One | A new hire | The new employee finishes their first day |
You can scope a process at different levels. Hire to Retire is a high-level process. Recruit to Day One is narrower.
After you agree on a process's input and outcome, they set the scope for every level of detail below it. When you drill down into an activity box, the next-level map is limited by that box's input and outcome.