How to Run the Audit, Interpret Results, and Prioritize Action
Run the assessment as a single facilitated session
Invite 3–6 participants who represent the work: a frontline practitioner, a manager, someone who hands off work, and, if relevant, a product or support partner. Spend 30–60 minutes. Have the group score each domain together, offer concrete evidence, and capture top problems and quick wins.
Interpret scores without overfitting
Scores create a diagnostic map, not a verdict. Use these simple rules:
- Low domain score (1–2): Suggests urgent blockers. Probe for concrete examples and the cost of inaction.
- Medium score (3): Useful opportunity — the practice exists but is inconsistent or siloed.
- High score (4–5): Practice is working, but ask whether it scales and if learning is captured for others.
Prioritize where to act
Use a simple impact vs. effort filter:
- Identify items with clear evidence and repeat incidents (from the evidence field).
- Estimate how much improvement will reduce rework, delays, or risk (qualitatively).
- Choose one low‑effort/high‑impact experiment and one medium‑term project to plan.
Translate a finding into an experiment
Turn each prioritized problem into a small bet using this template:
We believe [problem]. We will try [intervention] for [30 days] to cause [leading indicator]. We will measure [metric] and decide to adopt, adapt, or abandon.
Practical facilitation tips
- Keep the session short and evidence-focused. Push for specific examples rather than impressions.
- If people disagree on a score, ask for an example that would change a score by one point.
- Record decisions and owners immediately. Without owners, insights become noise.
Suggested next steps after the session
- Circulate the assessment summary and the chosen experiment within 48 hours.
- Run the experiment for a fixed period (30 days recommended) and collect simple leading indicators.
- Hold a short learning review and update the team’s playbook or onboarding artifacts based on the outcome.
When to dig deeper
If the audit points to cross‑team breakdowns, plan a short follow‑up: 4–6 interviews, a simple process map, and a causal timeline (when did the problem first appear). That evidence helps you design structural fixes rather than repeating point solutions.
Discussion
Comments and conversation will live here.