“Good,” Maya said. “Chaos is data.”
Maya thought of her guide—now highlighted, sticky-noted, and coffee-stained on her desk. “No,” she said. “I’m a gardener. I don’t grow people. I grow the conditions where they can grow themselves.”
Maya blinked. She had a shelf full of credentials—SPHR, SHRM-SCP—but OD felt like a different language. Diagnosis. Systemic intervention. Process consultation. It sounded like therapy for a corporation.
Maya formed a cross-functional “Flow Team”—sales, product, compliance, engineering. Not a committee. A design team. They met for two hours every Friday. No agendas. No status updates. Only one question: “What is one rule, approval, or handoff we can remove this week?” “Good,” Maya said
One year later, the CEO asked Maya to run another engagement survey. She laughed.
That’s the secret of Organization Development that no certification exam teaches: HR knows the rules. OD knows the rhythms. One administers the present. The other designs the future.
She spent two weeks shadowing, not auditing. She watched the product team wait three days for a compliance sign-off. She saw engineers rewrite requirements because marketing never looped them in. She heard the same phrase from five different departments: “We’d fix it, but no one asked us.” “I’m a gardener
Derek paused. “You’d see chaos.”
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.”
The guide called this : aligning people, process, and technology. She had a shelf full of credentials—SPHR, SHRM-SCP—but
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?
At the town hall, the room went quiet. The COO shifted uncomfortably when Maya showed that his weekly review meetings were actually causing a 40-hour delay in decision-making.