Policies are useful. They prevent repeated debate over known situations, create fairness, reduce compliance risk, and make expectations explicit. But policies are a poor substitute for operating principles.
A policy says what to do when the situation is already categorized. An operating principle says how to think when the category is unclear.
Companies get into trouble when they try to manage judgment with policies. The handbook gets longer, the exceptions multiply, and people learn to ask, "What is allowed?" instead of "What is right for this business, this customer, and this standard?"
Policies control boundaries; principles guide tradeoffs
A travel policy can tell people what expenses are acceptable. It cannot tell them when it is worth flying three people to save a strategic customer.
A discount policy can define approval thresholds. It cannot decide whether the deal is a bad-fit customer that will pollute the roadmap.
A product launch checklist can prevent obvious misses. It cannot decide whether the team should delay because the experience is technically functional but below the company's bar.
This is where operating principles matter. They help people make tradeoffs when policy runs out.
The best companies do not avoid policies. They keep policies from becoming a replacement for judgment.
Bad principles are slogans
Most stated principles fail because they do not create real constraints. They say things like:
- Move fast.
- Be customer-first.
- Act like owners.
- Collaborate.
- Raise the bar.
None of these are wrong. They are just incomplete. Move fast compared to what? Customer-first when the customer is wrong for the product? Ownership over which decisions? Collaborate with whom, and when does collaboration become consensus theater? Raise which bar, at what cost?
A principle that cannot be violated is not a principle. It is branding.
A useful operating principle creates an edge. It tells people what the company values more when values conflict. If everyone can nod without changing behavior, the principle is too soft.
Good principles name the tradeoff
A sharper principle sounds more like this:
- "Speed matters most on reversible decisions; quality matters most on customer trust boundaries."
- "We will lose deals before we sell work the product cannot support."
- "Disagree in the decision forum, then commit in execution; side-channel vetoes are not a process."
- "Bad news moves immediately; blame waits until the facts are understood."
- "Remote work requires written clarity; ambiguity is not absorbed by hallway conversation."
These principles are useful because they help people choose. They also expose disagreement. If leaders cannot agree on the tradeoff, the organization will not magically resolve it through inspiration.
A practical format helps: in situation X, we choose Y over Z because principle P, unless condition C is true. That sentence forces the company to name the decision rule rather than hide behind taste.
Principles need examples or they become folklore
Operating principles become real through examples. People learn the rule by watching what leaders do in specific cases.
If you say "bad news moves immediately," the organization will study what happens when someone brings bad news. Do leaders thank them and mobilize? Do they interrogate their competence? Do they punish the messenger later? The example becomes the principle.
If you say "quality matters," the organization will study the next launch date conflict. If the date wins every time, the real principle is "quality matters until it is inconvenient."
The best leaders narrate decisions explicitly: "We are delaying this launch because this defect crosses a trust boundary. This is not about perfection. This is about the standard customers rely on us for."
That narration turns a decision into reusable judgment.
The principle quality test
A strong operating principle passes five tests:
- Tradeoff test: Does it help decide between two good things?
- Behavior test: Does it imply observable behavior?
- Exception test: Do leaders know when not to apply it?
- Consequence test: Is violation corrected, not merely regretted?
- Transmission test: Can a new employee use it without private context?
- Remote test: Does it survive without hallway explanation?
If a principle fails these tests, it may still be a nice sentence. It is not yet operating infrastructure.
The trap: writing principles after the culture has already decided
Many companies formalize principles late. By then, the organization has already learned the real rules from years of decisions. Writing better words will not override that memory.
The work is not only drafting principles. It is reconciling them with incentives, rituals, authority, and consequences. If the promotion system rewards empire-building, a principle about company-first behavior will not survive. If leaders tolerate brilliant jerks, a principle about respect will become a joke. If all important decisions route upward, a principle about ownership will sound hollow.
Principles beat policies only when the rest of the operating system reinforces them. If the principle says one thing and the budget, promotion, escalation, or founder intervention pattern says another, the organization will believe the system.
Use policies where consistency matters; use principles where judgment matters
The goal is not a policy-free company. The goal is a company where policies create clarity at the edges and principles guide judgment in the middle.
Policies answer: what is the rule?
Principles answer: what kind of company are we when the rule is not enough?
