Example data. Fieldnote is a fictional company used to fill all 61 boards, so the examples tell one consistent story.
Scale-up Fieldnote: Karim, Julien (support), Tom and an ops person blueprint the intervention flow to find where invoicing data gets lost.
What the team took away
The leak is at step 5: two hours of manual cleanup every Monday. The Integrations squad got its first mission, Pennylane sync.
How to run it
Preparation
Invite one person from each function behind the scenes: ops, support, tech, plus product and design. Eight people max, and every function present or the blueprint has holes.
Start from an existing journey map. If you do not have one, run it first; a blueprint without the customer line is an org chart.
Collect the internal process docs, SLAs, and the tools list. Print the list of systems involved.
On the board: the customer actions row at the top, the line of visibility, front stage, back stage, systems rows, one column per journey step.
Agenda
20 min
Recall the journey Walk through the customer actions row from the journey map. Fix the columns. Nobody adds internal steps yet.
40 min
Front stage Under each step: what the customer sees or who they talk to. Screens, emails, humans. Mark where the customer waits.
60 min
Back stage What happens out of sight to make the front stage possible: manual checks, approvals, tickets, handoffs between teams. Support and ops drive this part; product listens.
30 min
Systems The tools and data behind each back stage action. Draw the lines: where information is re-typed from one tool to another is a failure point.
50 min
Find the bottlenecks Trace time and effort per column. Circle steps with a wait over 24 hours, a manual copy, or more than two handoffs. Vote for the three worst.
40 min
Owners and next step For each bottleneck: is it a product fix, a process fix, or a staffing fix? Name an owner and a date to come back with a proposal.
Pitfalls
Do not map the process as documented. Map what people actually do, including the spreadsheet nobody admits to.
Keep the customer row honest and short. Blueprints die when the back stage takes 80 % of the board and nobody remembers the customer.
Half a day is the minimum. Splitting it across two short meetings loses the cross-function conversation that is the whole point.
Afterwards
The bottlenecks list goes to the operations lead and the product lead together. Product fixes enter the prioritization matrix; process fixes go to the team charter or a dedicated ops sprint. Refresh the blueprint after any org change.