Ask a leader to describe their culture and you'll get adjectives, "collaborative," "fast-moving," "caring." Ask their team what actually happens and you'll get nouns: the Friday demo, the leaving card that nobody signs, the framed values poster nobody can recite. The gap between the two is the whole game. Rituals, symbols and artefacts are where an organisation's real culture becomes observable, and, because they're observable, they're the part you can actually change.

The quick version

  • Artefacts are the visible, tangible signs of a culture, the office layout, the dress code, the language, the awards, the rituals themselves. They're easy to see and easy to misread.
  • Symbols are artefacts that carry meaning beyond their function, a job title, a parking space, who gets cc'd, the logo on the wall. They signal what and who matters here.
  • Rituals are the repeated, patterned actions a group performs, stand-ups, all-hands, onboarding days, leaving dos. They tell people, week after week, what's normal and what's valued.
  • The trap: treating these as window-dressing. They're how culture is taught and reinforced, so if your rituals reward the wrong things, your values poster won't save you.

The idea in depth: what you can see sits on top of what people believe

The foundational map here is Edgar Schein's three levels of culture, set out in Organizational Culture and Leadership (first edition 1985; now in later editions with Peter Schein). Schein argues that culture operates at three depths. At the surface are artefacts: everything you can see, hear and touch, the open-plan desks, the slang, the rituals, the dress code. Below them sit espoused values: the stated strategies, goals and slogans an organisation says it believes. And underneath both are basic underlying assumptions: the taken-for-granted beliefs about how the world works that nobody argues about because nobody notices them (see this overview of Schein's model).

Schein's sharp point, and the one most leaders miss, is that artefacts are easy to observe but hard to decode. You can see that a team always eats lunch together; you cannot tell from the lunch alone whether that signals genuine warmth or enforced conformity. The visible thing is real, but its meaning lives one or two levels down. So here's the move: don't audit your culture from the values deck. Walk the floor and list the artefacts, what gets celebrated, what gets ignored, what the most-told story is about, and then ask, of each one, "what assumption would have to be true for this to make sense?" That question is the bridge from a poster to the belief actually running the place.

flowchart TD
  A(["Artefacts
what you can see, hear, touch
rituals, symbols, layout, language"]) --> B(["Espoused values
what we say we believe
slogans, strategy, the values poster"])
  B --> C(["Basic assumptions
what we actually believe
unspoken, taken for granted"])
  C -.->|"shapes"| A
Schein's three levels, the visible layer is easy to see and easy to misread; meaning lives underneath. Leaders Loop

An honest limitation. Schein's levels are a lens, not a measuring instrument. Reading an artefact "correctly" still relies on judgement, two observers can decode the same ritual differently, and the model offers no formula for resolving that. Treat it as a structured way to ask better questions, not a diagnostic that hands you the answer.

Rituals are how culture gets taught, so classify them honestly

If artefacts are the vocabulary of culture, rituals are its grammar, the repeated patterns that drill in what's normal. The most useful classification of organisational rituals comes from Harrison Trice and Janice Beyer, whose paper "Studying Organizational Cultures Through Rites and Ceremonials" (Academy of Management Review, 1984) laid out a taxonomy of rites, the bigger, staged events that bundle several rituals together. Their categories include rites of passage (onboarding, promotions, marking a change of status), rites of enhancement (awards that raise someone's standing), rites of degradation (the public removal of a leader who failed), rites of renewal (the annual offsite, the strategy refresh), rites of conflict reduction (grievance processes that restore order), and rites of integration (the holiday party that loosens hierarchy and rebuilds shared feeling).

The value of Trice and Beyer's list is that it forces honesty about what your rituals actually do. A "town hall" that's really a one-way broadcast is not a rite of integration; it's a rite of enhancement for whoever's on stage. Try this: take your three or four biggest recurring events and label each with the rite it genuinely performs, not the one it's named after. Then ask whether the thing it reinforces is the thing you want reinforced. A weekly status meeting that only ever surfaces who's behind is quietly running a rite of degradation; no wonder people dread it.

flowchart LR
  R(["A recurring ritual"]) --> Q{"What does it
actually reinforce?"}
  Q -->|"marks a status change"| P(["Passage
onboarding, promotion"])
  Q -->|"raises someone up"| E(["Enhancement
awards, recognition"])
  Q -->|"rebuilds shared feeling"| I(["Integration
offsite, celebration"])
  Q -->|"shames or punishes"| D(["Degradation
often unintended"])
Adapted from Trice & Beyer's rites taxonomy, name the rite a ritual truly performs, not the one on the calendar. Leaders Loop

Symbols are cheap to send and expensive to fake

Daniel Coyle's The Culture Code (2018) gathers field reporting and behavioural science into a practical claim: high-performing groups run on a steady stream of small signals he calls belonging cues, moments of attention, proximity and recognition that answer the unspoken question "am I safe and valued here?" Many of these cues are symbolic and tiny: who the leader makes eye contact with, whether the founder's desk sits among the team or behind a door, the ritual of thanking people by name. Coyle's reporting on groups like the San Antonio Spurs describes leaders who invest disproportionately in shared meals and personal recognition, symbolic acts with no direct task value that nonetheless do real cultural work.

A symbol is a message a leader sends whether they mean to or not.

The uncomfortable corollary is that symbols you don't intend are read anyway. The corner office, the executive parking space, the all-hands where leadership answers pre-screened questions only, each is a symbol, and each is interpreted. So audit the symbols your seniority already broadcasts, then deliberately spend a few of them. Give the demo slot to the most junior engineer who shipped something. Put the customer's thank-you letter on the wall instead of the revenue chart. Symbols are cheap to send and, because people watch what leaders do far more than what they say, expensive to fake, which is exactly why a genuine one lands. (A caution: Coyle's work is practitioner-credible reporting, not peer-reviewed proof, so treat the cues as well-argued patterns rather than laws.)

A worked example

Take a 40-person software company, call it Meridian, whose stated value is "we celebrate learning, including failure." (Illustrative scenario; the figures and details are a teaching example, not a real company.) On the wall: a poster saying exactly that. In the rituals: a weekly all-hands where only shipped wins get applause, and a quarterly awards lunch where the same three high performers collect the same prizes. A new engineer, Sara, runs an experiment that fails cleanly and saves the team from a bad bet, and hears nothing.

Run Meridian through the lens above. The artefact (the poster) espouses a value the rituals contradict. The all-hands is functioning as a rite of enhancement for winners and a quiet rite of degradation for everyone whose work didn't "ship." The basic assumption underneath, the one actually governing behaviour, is "only visible success counts." No amount of poster will outrun that.

The fix is not a new value; it's a new ritual that makes the espoused value observable. Meridian adds a two-minute "best thing we learned (including what didn't work)" slot to the all-hands, and the CEO goes first, describing a decision of their own that flopped. The leaving-card problem gets fixed too: HR makes signing it a named, time-boxed ritual rather than a passed-around afterthought. Within a couple of quarters the new engineers can point to a moment that taught them failure is safe here, because they watched a leader model it, repeatedly, in public. That repetition is the mechanism. A value stated once is a slogan; a value enacted every Friday is a culture.

Notice the order of operations: Meridian didn't rewrite the poster or run a culture survey. It changed two rituals and one symbol, the smallest, most visible levers, and let the assumption shift follow. That's this Toolkit entry on embedding values in miniature: values live or die in the rituals that enact them.

Frequently asked questions

What's the difference between a ritual, a symbol and an artefact?

An artefact is any visible feature of a culture, Schein's term for the whole surface layer. A symbol is an artefact that carries meaning beyond its function (a title, a logo, a reserved parking space). A ritual is a repeated, patterned action (the stand-up, the onboarding day). Rituals and symbols are both kinds of artefact; the labels matter less than the habit of reading all three as evidence of what a culture actually believes.

Aren't rituals just corporate theatre?

They can be, a ritual that nobody believes in is exactly that. But the research treats rituals as the primary way norms get taught and repeated, not as decoration. The test is whether the ritual reinforces something the group genuinely values. A hollow ritual (the unsigned leaving card) does real damage precisely because people read it as a signal of how much they matter.

How do I read my own culture's artefacts without fooling myself?

Schein's warning is that artefacts are easy to see and hard to decode, and you're the worst-placed person to decode your own. Ask newcomers and recent leavers, they still notice the things that have gone invisible to you. For each artefact, ask "what would have to be true for this to make sense?" and look for the answer that's unflattering; that's usually the real assumption.

Can you change culture by changing rituals, or is that backwards?

It works in both directions, which is the useful part. Assumptions shape rituals over time, but rituals are far easier to change than beliefs, and a repeated new ritual a leader visibly models is one of the few levers that can shift an assumption. You can't decree a belief; you can change what happens every Friday.

What's the most common mistake leaders make here?

Investing in the espoused-values layer (posters, slogans, the values workshop) while leaving the rituals untouched. When the stated value and the enacted ritual contradict each other, people believe the ritual every time. Fix the ritual first.

Related in the Toolkit

Rituals, symbols and artefacts are the visible end of how culture forms and persists, and they're the practical mechanism by which abstract values become observable behaviour, which is why they sit so close to defining and embedding values.

Where to go next