Business Process Mapping12% of the exam
Scoping and decomposing complex business processes
How to bound a complex process by its input and outcome, set its context with a capability model or SIPOC, and break it into readable levels of 8-10 verb-first activity boxes that drill down without losing scope.
Demonstrate how to define the scope of a complex business process and break it down into manageable steps.
~8 min read · 14 practice questions ·
What the exam expects
- Define a complex process by its triggering input and final outcome (Lead to Revenue), not by the applications it touches.
- Set the context and boundaries with a capability model or a SIPOC before detailed mapping.
- Break the process into levels of about 8-10 activity boxes, each drill-down scoped by its parent box's inputs and outputs.
- Write steps as verb phrases with clear inputs and outputs, and settle audience, purpose and resources (RACI) before a workshop.
- Know who decides in a mapping workshop and which process to map first.
Key terms:
- Input and outcome: what starts a process and what ends it; together, its scope.
- Activity box: one step, labelled with a verb phrase and its resource.
- Drill down: opening a lower-level diagram that details one activity box.
- Capability model: a list of high-level process areas.
- SIPOC: suppliers, inputs, process, outputs, customers.
- Process owner: the person who owns the end-to-end process.
Key facts
Process scope
- Detail
- Defined by input and outcome, not the application it runs in
Cross-boundary scope
- Detail
- A map can cut across departments and include external partners
Boxes per diagram
- Detail
- Aim for no more than 8-10 activity boxes on a screen
Lower-level scope
- Detail
- Set by the inputs and outputs of the box drilled into
Capability model
- Detail
- Lists high-level process areas; scopes the area and shows business context
SIPOC
- Detail
- Prepares for a detailed map; defines the scope of a complex process
Step labels
- Detail
- Start with a verb, clear inputs and outputs; avoid "manage"
Workshop decider
- Detail
- End-to-end process owner resolves differences and assigns next steps
First process to map
- Detail
- Start small: low risk, high impact, not a core process
Sources for this section (5)
- Create a Process Maptrailhead.salesforce.com (opens in a new tab)
- Get Started with Mappingtrailhead.salesforce.com (opens in a new tab)
- Understand UPNtrailhead.salesforce.com (opens in a new tab)
- Mapping in Practicetrailhead.salesforce.com (opens in a new tab)
- Mapping Languagetrailhead.salesforce.com (opens in a new tab)
- Why should a process be defined by its input and outcome rather than the application it runs in?
- When you drill down from an activity box, what limits the scope of the new diagram?
- Which two artifacts help define scope and context before a detailed map?
- When an organization is new to process mapping, which process should it map first?
- Who resolves a disagreement about the right sequence of steps during a mapping workshop?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Business Analyst pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 22 lessons of the Business Analyst guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (14 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams