Skip to main content

Map the work beneath the work.

Pick one operation your business runs every week. Four steps later you will have it written down: who does it, what starts it, where it waits and what comes out.

Begin my map

No stage selected yet. Begin with Define.

Quill Services

Map the work beneath the work.

Pick one operation your business runs every week. Four steps later you will have it written down: who does it, what starts it, where it waits and what comes out.

The painted rail shows a stage already active. That is a mock state in the supplied render: nothing is selected until you select it.

Mapping stage

No stage selected yet. Begin with Define.

Name the operation.

Step 1 of 4

One operation, four answers. What it is called, what starts it, who owns the result and how often it runs.

  • Operation name What the people who do it call it.
  • What starts it The event, request or date that sets it going.
  • Who owns the result The one person accountable at the end.
  • How often How many times it runs in a normal month.
Continue to the map

Step 1 of 4

Name the operation.

One operation, four answers. What it is called, what starts it, who owns the result and how often it runs.

  • Operation name What the people who do it call it.
  • What starts it The event, request or date that sets it going.
  • Who owns the result The one person accountable at the end.
  • How often How many times it runs in a normal month.

The four fields are painted already filled, with an example operation rather than a real one. The live fields are collected once, at step 4, so a visitor types the operation name in the same place they send it from.

Build the current-state map.

Step 2 of 4

Lay the operation out as it actually runs today, not as the process document says it runs. Five kinds of thing go on the canvas.

Test this path

Add step: Not yet available. The screen this control would open is shown in the artwork as a concept and has not been built.

Add decision: Not yet available. The screen this control would open is shown in the artwork as a concept and has not been built.

Add handoff: Not yet available. The screen this control would open is shown in the artwork as a concept and has not been built.

Step 2 of 4

Build the current-state map.

Lay the operation out as it actually runs today, not as the process document says it runs. Five kinds of thing go on the canvas.

The canvas, the zoom controls and the node inspector are artwork: the drawing tool they depict is not part of this delivery, so the three add controls ship visibly disabled rather than as buttons that do nothing. The operation drawn on the canvas, its owner names and its schedule are example content invented for the render. They are not a Quill client, a Quill project or a Quill result, and nothing from them is published as fact.

What goes on the map

Nothing selected yet.

Follow one task end to end.

Take a single piece of work and walk it from the thing that triggered it to the thing that came out. Every wait it sits in is a wait every other task sits in too.

  • Trigger What set this piece of work going.
  • Output What the business has at the end that it did not have before.

Follow one task end to end.

Take a single piece of work and walk it from the thing that triggered it to the thing that came out. Every wait it sits in is a wait every other task sits in too.

  • Trigger What set this piece of work going.
  • Output What the business has at the end that it did not have before.

The artwork paints six status cards between Trigger and Output. The four middle labels are not legible in the supplied plate, so only the two endpoints ship and the rest are on the verification list.

Find the friction.

Step 3 of 4

Four places the work loses time. Reading them together usually explains most of what the operation costs.

  • Current flow score A single reading of how well the mapped operation runs today. TBD
Scan my workflow

Step 3 of 4

Find the friction.

Four places the work loses time. Reading them together usually explains most of what the operation costs.

  • Current flow score A single reading of how well the mapped operation runs today. TBD

The flow-score gauge is painted with a "Demo score" badge and the value TBD. No number is published here. The four friction card labels are not legible in the supplied plate and are not invented.

See the better path.

The same operation twice: as it runs now, and as it would run once the waits are taken out. Switch between them.

Apply recommendations

Choose Current or Recommended.

See the better path.

The same operation twice: as it runs now, and as it would run once the waits are taken out. Switch between them.

The artwork paints three recommendation cards beneath the two diagrams. Their headings are not legible in the supplied plate and are not invented here.

Flow view

Choose Current or Recommended.

Your operations blueprint.

Step 4 of 4

The map, the friction and the better path, written down as one document Quill can build from.

Download my map: Not yet available. The file this control would open has not been supplied.

Send my map to Quill

Tell us which operation you mapped and where to reach you. The selections above stay in this browser, so repeat anything that matters here.

This form does not send anything yet. There is no approved submission endpoint for the Service pages, so nothing you type here is stored, transmitted or received by Quill, and no request is created. Use Start a project, or Talk to Quill, to reach us today.

The event, request or date that sets it going.

How many times in a normal month.

The places the operation waits, repeats, or gets lost.

This form does not send anything yet. There is no approved submission endpoint for the Service pages, so nothing you type here is stored, transmitted or received by Quill, and no request is created. Start a project, or talk to Quill, to reach us today.

Step 4 of 4

Your operations blueprint.

The map, the friction and the better path, written down as one document Quill can build from.

The artwork paints a "Deliverables included" checklist on the brass scroll. The list items are not legible in the supplied plate, so no deliverable is promised here.

Send my map to Quill

Tell us which operation you mapped and where to reach you. The selections above stay in this browser, so repeat anything that matters here.

This form does not send anything yet. There is no approved submission endpoint for the Service pages, so nothing you type here is stored, transmitted or received by Quill, and no request is created. Use Start a project, or Talk to Quill, to reach us today.

The event, request or date that sets it going.

How many times in a normal month.

The places the operation waits, repeats, or gets lost.

This form does not send anything yet. There is no approved submission endpoint for the Service pages, so nothing you type here is stored, transmitted or received by Quill, and no request is created. Start a project, or talk to Quill, to reach us today.

Ready to turn the map into a working system?

A map is worth having on its own. It is worth more when somebody builds against it.

Review my map with QuillKeep editing

Ready to turn the map into a working system?

A map is worth having on its own. It is worth more when somebody builds against it.

Review my map with Quill is the same request as Send to Quill on section 07, painted a second time. It opens that one form rather than creating a second destination for the same action.

Where this goes next.

Mapping one operation is the first of five connected capabilities. The rest build on what the map shows.

Your saved plan

Your plan is saved in this browser only. It is not sent to Quill, and anyone else using this browser can see it.

Not saved yet. Use the save control on this page to keep your selections in this browser.

Nothing is saved in this browser for this page yet. Make your selections above, then use the save control.

To verify before this page claims it

The supplied artwork paints figures, dates, names and statements that this build has not been able to confirm. Nothing on this list is published as fact until Quill confirms it.

  • Section 05 paints a flow-score gauge badged "Demo score" with the value TBD. No score is published. How is a flow score calculated, and what does it read against?
  • Sections 02 to 06 are painted around one example operation, with invented owner names and an invented schedule. It is not a Quill client and not a Quill result. Should the live page carry a worked example at all, and if so, whose?
  • Section 03 paints a drag-and-drop canvas editor with zoom, pan and a node inspector. No such tool is part of this delivery. Is it being built, and against what route?
  • Section 04 paints six status cards between Trigger and Output. The four middle labels are not legible in the supplied plate.
  • Section 05 paints four friction cards and section 06 three recommendation cards. Neither set of labels is legible, and none of them is invented here.
  • Section 07 paints a "Deliverables included" checklist whose items are not legible. Nothing is promised as a deliverable until that list is supplied.
  • Download my map and Send to Quill both need something that does not exist yet: a generated map file and an approved submission endpoint. Both are held until they do.

Corrected in the live text

The artwork is published exactly as supplied. Where it paints a misspelling or a wrong number, the live text beside it reads correctly.

  • The artwork paints a stage in the hero rail as already active, and the step 1 fields as already filled. The live controls ship with nothing selected and nothing typed, because the design spec forbids baking progress or a selectable value into the raster.

Start a project with Quill

Tell us what should work better and we will map the work before anyone builds anything.