Mapping & Implementing Workflows 🛠️
Process clarity first, then optimisation and AI.
You walk in with a workspace shell — teams, projects, members — and a list of processes from the Implementation Plan 🗺️ stage's Change Plan.
You walk out with workflows the team can actually run inside the platform, owned by named Change Leaders, and a Change Plan updated with what the work surfaced.
In this document
Mapping → Implementation — from the visual canvas to the platform
Simulation — the rehearsal that catches what the map missed
Automations — and where AI agents in project management responsibly begin
The Sum-up — handing ownership to the Change Leaders
What to prepare before this stage
Avoid this if you don't want your transformation to fail or delay
What you get with the full protocol
1️⃣ What happens at this stage
This stage has three workshops and one sum-up meeting, run over roughly three weeks.
🎯 Workshop 1 — Workflow Mapping (90 min). A facilitated session on a visual canvas (Miro, FigJam, Mural, or a wall of stickies). The Change Leaders, plus the people who actually run the steps, map one process end-to-end. Problems and conventions get captured with colour-coded stickies.
🎯 Workshop 2 — Workflow Implementation (90 min). Canvas → platform: project + sections, task templates, custom fields, dependencies, descriptions. The team's hands stay on the keyboard.
🎯 Workshop 3 — Workflow Simulation (90 min). The rehearsal. The workflow's named owner walks the team through it step by step; the team acts out their roles and surfaces what the map missed. The 80% test: does the workflow cover 80% of real-life scenarios?
⚠️ Meeting 4 — Mapping & Implementing Sum-up (60 min). Not a workshop — a handover. You walk the Guardian (and the Sponsor, if available) through the updated Work Management Change Plan: what got built, what got parked for later (🌱), and which Change Leader now owns each workflow. This is the meeting where the Sponsor either visibly endorses what just shipped or you have a problem.
Note on naming (Sponsor, Guardian, Change Leaders) — click to reveal
These roles were formally appointed at the
Kick-off 🏈 stage.
At this stage, the Sponsor signs off on scope and shows up at the Sum-up; the Guardian owns prep and chases attendance; the Change Leaders are the workshops' primary participants and become process owners by the Sum-up.
2️⃣ Mapping → Implementation — from the visual canvas to the platform
What's mapped on the canvas one week becomes what's built in the platform the next.
Mapping is a facilitated session on a visual canvas where the people who run the steps externalise the process end-to-end. Problems get marked with red stickies, conventions with black. The canvas is built activity-first — each step is a verb the doer performs, not a noun like "design phase." Each workflow gets classified as one of three blueprints (deadline-bound, ongoing, or reference). Get this wrong and it's hard to fix at Implementation.
Implementation is the translation step. Each red and black sticky becomes a platform element — a custom field, a rule, a template, a dependency. The principle: guide by hand, demonstrate, leaders implement, we verify, we teach. The Change Leaders' fingers are on the keyboard from minute one. The Operator never clicks "create team" for them — not even once.
3️⃣ Simulation — the rehearsal that catches what the map missed
The Simulation workshop is the cheapest insurance you'll buy in this engagement. The named owner walks the team through the workflow step by step; the people who'd run those steps act out their roles. Not pretend-roles — their roles. The team is checking three things: does the workflow cover 80% of real scenarios, does the next person know when a handoff is theirs, and when something goes wrong, does the workflow tell you whose problem it is.
4️⃣ Automations — and where AI agents in project management responsibly begin
Once a workflow is mapped, implemented, and rehearsed, it's ready for the layer that scales it: automations. The patterns repeat across workflows — completion ↔ section move, due-date reminders, custom-field changes that spawn the next sub-tasks, multi-homing on shared deliverables. The toolkit ships with eight ready-to-use rules that cover roughly 80% of common cases.
Where AI agents begin — and why this stage is the first responsible moment
This stage is the first stage where proposing an AI agent stops being premature and starts being responsible.
Before this stage, there's no mapped process for an agent to sit inside. Drop an agent into a fuzzy workflow and it amplifies the fuzziness — at the speed of automation.
After this stage, the prerequisite for placing an agent exists: a workflow that's mapped, implemented, rehearsed, and owned. The test for "is this step agent-able?" becomes answerable — if a junior on day one were handed this step with the workflow open in front of them, would they know what counts as "done"? If yes, it's a candidate. Agents and rule-based automations are the same family — both replace a human step, both need process clarity, both inherit ownership from the workflow.
5️⃣ The Sum-up — handing ownership to the Change Leaders
A 60-minute meeting between you, the Guardian, and ideally the Sponsor. The agenda is the updated Work Management Change Plan — what got built, who owns it, and what got parked with a 🌱 for the next quarter's conversation at the Business Impact Review 📈 stage. Sponsor absence here costs you Launch-day adoption.
6️⃣ What to prepare before this stage
- The list of in-scope workflows from the Implementation Plan 🗺️ stage. Not "every process the team mentioned" — the prioritised, scoped list the proposal committed to. If this list isn't pinned down, run a 30-minute scoping call before Workshop 1.
- A RACI matrix per workflow, if you have one. Translates cleanly into custom-field values for Accountable and Responsible .
- A working visual canvas. Miro, FigJam, Mural, a wall of stickies in a war room. Whatever the Change Leaders will actually use across the three workshops.
- The right people in the room. This is non-negotiable: at least one manager and at least one person who actually runs the steps. Manager-only mapping produces theoretical workflows whose task names don't match what the doers say.
- A named owner per in-scope workflow. Selected before Workshop 3. They'll present at Simulation, and they own the workflow from the Sum-up onward.
- Calendar runway for four sessions across ~3 weeks. Three workshops × 90 min plus a 60-min Sum-up. Surface vacation conflicts now, not at Workshop 2.
- A short Loom from the Operator. Recorded between Workshop 2 and Workshop 3, walking through how to add a custom field, create a sub-task, and set a dependency. Used by the Change Leaders while they're doing their between-meeting homework.
7️⃣ Avoid this if you don't want your transformation to fail or delay
‼️ Don't let the Sponsor ghost this stage. This stage is the most visible deliverable of the whole engagement — workflows the team can actually run. If the Sponsor isn't visibly engaged at the Sum-up, the team reads their absence as ambivalence, and ambivalence at this stage costs you Launch-day adoption.
‼️ Don't map processes from the manager's chair alone. Theoretical maps written by managers use task names that the people doing the work don't recognise. The first sign you have this problem: the workflow is implemented, you walk into Simulation, and the doers ask "wait, what does Stage 2: Refinement actually mean?" Map with both managers AND the people who run the steps in the room — every single workshop.
‼️ Don't try to perfect every workflow in the meeting. Three sessions of 90 minutes is the cap. Descriptions, sub-tasks, additional dependencies — that's between-meeting homework owned by the Change Leaders. Perfecting in the room trains the team to wait for you.
‼️ Don't propose an agent or automation before the workflow is mapped. Both amplify whatever they sit inside. If the process underneath is fuzzy, you're scaling fuzziness — at the speed of software. Map the workflow, run the simulation, then mark the steps that are candidates for automation or agentisation. Anything proposed earlier is automation theatre.
‼️ Don't skip the Simulation. "We mapped it and built it — let's just launch" is the line teams use to skip a 90-minute rehearsal. Three out of five times, Simulation surfaces a missing handoff or an unclear ownership boundary that would otherwise show up two weeks into Launch as silent breakdown.
‼️ Don't leave workflows un-owned at the Sum-up. Every implemented workflow leaves this stage with a named owner from the Change Leaders. Anonymous workflows at this stage become uninhabited workflows by the Onboarding 👋 stage.
‼️ Don't blow scope on the canvas. "While we're mapping, let's also do our finance process and our two product lines" is how this stage turns from three weeks into eight. The proposal scoped a specific number of workflows for capacity and pricing reasons. Park new requests with a 🌱 in the Change Plan — they belong in next quarter's scope, not this one's.
✅ What you get with the full protocol
The full Reliability Protocol is delivered as one weekly action by email. You don't read 15 stages in one sitting — you receive one stage at a time, with one implementable artifact, and one clear next step you (or your Guardian and Change Leaders) can act on that week. The artifacts you get for this stage:
- The Workflow Mapping Workshop runbook — agenda, the red/black sticky-note convention for problems vs. conventions, the Jamie/Tom/Lisa/Veronica example for calibrating the room, and the warm-up question bank.
- The Workflow Implementation Workshop runbook — the Deadline-bound vs. Ongoing vs. Reference blueprint decision tree, the guide → demonstrate → leaders implement → verify → teach pattern, and the post-meeting handoff checklist.
- The List of Simple Automations — the eight ready-to-use rules covering completion ↔ section move, multi-homing on custom-field change, due-date reminders, approval-triggered sub-tasks, and My Tasks auto-sort.
- The 7-Element Implemented-Process Checklist — the verification checklist you walk through before declaring a workflow "implemented" (sections, custom fields, templates, dependencies, automations, saved searches, multi-homing).
- The Workflow Simulation script — the rehearsal protocol, the 80% coverage rule, and the workflow-specific conventions capture sheet.
- The Sum-up Agenda + Change Plan update template — the end-of-stage handover script with the 🌱 upsell-marker convention for problems out of this quarter's scope.
💬 Take this with you and your Change Leaders can run the mapping and implementation themselves. Hit a wall — especially on agentisation candidates or the multi-process linking — and want a partner — book the session below.
💡 This is Stage 6 of the Reliability Protocol — Remote Sensei's 15-stage system for permanent organisational transformation, and the global standard for Asana implementation: making Asana and AI stick in mid-size and enterprise teams so work ships on time without anyone chasing it.