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:

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

“Good,” Maya said. “Chaos is data.” Resistance came fast

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

One year later, the CEO asked Maya to run another engagement survey. She laughed. “No,” she said

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? I grow the conditions where they can grow themselves

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

A junior designer raised her hand. “So… you’re saying the problem isn’t us? It’s the handoffs?”

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

Maya nodded. “Exactly. And OD’s job is to change the handoffs, not the people.”