The core idea
Contingency thinking rejects a single organisational arrangement for every situation. Lawrence and Lorsch examined differentiation between organisational units and the integration needed to coordinate them under different environmental conditions. Applied to HR, the question becomes whether staffing, development, rewards and authority fit the organisation’s tasks and strategy. Vertical fit concerns alignment with strategy; horizontal fit concerns whether people practices reinforce one another. These are analytical ideas, not permission to lower employment standards.
Source and attribution [1]Using it in practice
Specify the contingency you think matters: task uncertainty, safety requirements, scale, technology, skill scarcity or customer needs. Then describe the mechanism through which a different practice should help. Compare plausible alternatives instead of declaring the current system “a fit” after the event. Keep common principles explicit so that local tailoring does not become arbitrary treatment. Revisit the decision when its underlying conditions change.
An example, not a reported case
Worked example · illustrative
A maintenance operation needs reliable handovers, clear authorisation and consistent safety checks. A product-discovery team needs room to test uncertain ideas. Both need fair treatment and competent managers, but identical targets and approval rules may frustrate one of them. HR pilots different feedback rhythms and decision boundaries, while keeping common pay principles, accessibility standards and routes to challenge decisions.
What to watch for
“It depends” is only useful when you name what it depends on. Apparent fit can become an excuse for preserving poor practice, and yesterday’s successful arrangement may fail after growth or technological change.
Specify what the organisation needs to fit
List the relevant conditions: demand stability, technology, regulation, geographic spread, workforce capability and interdependence between tasks. 'It depends' becomes useful only when the dependencies are explicit. A tightly specified emergency response and an exploratory product project may require different coordination. Avoid importing a fashionable practice because it worked at a visible company. Explain which conditions are similar, which differ and why those differences might change the result in your organisation.
Distinguish necessary control from inherited habit
Examine one rule and identify the risk it manages. A mandatory check may prevent serious harm; an additional signature may exist because a previous manager preferred it. Ask what would happen if the rule changed, what evidence supports that expectation and what safeguards could remain. This exercise does not assume that flexibility is always better. It helps identify where standardisation protects service and where local discretion could improve responsiveness without undermining essential controls.
Compare two plausible designs
For illustration, a multi-site security provider could centralise licence verification while giving site managers limited discretion over local handovers. Compare this with a fully centralised model using the same criteria: accuracy, response time, accountability and employee experience. Include the coordination costs of each option. A local solution that works only because one experienced supervisor informally rescues it may not be robust. Make the proposed division of responsibility clear enough to test in practice.
Revisit fit when the context changes
Set review triggers such as a new service, rapid growth, increased automation or a different risk profile. Record the conditions under which the chosen design was expected to work. If those conditions change, review the design rather than blaming people for struggling with it. Contingency thinking should not become an excuse for inconsistent treatment: explain the work-related reason for differences and preserve common standards of fairness, safety and respect across units.
Translate fit into an explicit choice
Describe the environmental or organisational condition that makes one approach preferable. A small specialist firm and a dispersed high-volume service may need different coordination and reward arrangements. Record the trade-off and the conditions under which the choice should be revisited. Context is an explanation to test, not an excuse for inconsistent treatment or abandoning minimum standards.
Write the condition under which the choice would change
A centralised scheduling process may be appropriate for predictable work with common rules, while unusual local demand may require more discretion. State the conditions supporting the choice and the evidence that would trigger review. This makes “it depends” useful: the dependency is explicit. Include the cost of coordination, the capability needed locally and the risks of inconsistent decisions. Context should narrow options, not become an excuse to avoid explaining why one was selected.
Check fit across practices as well as with strategy
Recruiting for initiative while requiring approval for every decision creates a mismatch. So does rewarding individual speed while asking teams to share knowledge. Walk through one employee journey and identify where practices send incompatible signals. Test an adjustment to the system rather than asking employees to resolve the contradiction themselves. A locally successful practice is not automatically transferable to a different site: compare the conditions that enabled it before treating it as a universal standard.
Take it into your next conversation
Three useful questions.
- Which contextual difference matters?
- What must remain consistent?
- What change would make this design stop fitting?
Related terms
Go to the evidence
Sources & attribution
Further reading: Michael Armstrong with Stephen Taylor (2023), Armstrong’s Handbook of Human Resource Management Practice, 16th edition, chapters 8–9. Edition & reading notes ↗
[1] Lawrence & Lorsch (1967), Organization and Environment; HBS research review. ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.
Published 2026-09-20 · Reviewed 2026-09-25. Editorial approach