Individual / Team / Organization Level Selection¶
Organizational diagnosis method — instantiates Cross-Scale Intervention Matching
Walks a problem down the nested organizational ladder — individual, team, unit, enterprise — to find the level where the cause is generated and leverage is tractable.
Inside an organization, a recurring performance problem can be addressed at any of several nested levels: coach the individual, redesign the team's process, change a unit's routines and incentives, or alter enterprise structure and systems. Individual / Team / Organization Level Selection is the method for choosing which of those levels to act on. Its defining feature is that it works against a fixed ladder of containment — each level sits inside the next — and it asks two questions at every rung: is this the level that generates the pattern, and is this the level where leverage is actually tractable? Those can differ; a cause may live in enterprise incentives while the most changeable lever is a team routine. The method's discipline is to resist the organizational default of pushing every problem down to the individual.
Example¶
A fulfillment warehouse keeps logging the same defect: pickers grabbing the wrong item from adjacent bins, shipped and later returned. The reflexive fix is at the individual level — retrain the pickers, post accuracy scores. Individual / Team / Organization Level Selection walks the ladder instead. At the individual level, errors are spread evenly across staff, which argues against "careless workers." At the team level, the pattern concentrates on the night shift, whose handoff leaves bins restocked but unverified. At the enterprise level, the slotting system places visually similar SKUs in neighboring bins.
The cause scale turns out to be enterprise slotting, but re-slotting the whole facility is slow and expensive — low tractable leverage in the near term. The most tractable leverage is a team-level change: a scan-to-confirm step at pick time that catches the mismatch the slotting creates. So the chosen intervention acts at the team-process level to neutralize a cause that lives higher up, with re-slotting queued as a slower enterprise fix. Illustratively, the scan step cuts mis-picks by more than half within weeks, long before any bins move.
How it works¶
- Anchor the ladder. Fix the levels in play — individual, team, unit/management routine, enterprise structure — as nested containers, so the diagnosis has a defined set of rungs rather than a vague "where's the problem."
- Locate the generating rung. Look for where the pattern concentrates (a shift, a role, a system default) versus where it's evenly spread; concentration points to the level that generates it.
- Separate cause from leverage. Ask independently which rung is most changeable soon. The tractable lever is often lower or lateral to the cause.
- Act on leverage, queue the cause. Commit the near-term intervention at the most tractable rung and, where the true cause sits higher, schedule the slower structural fix rather than pretending the lever resolved it.
Tuning parameters¶
- Ladder granularity — how many rungs you distinguish (individual / team / enterprise, or a finer split adding sub-team and management-routine levels). Finer rungs locate the cause more precisely but add diagnostic overhead.
- Cause-versus-leverage weighting — how much to favor acting at the true cause versus the most tractable lever. Favoring the cause is more durable but slower; favoring leverage is faster but risks a patch.
- Default-resistance — how hard the method pushes back against reflexive individual-level attribution. Higher resistance catches system causes but can under-credit genuine individual factors.
- Escalation trigger — how much residual harm remains after the tractable fix before the queued higher-level cause must be addressed.
When it helps, and when it misleads¶
Its strength is countering the organizational reflex to blame the person nearest the error. A just-culture stance — asking what about the work design made the error likely, not only who made it — is the discipline this method operationalizes at the level-selection step.[n1] By separating the generating rung from the tractable lever, it also avoids the opposite trap of declaring "it's systemic" and doing nothing changeable soon.
Its failure mode is stopping at the wrong rung. Stop too low and you retrain individuals for a defect the system keeps manufacturing; stop too high and you launch a slow enterprise redesign while the harm keeps landing and a cheap team-level lever goes unused. A classic misuse is treating the tractable lever as if it were the cause — celebrating the scan-step patch and quietly never re-slotting — so the generator persists under a workaround. The guarding discipline is to keep the queued higher-level cause on the books with its own owner and review date, so a leverage-level patch is recorded as a patch, not a cure.
How it implements the components¶
cause_scale— identifies which nested rung generates the recurring pattern, using concentration versus even spread as the signal.leverage_scale— separately locates the most tractable rung to act on, which may sit below or beside the cause.intervention_scale_choice— commits the near-term action at the leverage rung and queues the structural fix where cause and leverage diverge.
It does not anchor on the visible symptom_scale as a starting move the way Upstream Intervention Selection does, nor track an outcome_scale_metric across levels — verification-by-metric is that sibling's; and it runs no feasibility_by_scale_assessment of political and cost viability across breadth options, which is Local-vs-Systemic Policy Choice's work.
Related¶
- Instantiates: Cross-Scale Intervention Matching — the intra-organizational case, choosing among nested levels of a single institution.
- Consumes: Scale-Matrix Decision Workshop can supply the competing level-framings different functions hold before this method adjudicates them.
- Sibling mechanisms: Authority Escalation Pathway Design · Clinical / Social-Determinant Matching · Cross-Scale Side-Effect Table · Ecological Intervention Level Choice · Infrastructure-vs-Behavior Intervention Comparison · Leverage-Point Screening Matrix · Local-vs-Systemic Policy Choice · Scale-Matrix Decision Workshop · Upstream Intervention Selection
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Individual / Team / Organization Level Selection operates as a computation, comparison, model, or analytic representation used to infer, estimate, or choose because it walks a problem down the nested organizational ladder — individual, team, unit, enterprise — to find the level where the cause is generated and leverage is tractable
Independent corroboration: The frozen evidence defines Individual / Team / Organization Level Selection as 'Walks a problem down the nested organizational ladder — individual, team, unit, enterprise — to find the level where the cause is generated and leverage is tractable', so its operative form is Analysis, Modeling & Optimization.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Selecting among individual, team, unit, and enterprise causes is principally an organizational-diagnosis practice.
Related originating lineages:
- Engineering & Design — Safety engineering and Just Culture materially contribute the move from individual error to system-design causes.
- Psychology — Individual and group-level behavioral explanation materially supplies the lower analytic levels.
- Systems Thinking & Cybernetics — Nested-system and cross-scale reasoning materially supplies the warning against treating local symptoms as local causes.
Review resolution: Both independent reviews place the primary lineage in organizational_management. The queued differences (alternate_origin_disagreement, encyclopedia_synthesis_disagreement) concern secondary metadata rather than primary provenance. The final retains psychology, systems_cybernetics, engineering_design only where a reviewer supplied a formative-lineage rationale; this does not convert downstream applicability into origin. origin_mode=cross_disciplinary_synthesis because the entry's present form deliberately composes methods from the documented lineages. domain_reach=multi_domain records application breadth separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Just Culture is the safety-management stance (associated with the work of Sidney Dekker and used widely in aviation and healthcare) that recurring frontline errors should first prompt questions about how the work is designed, rather than about the diligence of the person who erred. It is the disposition that keeps this method from stopping at the individual rung by default. ↩