BoardSnap is an iOS app that reads a service blueprint whiteboard — customer actions, onstage and backstage processes, support systems — and produces a complete structured service design summary.
A service blueprint is a user journey map with the backstage processes included. It shows not just what the customer experiences, but what happens behind the scenes to deliver that experience — the internal processes, the systems, the employees the customer never sees. A service blueprint on a whiteboard typically has five rows: Customer Actions, Onstage (visible) Employee Actions, Backstage (invisible) Employee Actions, Support Processes, and Physical Evidence.
The depth of a service blueprint makes it one of the hardest documents to produce. You need input from customer research, operations, IT, and front-line staff — all in the same room. The whiteboard is the only tool that can hold all five layers simultaneously and let diverse stakeholders contribute at their level.
Transcribing a service blueprint is a multi-day job. A single-row journey map is hard enough. Five rows, five to eight stages, up to forty cells of content — the amount of information in a finished service blueprint is immense. Teams often don't finish the documentation, which means the insights from the session are never fully captured.
Label five horizontal rows on the left side of the board: Physical Evidence (top), Customer Actions, Line of Interaction (draw a thick horizontal line), Onstage Employee Actions, Line of Visibility (another thick line), Backstage Employee Actions, Line of Internal Interaction (third thick line), Support Processes (bottom). The three lines of interaction are structural — draw them prominently.
Write stage headers across the top — the same customer-facing stages as a journey map. Each column is a stage of the service delivery. The columns and rows create the grid that every cell fills.
What does the customer do in each stage? This is the journey map row — the most familiar content. Write three to five specific actions per stage.
What does the customer-facing employee do in response to the customer actions? These are visible interactions — the check-in agent, the support rep, the barista. Be specific about what they say and do.
What's happening behind the scenes? Backstage employee actions the customer never sees. Support processes — the systems, databases, supply chains, and internal workflows that enable the frontstage. This is where the operational complexity lives.
Mark cells where the service regularly fails with an F. Mark cells with significant wait time with a W and the typical duration. These become the primary design targets.
Open BoardSnap. A service blueprint is one of the largest and most complex boards BoardSnap reads. Step back as far as the room allows. If the board is too large for one frame, snap the customer-facing rows and the backstage rows separately.
A multi-row service blueprint summary organized by stage and row. Each cell's content is summarized. Failure points are flagged as issues. Wait times are noted. Lines of interaction are described as structural boundaries. The output is a comprehensive service design brief — usable as input to a process improvement project, a vendor RFP, or an internal training document.
A hotel operations team mapped the check-in service blueprint with six stages and five rows. The backstage row revealed that three different internal systems had to be queried for each guest — a process taking 90 seconds that could be collapsed into one system call. BoardSnap captured the discovery. The IT team used the blueprint summary as the requirements brief for a system integration.
A product team mapped the onboarding process for enterprise customers. The backstage row showed that four internal teams were involved in the onboarding without a single owner. The blueprint made the ownership gap visible for the first time. BoardSnap's summary went to the VP of Customer Success as the diagnostic artifact.
A clinic ran a blueprint session with doctors, nurses, and admin staff. Five stage columns, five rows. The result was a 20-cell grid with specific failure points in the insurance verification backstage row. BoardSnap read the grid structure and produced a summary that the clinic director used to justify a new intake system to the board.
Service blueprints are among the most complex boards BoardSnap reads — large grid, multiple rows, dense content. For best results: label every row on the left side, label every stage column across the top, mark failure points with a consistent symbol (F or a star), and snap from as far back as the room allows. For very large blueprints, snap in two sections.
Yes. The three lines of interaction (Line of Interaction, Line of Visibility, Line of Internal Interaction) are structural. Draw them first as thick horizontal lines before filling cells. BoardSnap reads these as section boundaries and uses them to assign content to the correct row.
Write the name of the artifact or script in the relevant cell and underline it. BoardSnap will include it in the output. Physical samples (a form, a card) can be photographed separately and stored alongside the BoardSnap summary in the project.
Build the customer-facing journey first, then add the backstage to make it a service blueprint.
Diagram the internal backstage processes in detail with a dedicated process flow.
The customer journey map focuses on the outside-in view — complement it with the blueprint.
Snap the board, ship the action items in ten seconds.