Skip to content

Docs · Engines

Service Blueprint

Lynn-Shostack-style service blueprints. Five lanes — physical evidence, customer journey, frontstage, backstage, support — with the canonical 'line of interaction / visibility / internal interaction' dividers. Native engine, pure SVG; line-based DSL means every step is diffable in git.

Architectural composition of precision sculptural forms
Templates
10
Source language
plaintext
Workstation
Studio
Engine id
serviceblueprint

In the same space

Most users come to Service Blueprint from Figma blueprints, Miro service templates or Lucidchart swim-lanes. flowss runs this engine in the browser — no install, shareable via URL, exportable to PNG / SVG / PDF / source.

Syntax at a glance

title: Process name
evidence: Touchpoint A | Touchpoint B
customer: Step 1 → Step 2 → Step 3
frontstage: Action 1 | Action 2 | Action 3
backstage: Hidden A | Hidden B
support: System X | System Y

Paste this in the Studio code pane to see Service Blueprint render live. The full grammar is at the upstream-docs link above.

Sample templates

All 10 →
Engine reference: serviceblueprint · ← Browse all engines · Quick-start guide