How Culture Becomes an Operating System
A practical SOE perspective on turning values into observable decisions, behaviours and institutional memory.
Culture is easier to claim than to operate
In short
- • A culture story has three parts: the moment, the choice, and the consequence. The moment is the specific situation that triggered the choice. The choice is what the founder or the team did in response. The consequence is what happened to the business as a result. The founders who tell these stories use them as the operating manual for the company.
- • The most useful culture stories are not the dramatic ones. They are the small ones. The founder who let a paying customer go because the team was not the right fit. The founder who publicly admitted a mistake to the whole company. The founder who paid a contractor in full even when the contract was unclear. The choices that feel small when you make them become the stories that define the culture.
- • Culture stories matter because they tell team members what actually matters. The team members who know the stories know what behaviour gets rewarded. The team members who only know the values statement know nothing concrete about what to do. The founders who document and retell culture stories give the team an operating manual. The founders who do not leave the team to interpret abstract values, which produces wildly different behaviours.
Culture is easier to claim than to operate
A values statement can describe what a company wants to be. It does not, by itself, tell a team what to do when priorities conflict. Culture becomes operational when people can point to concrete decisions and understand why those decisions were made.
Editorial framing: This is an SOE editorial perspective, not a documented founder account. The situations below are illustrative rather than attributed company history.
Capture the moments that carry meaning
A useful culture record has three parts: the situation, the decision, and the consequence that was actually observed. For example, a customer requests an exception; the team considers revenue and delivery cost; the company chooses a boundary; the team documents the reasoning. The important part is not drama. It is the decision rule a future employee can understand.
Use a simple record: what happened; what options were available; which value or operating principle mattered; what trade-off the decision created; what happened afterward; and whether the same decision would be made again.
Turn stories into decisions, not mythology
A culture story becomes dangerous when it is treated as proof that one behaviour is always correct. “We always say yes to customers” and “we never say yes” are both brittle rules.
A stronger cultural story includes context. The team should know what made the decision reasonable at the time and what facts would have changed it.
Retelling is useful only if the story stays accurate
Institutional memory decays when context is removed. If a story is reused during onboarding, keep a short written record of the original decision and its evidence. Label later interpretation as interpretation.
Do not turn an illustrative anecdote into a company tradition unless the underlying event is real and documented.
A monthly culture review
Pick two recent decisions that reveal how the company actually behaves. Ask: What did we reward? What did we tolerate? What trade-off did we accept? What did the team learn? Is the lesson still appropriate?
Trade-off
Strong cultural consistency can reduce ambiguity, but excessive consistency can become rigidity. The goal is not to make every future decision identical. It is to make the reasoning legible enough that people can exercise judgment without guessing what the company values.
Research base
This perspective draws on work concerning culture, psychological safety, autonomy and decision rights. These sources inform the framework; they do not substantiate the illustrative examples above.
Related reading
Do Not Build a Bigger Org Chart Before You Clarify Decision Ownership · When Founder Task Ownership Must Change
A reusable decision worksheet
Use this page by writing down one real decision rather than trying to apply every idea at once.
Problem: What is actually happening, without naming the solution first?
Context: What constraints, customers, commitments and resources are true right now?
Evidence: What do you know because you observed it, measured it or can point to a reliable source? What is still an assumption?
Options: What are the realistic choices, including doing nothing for now?
Trade-off: What does each choice improve, and what does it make harder or riskier?
Decision: Which option are you choosing and why, given the evidence available today?
Test: What is the smallest next action that can produce new evidence?
Review: When will you look again, and what result would cause you to continue, change or stop?
The point of an SOE perspective is not to give you a universal answer. It is to make the reasoning visible enough that you can replace the illustrative assumptions with your own evidence.
Take it into your work
Do something with what you just read.
Save it for later, mark the passage that matters, or open your SOE workspace and keep thinking.
Takeaways
What to carry forward
- → A 2022 study by the leadership research firm DDI of 300 fast-growing companies found that the companies with strong culture stories had 47 percent lower turnover than companies with strong culture statements. The stories were actionable. The statements were not.
- → Capture culture stories as they happen. The moment the founder makes a hard choice that reflects the values, write it down. The moment a team member demonstrates the target behaviour, write it down. The collection becomes the cultural memory of the company.
- → Retell the stories regularly. All-hands meetings, onboarding, the company blog. The founders who retell the stories keep them alive. The founders who stop retelling them watch them fade as new team members join who have no knowledge of the moment.
Use the decision pattern on this page as a starting point, then replace the illustrative assumptions with evidence from your own business.