What is organizational development? Process, models and examples
A plain guide to organizational development: what OD is, how the process works, the main models and interventions, and how to measure it.

Organizational development (OD) is a planned, organization-wide effort to improve how a company works by changing its structure, processes, culture, and people practices together. Instead of quick fixes for one team, OD diagnoses why the whole system underperforms, designs changes, and keeps measuring until the new way of working sticks.
TL;DR
- Organizational development is planned, long-term change to the whole system: roles, decisions, leadership, culture, and processes, not one team's performance.
- HR runs people operations day to day. OD diagnoses why the organization underperforms and redesigns how it works.
- OD interventions fall into four families: human process, technostructural, HR management, and strategic change.
- Most OD work follows seven steps, from spotting the need for change to making the change part of daily work.
- Managers decide most of the result: Gallup finds they account for at least 70% of the variance in team engagement.
- Prove OD with four numbers: regretted attrition, internal fill rate, time to productivity, and decision cycle time.
- Start small: a 90-day cycle with two changes beats a year-long program that nobody finishes.

What is organizational development?
Organizational development is the practice of improving an organization's effectiveness and health through planned changes to its systems, using evidence about how people and groups behave at work. OD works on both sides of a company: the technical side (strategy, structure, systems) and the human side (culture, leadership, collaboration).

Richard Beckhard, one of the founders of the field, described OD as an effort that is planned, organization-wide, and managed from the top to increase organizational effectiveness and health through planned interventions in the organization's processes, using behavioral science knowledge. That definition still holds up well. Each part matters:
- Planned: OD is a deliberate, step-by-step effort, not a sudden change or a one-off workshop.
- Organization-wide: OD treats the business as a system. Change one part and you should expect effects elsewhere.
- Led from the top: without visible sponsorship from senior leaders, OD efforts lose direction.
- Evidence-based: OD relies on data from surveys, interviews, records, and observation, not on opinion.
OD also carries a set of people-first values from its early practitioners: treat people as human beings rather than resources, give them meaningful work, let them influence how work is done, and confront problems instead of avoiding them. Typical OD work includes culture change, leadership development, process redesign, team effectiveness, and change readiness programs. For a short definition, see the Testlify HR glossary entry on organizational change.
What are the goals of organizational development?
Organizational development aims to make a company competitive and ready for what comes next by improving performance, culture, people, and alignment at the same time. The point is continuous improvement, where people and the organization grow together instead of in separate programs.
- Improve performance: make teams and processes more efficient and remove the bottlenecks that slow decisions.
- Build a healthy culture: encourage collaboration, trust, and motivation across teams.
- Develop people: grow leadership skills and help employees reach their potential.
- Align goals: make sure everyone's work supports the company's strategy.
- Support change: help the company adapt to new technology, markets, mergers, or growth without losing its shape.
Where did organizational development come from?
Organizational development grew out of industrial and organizational psychology in the first half of the 20th century, and the term itself dates from the late 1950s. Richard Beckhard and Douglas McGregor are credited with coining it while consulting for General Mills, and the field spread through the 1960s and 1970s via the National Training Laboratories in the US.
Kurt Lewin's work in the 1940s on group dynamics and action research gave OD its method: study a problem with the people involved, feed the data back, and act together. In the 1980s and 1990s the focus widened to leadership development, change management, and industrial and organizational psychology applied at the company scale. Today OD leans on people analytics and skills data.
OD grew from five main roots:
Root | What it added | Main idea |
|---|---|---|
Laboratory training (T-groups) | Small groups learning from direct interaction, started at the National Training Laboratories | Change how people behave in groups first |
Action research and survey feedback | Collect data, share it with employees, act on it together (Kurt Lewin) | Use data and participation to diagnose problems |
Participative management | Employees take part in decisions instead of only following orders | People support what they help create |
Quality of work life | Attention to satisfaction and well-being at work | Fulfilled employees perform better and stay longer |
Strategic change | Links OD to strategy, mergers and digital change | Align people, processes and culture with long-term goals |
How is organizational development different from HR and change management?
Organizational development focuses on long-term change to how the whole organization works, while HR runs the people operations that keep it working day to day. Change management steers one specific transition, and training builds individual skills. OD often sits inside HR in large companies, but it needs executive sponsorship and cross-functional ownership to work.
Organizational development | Human resources (HR) | Change management | Training and HRD | |
|---|---|---|---|---|
Main question | Why does the system underperform, and what should change? | Are people hired, paid and managed well and legally? | How do we get people through this change? | Can this person do the job better? |
Scope | Whole organization: structure, culture, leadership, processes | Employment relationship: hiring, pay, policy, compliance | One project, system or restructure | Individuals and teams |
Time frame | Months to years, continuous | Ongoing operations | Project length | Course or program length |
Typical output | Diagnosis, redesigned roles and decision rights, new rhythms | Policies, hires, reviews, payroll | Rollout plan, communication, adoption | Skills, certifications |
A simple example shows the split. HR rolls out a leadership training program. Training teaches a manager to run a one-to-one. OD works out why leadership gaps exist, how they connect to strategy, culture and incentives, and whether one-to-ones should happen weekly at all.
Human resource development and talent development sit between the two: they grow the capabilities the strategy needs next, while OD makes sure the structure lets people use them.
OD is also different from organizational behavior (OB). OB is the study of why people act as they do at work; OD applies that knowledge to change the organization. For the change side, see the HR glossary entry on change management.
What are the main types of OD interventions?
OD interventions are the planned actions an OD team uses to fix a problem or help the organization adapt, and they fall into four families: human process, technostructural, HR management, and strategic change. Each family works at a different level, from a single team's conflict to a merger.
Intervention family | Works on | Examples |
|---|---|---|
Human process | How people and groups communicate, decide and resolve conflict | Coaching, team building, process consultation, intergroup work, large-group sessions |
Technostructural | Structure, work design and technology | Restructuring, job enrichment, work redesign, quality programs |
HR management | The systems that develop and reward people | Performance management, talent and leadership development, succession planning, diversity, well-being |
Strategic change | Strategy, culture and relationships with other organizations | Culture change, mergers and integration, new operating models |
Older OD texts split the same ground into five types (individual and interpersonal, team, intergroup, structural and comprehensive interventions). The four-family view is the one most practitioners use today. To pick between them, see how to choose the right organizational development intervention.
What are the steps in the organizational development process?
The organizational development process usually runs in seven steps: identify the need for change, diagnose, collect data, feed the findings back, design and implement the intervention, evaluate, and make the change part of daily work. Many sources group these into five stages: entry and contracting, diagnosis, intervention, evaluation, and exit.
- Identify the need for change: A problem or opportunity shows up, such as falling performance, low morale, or a market shift. The OD lead agrees with goals, scope, and expectations with leadership, treating the symptoms as clues to a deeper cause.
- Diagnose the current situation: Review HR, financial, and operating records to find root causes rather than surface symptoms.
- Collect data: Run surveys, interviews, focus groups, and document reviews. Keep answers confidential and explain why each piece of data is collected.
- Feed back the findings: Share the diagnosis with leaders in a form they can act on: clear, accurate, focused, and timely. A short deck with the three biggest findings works better than a 60-page report.
- Design and implement the intervention: Leaders and the OD lead agree on a plan that fits the company's culture and capacity. For example, if relying on an outside recruitment agency causes delays, the fix might be to build an internal recruiting team.
- Evaluate and adjust: Track results against the baseline and adjust. Good change management matters here: a clear vision, visible support, and momentum after launch.
- Make it stick: Build the change into everyday operations, roles, and reviews, then close the project.
Data collection has three traps worth knowing. The Hawthorne effect means people change their behavior because they know they are observed. Observer-expectancy bias means people answer the way they think the interviewer wants. Regression to the mean means extreme situations often settle on their own, so a crisis that calms down after a consultant arrives may not be the consultant's doing.
Pro tip: Protect the diagnosis step. Teams that skip straight to interventions fix the loudest problem rather than the costliest one. For more on rollout, read how to implement organizational development successfully.
What are the main organizational development models?
The main organizational development models are Lewin's three-step model, the action research model, the Burke-Litwin model, McKinsey 7-S, the Nadler-Tushman congruence model and Weisbord's six-box model. Each one gives a different lens for diagnosing what needs to change and in what order.
Model | Developed by | Core idea | Best for |
|---|---|---|---|
Lewin's change model | Kurt Lewin, 1940s | Unfreeze the current state, change, then refreeze the new one | The people side of a single change |
Action research | Kurt Lewin, expanded by later practitioners | Diagnose, collect data, feed back, plan jointly, act, evaluate, repeat | Collaborative, data-driven improvement |
Burke-Litwin | W. Warner Burke and George Litwin, 1992 | 12 linked factors, from external environment and strategy to climate and motivation | Finding the real cause of performance problems |
McKinsey 7-S | McKinsey consultants Peters and Waterman, late 1970s | Strategy, structure, systems, shared values, skills, style and staff must align | Checking internal alignment |
Nadler-Tushman | David Nadler and Michael Tushman, early 1980s | Performance depends on the fit between work, people, structure and culture | Spotting misfits and what to change first |
Weisbord's six box | Marvin Weisbord, 1976 | Purpose, structure, relationships, rewards, leadership and helpful mechanisms | A quick first diagnosis |
What are some examples of organizational development?
Examples of organizational development include replacing a performance system to change culture, designing a company around innovation, and giving a growing team clear decision rights. The common thread is that each one changed the system people work in, not just what individuals were told to do.
Microsoft: from ranking to growth conversations
Microsoft found that ranking employees against each other hurt collaboration. In 2013 the company dropped the ranking system and replaced annual reviews with regular "Connect" conversations about goals, progress and growth, backed by manager training. The shift moved the culture from internal competition toward learning and teamwork. The OD lesson: redesign the process and the culture follows.
Google: culture designed for experimentation
Google built structures that encourage open communication and experimentation, and trained managers to support teams rather than control them. This was a deliberate choice to align structure, leadership and culture with its innovation goals. The OD lesson: culture can be designed on purpose.
A growing company: when one person leaves
An operations manager at a 25-person company resigns on a Tuesday, and by Thursday nobody can say who owns half her work. The fix is classic OD: write down the 10 decisions the business makes most often, name an owner for each, document what each critical role knows, and spread that knowledge across at least two people. The OD lesson: structure, not effort, decides whether a small team holds its shape.
More cases are in case studies of successful organizational development programs.
How does organizational development change with company size?
Organizational development works at three levels (individual, group and organization) and its focus shifts with company size. Small companies need role clarity and decision rights first, mid-sized ones need manager capability and a feedback rhythm, and large ones need alignment across functions and regions.
- Individual level: coaching, mentoring and extra support for people who are struggling, joining or leaving.
- Group level: team interventions, run by managers or an OD consultant. If the sales team keeps missing targets, OD looks at how the team is set up, not only at each rep.
- Organization level: company-wide issues such as hiring culture, talent strategy or how decisions flow across departments.
Company stage | Typical symptoms | OD focus first |
|---|---|---|
Under 50 people | Decisions stall at the founder, two people absorb every new problem | Decision rights, role outcomes, documenting critical knowledge |
50 to 200 people | First-time managers promoted for tenure, uneven feedback | Manager capability, a quarterly feedback rhythm, skills visibility |
200+ people | Silos, slow cross-team decisions, misaligned goals | Structure and operating model, succession, culture across sites |
Managers carry most of the weight at every stage. Gallup's employee engagement research reports that managers account for at least 70% of the variance in team engagement, and that only 20% of employees worldwide were engaged in 2025. In a 40-person company with five managers, one weak manager affects a fifth of the business.
For early-stage teams, see organizational development for startups, and for distributed teams, see how to manage a remote team.
How do you run an organizational development plan in 90 days?
An organizational development plan works best as a 90-day cycle: two weeks of diagnosis, one week to publish decision rights, two weeks to measure skills, then two chosen changes, manager training and a new rhythm, with a review in week 13. Short cycles let teams absorb change in small doses and correct course early.
- Weeks 1 and 2, diagnose: Interview every employee (or a sample in larger teams) for 30 minutes, ask where work slows down, and group the answers into structural causes.
- Week 3, publish decision rights: Name the owner, the people to consult and the deadline for your 10 most frequent decisions.
- Weeks 4 and 5, measure capability: Run a skills audit with role-relevant assessments and build a skills inventory from verified results, not self-ratings.
- Week 6, pick two interventions: Choose the two changes that unblock the most people and park the rest in a visible backlog.
- Weeks 7 and 8, train managers: Teach three behaviors: setting expectations, giving feedback within a week of the event, and running a weekly one-to-one about work rather than status.
- From week 9, run the new rhythm: Quarterly outcome conversations (three outcomes per person, one capability to build) and weekly one-to-ones. Nothing else new.
- Week 13, review and reset: Compare your metrics with the baseline, keep what moved and retire what nobody used.
Give the whole cycle one owner. In smaller companies, that is usually the founder, a general manager or an operations lead with cross-functional context; in larger ones, an OD lead or HR business partner.
How do you measure organizational development?
Organizational development is measured with a small set of numbers tracked against a baseline every quarter, plus qualitative feedback from surveys, interviews and focus groups. Four metrics show whether the structure itself improved: regretted attrition, internal fill rate, time to productivity and decision cycle time.
Metric | What it tells you | Where to find it |
|---|---|---|
Regretted attrition | Whether people you wanted to keep are leaving | Exit records, with managers flagging each regretted exit |
Internal fill rate | Whether your development pipeline produces successors | Share of open roles filled by current employees |
Time to productivity | Whether onboarding and role clarity work | Weeks until a new hire delivers unsupervised output |
Decision cycle time | Whether decision rights removed the bottleneck | Days from raising a decision to resolving it |
Engagement score | Whether managers and culture changes land | A short quarterly pulse survey |
Read the numbers as a set. Falling attrition next to a flat internal fill rate usually means people are comfortable but not growing, which stores up a succession problem. In small teams, single-quarter swings are signals, not proof. For more detail, see how to measure the success of organizational development.
Key takeaway: OD is working when decisions get faster, the right people stay, and open roles are filled from inside. If none of those move after two cycles, revisit the diagnosis, not the tactics.
What are the benefits and challenges of organizational development?
Organizational development improves performance, engagement, change readiness and collaboration, but it is slow, depends on leadership commitment and is hard to measure. Most failures come from predictable mistakes, such as copying an enterprise framework or changing everything at once.
Benefits:
- Better business performance: people, processes and strategy line up, so work flows with fewer bottlenecks.
- Growth and engagement: training, feedback and open communication help people feel supported, which lowers turnover.
- Change readiness: a culture used to small, regular changes adapts faster to new technology or markets.
- Collaboration: clear roles and decision rights break down silos.
Challenges:
- Resistance to change: people may be uncomfortable with new structures or ways of working.
- Leadership misalignment: without visible commitment from the top, OD loses momentum.
- Short-term expectations: OD takes months or years, and leaders who expect results in weeks pull the plug early.
- Measuring impact: culture and collaboration gains take time to show in the numbers.
Common mistakes:
- Copying an enterprise framework: large-company models assume layers and specialists a growing company does not have.
- Starting with culture statements: values on a wall change nothing until decisions, feedback and promotions match them.
- Promoting the best specialist: technical excellence predicts management ability poorly. Assess management potential before you promote.
- Running everything at once: three simultaneous changes mean you learn nothing about which one worked.
Read more on the benefits of organizational development and common mistakes to avoid in organizational development.
What skills does an organizational development practitioner need?
An organizational development practitioner needs diagnostic and data skills, change management, business acumen, project management and emotional intelligence. HR business partners and L&D leads use the same skills, because they often lead OD work without the title.
- Analytical and diagnostic ability: interpret data, spot patterns and use surveys, interviews and diagnostic models. Test it with an analytical ability test.
- Change management: plan and lead change using both technical and people skills.
- Business acumen: understand how the business makes money and how market shifts affect it. See the business acumen test.
- Data analysis: collect, analyze and present the data every OD decision rests on.
- Project management: run a project from idea to close: planning, communication, negotiation and risk.
- Emotional intelligence: manage emotions, your own and others', while people go through change.
Most OD practitioners hold a degree in HR, psychology, business or training and development, and many add an OD or change management certificate. The closest US occupation in government data, management analysts, earned a median of $101,860 in May 2025, and the US Bureau of Labor Statistics projects 10% job growth from 2025 to 2035. To see what the role involves in practice, read about the role of an organizational development consultant.
How do skills assessments support organizational development?
Skills assessments give organizational development hard evidence about what people can actually do, which turns a skills inventory from an opinion survey into data you can plan against. The same assessments work for hiring, promotions, internal moves and succession, so the whole company is compared on one scale.
- Diagnosis: compare the skills your team has with the skills each role needs, then run a skill gap analysis to decide what to train, hire or outsource.
- Succession: name the five roles whose sudden loss would hurt most, then use assessment results to find ready successors. See why succession planning matters.
- Internal mobility: weigh internal mobility against external hiring for each opening using the same evidence for insiders and outsiders.
- Hiring OD talent: Testlify's organizational development skills test checks applied OD knowledge, problem-solving and strategic thinking before you hire an OD lead.
Testlify has 3,500+ validated tests, from role-specific and cognitive ability tests to situational judgment and personality tests, and its AI test builder creates a role-specific assessment from a job description. Results include a per-skill breakdown for each person, so OD teams can see capability across a whole department.
Where is organizational development heading?
Organizational development is moving toward continuous, data-driven change, with more use of people analytics, skills data and AI to spot problems early and adjust interventions as they run. HR leaders already rank it near the top of their agenda.
In SHRM's 2025 CHRO priorities research, 51% of chief HR officers named leadership and manager development as a top priority and 30% named organization design and change management, ahead of recruiting at 23%. Both are core OD work.
Three shifts stand out:
- From programs to rhythms: one-off change programs give way to small, regular changes built into how teams already work.
- From opinion to evidence: skills data, engagement pulses and decision metrics replace gut feel in diagnosis.
- From HR project to leadership job: OD works best when leaders own it, with HR and OD specialists as partners.
Read more on the future of organizational development.
Ready to see what your team can do?
Start your OD diagnosis with evidence. Run role-based skills assessments across your current team and your next hires, and see where the real gaps are. Start a 7-day free trial of Testlify, no credit card required, or browse the Testlify test library.
Frequently asked questions
People and Talent Partner
Arushi Shah runs day-to-day talent acquisition and candidate experience at Testlify. She writes on interviewing, structured hiring, and giving candidates a fair, fast process.
LinkedInRelated resources
View all
HR & recruitment
Top 8 case studies of successful succession planning

HR & recruitment
Importance of Assessing Ethics for Ethical Decision-Making

HR & recruitment
Talent management metrics: 15 KPIs, formulas and ROI

HR & recruitment
The importance of talent management in today’s economy

HR & recruitment
Benefits of Organizational Development: 10 Gains and How to Measure Them

HR & recruitment
How to create a workplace where employees thrive?
Get started.
Hire on proof, not resumes.
Run your first skills-based assessment free — no credit card required.