Topic
Leavitt diamond model
Weak Weak
Paired instrument: Leavitt diamond model questionnaire
Harold Leavitt's 1965 diamond is the ancestor of most later diagnostic models, and still the most compact. Four interacting variables:
- Task: the work itself, its goals and its complexity.
- People: the actors, their skills, attitudes, and needs.
- Structure: authority, communication paths, workflow.
- Technology: tools, machines, systems, techniques.
The claim: these four are interdependent, so a deliberate change in any one produces compensating changes in the others — whether or not those changes were planned.
Evidence: Weak. A conceptual checklist from 1965, never validated. Its claim — that a deliberate change to one variable produces unplanned changes in the other three — is supported anecdotally and by the sociotechnical literature, but the model offers no way to predict which changes or how large. Use it as a five-minute prompt, not as a diagnostic.
Use when: you want a five-minute check on the second-order effects of a planned change, especially a technology change.
Do not use when: you need depth. Four variables cannot separate culture from structure, or leadership from management practice.
The diagnostic use
For any proposed change, ask what it does to the other three points.
- Introducing a tool (Technology) changes who holds information (Structure), what skills matter (People), and how the work is done (Task).
- Restructuring (Structure) changes who can do which tasks and which tools become necessary.
- Redefining the task changes required skills and preferred structure.
Leavitt's own point was that change agents choose a favorite point of entry — technologists change technology, HR changes people, executives change structure — and then are surprised by the effects at the other three.
Examples by audience
Health care: adding a digital triage tool (Technology) shifts decision authority from experienced nurses to an algorithm (Structure), devalues a skill built over years (People), and changes what triage means (Task). All four move; only one was planned.
Software: adopting infrastructure as code changes who can deploy (Structure) and makes some operations roles obsolete while creating new ones (People). See https://github.com/joelparkerhenderson/maturity-models.
Executive: a shared services consolidation is presented as a Structure change and a cost saving. It is also a Task change for every unit that previously had local support, and those units will invent shadow capability.
Limitations
- Too coarse for serious diagnosis; use it as a checklist, not a model.
- No environment term. Later models added it; Leavitt's does not have one.
Questionnaire
A paired, copy-and-use diagnostic instrument for this model: leavitt-diamond-model-questionnaire.