The core idea
The Cultural Web places a central paradigm—the assumptions shaping what feels normal—among six connected elements: stories, symbols, rituals and routines, power structures, organisational structures and control systems. It is associated with Johnson and Scholes and later editions of Exploring Strategy with Richard Whittington. The model helps connect a general statement about culture to observable features of organisational life. Its centre is an interpretation to investigate, not a slogan to invent and impose.
Source and attribution [1]Using it in practice
Choose one issue and gather examples for each element. Distinguish the formal organisation chart from informal influence, and stated priorities from measures that actually affect decisions. Build a current map before describing a desired one. Then identify a small set of mutually reinforcing changes, with owners and review dates. Keep contrary evidence and disagreement on the map: the purpose is to understand patterns, not to manufacture consensus in a workshop.
An example, not a reported case
Worked example · illustrative
A fictional security business celebrates the supervisor who personally rescues a failed shift. Overtime totals are highly visible, while avoided disruption is almost invisible. Experienced schedulers influence decisions despite limited formal authority. HR explores a possible paradigm that dependable service requires constant heroics. A pilot recognises early planning, adds a short capacity review and gives schedulers an explicit escalation route. The evaluation checks whether disruption falls without encouraging teams to conceal uncovered work.
What to watch for
A completed diagram is not proof of a causal explanation. Maps may reflect the people invited and the stories they feel safe telling. Do not confuse a power structure with a list of senior job titles, or symbols with branding alone. Changing a symbol while retaining contradictory incentives may change little. Use the web with observation, operational evidence and follow-up conversations.
Stories and symbols
Ask which incidents are repeatedly retold and who appears as the hero, problem-solver or cautionary example. Inspect visible signals of status and access as well as logos and office space. Our working question is what a new starter would learn about whose work matters. Capture more than the senior team’s preferred story.
Rituals and routines
Observe a handover, meeting or promotion discussion. What happens every time, what gets skipped under pressure and what behaviour attracts approval? Choose one routine that can be changed without disrupting essential operations. State the intended behaviour in practical terms, then observe whether the change survives a busy period.
Formal structure and real influence
Draw decision routes as people experience them. Identify where advice is routinely sought and where an informal objection can stop progress. Compare that with official responsibility. Our suggested intervention is to clarify a specific decision and escalation path, rather than assuming a new chart will change influence by itself.
Control systems
Inspect the measures, budget rules, rewards and sanctions that shape choices. Ask which important outcomes are absent from the scorecard. A measure of speed may need a quality check; a cost measure may need visibility of work shifted elsewhere. Make the trade-off explicit and review possible unintended effects before expanding a new measure.
From current web to change plan
For every proposed change, record the supporting element and any contradiction elsewhere in the web. If leaders ask for early reporting but still punish every inconvenient report, address that conflict first. Set a review date and specify observable evidence. Treat the map as a living hypothesis rather than a finished poster.
Gather examples around one concrete issue
Choose a question such as why staff hesitate to report near misses. Collect stories people tell, visible symbols of status, everyday routines, decision-making power, formal reporting relationships and the measures that receive attention. Record examples rather than adjectives. 'Safety is important' provides less diagnostic value than an account of what happened when a shift was delayed for a check. Include contrasting experiences so the web does not merely reproduce the most senior person's interpretation.
Look for a reinforcing pattern
Ask how the elements support one another. A story celebrating someone who 'saved the contract', a reward based only on uninterrupted service and a routine of bypassing escalation may reinforce the assumption that problems should be hidden. This is an illustrative hypothesis, not a finding about a real employer. Check it with further evidence and alternative explanations. The central paradigm should summarise a pattern, not become a dramatic label chosen at the start of the exercise.
Change several connected signals
If safer escalation is the aim, revise the reporting routine, clarify authority to pause work and recognise responsible intervention. Leaders' responses and the stories repeated afterwards matter alongside the formal process. Changing only a symbol, such as a poster, leaves the reinforcing system largely intact. Select a manageable set of connected actions and explain why each supports the desired behaviour. Keep operational consequences visible so the change is workable under pressure.
Revisit the web with fresh incidents
After implementation, collect new examples of decisions and ask whether the old pattern still explains them. Do staff describe a different response to bad news? Are performance conversations still rewarding the behaviour the project intended to reduce? Track exceptions and differences between sites. The web is a qualitative diagnostic aid, so avoid presenting the number of sticky notes in each category as a culture score. Its value lies in the explanation and the action it helps test.
Trace how the elements reinforce one another
Choose one behaviour, such as avoiding bad news. Stories may celebrate the manager who rescued a client at any cost; controls may reward uninterrupted delivery; power may sit with people who dismiss concerns; routines may leave no space for reflection. Record the connection between these features instead of producing six separate lists. Include contradictory examples and ask who experiences the pattern differently. The central paradigm should emerge as a tentative interpretation of the evidence, not as a slogan supplied at the start.
Change a reinforcing practice and watch the response
A new speaking-up message will struggle if the first employee to report a problem loses desirable shifts. Change how managers respond, what gets recognised and how concerns are reviewed together. Select a bounded team or process and keep a record of reported issues, responses and follow-through. Nabeel’s focus on observable behaviour is useful here, but do not mistake a before-and-after improvement for definitive causal proof. Customer demand, staffing and leadership changes may also affect what people do.
Take it into your next conversation
Three useful questions.
- What observable evidence supports this interpretation?
- Whose experience differs from the dominant story?
- What small change could we test, and how would we know it helped?
Related terms
Go to the evidence
Sources & attribution
Further reading: Hani Nabeel (2025), Culture Analytics: An evidence-based approach to company culture, First edition, Chapters 3 and 13; PDF pp. 38–39, 190–191 and 214. Edition & reading notes ↗
[1] Cultural Web teaching resource, citing Johnson, Scholes and Whittington, Exploring Strategy ↗
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.
Compare all eight culture models → · Read the practical playbook →
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-22. Editorial approach