Organization Development · OD
Organization Development
What is organization development?
- Planned improvement of an organization’s health and effectiveness
- Runs as a cycle of diagnosis → intervention → evaluation
- Unlike training (individuals), it addresses culture, structure, and processes (the organization)
What OD actually works on is not employees’ knowledge but the rules between them. Who calls meetings and who makes the final decision, where information stalls, and what earns recognition are all in scope. That is why the deliverables of an OD project are not textbooks or certificates of completion but things like a newly formed coordination council, decision-making authority that has been moved, and team ground rules that have been renegotiated. Even with the same people, once these rules change, behavior next Monday changes too.
In practice, it helps to think of interventions in layers: individual (coaching), team (team building, ground rules), cross-department (process redesign, role redefinition), and company-wide (structure, policy, culture). If you intervene at a layer below where the real problem sits, even excellent execution won’t last. Trying to resolve conflicting interests between departments with a team workshop is the classic example. Common methods include survey feedback, process consultation, future search, and appreciative inquiry (AI), and a cycle from diagnosis to re-diagnosis typically takes 6 to 12 months. OD is also distinct from change management. Change management is about landing a change that has already been decided, such as an ERP rollout or a merger, whereas OD also covers the stage of working out with employees what should change.
The most common mistake is treating OD as a one- or two-day workshop event. If you run a diagnostic and then shelve the results, cynicism builds up in the organization. Once word spreads that "nothing changes after we take the survey," the response rate on the next diagnostic drops by half or more, and after that you can no longer get honest answers at all. Leaving policies untouched has the same effect. If you tell people to collaborate but keep evaluation at 100% individual goals, behavior snaps back within three months. OD driven by HR alone, without an executive sponsor, usually ends up as 'an activity only the well-meaning take part in.'
Anna ChoExpert in organizational culture, coaching, emotion management, and CS consulting
John KimInstructor John Kim, CEO of Nanum Consulting and author of B2B Marketing DesignOD began in the 1940s and 50s with Kurt Lewin’s research on group dynamics and action research, and grew into a distinct field devoted to organizational change.
Consider a hypothetical case: Company A, a food manufacturer with KRW 120 billion (≈ US$89,780,000) in annual revenue and 320 employees. Conflict between the Sales and Production divisions had pushed on-time delivery down to 82%, with 27 emergency production changes a month. Separate sales training and production training had changed nothing, so the HR team launched an eight-month project and took an organization development (OD) approach instead.
- When the head of HR ran an organization-wide diagnostic survey (78% response rate) plus in-depth interviews with 22 team leads, the complaint "Sales sells everything first and only tells us afterward" came up in 17 of the 22 interviews.
- Without filtering the results, they presented the diagnostic findings as-is at an executive workshop. The CEO framed it as "this isn’t about someone being lazy, it’s a problem with how our meetings are structured," and put their own name down as sponsor of the initiative.
- Treating it as a cross-department problem, they set up a weekly Tuesday order-and-production coordination meeting and moved the authority to confirm delivery dates from the sales team lead to this meeting. Sales and production planning staff were paired up across 12 product groups.
- They also adjusted the policies. They built a collaboration metric worth 20% into team lead evaluations and added biweekly group coaching for 9 sales and production team leads over three months, so that people saw "the one who calls first doesn’t lose out."
- In the re-diagnosis eight months later, the cross-department collaboration score rose from 3.1 to 3.9 on a 5-point scale, on-time delivery went from 82% to 94%, and emergency production changes fell from 27 to 11 a month.