The organizational development process cycle

Organizational development is a cycle, not a project. The classic sequence runs entry, contracting, diagnosis, feedback, planning, intervention, evaluation, and either institutionalization or exit. The cycle repeats, because each intervention changes the system and therefore invalidates part of the original diagnosis.

Evidence: Not an empirical model. This is a practice convention, not a tested theory. Its strongest component is the diagnose-before-intervene rule, supported indirectly by the poor track record of intervention-first programs, and by the survey feedback studies described in survey-feedback-method. Treat the eight stages as a checklist, not as a claim about how change necessarily proceeds.

Use when: you are responsible for an improvement effort larger than a single team and longer than a single quarter.

Do not use when: the problem is a defect with a known fix. Fix it.

The eight stages

1. Entry: someone presents a problem. Your job is not to accept the presenting problem at face value. "We need team building" usually means "two directors are at war". "We need a new tool" usually means "our process is undefined and we hope the tool will define it".

2. Contracting: agree the scope, the roles, the access, the confidentiality rules, the decision rights, and how the work ends. See entry-and-contracting.

3. Diagnosis: gather data through interviews, observation, surveys, documents, and system telemetry. Choose a diagnostic model to organize what you gather. See mckinsey-7s-framework, burke-litwin-causal-model, weisbord-six-box-model.

4. Feedback: give the data back to the people it came from, before you give it to the sponsor. This is an OD value, not merely a courtesy: the people in the system are the ones who must act on it, and they will correct your misreadings. See survey-feedback-method.

5. Planning: convert diagnosis into hypotheses, and hypotheses into interventions with named owners, dates, and measures. State what you expect to change and by when, in advance.

6. Intervention: do the work. See interventions-catalog.

7. Evaluation: compare what happened against what you predicted. Include the possibility that nothing changed, or that something got worse. See measurement-and-metrics.

8. Institutionalization or exit: make the change survive the sponsor's departure, or wind the effort down honestly. Changes that depend on one enthusiastic person are not changes; they are that person.

The rule that matters most

Diagnose before you intervene. The most common failure in the field is the intervention-first program: a reorganization, an offsite, a values launch, or a tool rollout selected before anyone established what was wrong. Intervention first is expensive, it burns the organization's willingness to try again, and it teaches people that improvement efforts are theater.

Examples by audience

• Health care: a hospital reports rising medication errors on a ward. Entry is the presenting problem "the nurses need retraining". Diagnosis finds a staffing ratio change, an interruption-heavy drug round, and a reporting culture in which errors are punished. Training was never the intervention.

• Software: a platform group reports "we can't ship fast enough". Diagnosis finds four teams sharing one deployment pipeline and one approval board. The constraint is structural, not motivational. See conways-law, dora-metrics.

• Executive: a CEO reports "we lack accountability". Diagnosis finds overlapping decision rights across three executives and no forum where tradeoffs are resolved. Accountability is an effect, not a cause.

Common failure modes

• Skipping feedback and going straight from diagnosis to a leadership readout.
• Contracting with a sponsor who cannot authorize the changes the diagnosis will require.
• Treating evaluation as a report rather than a decision point.
• Running the cycle once and calling it a transformation.

See also

• action-research — the underlying research logic.
• evidence-based-practice
• od-ethics