Audit 🔍
Diagnosing what the actual blockers in the company are.
You walk into this stage with a plan written on assumptions. You walk out with a plan written on evidence. The gap between the two is where every transformation either earns its Implementation Plan or guesses at it.
The job at this stage is narrow and unglamorous: sit with the people who do the work, ask better questions than they're used to being asked, and write down what's actually true. No diagnosis, no prescriptions, no "we recommend."
In this document
Part 1 — Group Audit Meeting with Change Leaders
Part 2 — Tooling Landscape Workshop
Optional — 1-on-1s with Change Leaders
What to prepare before this stage
What you get with the full protocol
1️⃣ What happens at this stage
Audit is one stage with two distinct meetings, plus two optional escape hatches that get used more often than you'd think.
🎯 Meeting 1 — Group Audit Meeting with Change Leaders. A 1.5-2 hour facilitated session, run with all the Change Leaders together. The first time the methodology touches the operating layer of the company beyond the Sponsor and Guardian. This meeting alone surfaces 70-80% of the friction Stage 5 will need to design around.
🎯 Meeting 2 — Tooling Landscape Workshop. A separate session, with the same Change Leaders, that maps the actual tool stack: which tool is used for what, by whom, and when. Run only when Meeting 1 reveals that the tool stack itself is part of the problem (high digital-literacy variance, overlap between tools, or no shared conventions on what-goes-where).
🎯 Optional — 1-on-1s with individual Change Leaders. When something in the group meeting didn't quite get said. Run privately, with a different posture and a different question set.
🎯 Optional — Intervention. When the audit reveals something that isn't a process problem at all — a Change Leader who shouldn't be one, a hidden conflict between functions, a Sponsor who's quietly disengaged. The audit pauses. The Implementation Plan 🗺️ stage doesn't start until the underlying issue is resolved.
All of this feeds the Work Management Change Plan — the Implementation Plan 🗺️ stage's deliverable that becomes the spine of everything from Foundation onward. Audit produces the evidence; the Implementation Plan 🗺️ stage turns the evidence into a plan.
Note on naming (Sponsor, Guardian, Change Leaders) — click to reveal
These titles were formally appointed at the
Kick-off 🏈 stage and hold for the rest of the Protocol.
At Audit, the Guardian chases survey discipline and meeting cadence, the Change Leaders are the audit's primary subjects, and the Sponsor only joins if an Intervention is triggered.
2️⃣ Part 1 — Group Audit Meeting with Change Leaders
This is the meeting that makes or breaks the audit.
The setup is deceptively simple: 1.5-2 hours, all Change Leaders in one room (or one call), a facilitator who's neither their boss nor their direct report, recording on, no slides. The whole meeting is questions and listening.
What you're trying to surface, in three layers:
- Relationships around work — how delegation, communication, motivation, and culture actually function between the people in the room.
- Habits around work — the behaviours and rituals that shape (and warp) effectiveness day-to-day.
- Substantive work — what they actually do, kept deliberately brief. The audit is interested in how work gets done, not what work gets done. Most managers default to describing tasks; a good facilitator pulls them back to the system.
The first five minutes set everything
Most of the meeting's success is decided before the first real question. The facilitator's opening establishes four things, in this order:
- Why we're here. "I'm here to understand how you work, not to evaluate how you work. There are no right or wrong answers."
- How long this takes. "We have 1.5-2 hours. We'll move at a comfortable pace."
- Recording consent. "I want to focus on listening, not note-taking. Is it okay if I record?"
- Permission to be honest. "Nobody is being assessed. The only way this is useful is if you say what you actually think."
The 🟢 → 🟡 → 🔴 question gradient
Every question in the audit is sorted into one of three difficulty bands. The order in which you ask them matters more than the specific wording.
🟢 Easy / warm-up. "How long have you worked here?" "Where do you work — remote, on-site, hybrid?" "What feels inefficient about your current state of working?" These exist to get people speaking. The more someone speaks early, the more comfortable they are speaking when the questions get harder.
🟡 Intermediate. Operational questions about how the work actually flows. "How do you delegate tasks?" "How do you track each other's progress?" "What metrics do you track?" "How often do you miss deadlines?" These produce most of the evidence the Change Plan will use.
🔴 Hard. The relational and cultural questions. "How is your team's cooperation perceived by other teams?" "Are the rules of cooperation the same for everyone?" "Do you feel encouraged to share information openly across departments?" Asked too early, these get sanitised answers. Asked after the warm-up has built rapport, they get the truth.
Two exercises that earn their place
Most of the meeting is questions. Two exercises do something the questions can't.
- The optimistic ending. Near the close, with eyes closed if the group is willing: "Describe the ideal version of how this works — your perspective, no constraints." It ends the meeting on a constructive note (which matters for what they say to colleagues afterwards) and surfaces aspirations that the rest of the meeting hasn't reached.
- The user manual. "If you were to give me a user manual on how a team communicates and collaborates, what would you include?" This one bridges directly into the Tooling Landscape Workshop. The Change Leaders almost always realise, mid-answer, that the rules they assume are shared are not in fact shared. That realisation is what makes the Tooling Landscape meeting feel necessary instead of imposed.
One-week rule for documentation
Whatever happens in the meeting, you have one week to convert it into structured notes on the working board (we use Miro internally; any visual workspace works). After a week, the texture of what was said starts to fade — and the texture is where the evidence lives.
Bringing this to your CFO.
💬 "The Group Audit Meeting is the only point in the project where every team lead tells the same neutral facilitator the same operational truth. After this, we have evidence — not opinions — to plan against. It's the cheapest insurance against an Implementation Plan based on assumptions."
3️⃣ Part 2 — Tooling Landscape Workshop
The Tooling Landscape Workshop is not a tool selection meeting. Nobody adopts or retires anything as a result of this session. The single goal is clarity — a shared, written-down map of which tool is used for what, by whom. Without that map, the workflow mapping work at the Mapping & Implementing Workflows 🛠️ stage starts on quicksand.
What the workshop produces, in order:
- An inventory of the tools the team actually uses. Not the tools IT has licensed — the tools that show up when work happens. Slack, email, WhatsApp groups, that one shared spreadsheet, the wiki nobody updates, the personal Notion someone keeps "just in case."
- A map of overlap, gaps, and inefficiencies. Two tools doing the same job. One job no tool is doing. Two sub-teams using the same tool for different purposes. The map names them.
- Working rules for when each tool should and shouldn't be used. Not policy. Working rules — the conventions that, if followed, would remove the most friction. These become the input for the Work Conventions 🤝 stage.
The Change Leaders' role evolves through this workshop
Up to now, "Change Leader" has been a single role. In the Tooling Landscape Workshop, the Change Leaders begin to feel the three sub-roles they'll formally split into at the Change Alliance 👥 stage:
- Convention Setter — the one who'll define and enforce organisation-wide rules.
- Workflow Guardian — the one who'll keep specific workflows current.
- Awareness-builder — the one who'll keep the why alive inside their team.
4️⃣ Optional — 1-on-1s with Change Leaders
Some things won't get said in a group. They'll get said in a 1-on-1, by people who needed twenty minutes of being listened to before they were willing to name the actual problem.
You run 1-on-1s when:
- A Change Leader was conspicuously quiet in the group meeting.
- A Change Leader contradicted the group narrative once and was talked over.
- The group meeting surfaced a tension between two functions that neither side will name openly.
- A Change Leader has been at the company longer than anyone else in the room and the group meeting felt sanitised.
5️⃣ Optional — Intervention
Sometimes the audit reveals something that isn't a process problem.
A Change Leader who's been quietly checked out for a year. A Sponsor who's lost the political room to back the project. A Director who's running a competing initiative that nobody mentioned at kick-off. A function-against-function conflict that predates the engagement and will outlive it.
When that happens, the audit pauses. The Implementation Plan doesn't start until the underlying issue has been brought into the open and resolved — usually in a Sponsor-level conversation that the Guardian and the facilitator co-design.
6️⃣ Where teams stall
‼️ The audit is run by the team's own boss. The single most common DIY failure mode. If the facilitator reports to the Sponsor (or is the Sponsor), the answers in the 🔴 band stop being honest. The audit produces a sanitised version of reality, and the Implementation Plan is built on it. Use a neutral facilitator — internal HR, an Ops lead from a different function, an external coach — anyone the Change Leaders don't depend on for performance reviews.
‼️ The meeting drifts into a complaint session. Without the 🟢 → 🟡 → 🔴 discipline, the questions skip straight to the painful territory and the meeting becomes a vent. Vent meetings feel productive — everyone leaves having said true things — but they don't produce evidence the Change Plan can use. The gradient is what turns complaints into data.
‼️ Tooling Landscape skipped on instinct. "Our team is digitally fluent, we don't need that workshop." Sometimes true. Often a misread. The signals that trigger this workshop come from Part 1, not from gut feel. Skip it when the data says you can; don't skip it because nobody wants another meeting.
‼️ Documentation slips past the one-week mark. A Group Audit Meeting recorded but not transcribed-and-mapped within seven days starts to lose its texture. By week three, the only thing left is your high-level memory of who said what, and the high-level memory always flattens into the most familiar narrative. The transformation is then planned around that flattened story.
‼️ Intervention swallowed instead of named. A facilitator notices a Sponsor-level problem in the audit and decides "we'll just route around it." Three stages later, the routed-around problem is the reason adoption stalls. If the audit reveals an intervention, the audit must become the intervention.
‼️ No baseline = no ROI proof at the Business Impact Review 📈 stage. This one's inherited from the Kick-off 🏈 stage. If the kick-off survey was never closed out, the audit can't anchor "before" to anything. Bringing this to your Sponsor: "If we haven't captured a baseline by the end of Audit, we'll be guessing at impact at the Business Impact Review. That's a ten-minute conversation now or a six-month problem later."
7️⃣ What to prepare before this stage
- A neutral facilitator named — someone the Change Leaders don't report to and don't manage.
- The full Change Leaders group on calendars for Meeting 1, with at least three weeks' runway (per the cadence rule from the Kick-off 🏈 stage).
- Recording infrastructure — meeting platform, consent script, secure storage for the recording.
- The kick-off baseline survey closed out — a Guardian-led chase to >80% completion before Audit begins.
- A working board — Miro, Mural, FigJam, a wall of sticky notes; whatever you'll use to map the audit findings within the one-week documentation window.
- An audit question bank — sorted by 🟢 / 🟡 / 🔴 and grouped by category, with the facilitator's permission to skip any question that's already been answered organically.
- A blank template for the Tooling Landscape canvas — kept in your back pocket, deployed only if Part 1 triggers it.
✅ What you get with the full protocol
The full Reliability Protocol is delivered as a sequence of weekly emails. 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 facilitator) can act on at the pace your organisation can sustain. The artifacts you get for this stage:
- The Audit Question Bank — every question across the seven categories, sorted by 🟢 / 🟡 / 🔴 difficulty, with the facilitator's notes on when to skip and when to push.
- The facilitator brief — the first-five-minutes script, the optimistic-ending exercise, the user-manual exercise, and the recording/consent template.
- The Tooling Landscape Canvas — the blank workshop template; deploy only if Part 1's signals trigger it.
- The 1-on-1 question set — the shorter, less structured rubric for following up on a quiet Change Leader or a tension that didn't get named in the group.
- The Intervention playbook — what the audit-pause looks like, who's in the room, and how the conversation gets designed when one is needed.
- The audit-to-Implementation-Plan handoff template — the structured notes layout you fill in within the one-week window so the Implementation Plan 🗺️ stage starts on evidence, not memory.
💬 Take this with you and your facilitator can run the audit yourselves. Hit a wall — especially on Intervention — and want a partner — book the session below.
When to bring in a partner
The package above is what we use to run audits ourselves. Skilled facilitators can run it themselves. Bring in a partner when:
- No-one internal can credibly play the neutral facilitator role. Every plausible candidate either reports to the Sponsor or manages a Change Leader. The audit needs distance you don't have.
- The audit reveals an Intervention. Pausing the project and naming a Sponsor-level problem is the work a partner can do that an internal voice rarely can.
- This stage happens across multiple business units or geographies and parallel audits are needed. Coordination cost rises faster than headcount.
If any of those land, the Reliability Diagnostic below is the lightest possible engagement — 60 minutes, no commitment beyond the session.
💡 This is Stage 4 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.