Mapping a Manual Process
Operations
The goal is to turn day-to-day work into a clear map before writing code. Observe the work, map reality, confirm with the team, locate friction, compare a better path, create a blueprint, review with Quill, and build only what is justified.
- People Who performs the work and who receives it.
- Data What information the work needs and produces.
- Tasks What is actually done, in the words the team uses.
- Approvals Who has to agree, and what they are waiting for.
- Output What the process hands on, and to whom.
Overwhelmed to oriented to heard to represented to relieved to informed to confident to ready. That is the progression this section is built around.
System Mapping
Mapping a Manual Process
The goal is to turn day-to-day work into a clear map before writing code. Observe the work, map reality, confirm with the team, locate friction, compare a better path, create a blueprint, review with Quill, and build only what is justified.
- People Who performs the work and who receives it.
- Data What information the work needs and produces.
- Tasks What is actually done, in the words the team uses.
- Approvals Who has to agree, and what they are waiting for.
- Output What the process hands on, and to whom.
Overwhelmed to oriented to heard to represented to relieved to informed to confident to ready. That is the progression this section is built around.
- Start with the work — begins a new map
- View a sample map — opens a verified example
Eight steps, in order
Mapping method
The rail beside this section is a navigation aid, not a completion tracker. Scrolling past a step never marks project work complete.
The eight steps
- Overview Mapping comes before software, automation or redesign, because a system built on an unexamined process automates the confusion as well as the work.
- Start with a boundary.
- Name the trigger and outcome.
- Follow one real example.
- Capture people, information, tasks, approvals, and tools.
- Mark decisions and handoffs.
- Find friction without blame.
- Confirm the map with the team.
- Turn the map into requirements.
Mapping method
Eight steps, in order
The rail beside this section is a navigation aid, not a completion tracker. Scrolling past a step never marks project work complete.
The artwork paints a site navigation rail down its left edge. It is decoration here and carries no links; the site navigation is the one at the top of every page.
Field notes and common mistakes
On this page
Use the words the team uses. Treat the map as a mirror, not a solution.
Notes from the work
- Field notes Capture what people see and do, not what the facilitator expects. Use the words the team uses. Treat the map as a mirror, not a solution.
- Common mistakes Do not map an ideal instead of reality. Do not skip edge cases, approvals or handoffs. Do not mix unrelated processes to make the map look complete.
On this page
- Overview
- 1. Start with a boundary
- 2. Name the trigger and outcome
- 3. Follow one real example
- 4. Capture people, information, tasks, approvals, and tools
- 5. Mark decisions and handoffs
- 6. Find friction without blame
- 7. Confirm the map with the team
- 8. Turn the map into requirements
- Example: New Client Onboarding
- Field Notes
- Common Mistakes
- Printable Mapping Checklist
- Worksheet Preview
- Related Notes
On this page
Field notes and common mistakes
Use the words the team uses. Treat the map as a mirror, not a solution.
The contents list painted into this section is too small to be a reliable target, so it is shown here as artwork and the working list of links is directly below it.
Example: New Client Onboarding
Worked example
Inquiry, Discovery Call, Proposal, Contract, Kickoff, Access, First Delivery, Review. One real example, followed end to end.
- People Who does each step, and who is waiting on it.
- Information What each step needs before it can start.
- Task The work itself, named as the team names it.
- Decision A branch, and who decides which way it goes.
- Approval A gate, and the evidence it waits for.
- Handoff Where the work changes hands.
- Tool Where the step actually happens.
Worked example
Example: New Client Onboarding
Inquiry, Discovery Call, Proposal, Contract, Kickoff, Access, First Delivery, Review. One real example, followed end to end.
- People Who does each step, and who is waiting on it.
- Information What each step needs before it can start.
- Task The work itself, named as the team names it.
- Decision A branch, and who decides which way it goes.
- Approval A gate, and the evidence it waits for.
- Handoff Where the work changes hands.
- Tool Where the step actually happens.
Printable Mapping Checklist
Checklist
Twelve things a usable current-state map carries. Tick them here to keep track while you read.
These ticks stay on this page for this visit only. Nothing is stored, nothing is sent to Quill, and nothing here is a record of project work.
Download checklist: Not yet available. The file this control would open has not been supplied.
Checklist
Printable Mapping Checklist
Twelve things a usable current-state map carries. Tick them here to keep track while you read.
These ticks stay on this page for this visit only. Nothing is stored, nothing is sent to Quill, and nothing here is a record of project work.
- Not yet available. The file this control would open has not been supplied.
Worksheet Preview
Worksheet
A blank worksheet for one process: boundary, trigger, outcome, owner, steps, decisions, approvals, handoffs, tools and exceptions.
- Boundary Where this process starts and where it stops.
- Trigger What starts the work.
- Outcome What has to be true for the work to be finished.
- Owner Who is accountable for the process as a whole.
- Evidence What you observed, and what was only reported to you. To Verify
Worksheet
Worksheet Preview
A blank worksheet for one process: boundary, trigger, outcome, owner, steps, decisions, approvals, handoffs, tools and exceptions.
- Boundary Where this process starts and where it stops.
- Trigger What starts the work.
- Outcome What has to be true for the work to be finished.
- Owner Who is accountable for the process as a whole.
- Evidence What you observed, and what was only reported to you. To Verify
The artwork spells the trigger field label "TROGER". The correct label is TRIGGER, and the live text beside the plate reads correctly.
- Open worksheet — opens the mapping project page
Three notes worth reading first
Related notes
- Deciding What to Automate Which steps earn automation, and which only look like they do.
- Designing Human Approval Steps An approval is a gate with evidence behind it, not a rubber stamp.
- Protecting Creative IP What a map should and should not record about creative work.
Read note: Designing Human Approval Steps: Not yet available. This control points at a service page that is not part of this delivery and has no route in the site.
Related notes
Three notes worth reading first
- Deciding What to Automate Which steps earn automation, and which only look like they do.
- Designing Human Approval Steps An approval is a gate with evidence behind it, not a rubber stamp.
- Protecting Creative IP What a map should and should not record about creative work.
- Read note: Deciding What to Automate
- Not yet available. This control points at a service page that is not part of this delivery and has no route in the site.
- Read note: Protecting Creative IP
Get Building at Quill in your inbox
Building at Quill
Notes on mapping, workflows and the systems behind them.
Building at Quill
Get Building at Quill in your inbox
Notes on mapping, workflows and the systems behind them.
The eight stages of a Quill map
Map reality. Confirm together. Improve with evidence. Build with purpose.
- Learn. Understand why mapping comes before software, automation or redesign.
- Define. Establish the process boundary, trigger, intended outcome, owner and evidence.
- Map. Trace one real example through people, information, tasks, decisions, approvals, handoffs, tools, outputs and exceptions.
- Diagnose. Identify delay, rework, ambiguity, duplication, missing information, access problems and fragile dependencies without blaming individuals.
- Confirm. Review the current-state map with the people who perform and receive the work.
- Improve. Compare the confirmed current state with a proposed future path.
- Blueprint. Convert confirmed findings into requirements, open questions, assumptions, risks, priorities and human approval points.
- Handoff. Route the reviewed blueprint to the appropriate Quill path without asking the client to start over.
To verify before this page claims it
The supplied artwork paints figures, dates, names, statuses and statements that this build has not been able to confirm. Nothing on this list is published as fact until Quill confirms it.
- The hero paints the credit "RICK LOFTON — FOUNDER • COO • CTO • MARKETING DIRECTOR". The titles are not confirmed by any supplied document and are not repeated as fact in the live text.
- The blueprint annotations in the hero margins are drafting decoration. They carry no data and nothing on this page is derived from them.
Corrected in the live text
The artwork is published exactly as supplied. Where it paints a misspelling, a wrong number or a state nobody chose, the live text beside it reads correctly.
- The worksheet plate paints the field label "TROGER:". The correct label is "TRIGGER:", and the live text beside the plate reads correctly. The plate itself is published exactly as supplied.
What the sources do not carry
These are gaps in the supplied material, not decisions. They are recorded here so a reader can see why a control is disabled rather than guessing.
- Sample Maps. The UX map defines /system-mapping/sample/{slug} in full and no package was ever made for it. The route is registered at its final URL and says so; View a sample map opens it rather than 404ing.
- The mapping studio. UX map §10 defines a current-state canvas with steps, connections, an inspector, evidence and comment panels, undo and redo and a synchronised table view. No artwork of any kind was supplied for it, so Start with the work, Open worksheet and Start mapping all open a registered page that states where the work stands.
- Designing Human Approval Steps has no route anywhere in the site, so its Read note control is disabled rather than pointed at a guess.
- No printable checklist file exists in any approved archive, so Download checklist is disabled.
Where this goes next
Every one of these is a page that exists today. Nothing here points at a route that has not been built.
Map the work beneath the work
Clarity today. Better systems tomorrow. Tell us what should work better and we will map the work before anyone builds anything.
Review with Quill
A human review of a map or a blueprint is requested, not scheduled here. Submitting a request asks Quill to review and respond. It does not approve scope, authorise payment, begin implementation or confirm timing.
Review the Map with Quill explains what a review covers and how to ask for one. It does not book, confirm or schedule a review: there is no calendar behind it and no availability has been verified. Talk to Quill reaches a person today.