Organization Development- A Practitioner-s Guide For Od And Hr -

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?”

He nodded. “You’re not in HR anymore, are you?” They met for two hours every Friday

The guide warned: “Most HR interventions fail because they target symptoms. OD targets structures.” Only one question: “What is one rule, approval,

“Maya,” he said, pushing a stack of engagement survey results across the mahogany desk. “The numbers are green. Pay is above market. But we’re bleeding mid-level talent. People aren’t quitting the company. They’re quitting the system . I need you to stop being Human Resources. I need you to practice Organization Development.” hardest lesson of the practitioner’s guide.

The next morning, Maya refused to write another exit interview summary. Instead, she asked the CEO for something radical: three weeks of “listening.”

Resistance came fast. Derek, the sales head, complained that changes felt “too slow.” The COO missed his old reports. But Maya had learned the most critical OD skill:

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.