Reading Organisational Culture
Also known as:
Developing the ability to rapidly decode an organisation's actual culture — the real values, informal power structures, unwritten rules, and sacred cows — from observable behaviour rather than stated values.
Developing the ability to rapidly decode an organisation’s actual culture — the real values, informal power structures, unwritten rules, and sacred cows — from observable behaviour rather than stated values.
[!NOTE] Confidence Rating: ★★★ (Established) This pattern draws on Organisational Theory / Cultural Intelligence.
Section 1: Context
Most organisations operate as dual ecosystems: the formal structure published in org charts and mission statements, and the living culture that actually shapes decisions, resource flows, and who holds real power. In hybrid-value-creation systems — where corporate entities partner with public institutions, activist networks, or product teams — this gap widens. A government agency claims transparency but decisions cluster in informal breakfast meetings. A tech startup posts values about “psychological safety” while engineers who voice concerns get sidelined. An activist collective professes horizontal structure but certain voices consistently set the agenda. The system fragments when newcomers (or partners from different traditions) misread these signals and invest effort in the wrong levers. Decisions that should be influenced through formal channels fail because the actual authority lives elsewhere. Conversely, those who intuitively grasp the culture navigate it with ease — but that intuition rarely transfers, leaving organisations vulnerable when key readers leave. The pattern emerges from necessity: how do you systematically surface what everyone knows but no one names?
Section 2: Problem
The core conflict is Reading vs. Culture.
The tension holds two legitimate forces. Reading — the drive to decode, understand, and make visible — wants clarity, explicitness, and transferable knowledge. It asks: What are the actual norms? Who holds real authority? What topics are undiscussable? This impulse serves newcomers, builds resilience, enables intentional change.
Culture — the living, implicit web of meaning — resists codification. It lives in tone, timing, relationship, history. The moment you name a sacred cow, it shifts. Cultures preserve adaptive wisdom that formal rules obscure; they also embed exclusions and power imbalances that thrive in darkness.
The break comes when one side wins completely. A culture that remains entirely opaque becomes fragile — knowledge walks out the door with key people, onboarding fails, partners from other traditions cannot navigate it. Partners waste energy on wrong channels; vital informal networks stay invisible; toxic patterns persist unchecked because naming them feels taboo.
Conversely, a culture that is fully read and systematized loses resilience. Relationships become transactional. The tacit knowledge that holds the system together — knowing when a rule can bend, reading the room’s actual readiness for change — atrophies. Practitioners become analysts rather than participants.
The actual need is for selective, iterative reading — making visible what blocks collaboration or embeds harm, while protecting the implicit relationships and local wisdom that sustain vitality. The pattern asks: What is worth naming, and who needs to know it?
Section 3: Solution
Therefore, cultivate a structured practice of cultural reading where designated practitioners observe patterns of behaviour, resource allocation, and communication flow to surface unwritten rules and informal power structures, then feed these insights back into the system with consent and specificity.
This pattern treats culture-reading as a disciplined craft, not a talent only intuitive people possess. The mechanism works through three movements:
First, systematic observation. Rather than relying on gossip or intuition, readers develop a structured lens: Where do decisions actually get made? Whose informal sign-off is required before formal approval? Which topics appear in public meetings versus closed conversations? Where does budget flow? Which failures are forgiven and which are unforgivable? How long do people actually stay? This is not surveillance — it is pattern recognition using the same rigor an ecologist uses to read a forest’s health.
Second, sense-making with anchor points. Individual observations are noise. The reading stabilizes when practitioners triangulate: comparing what people say the culture is (stated values) with what happens (resource allocation, who gets promoted, what meetings happen off-calendar), and what people feel (psychological safety surveys, exit interviews, trust networks). The gaps between these three map the culture’s actual topology.
Third, bounded sharing and iteration. Insights are fed back into the system through structured channels — not as gossip or critique, but as pattern observations offered to people who can act on them. A team lead learns that high performers leave after 18 months; the culture-reading surfaces that these people report feeling unseen after initial onboarding. That observation, shared with consent, creates space for change. A government division discovers that decisions happen in email chains after formal meetings; naming this pattern allows them to ask: Is this intentional? Does it serve us? What should we change?
This resolves the tension because it holds both forces: making culture visible enough to be stewarded intentionally, while preserving the implicit relationships and tacit knowledge that sustain it. Readers become translators between formal and lived realities, not critics of either.
Section 4: Implementation
Map the observable signals. Begin by establishing what you will actually look at. Create a simple frame with four quadrants: Formal Structure (official channels, stated process), Resource Flow (where money, time, and attention actually move), Communication Patterns (who talks to whom, which conversations are public vs. private), and Consequence Patterns (what behaviours are rewarded, tolerated, or punished). Spend two weeks observing without intervention — sit in meetings, review who attends which gatherings, notice whose opinions shift the room, track which failures lead to firing and which to learning conversations.
In a corporate context: Attend cross-functional meetings but also observe the informal huddles before and after. Ask finance, HR, and ops teams the same question independently: If something needs to get done quickly and can’t wait for formal approval, who do you actually call? The convergence of answers reveals the real decision-making network. Map how different functions describe “collaboration” — if engineering sees it as asynchronous handoff but product sees it as daily alignment, you’ve found a cultural fault line.
Conduct structured interviews — not surveys, conversations. Speak with people across seniority and tenure: those hired in the last three months, those who’ve been there five years, and those who’ve recently left if you can reach them. Ask three consistent questions: (1) What surprised you most about how things actually work here? (2) What topic or decision would be risky to question openly? (3) Who would you go to if you needed something done and couldn’t use formal channels? Record patterns, not anecdotes. When five people independently mention the same informal decision-maker or taboo topic, you’ve identified a real structure.
In a government context: Look at budget timelines and approval chains. Notice where decisions accelerate or stall. Interview people across hierarchy levels separately — they will describe the same organisation very differently. Pay special attention to which reforms were attempted but abandoned; the reasons reveal what the actual culture values versus what it claims to value. Ask civil service veterans: Which decisions do ministers actually make, and which are predetermined? This surfaces the real authority distribution.
Document the gaps between stated and lived culture. Create a simple table: in one column, list the organisation’s published values or stated processes. In the next, describe what you actually observed. Stated: “We have open-door leadership.” Observed: The door is open but interruptions are subtly discouraged; leaders hold real conversations in one-on-ones, not open forums. These gaps are not failures to document — they are the culture itself. Treat them as data, not judgment.
In an activist context: Map who sets agendas for meetings, whose frameworks shape strategy, whose concerns get revisited versus dismissed. Notice whether “horizontal structure” means genuine rotation of power or ritual redistribution while actual authority stays concentrated. Ask people: When have you changed your mind because someone else convinced you? Who convinced you? The patterns reveal where influence actually flows. Interview people who’ve left — activist burnout often traces to culture reading failures, where newcomers couldn’t navigate unwritten power hierarchies.
Create a “culture codex” — a living document, not a report. Organize findings by function or team. For each section, describe: (a) The formal process, (b) How it actually works, (c) The unwritten rules that make it work, (d) The consequences if you ignore them. Include examples but not names. This document lives in a shared space and updates as culture shifts. It becomes onboarding material, not anthropological record.
In a tech context: Track how product decisions actually get made. Is it genuinely data-driven or does leadership intuition override metrics? Who has voice in roadmap conversations? Which bug reports get prioritized? How are engineers who raise technical debt concerns treated? Notice whether “build fast and iterate” means psychological permission to fail or pressure never to slow down. Interview people who left your company — their reasons reveal culture gaps. Use this codex to guide new hires and prevent partners (other teams, vendor relationships) from misreading your actual norms.
Establish consent and circulation. Before sharing any findings broadly, offer them to key stakeholders — team leads, culture stewards, people mentioned in patterns — and ask: Is this accurate? What am I missing? Is it okay to share this more widely? This prevents the reading from becoming a weapon and keeps it grounded. Some patterns may not be ready to surface; respect that. Others will clarify themselves once named.
Section 5: Consequences
What flourishes:
New hires and external partners navigate the organisation far more effectively because they can read the actual landscape instead of guessing. Onboarding accelerates when cultural norms are made explicit. Decision-making becomes more intentional — teams can ask Is this rule serving us or just habit? and change what no longer fits. Hidden power structures become visible, which creates possibility for more equitable distribution. Burnout decreases because people stop exhausting themselves trying to influence through wrong channels. Leadership gains the ability to see their own culture as outsiders see it, creating space for conscious evolution. Knowledge becomes less dependent on key individuals — the culture’s operating logic transfers instead of walking out the door.
What risks emerge:
If reading becomes voyeuristic — turned into gossip or used as ammunition in political conflicts — it poisons the system. People stop sharing openly; culture hardens defensively. There is also risk of false objectivity: a reader can mistake their own cultural assumptions for universal norms, and misinterpret what they observe. The pattern’s low resilience score (3.0) reflects a specific vulnerability: reading culture does not itself build adaptive capacity. You can understand a dysfunctional culture perfectly and remain stuck in it. Making culture visible does not guarantee it will change — sometimes visibility just makes the dysfunction sharper. The pattern also risks creating a priesthood: those who can “read” the culture gain advantage, deepening rather than flattening hierarchy. Finally, there is the decay of routinisation. Once codified, a culture reading can become stale doctrine that people follow mechanically instead of living intelligently. The vitality reasoning warns directly here: “Watch for signs of rigidity if implementation becomes routinised.” A three-year-old culture codex may describe a dead system, not the living one.
Section 6: Known Uses
Edgar Schein and organisational culture diagnostics. Schein’s framework — distinguishing between artifacts (what you see: office layout, language, dress), espoused values (what people say matters), and basic assumptions (what people actually believe and act from) — became foundational to culture-reading as a discipline. When Schein worked with technology companies in the 1980s, he would observe meetings, conduct careful interviews, and surface the gap between stated “innovation culture” and actual risk-aversion embedded in hiring and promotion decisions. He would document that people claimed to want bold ideas but killed proposals that challenged established markets. Once made visible, teams could choose: defend the actual culture or deliberately change it. This pattern appears in every culture-reading practice that distinguishes stated from lived values.
The Government Digital Service (UK) scaling across ministries. When GDS teams moved into different departments to implement digital transformation, early efforts failed because external teams assumed the barrier was technical. Senior practitioner Ben Holliday and others learned to first read each department’s actual culture: which decisions were genuinely delegated, which were subject to invisible veto, how did hierarchy actually work, what was the appetite for uncertainty. In the Department of Work and Pensions, they discovered that formal processes suggested senior civil servants made decisions, but actual power lay with long-serving middle managers who had institutional memory. Once this was visible, GDS stopped presenting change to the top and instead brought middle managers into co-design. Projects that had stalled for months moved. The pattern — systematic reading before intervention — became standard practice across government digital work.
Organisational Culture and Innovation in activist networks. The organiser Jane McAlevey documents how she reads movement culture: not through surveys but by mapping communication networks, observing which voices shape strategy, noticing whose concerns get revisited and whose get dismissed. She explicitly coaches organisers to decode the difference between stated “participatory” culture and actual power concentration. In campaigns she studied, groups claimed horizontal structure but key decisions were made by three people in side conversations. Once visible, groups could name it and decide: Is this intentional? Should we change? Some chose to defend distributed decision-making; others realised they actually needed faster, centralised decisions during action and designed rotating authority instead of pretending it didn’t exist. The reading itself created agency.
Section 7: Cognitive Era
In a world of AI-assisted analysis and networked intelligence, culture-reading shifts in important ways. New leverage: Large language models can now surface patterns in communication archives — emails, Slack histories, meeting transcripts — far faster than humans. They can identify who speaks in meetings, whose questions get addressed, which topics appear in closed channels versus public ones. This is not insight itself, but it dramatically accelerates the signal collection phase. A practitioner who previously spent weeks in observation can now feed data into analysis and ask: Who are the informal connectors? Which topics cluster? Which meetings are really where decisions happen?
New risks: There is profound danger in treating AI pattern-extraction as objective truth. An LLM trained on corporate communication will inherit and amplify existing biases — it may systematically undercount quieter voices or interpret silence as agreement. It can miss the most crucial cultural signals: the pause before someone speaks, the tone that says “this decision is already made,” the relationships that exist outside recorded channels. The pattern becomes dangerous if practitioners mistake algorithmic pattern-matching for cultural understanding. They may read the data and lose the ability to read the room.
For tech products specifically: Teams building platforms are increasingly aware that they are not just reading their own culture but designing culture-reading infrastructure for others. Slack, Notion, and similar tools embed assumptions about how communication should happen and how decisions should be visible. These platforms have inadvertently made culture-reading both easier (everything is searchable) and harder (performed communication replaces tacit knowledge). Smart teams now ask: What culture are we embedding in our tools? A product that makes all decisions visible might erode the psychological safety needed for real risk-taking. One that emphasizes asynchronous documentation might lose the relational glue. The pattern inverts: instead of reading existing culture, practitioners design tools that shape it, then read what emerges.
Distributed systems compound the challenge. When teams are remote and async-first, much cultural information becomes algorithmic (who responds to messages, who initiates) rather than relational. The informal power structures persist but become harder to read — they hide in DMs, side channels, and timing choices. Yet this also creates opportunity: distributed teams often codify culture more deliberately because they cannot rely on osmosis. The pattern becomes more crucial, and the codex becomes infrastructure.
Section 8: Vitality
Signs of life:
New hires can describe unwritten rules accurately within their first month, showing culture is legible. Teams discuss which informal practices are intentional versus inherited habit, demonstrating conscious agency. When someone says “That’s not how we do things,” others can explain why — the reasoning is visible, not mysterious. Exit interviews reveal that people leaving understand the culture clearly and can articulate why they’re leaving, rather than vague dissatisfaction. Informal power structures are known and occasionally challenged or rearranged, showing culture is alive rather than fossilized. People across hierarchy and function give convergent answers when asked about decision-making norms, indicating shared understanding. New partners or teams integrating from outside can navigate effectively without extended apprenticeship.
Signs of decay:
The codex becomes stale — it documents a culture that no longer exists but people still treat it as gospel. Naming unwritten rules stops happening; people revert to “that’s just how it is.” Exit interviews show people leaving confused or blindsided by culture, indicating it stopped being legible. Informal power becomes invisible again, often concentrating in fewer hands. Teams stop asking Is this rule serving us? and start enforcing rules mechanically. The reading practice itself becomes ritualistic — annual culture survey, quarterly “culture assessment” — performed without changing anything. New hires spend months figuring out unwritten rules instead of weeks. Culture-reading knowledge concentrates in a priesthood of HR or organisational development staff rather than being distributed.
When to replant:
Restart the practice when you hire significant new cohorts, merge with another organisation, or notice the gap between stated and lived culture widening. You know it’s time when people can no longer clearly explain why things are done certain ways — when culture has drifted into pure habit. The right moment is also when the organisation faces genuine choice: Do we want to keep this culture or change it? A reading at that threshold creates the clarity needed for conscious decision-making. Redesign the practice if the codex has become dogma — shift from documentation to ongoing conversation, from static artifact to living inquiry. Consider new methods if the organisation’s communication infrastructure has shifted (fully remote teams, new platforms, different team composition).