She taught the Flow Team to run their own diagnostics. She built a simple “health check” that any team could use: How long does a decision take? Who is missing from the room? What rule would you delete?
Maya gathered her findings into a single slide deck—but not a polished boardroom version. She used the method: raw, anonymous quotes, process maps with red zones, and a question at the end: “What part of this system do you own?” She taught the Flow Team to run their own diagnostics
The guide’s final chapter read: “Your goal as an OD practitioner is to make yourself unnecessary. If the system needs you to stay healthy, you’ve built dependency, not development.” What rule would you delete
Six months later, the mid-level turnover had dropped by 60%. But Maya didn’t celebrate with a slide titled “Success.” She celebrated by fading into the background—the final, hardest lesson of the practitioner’s guide. If the system needs you to stay healthy,
She sat with Derek and asked, “What are you losing?” He admitted, “Control. I don’t know where my deals are if I’m not in every email.”
“That’s not a system problem,” Maya said gently. “That’s a trust problem. OD can fix handoffs. Only you can fix trust.”