Why Principles Matter More Than Rules

Rules define the boundary. Principles guide the space inside it.

A rule says: respond to every customer email within 24 hours. A principle says: treat every person who contacts you as someone worth taking seriously. The rule can be satisfied mechanically: a canned reply at hour 23. The principle cannot. It demands that you understand what actually matters, and act accordingly.

This distinction is not just semantic. Most organisations invest enormously in defining rules: policies, procedures, service level agreements, codes of conduct. These have genuine value. Rules establish baselines and protect against the worst outcomes. But they don’t produce greatness. A team that operates only by rules will never exceed them. Principles are what move behaviour from compliance to excellence, because they guide judgment in the situations rules don’t cover, which is most of the situations that actually matter.

Some of these ideas are not original; versions of each have been articulated before, in different contexts. But this is my synthesis, the version I keep returning to when a situation is hard and the rules run out.

There is a persistent belief that high performance and high respect trade off against each other: that demanding excellence requires hardness, and that treating people well requires softening standards. I don’t believe this is true.

The most effective environments hold both at once. High performance means high standards: clarity about what good looks like, honest feedback when it is missing, a genuine commitment to doing difficult work well. High respect means treating every person as someone with dignity, perspective, and the capacity to grow. These are not opposites. They are complements. And the combination produces something neither delivers alone.

Zero compromise means applying these principles to everyone, including especially yourself. A leader who holds the team to high standards but excuses themselves from them has a respect problem. A team that is warm and collegial but avoids hard conversations has a performance problem. The principles below are the specific commitments that sit beneath this frame.

The Seven Principles at a Glance

1. Don’t Be a Jerk: Demanding and unkind are not the same thing. Psychological safety is a performance lever.
2. Be Honest, Even When It’s Hard: Silence is not kindness. Withheld truth is deferred cost.
3. Own It. Lead by Example: No backseat driving. Culture is shaped by behaviour, not by what policy says.
4. Think Deep. Start From First Principles: Question the assumption before accepting the convention.
5. Move Fast. Stay Disciplined: Speed without discipline creates debt. Match the care you bring to the weight of the decision.
6. Challenge Ideas. Respect People: Attack the argument, never the person holding it.
7. Raise the Bar. Together: Excellence is collective. Someone else’s growth is not a threat; it is an asset.

1. Don’t Be a Jerk

This comes first because it is the principle most frequently violated in the name of performance.

There is a persistent mythology around the brilliant, difficult person: the one who gets results precisely because they don’t soften edges, who treats harshness as a proxy for seriousness. The mythology is wrong, not just ethically but empirically. Psychological safety, the condition in which people feel they can speak up, take risks, and be wrong without punishment, is one of the strongest predictors of team performance. Behaviour that destroys it is not a performance feature. It is a performance cost that compounds invisibly until it becomes structural.

Being demanding is different from being unkind. You can have high expectations and communicate them clearly. You can challenge work rigorously without attacking the person who produced it. You can say hard things with enough care that they can actually be heard. The alternative, an environment where people walk carefully, protect themselves, and withhold genuine concern, is not high performance. It is high conformance, which is the opposite.

This principle does not mean softening honest feedback. It means delivering it in a way that makes the recipient want to improve rather than hide.

2. Be Honest, Even When It’s Hard

The most destructive behaviour in most teams is the thing no one is saying.

Dishonesty in organisations rarely looks like lying. It looks like not raising the concern in the meeting. The vague “looks good” on a review. The issue flagged in private that was never escalated. The thing said in the corridor that wasn’t said in the room. These feel like kindness or caution. They are usually neither. They are the accumulation of avoided discomfort that turns, over time, into structural dysfunction.

Honest feedback is one of the most generous things you can offer someone who wants to grow. Not brutal, not weaponised, but honest: here is what I observe, here is what I think it means, here is where I see a gap. Delivered with care, this is a gift. Withheld indefinitely, it becomes a liability the person carries without knowing it.

The same applies to bad news about a project, a product, a plan. Teams that surface hard things early spend far less time dealing with the consequences of having surfaced them late. Honesty is almost always cheaper than the alternative. It just doesn’t feel that way in the moment.

3. Own It. Lead by Example

Ownership is not a title or a role. It is a posture.

An owner notices what is broken and fixes it, whether or not it is technically their job. An owner says “I got this wrong” rather than “the situation was difficult.” An owner does not look for someone to hand the problem to; they are already thinking about what they are going to do. This is not martyrdom. It is the difference between being a force in a system and being carried by one.

No backseat driving. If you have a view about what should be done, you have a responsibility to either do it, escalate it to someone who can act on it, or let it go. Critique should move the work forward. Raise the concern, offer a better path, help the person responsible, or take responsibility yourself. Don’t confuse commentary with contribution. The distinction is between raising a concern as someone invested in what happens next, and voicing it as a commentary on what others are doing.

The hardest version of this principle applies to people in authority. A team will not do what its leaders say. It will do what it observes its leaders doing. If you say integrity matters and then make an expedient exception, you have told the team what actually matters. If you say it is safe to raise problems and then punish the person who does, you have told them what is actually safe. Principles are not enforced by words. They are enforced by behaviour, and the behaviour of people with authority carries more weight than they often realise.

4. Think Deep. Start From First Principles

First-principles thinking is not about ignoring accumulated knowledge. It is about understanding where that knowledge comes from before deciding whether to apply it.

A pattern exists because, at some point, someone solved a problem and the solution worked. That solution got named, documented, and repeated. Over time it became a convention. The convention got taught. People learned it as the right way to do a thing, without necessarily understanding the context that made it right. That is not always a problem; conventions carry genuine information. It becomes one when the original constraint no longer holds, when the convention is applied in a context where it doesn’t fit, or when it is used as a substitute for thinking rather than as a tool.

The alternative is to go upstream: what is the actual problem here? What would we conclude if we reasoned only from what we know to be true, without reaching first for an analogy or an established pattern? What assumptions are we carrying that we haven’t examined?

This is harder than it sounds. Reaching for a familiar framework is faster and feels more confident. But decisions about strategy, architecture, team structure, and direction rarely have good analogical solutions. They require working from the problem itself. First-principles thinking is the discipline that makes this possible.

5. Move Fast. Stay Disciplined

Speed and discipline are not opposites. They are partners, and either one without the other becomes a liability.

Moving fast without discipline incurs costs that are invisible at first: technical debt, broken trust, missed context, rework. These accumulate silently. They become visible later, when a team is so burdened by the consequences of past shortcuts that it can no longer move. Speed is not valuable in itself. Only movement toward the right things, with enough care to stick, is actually valuable.

Discipline without urgency produces different problems: over-engineering, analysis paralysis, work that is impeccable and irrelevant, decisions researched past the point where any decision would do. Time and attention are finite. The world changes. Not everything deserves the same level of care, and treating everything as if it does is its own form of failure.

The discipline this principle demands is not process for its own sake. It is the discipline to understand what actually matters about a decision, and to match the care you bring to it against its real weight. That requires judgment, which is, again, something principles provide and rules do not.

6. Challenge Ideas. Respect People

Strong teams disagree frequently and vigorously. This is not a dysfunction; it is how good ideas survive contact with reality, and how weak ones get found out before they cause damage.

But there is a version of this that corrodes rather than strengthens: when disagreement becomes personal, when challenging a decision means challenging the person who made it, when “I think you’re wrong about this” and “I think you’re bad at your job” become confused. This confusion is common. And it is destructive, because it creates environments where people stop bringing their real views and start bringing only positions they are confident they can defend without risk.

The discipline is to separate the idea from the person holding it. Challenge the argument, not the character. Ask whether the conclusion follows from the evidence, not whether the person who reached it is competent. Hold your views firmly enough to defend them and loosely enough to update them when the argument is actually better.

This works in both directions. Receiving challenge well, staying open, staying curious, not collapsing into defensiveness, is a skill as important as delivering it cleanly. A team where people cannot be challenged is not safer than one where people challenge badly. It just fails differently, and more quietly.

7. Raise the Bar. Together

This principle is sometimes misread as competitive: the idea that the goal is to ensure everyone performs above some threshold, or to hire people who exceed whoever hired them. There is something to that framing. But it misses what matters most.

The real goal is collective. A high-performing team is not a set of high-performing individuals arranged in proximity. It is a group of people who make each other better: who share what they know, elevate the quality of each other’s work, hold each other to standards that would be harder to maintain alone, and who understand that someone else’s excellence is an asset, not a threat.

Raising the bar means making your best work visible so others can see what is possible. It means giving feedback that helps someone close a gap they didn’t know they had. It means building the conditions, the systems, the culture and shared language, in which doing great work is easier for everyone. And it means accepting that you, too, are part of what is being raised.

The bar goes up together, or it does not go up at all.

Leaders Are Held to a Higher Standard

If these principles apply to everyone, and they do, they apply more acutely to anyone in a position of authority.

The gap between what a leader says and what they do is the most destructive force in organisational culture. Not because of any individual inconsistency, but because of what it communicates at scale: that the values are decoration, not structure; that the principles apply to the people you lead, not to you; that performance means one thing in public and another in practice.

Leaders shape culture not through the values they articulate but through the behaviour they model and the behaviour they tolerate. If a leader speaks about respect but is routinely dismissive, the team will learn that dismissiveness is the actual standard. If a leader talks about honesty but punishes the person who delivers unwelcome news, the team will learn what honesty actually costs. None of this is usually intended. All of it is understood.

This is the accountability that comes with authority. You do not get to enforce a standard you are not willing to hold yourself to.

The principles above are not guidelines for other people. They are commitments, made to yourself first and to everyone who looks to you for direction second.

These seven principles are not a rulebook. They are a lens: a way of looking at difficult situations and asking what a person with good judgment would do.

I’ve tried to write each one at the level of the underlying idea rather than as a prescription. That is intentional. A prescription tells you what to do in the situation in front of you. A principle helps you reason about the situation you haven’t encountered yet.

Rules define where the floor is. Principles determine where the ceiling can go.

We need rules that protect what matters. But we also need principles strong enough to guide us when the rules are silent.