Organizational Assessment and Diagnosis
Levels and methods
Organizational diagnosis examines individual, team, and system levels. Candidates should know the classic open-systems model (inputs, transformation, outputs, feedback, environment) and diagnostic frameworks such as structure, strategy, culture, rewards, and processes. Methods include interviews, focus groups, surveys, observation, document review, and archival metrics; strong diagnosis triangulates multiple sources and distinguishes symptoms from root causes.
Diagnosis vs. evaluation
Diagnosis is formative and improvement-oriented; evaluation is often summative and judgmental. Confusing the two is a frequent trap. Another trap: treating a single vocal stakeholder's complaint as the organizational diagnosis. Also watch for criterion problems-measuring what is easy rather than what matters-and for sampling bias when only volunteers or senior staff are surveyed.
Feedback and sense-making
Diagnostic data must be fed back to the system in a way that builds ownership. The classic caution: feedback that names problems without engaging the people who own them produces defensiveness. Present themes, protect anonymity, and facilitate the client's own interpretation.
Rule of thumb
Use the "data → theme → hypothesis → test" sequence. Never present a single-source finding as a diagnosis; label hypotheses as hypotheses and identify what evidence would confirm or disconfirm them.
Worked example
Turnover is high in one department. Interviews blame the manager; engagement data show workload spikes; exit data show schedule conflicts. The diagnosis is a workload-scheduling system issue with a supervisory communication contributor-not simply "bad manager." Interventions target both.