Part 2: Map Your Process to Reality (Not the Ideal)

How do you map a business process correctly?

Start from a real, recent instance of the work and write down every step in the order it actually happened — including the messy parts. Map reality first; improve it second. A process that ignores how work really happens will be ignored.

This is part 2 of the Process Implementation Playbook.

Step-by-step: mapping the work

1. Pick a real example. Choose the last time you delivered this work. Memory of a specific instance beats abstract theory.
2. List every step in order. Don't filter yet. Capture even the "obvious" ones — they're often where new hires stumble.
3. Note the owner of each step. Who actually does it?
4. Capture decisions and branches. "If the client is enterprise, do X; otherwise Y." These become conditional rules.
5. Record the edge cases. The exceptions are where quality breaks down.
6. Then simplify. Now you can remove waste and reorder — knowing what you're changing.

What to capture for each step

• A clear, action-oriented name ("Send kickoff email", not "Kickoff")
• The owner or role responsible
• Inputs needed and outputs produced
• Any data to collect (these become form fields)
• The condition under which it runs (if not always)

Do this in ProcessKit

Use the AI co-pilot to turn your written notes into a draft process, then refine the steps, fields, and rules. The co-pilot gets you 80% of the way in minutes; you provide the judgment.

Continue the series

⬅️ Previous: Part 1 — Process Implementation overview ➡️ Next: Part 3 — Assign roles and handoffs