Download the illustrative sample CSV
Set the map boundary
The start is an accepted sale; the finish is a first milestone reviewed by the project owner. Lead generation, detailed delivery steps, and final billing sit outside this map. Limiting the boundary keeps the workshop focused on whether sold work can start responsibly.
Read the process map
| Step | Owner | Input | Decision or action | Output / next step |
|---|---|---|---|---|
| 1. Record accepted scope | Seller | Accepted agreement and discovery record | Capture scope, exclusions, dependencies, and promises | Handoff brief to delivery lead |
| 2. Check readiness | Delivery lead | Handoff brief and capacity plan | Are scope, access, and capacity sufficiently resolved? | Accept or return a named blocker |
| 3a. Resolve blocker | Assigned owner | Specific missing prerequisite | Obtain evidence or agree a revised commitment | Return to readiness check |
| 3b. Schedule kickoff | Coordinator | Accepted readiness decision | Confirm a feasible date and customer responsibilities | Customer receives owner, date, and next action |
| 4. Review first milestone | Project owner | Delivery record and acceptance criteria | Confirm progress and resolve any remaining handoff gap | Normal delivery or an owned exception |
The decision that matters
Step two separates a sold job from an accepted delivery handoff. If readiness is incomplete, the process returns a specific blocker to a named owner. It does not send a vague request to a department or silently proceed to scheduling. After the blocker is resolved, the case returns to the readiness decision.
What this map intentionally leaves open
The sample does not prescribe exact staffing, a particular CRM, or a universal response deadline. Those depend on the business. The map identifies where those choices must become explicit: who accepts the work, what readiness means, and how the customer receives an agreed next step.
Validate with an actual case
Select one ordinary job and one difficult job. Ask each participating role to walk the sequence and point to the source record used at each step. Add exceptions the sample omits, such as a cancellation or a changed start date. If two people describe different routes, record the disagreement and verify it rather than voting for the tidier diagram.
From map to procedure
Once the sequence is agreed, write the instructions for the highest-risk decision or handoff. The map explains the relationship between steps; the procedure explains how an intended user performs a task. Link both to the same owner and review date so they do not drift apart.
Related implementation resources
Discuss the operating problem
Elixir consulting starts at $5,000 per month, with final pricing based on scope. Bring a recent example, the current workflow, and the person who owns the result to define the appropriate implementation scope.