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

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:

“That’s not a system problem,” Maya said gently. “That’s a trust problem. OD can fix handoffs. Only you can fix trust.”

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.

And the best practitioners? They don’t fix companies. They teach companies how to fix themselves. Resistance came fast

“What if I don’t give you any solution today?” she asked. “What if I just map how work actually flows—not the org chart version, but the real one?”

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.

That night, she opened her dog-eared copy of Organization Development: A Practitioner’s Guide for OD and HR . She’d bought it years ago at a conference but had used it mostly as a doorstop. Now, she read it like a lifeline. “That’s a trust problem

Maya remembered the guide’s advice: “Don’t be the expert with answers. Be the curious stranger with questions.”

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 nodded. “Exactly. And OD’s job is to change the handoffs, not the people.” The COO shifted uncomfortably when Maya showed that

But then she did something the guide called . She didn’t let people blame “leadership” or “lazy teams.” She said, “We built this together. We can rebuild it together. But first, we have to admit we designed a system that rewards waiting, not acting.”

“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.”

“No,” she said. “Let’s run a instead. Let’s ask people: ‘Does the structure help you succeed? Do handoffs create flow or friction? Are you solving problems or managing bureaucracy?’”

She started with the sales team. They were siloed, anxious, and drowning in internal approvals. The head of sales, a bullish man named Derek, crossed his arms. “HR is just going to give us another wellness app,” he grumbled.

The guide called this : aligning people, process, and technology.