← Back to jobs

Creating a value-stream diagram

What it is

A value stream is a single picture that shows how work, value, or product moves through your business — from where it starts (an order, a material, a request) to where it ends (a delivered product, a payment, a closed case). It is one of the most useful pictures you can put on a workshop wall: it tells your audience the shape of the flow at a glance and lets them point at specific Epics and Processes when they want to discuss them in detail.

A value-stream diagram has two structural ingredients:

  • Epics — the big groupings. Most diagrams have 4–8. They might be plants, departments, business areas, phases, or named streams ("Order to Cash", "Hire to Retire") — whatever your audience recognises.
  • Processes — the discrete activities inside an Epic. Each Process has a short verb-noun label like "Receive cylinder", "Weigh post processing", "Issue invoice".

Anything else on the diagram — system labels, role icons, numbered IDs, status flags, decision diamonds, handoff arrows — is decoration. Decorations are useful when you have the data for them, and visual clutter when you don't.

Deliverable definition

Objective. Show how work moves through a business in a single named flow, in enough detail to drive a process-architecture review, an integration-point workshop, or an operational onboarding session.

Nature. Precise, structured, label-led. The visual register is panels, arrows, named processes, system overlays, persona icons. A value stream is read by a technical or operational audience and is expected to support questions like "where does this hand off?", "which system carries this?", "who does this work?".

Required ingredients.

  • A title naming the flow.
  • Between four and eight epic panels arranged left to right or in a branched flow.
  • Each epic has a title, the system that supports it (where named in input), one to three named processes (verbatim from input), and optionally a persona role.
  • Connecting arrows showing flow between epics.

Optional ingredients. Broader phase groupings (greyed background panels) bundling related epics; process codes (e.g. 3.2.1.4) when the input provides them; scenario overlays (e.g. dashed boxes outlining a specific variant); a legend strip.

Out of scope. Decorative imagery beyond the iconographic vocabulary; multiple unrelated value streams in one diagram (if the input implies multiple flows, use the value-stream preprocessing prompt to split them and run each as a separate diagram); free-form prose annotations.

What it is for

A value stream is a communication artefact, not a database. Before you start, decide:

  • Who is the audience? A process-architecture team running a design review wants step-level fidelity, decision points, system labels, and IDs they can quote. An executive sponsor wants Epic names, one-line captions, and a single readable left-to-right flow. An ops team wants the steps it owns and clear handoffs to other teams.
  • What is the purpose? Are you walking through handoffs to find integration risk? Showing how a future-state target differs from the current state? Onboarding a new team member? Each of those needs a different label density and a different emphasis.

The same business can have several valid value-stream diagrams — one per axis, one per audience. The tool serves whichever axis you describe in the input. It does not pick one for you.

What this tool does

The tool produces a 60–80% first draft of a value-stream diagram from your input. The draft is meant to be a starting point your team can refine by hand — not a finished artefact.

It is not a research tool. Anything that appears on the output diagram has to come from one of your inputs — your text, your images, or the visual idiom of your style image.

What inputs the tool needs

A minimum-viable input

  • Request — one sentence naming the value stream and the audience. "Show how a fuel cylinder physically moves through Urenco's plants end-to-end, for the process-architecture team."
  • A style image — one diagram whose visual idiom you like. The output will look like this image (idiom, palette, density).

That's enough to get a thin diagram. Epics will be inferred from your sentence (so be specific). Processes will be sparse.

A useful input

Add a Details section that lists the Epics in order with a short caption each. Optionally, under any Epic where you have step-level content, add a bullet list of Processes. Where you don't have content, leave the Process list empty — the tool will render the Epic as a named grouping with a "(detail TBD)" caption rather than invent steps.

A rich input

Add content reference images via the "Add reference image" button — one per Epic where you have step-level detail, or one shared reference covering several Epics. Each reference image should have an intent note telling the tool what to take from it. Examples:

  • "Detailed Processes for the cylinder feed side; use as supporting detail for the Enrichment Epic."
  • "Authoritative content for the Order to Cash Epic — render the named Processes verbatim."
  • "Visual style only — do NOT lift any text from this image."

The intent note matters. Without it the tool guesses the image's role and may treat content as style or vice versa.

What to expect from the output

  • The visual idiom will match your style image.
  • Epic names will match your input exactly. Six Epics named in Details produce six Epics in the output.
  • Processes will match your input exactly. Where you do not list Processes, the Epic appears as a named grouping with a "(detail TBD)" caption.
  • Decorations will be conditional. System pills appear only where you name a system. Role icons appear only where you name a role. Numbered IDs appear only where you supply IDs.

The output is one PNG (final-image.png) plus a copy of the brief that fed the image model (generated-visual-brief.md). Read the brief — it shows you exactly what the tool extracted from your input.

Common mistakes

  • Promising more than you supply. "Show me the 5–6 value streams" followed by content for one stream produces invented streams. Either enumerate the streams you want, or scope the request down to the one you can describe.
  • Using one image as both style and content. Better: split into two images — one for style, one for content — and add intent notes.
  • Letting the style image's text bleed into the output. Write "do not lift system names, role labels or IDs from the style image" in your Visual guidance section.
  • Treating the first output as final. It is a 60–80% draft. Plan for one or two refinement passes via the Refinement bullets section.

Glossary

  • Epic — a top-level grouping in a value stream (4–8 typical).
  • Process — a leaf-level activity inside an Epic (verb-noun label).
  • Decoration — optional metadata on a Process: system, role, ID, phase, status.
  • Skeleton — the ordered list of Epic names — the diagram backbone.
  • Style image — the image the output should visually resemble.
  • Content reference — an image carrying named Processes, systems or roles to be rendered on the output.
  • Intent note — a short text that tells the tool what to take from an image. Set it via the upload form.

→ Help on rich pictures  ·  ← Back to jobs