Values describe the culture you want. Rituals reveal the culture you have. Strategy says “we will innovate responsibly.” Culture is what happens when someone proposes an unfamiliar, yet creative, idea in a meeting. Strategy says, “we are one enterprise!” Culture is what connects – or frazzles and fragments – recently merged teams so that they share information, give feedback, resolve tensions, and serve clients with the same behaviours and consistent practices even if they in different markets and geographies.

This is why culture can, for better or worse, eat strategy for breakfast. Not because strategy is unimportant, but because culture determines how strategy is interpreted when nobody is reading the plan.

Culture is a repeated, observable way of meeting, deciding, questioning, escalating, learning, recognizing, and recovering every day and all the time in our workplaces, classrooms, and communities.

A slogan is something people remember: “See it, say it!”
A practice is something people do: “when we see something great, we recognize in the moment; when we notice a microaggression, we intervene by saying it’s not okay; when we notice a growth opportunity, we recommend content or connections to help build a skill or strengthen a career-capability.”
A ritual is a practice that accumulates shared meaning: “when everyone is vocal about the right and wrong behaviours, culture change happens at scale.”

MIT’s Sloan Management Review offers a useful metaphor: culture is an organization’s nervous system, transmitting strategic intent to the front line and carrying information about results back to leadership. When that system works, strategy and execution learn from each other. When it does not, decisions are misaligned and the member/client-experience is fractured.

That distinction matters in financial and community-impact organizations, like credit unions, non-profits, social enterprises, and public-serving pension plans, where leaders must simultaneously protect trust, meet compliance expectations, allocate capital wisely, serve communities, and adapt to relentless change. These tensions cannot be solved by choosing between care and performance, safety and innovation, or stewardship and speed. They require repeatable ways of holding all sides at once.

Culture is what gets repeated

Every organization already has rituals.

The meeting that begins ten minutes late because the real decisions happened beforehand is a ritual. So is the tolerating the leadership behaviour of asking a difficult question, requesting “hard answers”, and then punishing the uncomfortable answer. So is the performance process that never achieves 100% completion. So is the post-merger town hall promising “one team” while each legacy organization keeps its own decision rules and member lists.

None of these practices need to appear in the employee handbook to shape behaviour. Repetition teaches people what matters: who has a voice, what gets rewarded, which risks can be named and whether commitments have consequences.

This is why culture transformation is less like launching a campaign or delivering a program and more like refactoring code. Leaders must identify the routines currently running, decide which ones support the strategy, rewrite the ones that do not, and retire the legacy processes and behaviours that are still producing yesterday’s outcomes. INSEAD’s Charles Galunic suggests that culture change often fails because organizations focus on lofty values at the top and individual behaviours at the bottom while neglecting the “messy middle” of what happens when leaders are aligning on decisions, delivering and receiving feedback, rewarding achievements, running meetings, and leading change.

A useful culture-practices architecture has three connected levels: micro-habits and everyday behaviours, systems and processes, and transformational practices.

Figure 1: Culture operates through three connected layers: everyday cues, embedded systems, and enterprise-wide transformational practices. Strategy travels downward into behaviour, while learning travels back upward.

Micro-habits make culture visible

Micro-habits are small, repeated behaviours that reflect a community’s culture. They seem modest because they are, and this is their superpower.

Consider beginning a meeting with one of two questions:

• “What are we getting done today?” when the purpose is deciding or delivering; or
• “What’s on your mind?” when the purpose is coaching, sense-making or care.

Two questions, two social contracts. One signals movement and accountability. The other signals attention and exploration. Both prevent the cultural mush of a meeting that is simultaneously an update, brainstorm, therapy session and decision forum.

Other micro-habits are equally ordinary:

• Close laptops when full attention is needed (and keep them open when the work genuinely requires shared documents or note-taking).
• Begin meetings with a commitment review: What did we agree to? What has moved? What is blocked?
• End meetings with named decisions, owners, and dates.
• Provide quiet thinking time before inviting debate, so the fastest talker does not become the default strategist.
• Ask, “Who sees this differently?” before declaring alignment.
• Penalize (in a fun way) talking over each other.

These actions will not transform an organization by themselves. But they create behavioural evidence. Closing a laptop communicates, “You have my attention.” Reviewing commitments communicates, “Our decisions survive calendar invitations.” Inviting dissent communicates, “Agreement is not the admission price for belonging.”

I’ve written about communication rituals, such as asynchronous updates, human connection at the beginning of meetings, silent reading, after-action reviews, and routine requests for feedback, that improve team performance. The common thread is not novelty. It is consistency and discipline: the practice becomes meaningful because people experience it repeatedly and can predict what it asks of them.

There is also a useful design constraint here: a micro-habit should reduce ambiguity, not add bureaucracy. If it requires a 40-page toolkit, six approvals, and a certification badge, well, congratulations, you have probably made a policy or a program, not a ritual.

Rituals encode organizational norms by turning expected behaviours into repeated practice.

Systems and processes make culture durable

Micro-habits influence moments. Systems influence thousands of moments.

If an organization says collaboration matters, but rewards only individual or divisional results, the incentive system will overwhelm the micro-habits. If leaders espouse the value of development, but performance evaluations are routinely delayed or treated as paperwork, employees learn that development is optional and feedback isn’t valued. If leaders encourage appropriate risk-taking, but every failed experiment tags the project lead as a failure, “innovation” becomes corporate fan fiction.

Systems-and-process practices embed culture in how the garden is grown:

• how meetings are designed and facilitated;
• how enterprise processes such as performance evaluations are completed;
• how decisions and rationales are documented;
• how risks are surfaced and escalated;
• how cross-functional work is measured and recognized;
• how teams learn from errors, near misses and changing evidence.

One practical example is a “Check Before You Act” team pause. Before sending, sharing, storing, approving, or changing information, an employee asks: what compliance expectation applies here?

This is not about making everyone a lawyer or encouraging paralysis by policy. It turns compliance from a distant department into a brief, repeatable moment of professional judgment. Asking first becomes evidence of curiosity and accountability, not uncertainty or incompetence.

That distinction is particularly relevant in pensions, banking, credit unions and institutional or impact investing. These organizations need cultures where people can innovate without treating privacy, fiduciary duty, information governance or member trust as annoying obstacles. The strongest risk cultures do not force employees to choose between “moving fast” and “being safe.” They equip people to recognize which decisions are reversible, which require challenge and which deserve a deliberate pause.

Cultivating these systemic practices sounds a lot better than annual, 90-minute compliance training, too.

Consistent systems and processes are critical following mergers and acquisitions. Culture integration is not achieved by choosing a new set of adjectives. It requires deciding how the newly connected identities, histories, and practices will be combined (or erased) to make decisions, enable performance, recognize contribution, share information, and resolve conflict. McKinsey’s Ignacio Fantaguzzi and Christopher Handscomb believe that leaders need to diagnose “how work gets done”, defining the cultural aspiration and then embedding change across the integration, as opposed to running culture as a separate learning and communications stream.

Shared practices create connective tissue without demanding cultural sameness, which is critical for merged organizations that align processes with shared systems and grow through increased capital, but maintain local identifies when engaging their communities. Local traditions can remain. Professional identities can remain. What must become clear is where teams need common rules of engagement to steward one enterprise into the future.

Transformational practices make culture transferable

Transformational culture practices are the throughlines that change how we work through training, storytelling, and measuring how things get done.

One useful example is the practice of aligning on decisions, which addresses a different cultural failure: confusing silence with agreement or head-nods with clarity of execution and accountability.

HBR’s analysis on “the false alignment trap” (Julia Dhar, Kristy R. Ellmer, and Philip Jameson) suggests that leadership teams often believe they agree on why, what, and how to change when their proposed approach is still vague and often fractured. The authors recommend specificity, safe dissent, rigorous debate, clear decision rights, formal commitment, and unified communication as the culture practices that everyone with decision-making authority must demonstrate.

This matters because alignment is not consensus.

Consensus means everyone prefers the decision, which is ideal. Alignment means people understand the decision, know how it was reached, recognize who holds the decision right, and what executing the decision will take from everyone – if these standards aren’t met, decision-makers must explicitly raise a material risk.

An Align on Decisions practice might require leaders to finish an important discussion by stating:

1. Here is the decision.
2. Here is who made it and why.
3. Here is what we heard but did not choose.
4. Here is what commitment now looks like.
5. Here is what evidence would cause us to revisit it.

That short ritual converts debate into coordinated action. It also makes disagreement safer: people can challenge each other before the decision is completed without being branded as a troublemaker or complainer, then support execution without pretending they got their preferred outcome.

Align on Decisions creates a cultural sequence:

surface difference → examine evidence → make the call → commit → learn → improve

That sequence is useful in governance meetings, investment decisions, transformation portfolios, member-impacting changes, and post-merger integration of systems and culture, too. It enables care without drift and decisiveness without theatre.

When rituals go rogue

Rituals are powerful precisely because they shape belonging. That also makes them risky and, when the wrong rituals or practices are tolerated, dangerous. Industry advisory expert Sam Walker, author of The Captain Class, argues that “your culture is the worst behaviours you tolerate.”

Practices can become performative when people repeat the words but avoid the behaviour. It can become rigid when compliance with the ritual matters more than the original purpose of the ritual. It can become exclusionary when participation assumes the same schedule, communication style, physical ability, cultural background or appetite for public vulnerability.

Research discussed by Reworked found that intended benefits disappeared when employees experienced workplace rituals as exclusionary, unrecognized or compulsory. Mandatory fun, culturally narrow celebrations and recognition that repeatedly favours the same people can produce the opposite of belonging.

The test is therefore not, “Did everyone perform the ritual?”

The better questions are:

• Did it produce the behaviour we intended?
• Did more people contribute—or did power simply become better choreographed?
• Did it improve the quality or speed of work?
• Did it strengthen accountability without suppressing judgement?
• Who experienced the practice differently?
• Is it still connected to the strategy?

A ritual that cannot be questioned has stopped serving culture. It has become dogma.

The leadership choices

Leaders do not get to decide whether their organization has cultural practices. They get to decide whether those practices are intentional, coherent and open to revision.

Start with five moves:

1. Observe before designing. Identify what people repeatedly do when they meet, decide, escalate, recognize and recover. Study actual culture, not the adjectives in corporate materials.
2. Name the strategic shift. Be specific: from safety that produces caution to safety that enables informed experimentation; from local excellence to enterprise stewardship; from polite agreement to caring challenge.
3. Choose a small portfolio of practices. Select micro-habits, systems and transformational practices that reinforce one another. Three practices repeated well will outperform 30 launched theatrically.
4. Test in real work. Pilot practices in actual governance forums, team meetings and enterprise processes. Look for behavioural evidence, friction and unintended exclusion.
5. Reinforce or retire. Embed useful practices in leadership development, onboarding, performance systems, stories and tools. Retire practices that no longer serve the strategy. Culture should have version control.

Culture helps translate strategy into behaviour and return real-world intelligence to leadership. That is the core leadership opportunity: design practices that do both.

Because strategy may choose the destination.

But rituals decide how people travel, what they notice, and whether they arrive together singing from the same song sheet.