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

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

One year later, the CEO asked Maya to run another engagement survey. She laughed. Maya gathered her findings into a single slide

“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?’” “No,” she said

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. Do handoffs create flow or friction

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

He nodded. “You’re not in HR anymore, are you?”