The Culture of Action

Interpretation

Rules try to control behavior from the outside; culture produces the right behavior from the inside, without anyone watching. When you have to write a policy for every possible mistake, you have already lost the thing policies are meant to protect—shared judgment.

The executive lens

Every growing organization faces the same fork in the road after its first serious failure: write a new rule, or reinforce the principle that would have prevented it. Most choose the rule, because it is fast, visible, and defensible in a postmortem. But rules compound. Ten years in, a once-nimble company is buried under a rulebook so thick that new hires spend their first month learning what they can't do instead of what the company stands for.

A thin rule book is not a sign of low standards—it is a sign of high trust, purchased at the price of hiring carefully and reinforcing values relentlessly. The leaders who pull this off spend disproportionate energy on the few rules that truly matter—safety, ethics, legal exposure—and otherwise invest in making the culture so clear that employees can answer 'what would we do here?' without consulting a manual. The strategic insight: a rule tells someone what to do once; a culture tells them what to do in situations you never anticipated.

Key lessons

Write principles, not procedures, wherever you can. A principle scales to situations you haven't imagined yet; a procedure only covers the one you already had.
Every new rule has a cost. Before adding one, ask whether reinforcing an existing value would have prevented the problem just as well, with none of the rigidity.
Model the behavior you want copied. In a strong culture, the loudest teaching tool is what leadership visibly does under pressure, not what the handbook says.
Hire for judgment, not just skill. A thin rule book only works with people capable of filling the gaps with good sense—screen for that as hard as you screen for competence.

Symbolic parable

The Village Without Locks

A visitor to a mountain village noticed that none of the doors had locks, and asked the elder why. The elder explained that a generation ago, after a series of thefts, the council had debated installing locks and posting a night watchman with a long list of curfews and searches. Instead, they chose to spend a full year doing something slower: they held gatherings where families told each other their histories, worked each other's fields during harvest, and shared meals across old rivalries, until neighbors simply knew each other too well to steal from one another.

The visitor asked what happened when, occasionally, someone still did something wrong. The elder said the village didn't reach for a new rule—it reached for the person, sitting with them, asking what had gone missing in their life that a theft was meant to fill. "Locks only stop the people who were already going to knock first," she said. "They do nothing for a stranger, and they insult a neighbor."

“Locks only stop the people who were already going to knock first.”

The Thin Rule Book Audit

01
List every written rule
Pull your team's actual policies and procedures into one list, however small or large. Most leaders are surprised how many they've never revisited.
02
Sort by cause
For each rule, write down the one incident that caused it to exist. If you can't remember a specific cause, that rule is a candidate for deletion.
03
Replace three rules with one principle
Pick your three most restrictive or resented rules and write a single guiding principle that would have produced the right behavior without them. Test it for a quarter.

Marcus's story

Marcus managed a fast-growing operations team, and every time something went wrong—a missed shipment, an expense report abused, a customer mishandled—his instinct was to write a new policy so it could never happen again. Within two years his team was operating under a 40-page procedures document that new hires printed out and never fully read. Decisions slowed to a crawl because employees were afraid to act without checking the manual, and the ones with the best judgment felt the most stifled, since the rules were written for the worst-case employee, not the best one.

After a particularly talented hire quit, citing exactly this frustration, Marcus rewrote the entire document down to one page of principles—things like 'treat the company's money like it's your own' and 'when in doubt, ask what's best for the customer, not what's covered by policy.' He backed it up by publicly praising the judgment calls people made under those principles, right or wrong, as long as the reasoning was sound. Within six months, decisions were faster, morale was up, and the handful of genuine problems that arose were handled person to person rather than clause by clause.

Conclusion

A life—and a team—governed entirely by rules is a life that has stopped trusting itself to reason. The deepest cultures, like the deepest characters, are not the ones with the most restrictions but the ones with the clearest sense of what they stand for, which makes most restrictions unnecessary.

Closing line: Build people who don't need a rulebook, and you'll rarely need one.

The Culture of
Action

A 4-minute reading is coming soon.