05. The Team — Culture as Operating System

Part 2 — Where I’m spending most of my time. Team, product, and tech are the three areas I’ve lived in deepest, and the three I want to give the most detail to.

The Principle

Every role on the team is its own promise, nested inside the company’s promise. A team of trustworthy promise-keepers is the smallest, fastest, most resilient unit of work there is.

Why It Matters

A small team of trustworthy people is the highest-leverage thing you can build. Friction collapses. Decisions take minutes instead of meetings. The company’s promise to the outside world is held up by a chain of smaller, internal promises — each role to the next — and when every link is reliable, the whole thing carries weight far beyond its size.

This is why three trustworthy people can outperform thirty mediocre ones. It is not about hours or headcount; it is about how much energy is lost to verifying, chasing, second-guessing, and re-doing each other’s work. In a high-trust team, that overhead is close to zero. In a low-trust team, it is most of the workday.

Each role is a brand inside the brand. The engineer’s promise (this will work, I will tell you when it won’t), the designer’s promise (this will be usable, I will defend the user), the salesperson’s promise (I will not sell what we cannot deliver) — these are sub-brands, and the team member who treats their role as a personal brand inside the company will outperform the one who treats it as a job description.

A Story

The Mechanics

1. Each role is a promise. When someone joins the team, they are not taking a job; they are signing up to make and keep a specific promise that contributes to the company’s promise. Name that promise out loud — in the role description, in the first 1:1, in performance conversations. “Your job is X” is weaker than “Your promise to this team is X.”

2. Wear your role like a personal brand. Encourage team members to treat their role as their own brand inside the company. The way they show up in messages, in meetings, in handovers — that is their brand. A team where every individual takes pride in keeping their own small promise is a team that almost cannot fail to keep the larger one. Making realistic promises and delivering on them should be a personal aspiration, not a compliance target.

3. Small and trustworthy beats large and uncertain. Default to keeping teams small. Add people only when the cost of not adding them is greater than the cost of the trust dilution they introduce. Every new person is a new node in the trust graph, and the graph gets harder to maintain non-linearly.

4. Rituals to detect trust breakdowns early. Trust does not collapse in a single moment; it leaks. Build rituals that surface the leak before it becomes a flood:

• Regular 1:1s with a standing trust question. “Is there anyone on the team you are finding harder to rely on right now? Why?” Asked plainly, every time.
• Retros that explicitly look at commitments. Not just “what shipped” but “what did we promise each other, and did we keep it?”
• Pre-mortems on shared work. Before a project starts, ask: “If this fails in three months, what will have caused it?” Most answers are trust-related and visible from day one.
• Promise check-ins. A quick standing question in team meetings: “Is anyone carrying a promise they are no longer sure they can keep?” Normalise raising it early.

5. Keep each other honest on the realism of promises. A team’s biggest internal risk is people quietly accepting promises they cannot keep — to be polite, to look capable, to avoid the harder conversation. Treat estimate-padding and over-commitment as a trust issue, not a planning issue. The team norm should be: “It is more useful to me that you tell me now you can’t, than to discover it next week when you couldn’t.”

6. Value early honest communication over heroic recovery. The team member who flags slippage two weeks out is more valuable than the one who pulls an all-nighter to recover from a slippage they knew about three weeks ago. Reward the early signal, even when it is uncomfortable. Punish the silent miss, even when it gets rescued.

7. Grace for failure, intolerance for the pattern. This is the hardest balance in team leadership. People will fail. When they do, your job as a teammate or leader is twofold:

• Have grace for the person. Failure is a data point, not a character verdict. Assume good intent. Make space for the human reality (tiredness, overload, life outside work, gaps in skill) that contributed.
• Step in front of the pattern. The destructive pattern that caused the failure — unclear ownership, no early-warning channel, a culture of optimistic estimates, a teammate set up without context — is what you go after. Protect your teammate from being defined by the failure while you dismantle the conditions that produced it.

A practical sequence when a teammate fails:

1. Cover them, publicly. Don’t let the failure become a public weight they carry alone. “We missed this — here’s what we are doing about it.” We, not they.
2. Get curious, privately. Ask what they saw, when they first sensed trouble, what got in the way of raising it earlier. Listen for the system around them, not just the individual choices.
3. Name the pattern, not the person. “We have a pattern where slippage gets reported late. Let’s fix the pattern.” This separates the diagnosis from the diagnosis-of-them.
4. Make the next promise smaller and clearer. Rebuild trust through a small kept promise, not a big new commitment.
5. Only escalate to the person if the pattern persists across attempts to fix the system. If you have removed the systemic causes and the same failure keeps happening, then it is a fit conversation — held with the same grace, but honestly.

8. Hiring is promise-fit, not just role-fit. Screen for whether the person treats their work as a promise. The interview question is less “can you do this job?” and more “tell me about a commitment you made that you found hard to keep — what did you do?”

Questions to Ask Yourself

• Can each person on your team articulate their own promise to the team in one sentence?
• Do your team members treat their role as a personal brand, or as a job description?
• What ritual do you have for detecting trust breakdowns before they become resignations or outages?
• When a teammate over-commits, is it safe for them to walk it back the next day? Or are they punished for the correction?
• Are you rewarding early honest signals more than heroic recoveries?
• The last time someone on your team failed: did you go after the person, or the pattern?
• Whose failure are you currently letting them carry alone in public?

Anti-patterns

• Treating roles as job descriptions, not promises. Roles framed as task lists produce task-completers. Roles framed as promises produce owners.
• Growing the team to solve a trust problem. Adding headcount because two people cannot work together is paying compound interest on the original issue.
• Hero recovery culture. Celebrating the late-night rescue and ignoring the early-warning skipped. The team learns to wait until it’s a crisis.
• Polite over-commitment. A team where everyone says “yes” in the meeting and “no” in their head. Every unkept private “no” is a future broken promise.
• Punishing the messenger. When the person who flags risk gets treated as the problem, you have just bought silence on every future risk.
• Public blame, private grace. The reverse of what you want. Do the protecting in public and the honest conversation in private.
• Tolerating the destructive pattern because the person is talented. Talent does not pay back the trust debt their patterns are accumulating in the team.

One Thing to Do This Week

In your next 1:1 with each direct report (or peer), ask two questions:

1. “What is the promise you are making to this team right now? Say it in one sentence.”
2. “Is there a promise you’ve made that you are no longer sure you can keep? Tell me now, not later.”

Listen. Don’t fix anything in the meeting. Take notes. The pattern across the answers will tell you where to work next.