The most confident person in your final interview round is often the most fragile hire on your shortlist.

In 1955, a 21-year-old psychologist was assessing officer candidates for the Israeli army. The test was a leaderless group challenge: eight strangers, a log, a wall to get it over. Watching who took charge, he felt vivid certainty about who would make a real officer. Then the follow-up statistics came back from officer school, and his predictions were barely better than guessing. Here is the part that should worry every founder and CEO who trusts their read of a final-round interview: knowing his forecasts were nearly worthless changed nothing. The next batch of candidates produced the same vivid certainty, with the same feeling of seeing the truth about a person. The psychologist was Daniel Kahneman, and he later gave the error a name that stuck: the illusion of validity.

A founder I work with lived this from the hiring side. He was filling a critical technical seat. One candidate had presence, fluency, answers that landed like they'd been rehearsed in front of a mirror because they had been. Another candidate hedged, poked holes in the company's plans, and came across as flatly negative. The founder nearly passed on him.

Hold that decision for a moment, because what happened next only makes sense once you see what an interview actually measures. The format rewards one specific skill: performing certainty in front of strangers for an hour. That would be fine if performing certainty had anything to do with the job. It doesn't, and on the days that matter most it runs backwards.

What you are actually trying to read across that table is where a person's confidence comes from, because the source decides what happens to them under pressure. Confidence comes from three places.

Borrowed confidence lives in other people's reactions. An interview is its home game: a room full of strangers to win over is exactly the fuel it runs on. The rehearsed candidate was running on it in front of the founder's eyes, every answer built for the room rather than the problem. It looks superb for an hour and goes missing the first week the room turns cold.

Rented confidence lives in outcomes. The streak, the title, the last win. It reads beautifully right up until the streak ends, and then the same person who filled your boardroom can't send an email. Every win raises the rent.

Forged confidence is built from two things nobody in that room controls: clarity about who they are, and a practiced habit of turning hits into evidence. It often reads quieter than the other two. Sometimes it reads like pessimism.

The founder hired the pessimist. That apparently negative candidate became the best hire he has made: relentlessly open, hungry for feedback, treating every correction as information rather than insult. The pessimism turned out to be the surface of something valuable, a mind that refused to perform certainty it hadn't earned yet. The display had been telling the founder almost nothing. The source told him everything that mattered.

So how do you interview for the source instead of the display? The richest seam is the candidate's worst professional loss, and specifically the weeks after it. Listen to what they describe. People running on rented confidence describe the event: what happened, what was done to them, whose fault it was. People with forged confidence describe their response, usually with a date or a number attached. "It took me about two weeks to get my legs back, and then I rebuilt the pipeline from scratch" tells you more than every strengths question ever written.

There's a second move, one I now hand to every founder who will take it: flip the format entirely. Skip the question list. Tell the candidate exactly what you're building, put one live problem in front of them, the one that's actually keeping you up, and watch what they do with it. The response under live conditions is the interview. Prepared certainty never gets a chance to perform.

Kahneman's own fix is the part that travels. He didn't stop assessing candidates; he governed the assessment. Dimensions chosen before the interview, factual questions, each trait scored on its own, intuition allowed in only after the scores were down. His interviewers told him he was turning them into robots. The army used the method for decades. A work trial works the same way: decide what you're scoring before you watch, or the watching will write the story for you.

I should declare an interest here. I coach confidence for a living, which makes me roughly the last person who should tell you to ignore it in an interview. So I'll be precise about the claim: the display tells you almost nothing, and the source tells you most of what you need. One is free to fake for an hour. The other leaks out in how a person talks about their worst year.

The candidate who ran the room is confident today. The interview can't tell you whether he'll still be confident the week your biggest client walks. The answer to that question exists, and it's sitting in his history, in what he did across the fortnight after the worst thing that ever happened to his work. You just have to ask for it.

What did your best hire look like in their interview?

Tim Ferriss has interviewed somewhere north of two hundred people at the top of their fields. Athletes. Investors. Generals. Writers. After about a hundred conversations he noticed a thing he didn't expect, and he kept noticing it. More than 80% of them had a daily mindfulness or meditation practice [1]. He said it surprised him every time, which is the only honest thing to say about it. The 80% line gets passed around as a productivity hack now, which is a small tragedy. What's interesting isn't the number. It's the question underneath it. What do people who get to the top of their work know about attention that the rest of us are missing?

Most of the writing about focus starts from the assumption that your attention is broken. That something is wrong with you. The phone did it, or the algorithm did it, or your childhood did it, or you've got some flavour of ADHD nobody diagnosed. The fix on offer is always external. An app, a supplement stack, a dopamine fast, blue-light glasses, a productivity system named after a tomato or a four-letter Japanese word. The premise underneath the whole industry is that you are the patient and someone else has the cure.

Your attention is fine. It's working exactly the way evolution designed it to. Whatever is loudest in your environment, your attention goes there. The pings get checked. The system isn't broken. It's been pointed.

Gloria Mark runs the attention lab at UC Irvine. She has been measuring how knowledge workers spend their attention for two decades. In 2004 she clocked average sustained attention on a single screen at about two and a half minutes. By 2012 it was 75 seconds. By 2021 it was 47 seconds [2]. The collapse happened inside your working life. You did not get worse at paying attention. The environment got better at spending it for you.

Mark's other famous number is 23 minutes and 15 seconds. That's the average time it takes to get back to the task you were doing before a single interruption [3]. Not to refocus. Just to remember where you were. A phone buzz at 10:14am means whatever you were doing at 10:13 is gone until at least 10:37, and that's if nothing else interrupts you in between. The math, played out across a day, is the reason most of your week feels like running on a treadmill that is also on fire.

This is not a defect in you. This is a feature of an attention market that runs on extracting fractions of a second from a billion people. The slot-machine architecture inside your phone wasn't an accident. The variable-reward schedules in social-media apps were borrowed straight from casino design. You are not weak-willed. You are a mammal being pointed at.

The good news, if there is any, is that attention is a capacity, not a fixed quantity. It can be trained the way a muscle can be trained. There are studies on this; short ones and long ones, on monks and on Marines, on surgeons and on sales reps. Yi-Yuan Tang's group at Dalian University found that five days of brief meditation training improved scores on the Attention Network Test [4]. Five days. The signal is small but real, and the larger meta-analyses (Goyal 2014 [5] is the cleanest hedge here) find moderate effects on anxiety, depression and pain rather than the breakthrough claims sometimes made for the practice. Treat the science as confirmation that something is there, not as the reason to sit.

I should name a thing before I keep going. I'm a coach. My livelihood depends on this kind of argument mattering. That's exactly why you should pressure-test it. Read the citations. Run a Saturday sit yourself before you take anyone's word for any of this, including mine.

So this is what the Saturday Sit is, and what it isn't. It isn't a fix for what's wrong with you. Nothing is wrong with you. It is one hour of attention training, in a room in Bondi, with twenty other people who decided the same thing on the same Saturday. The room is the instrument. Twenty people deciding to stay is harder to walk out on than one person deciding alone. The phone is in a basket by the door. The bell rings at 1pm. Nobody talks. You sit. You notice what your attention does. You come back. You do it again. You do it a thousand times in an hour.

There is one thing I want to be careful about saying. The point of sitting is not to engineer a better version of yourself. Pema Chödrön, who has been writing about this for forty years, would push back hard on anyone who framed practice that way. The mind doesn't get quiet. You don't transcend anything. You don't escape your life. What changes, slowly and without fanfare, is that you become slightly less interested in the noise. The thoughts still arrive. You're less likely to chase every one out the door. That's most of what people end up calling equanimity, and it's smaller than the marketing suggests.

I sat this morning at 6:30am. I'd been awake since 5:45 doing what most of us do, which is reaching for the phone before getting out of bed. Nothing on it. Nothing waiting. Just the small pull of wanting something to grab me. I counted the reaches once I noticed them. Nine, before I sat down on the cushion. The morning sit didn't fix the reaching. It made me see the reaching, which is most of what sitting ever does. The seeing is the practice. Whether I reach less tomorrow is a side effect.

If you've read this far the practical version is short. Saturday 20 June 2026, 1pm to 2:30pm, BodyMindLife in Bondi. Twenty seats. $15 until midnight on Friday 19 June, $40 after that. luma.com/5pfeuysh. There's no follow-up sequence, no upsell, no course. After the hour we put the chairs back and walk out. The whole thing takes the afternoon out of your Saturday and gives you back a slightly less reactive Monday. That's the honest claim, and the only one I'm willing to make in writing.

The bet is small. The asymmetry is large. One hour against the rest of an operating life spent half-present.

Attention is a capacity you already have. Most of the time you're using it on whatever grabs you. One hour of sitting is how you take it back. Not by tightening. By noticing.

Sources

[1] Tim Ferriss, Tools of Titans, Houghton Mifflin Harcourt (2016). Ferriss's introduction to the book notes that more than 80% of the world-class performers he has interviewed have some form of daily mindfulness or meditation practice. Sample drawn from ~200 interviews on The Tim Ferriss Show. Original post: https://tim.blog/2015/12/14/meditation/

[2] Gloria Mark, Attention Span: A Groundbreaking Way to Restore Balance, Happiness and Productivity, Hanover Square Press (2023). UC Irvine: https://news.uci.edu/2023/02/02/attention-spans-while-working-in-front-of-a-computer-getting-shorter/

[3] Mark, G., Gudith, D., & Klocke, U. (2008). "The Cost of Interrupted Work: More Speed and Stress." Proceedings of CHI 2008, ACM. Average time to return to the original task after an interruption: 23 minutes and 15 seconds. https://www.ics.uci.edu/~gmark/chi08-mark.pdf

[4] Tang, Y.-Y., Ma, Y., Wang, J., et al. (2007). "Short-term meditation training improves attention and self-regulation." Proceedings of the National Academy of Sciences, 104(43), 17152–17156. https://www.pnas.org/doi/10.1073/pnas.0707678104

[5] Goyal, M., Singh, S., Sibinga, E. M. S., et al. (2014). "Meditation Programs for Psychological Stress and Well-being: A Systematic Review and Meta-analysis." JAMA Internal Medicine, 174(3), 357–368. Meta-analysis of 47 trials (3,515 participants); moderate evidence for anxiety, depression and pain reduction, less for other outcomes. The cleanest hedge against breakthrough claims. https://jamanetwork.com/journals/jamainternalmedicine/fullarticle/1809754

You're eight prompts in and the output has gone soft. You re-read your last prompt. It was clear. Direct. So you type it again, almost word-for-word, and get back the same beige mush. The problem isn't the prompt. It's the sixty prompts stacked above it. Scroll up. Look at the weight you've loaded on that conversation. Three abandoned drafts, a pasted-in PDF, two tangents about tone. You filled the whiteboard.

Every office has someone who thinks clearly when everyone else is drowning in noise. Kate from ops is that person. She would have seen this coming twenty minutes ago. You didn't.

Here's what she would have done instead.

The Director Who Leaves the Set

Steven Spielberg doesn't operate the camera. Never has, not on a professional film. He walks onto a set with two hundred people and his job is to hold the whole film in his head: the tone, and what the audience should feel walking out of the cinema. He sends a second unit to shoot the desert chase. Each unit brings back only the finished piece. Not the raw footage, not the forty-page location report. The shots that made the cut. Spielberg never stood in the sand.

He said once that as a kid, filmmaking was him with a camera bossing his friends around. As an adult, it became about knowing he could never have made any of these films alone. His cinematographer Janusz Kamiński, who's shot every Spielberg film since Schindler's List, put it plainly: "He knows exactly what he wants. He's the one who makes notes."

You can direct Claude the same way. Instead of loading every task into one conversation, you send agents out. Each one gets a specific job, works with its own clean whiteboard, and reports back with only what matters. One reads your competitor's pricing pages and returns four sentences. Another pulls financial data and finds the patterns worth knowing. When they finish, the findings land in your main conversation. A paragraph. A data point. Nothing else.

Your main thread never saw the forty-seven pages of competitor pricing. It never processed the raw data. It got what the second unit brought back: only the footage that mattered.

Every team has a Craig. The person who mistakes volume for value. He'd paste all forty-seven pages into one window. The whiteboard fills and the output degrades. A director doesn't work that way. A director says: here's the emotion I need, go shoot it. The unit comes back with what matters. The main conversation stays clean.

The Ritual of Forgetting

A surgeon scrubs between procedures. Not sometimes. Every time. It looks ceremonial: the washing, the gowning. It's not. It's a hard boundary between one patient and the next. Whatever happened in the last surgery (the complications, the moment that almost went sideways) stays on the other side of that scrub. You walk into the next theatre with clean hands and a clear head. The alternative is contamination. And contamination is invisible until it's already in the output.

Your conversation with Claude accumulates the same kind of residue. Old drafts. Abandoned directions. Context from a problem you solved six prompts ago. Still on the whiteboard. Still taking up space. You can't see it happening. You just notice the output getting worse.

When you feel the conversation getting heavy, stop. You'll know. The responses get longer and say less. Tell Claude what to keep. Be specific: "Hold the brand voice we agreed on and the four headlines from prompt six. Forget everything else." Then compact the conversation. Claude condenses everything else into a few tight bullets. That's your clean tray for the next procedure.

Kate does this every time Craig runs one of his forty-four-slide decks. Cold coffee in hand. She lets the noise wash past. Holds one question, discards the rest. Everyone else leaves foggy. She leaves with the answer.

Throwing away context you spent twenty prompts building feels wasteful. But a surgeon doesn't keep the last patient's blood on their gloves because the procedure was hard. Clean hands think better.

What Survives the Scrub

Kate carries a notebook. Not for the meeting. For after. The whiteboard in the conference room gets erased every night by the cleaner. Anything left on it disappears. The notebook comes home with her.

Claude works the same way. Every conversation starts with a blank whiteboard and ends when you close the tab. Gone. But project files persist across every conversation. They're the notebook. Your brand voice, the standing decisions you've already made. Write them down once. Every new conversation reads them before you type a word.

My project file for client proposals is eleven lines. Tone of voice. Pricing. The two objections I hear most. I wrote it once, in January. It's saved me from re-explaining myself maybe two hundred times.

Kate's notebook was never a transcript. She wrote down the vendor decision and nothing else. Keep your project files the same way. Paste your entire company wiki in there and you've just given Craig a permanent desk.

The whiteboard is for thinking. The notebook is for things you've already thought.

Last time I asked whether you're Kate or Craig. That was diagnosis.

What are you protecting by refusing to change how you work?

You're forty minutes into a quarterly review. The guy from partnerships (Craig, always Craig) is on slide 31 of what he's promised is a "quick deck." He's reading every bullet point aloud. Market penetration across APAC verticals. Customer acquisition cost trends segmented by channel. A bar chart that means nothing without context he hasn't provided and won't.

You stopped listening at slide nine.

By the time Craig wraps up (slide 44, not 40 like he said) you can't multiply single digits. Someone asks what you think about the vendor shortlist and you stare at them like they've asked the question in Mandarin. You had an opinion on this an hour ago. A strong one. Now there's nothing. Just fog.

You walk to your car. You sit there for a minute trying to remember whether you're picking up the kids or going home. You drive the route you've driven five hundred times and miss the turn. At the lights, a thought arrives that you don't say aloud: is this how it starts?

It's not dementia. It's Craig.

Your brain runs on a whiteboard. Not storage, workspace. Every piece of information you're holding, every decision you're weighing, every thread you're tracking goes on that board. It's where you think. And it's finite. Craig just spent forty-four slides filling every square inch of it with noise you didn't need and can't use. He didn't leave you room to think. He left you room to nod.

That's the mechanism. Blank space on your whiteboard isn't wasted space. It's where the thinking happens. Even good signal has a ceiling. Past it, sharp turns to fog. Fill the board with noise and you never had a chance.

And the thing nobody tells you about AI is that it works on exactly the same constraint.

Claude's whiteboard

You open a new chat. You type: "Build me a landing page for a consulting firm. Clean, modern, positions us as experts in operational strategy. Write the copy." Claude nails it. The headline is better than anything your last agency produced in six weeks, and you barely gave it a brief.

So you keep going.

You paste in your brand guidelines. Your tone of voice doc. Three competitor URLs. A blog post you liked. You ask for revisions. Then more revisions. You add your bio, your client list, your service descriptions. Each prompt loads more onto the board.

By prompt twelve, something has shifted. The copy has gone beige. You ask for a headline and get "Empowering Your Business Through Strategic Excellence," the kind of sentence nobody would say out loud. That's not Claude being creative. That's Claude drowning. By prompt twenty, Claude has forgotten you wanted a world-class site. You're fighting it, re-explaining things you told it an hour ago.

The AI's whiteboard is full.

Every message you send, every document you paste, every revision you request takes up space in Claude's context window.* The more you put in, the less room it has to reason. You buried it in so much context it can't think anymore. Same as Craig. Same as you in that parking lot.

The difference is that Craig eventually stops talking. With AI, you're Craig. You just don't know it.

And most people never find out, because nobody teaches you how to manage the one thing that determines whether your AI gives you something worth reading or mush.

Clearing the whiteboard

There was someone else in Craig's meeting. You probably didn't notice her. Kate from ops. She sat in the back with a cold coffee she'd been carrying since nine, didn't take many notes, and left before the Q&A. You've seen her do this before. Walk into a room late, say almost nothing, and somehow walk out with the one thing that mattered. It's annoying, honestly.

While Craig marched through forty-four slides, Kate held one question in her head: do we renew the vendor contract or not? She didn't try to absorb the APAC verticals. She didn't track the bar charts. She let Craig's noise wash past her and kept her whiteboard almost empty. Just that one question, and whatever Craig said that helped her answer it.

Kate walked out sharp. You walked out foggy. Same meeting. She just used her board differently.

That's the fix. Not a smarter AI. Just a clearer sense of what deserves to go on the board before you start writing on it.

With Claude, it's the same discipline. Sometimes you know your question before you start. Sometimes you need a few prompts to find it. Either way, once you know what you're asking, strip the board. Give Claude what it needs to answer that question and nothing else. When the conversation gets long, clear the board. Tell Claude what to keep and what to forget. Start a new chat when the old one gets heavy. Think of every prompt as a slide. Ask yourself: is this Craig's slide, or Kate's?

Most people never manage their AI's whiteboard. They paste in forty-page brand guides. They ramble through voice notes without thinking first. Then they're surprised when the output reads like it was written by a committee. But Claude didn't get dumber. You just gave it a forty-four-slide deck and expected it to think.

I'll walk through the specific tools and techniques for managing Claude's context in a follow-up piece. But the tools are just ways of doing what Kate did in that meeting.

Next time you open a chat, ask yourself: am I Kate, or am I Craig?

Hannah Sundberg writes about AI context management on her blog In The Weeds. Worth reading.

In the Weeds

Practical AI workflows to help you get things done - no coding required. Plus, my AI side projects and tips & tricks I discover along the way.

By Hannah Stulberg

If the system is where much of the intelligence lives, then culture is not your values statement. Culture is the interaction rules — how information flows, how problems surface, how decisions get made. Whether a problem spotted on Monday becomes a solution by Wednesday, or dies in a Slack thread nobody reads.

This is where most founders stop nodding along and start getting uncomfortable.

Because if this is true, we've been investing in the wrong variable. Developing better people is a serial game — you invest in someone, they grow, they leave, the gap reopens. Better interactions compound. The intelligence accumulates in the structure, not in any one person's head. It doesn't walk out the door.

Consider Steve Jobs returning to Apple in 1997. The common narrative is pure individual genius — one man saved the company. But look at what Jobs did. He killed product lines. Simplified the org structure. Rebuilt product development from scratch. He redesigned the system.

He was also the system.

Both things are true. When he left in 1985, the system degraded. When he returned, he rebuilt it — but he didn't rebuild it alone. Jony Ive was already inside Apple, marginalised under the old structure; Jobs found him and gave him authority. Tim Cook was recruited to redesign the supply chain. The genius wasn't just seeing which structure was needed — it was knowing who to place inside it.

But most leaders aren't Jobs. They're the Admiralty. The British Navy had empirical evidence that citrus prevented scurvy as early as 1601. James Lind replicated it in 1747. The Admiralty still waited 48 years to mandate lemon juice — because confident experts preferred their theoretical explanations over what was already working. Sailors died not from ignorance but from high-confidence individuals overriding structural knowledge that had already solved the problem. The hero-leader doing active harm. That's the version of this story the leadership industry doesn't tell.

Which means the argument isn't really "systems over individuals." It's that we've been investing in the wrong kind of individual. We celebrate the charismatic leader, the inspiring speaker, the person who commands a room. The evidence says we should be investing in the architect — the person who designs the system everyone else operates in. A different kind of individual than the one the leadership industry has been celebrating.

I'm aware this is convenient for someone who coaches founders on exactly this kind of work. I have skin in this argument. But the tension is real, and I'd rather sit inside it than pretend it resolves neatly.

Designing environments is harder than developing individuals. Less visible, less dramatic, less satisfying. There's no applause for plumbing. No magazine profile for the founder who quietly restructured how feedback moves through their organisation. The work that matters most looks like nothing from the outside.

And it demands something most leaders aren't willing to give — humility. The kind that comes from admitting your team's performance has less to do with you than you'd like to believe. That the culture you take credit for might have been built by someone before you. That your "leadership" might be a function of the system you inherited, not the person you are.

That the success you wear as identity might belong to a structure you didn't design and barely understand.

The leadership industry runs on the opposite assumption — that you are the protagonist, the lever. It's a more flattering story. But the evidence says we've got the weighting wrong, and at some point, that has to matter.

So the question isn't what to do next. No five-step framework.

I've asked myself. I don't like the answer.

How much of my success is me — and how much is the system I'm standing in?

If we're massively underweighting systems, what does the evidence look like when you actually examine it?

It turns out this question has been answered — repeatedly, across completely unrelated fields. And the answers converge on something most leaders would rather not hear.

Start with biology. Termite mounds are among the most sophisticated structures in nature — temperature-regulated, ventilated, architecturally precise. No termite understands the plan. There is no plan. Each insect responds to chemical traces left by others in the environment. The intelligence isn't in the termite. It's in the structure of interactions between termites. Ant colonies, immune systems, slime moulds — this pattern, intelligence embedded in the system rather than the agent, shows up across billions of years of natural selection. Not because evolution "arrived at an answer." Because organisms that distributed intelligence into their environment kept surviving, and organisms that didn't, didn't.

That's interesting. But it's biology. You could dismiss it as a metaphor.

Harder to dismiss is what happened in a 1993 economics experiment. Two economists wanted to understand what drives market efficiency. So they did something radical: they replaced human traders with "zero-intelligence" agents — algorithms that made completely random bids and offers. No strategy. No learning. No memory. No skill whatsoever. They expected human traders to dominate.

The result: when these random agents operated inside a specific market structure — buyers and sellers competing on both sides, nobody able to spend more than they had — they produced outcomes that were nearly as efficient as markets run by experienced human traders.

Read that again. Random agents. No intelligence. No training. No development programmes. Just the right structure. And that particular market worked.

The result is stunning — and it's specific. It's a finding about a particular kind of market with particular rules. It doesn't prove that any random agent in any well-designed system produces great outcomes. What it does show is that the right structure can do far more of the heavy lifting than we instinctively credit. If you're a founder obsessing over your next hire while ignoring the rules your team operates under, this should give you pause.

Behaviour is a function of the person and the environment. Kurt Lewin put it as an equation — B = f(P, E) — in the 1930s. Not just the person. Both variables. We've spent a century investing almost exclusively in P while barely touching E.

Picture someone living in Framingham, Massachusetts in the late 1980s. She's not thinking about her weight. She's thinking about her kids, her mortgage, the commute. Her closest friend — someone she has dinner with, someone whose house she knows the layout of — has slowly, quietly, put on weight over the past two years. Nothing dramatic. Just the way portions expanded, the way walks got shorter, the way second helpings became normal. She begins to follow the same gradient. Not because she decided to. Not because she was told to. Because the ambient signals around her shifted — what was offered, what was normal, what went unremarked. Now follow the chain one link further: her friend's weight change was itself shaped by someone she barely knows, a coworker's husband she met twice at parties. He changed. Her friend changed. She changed. She has no idea any of this happened. When Nicholas Christakis and James Fowler analysed three decades of data from the Framingham Heart Study, they found this transmission in the numbers. If your friend becomes obese, your own risk rises 45%. A friend of a friend — someone you may have never met — still raises your risk 10%. The effect runs to three degrees of separation, and it holds for smoking and happiness too. Christakis and Fowler argue the network structure itself is shaping outcomes — that the pattern is too consistent, too directional, and too persistent to be explained by people simply gravitating toward similar others. Others have pushed back, arguing that shared environment and selection effects account for much of what looks like transmission. The debate is real. But even the conservative reading leaves something significant on the table: your best people didn't develop their habits, their standards, or their ambitions in isolation. They were shaped, to a degree none of us has fully reckoned with, by connections they can't even name.

Three fields. Three independent lines of inquiry. One correction: we have been systematically underweighting the environment side of Lewin's equation. Not that individuals don't matter. They do. But the system they operate in matters far more than we've been willing to admit — and we've been pouring resources into the smaller variable while ignoring the larger one.

You're busy. You already know that. What you probably don't know is where all that time actually goes.

Most founders I work with have a massive perception gap between how they think they spend their time and how they actually spend it. The gap is scary. It should be.

This protocol takes about 90 minutes. Do it once a quarter. It will change what you work on more than any strategy session.

Step 1: Capture Your Reality

You have two options here. Pick the one that fits how you operate.

Option A: The Retrospective (90 minutes, one sitting)

Pull up the last two representative weeks of your calendar. Print them or screenshot them. Not your ideal weeks — your real ones. If one of those weeks had something unusual (a conference, a holiday, travel), go back a week further.

Now add in the stuff that doesn't show up on the calendar. The Slack rabbit holes. The "quick" troubleshooting that ate an afternoon. The admin tasks you squeezed between meetings. Write them in the gaps. Be honest — nobody's watching.

Option B: The Daily Log (5 minutes a day for two weeks)

At the end of every workday, before you shut the laptop, spend five minutes writing down everything you actually did that day. Not what was on the calendar — what happened. The meeting that ran over. The 45 minutes you spent debugging a client issue. The "quick call" that turned into a strategy session.

Keep a simple running list. A notes app, a spreadsheet, a piece of paper on your desk — doesn't matter. Date it. List every activity and roughly how long it took.

Do this for two full weeks. Don't skip days. The days you want to skip are usually the ones with the most revealing data.

Option B is slower, but it catches what Option A misses — the stuff that never made it to a calendar in the first place. If you're someone whose real work happens between meetings, this is the better choice.

Step 2: The Energy Filter

Go through every block of time, hour by hour, and ask one question:

Did this energize me, or drain me?

That's it. Binary. No "neutral." If it didn't give you energy, it drained you. Mark each block green (energized) or red (drained). Use highlighters, colored pens, or just write an E or a D next to each one.

When you're done, you'll see a pattern. Probably more red than you expected.

This idea comes from Diana Chapman and the Conscious Leadership Group. Matt Mochary uses it with every CEO he coaches. The brain science behind it is real — Robert Sapolsky's work at Stanford shows you perform measurably better when you're doing things that energize you. Not marginally better. Measurably.

Step 3: The Importance Filter

Now go through the same blocks again. This time you're using the Eisenhower Matrix — four quadrants:

Quadrant 1 — Urgent and Important. The fires that actually matter. A key client escalation. A critical hire decision. A cash flow crisis. These need your attention now.

Quadrant 2 — Important, Not Urgent. Strategy. Culture. Systems. Relationships. The work that compounds over time but never screams for attention. This is where founders should live.

Quadrant 3 — Urgent, Not Important. Most of your inbox. Slack notifications. Meetings that could have been async. Someone else's emergency that landed on your desk. These feel pressing but don't move the needle.

Quadrant 4 — Not Urgent, Not Important. Checking social media. Reorganizing your task list for the third time. Attending a meeting out of guilt. You know what these are.

Label each block: Q1, Q2, Q3, or Q4.

Step 4: The Overlap

Now you have two data points for every hour of your last two weeks — energy and importance. Look for the combinations:

Energizing + Q2 (Important, Not Urgent) — This is your zone of genius. You should be spending 60-80% of your time here. If you're not, everything else in this protocol exists to get you there.

Energizing + Q1 (Urgent and Important) — Good. You're lit up and it matters. Keep these, but work to prevent the urgency through better systems so they move to Q2.

Draining + Q3 (Urgent, Not Important) — This is the silent killer. It feels like real work. It isn't. Delegate it. Automate it. Eliminate it.

Draining + Q1 (Urgent and Important) — Dangerous. You can't ignore it, but it's burning you out. Find someone who's energized by this work and get it to them. Fast.

Anything in Q4 — Delete it. Don't delegate it. Don't optimize it. Kill it.

Step 5: The Perception Gap

Before you looked at your real calendar, you had a story about how you spend your time. Write it down now, from memory — what activities do you do, and roughly what percentage of your time goes to each?

Now compare that to what you actually found.

Here's what this looks like in practice. A SaaS founder I worked with wrote down his perceived time:

Activity | Perceived | Actual |

Product strategy and roadmap | 35% | 8% |

Customer calls (sales and success) | 25% | 18% |

Customer onboarding and training | 10% | 28% |

Team meetings and 1:1s | 15% | 14% |

Admin, email, Slack | 10% | 22% |

Hiring and recruiting | 5% | 10% |

He thought he was spending a third of his time on product strategy. The calendar said less than a tenth. Meanwhile, onboarding — something he kept saying he'd hand off — was eating nearly a third of his week. He didn't even list admin as a real category. It was his second biggest time block.

That's the perception gap. And until you see it in black and white, you'll keep telling yourself the story that you're spending your time on the right things.

The gap between those two lists is where your time is leaking. Every founder I've done this with has been wrong by at least 15-20 percentage points on their most important activity. They think they're spending 40% on strategic work. The calendar says 12%.

Be afraid of that gap. It's telling you something.

Step 6: Re-Allocate

Here's the rule: don't try to add more of the important stuff. You can't stretch time.

Instead, subtract. For every red block, for every Q3 and Q4 activity, ask:

1. Can I eliminate it entirely? Most meetings can be killed. Most reports can be automated. Most recurring tasks exist because nobody questioned them.

2. Can I delegate it? Not "someday when I hire someone." This week. Who on your team could own this? Who could grow into it?

3. Can I automate it? A system, a script, a template, a process — anything that removes you from the loop.

4. Can I batch it? If you can't eliminate it, contain the damage. Email gets one hour. Admin gets one block. Don't let it bleed across your calendar.

Write down the specific action for each item. Not "I should delegate onboarding." Instead: "Ask Catherine to take over onboarding this week. Send her the process doc by Tuesday."

Step 7: The Weekly Check-In

A one-time audit changes nothing. The pattern reasserts itself within a month.

Set a 15-minute weekly check-in with yourself. Friday afternoon works. Review the week:

• What drained me this week that I haven't dealt with yet?

• What Q3/Q4 activity crept back onto my plate?

• What's one thing I can move off my plate before Monday?

One thing. Every week. That's 52 things off your plate in a year.

The Shortcut Version

If 90 minutes feels impossible right now, do the fast version:

1. Open your calendar and to-do list from the last 7 days

2. For each item, answer two questions: Energise or drain? and Which quadrant?

3. Anything that drains you AND sits in Q3 or Q4 — write down who or what takes it from you

4. Do that thing before the end of the week

Then do the full version when you have the space. You'll find the space faster than you think — because the shortcut version just freed some up.

FAQ

What if almost everything on my calendar drains me?

That's data, not a life sentence. It usually means you've drifted into an operator role when you should be in an architect role. The audit shows you where — your job is to start moving one thing off your plate per week. You didn't get here overnight. You won't get out overnight either.

What if something drains me but I'm the only person who can do it?

You're probably wrong about that. The question isn't "can someone do this as well as me?" It's "can someone do this well enough?" If the answer is yes, hand it over and let them grow into it. If it genuinely requires your specific expertise — a key client relationship, a board-level decision — then it stays, but you contain it. Time-box it. Don't let it sprawl.

What about things that energize me but aren't important?

Be honest about these. They're comfort food. The side project that lights you up but doesn't move the business forward. The meeting you love because the people are great but the output is zero. You don't have to kill all of them — you're human. But don't let them crowd out Q2 work. Cap them.

How often should I do the full audit?

Once a quarter. Your calendar drifts constantly. New hires change what you delegate. New clients change what's urgent. A quarterly audit catches the drift before it becomes a landslide. Between audits, the weekly check-in (Step 7) keeps you honest.

Should I do this with my co-founder or team?

Do it alone first. Your honest answers change when someone's watching. Once you've done your own, it's a powerful exercise to do with your operations lead or co-founder — compare notes, spot where you're duplicating effort, find tasks that drain one of you but energize the other. That's where the real delegation opportunities hide.

What if I don't have anyone to delegate to?

Then the audit just told you your next hire. Look at the cluster of red blocks — that's the job description. Most founders hire based on a title they think they need. The audit tells you what you actually need off your plate.

I did the audit. Nothing changed.

You skipped Step 6. Seeing the problem isn't the same as acting on it. Go back and write down one specific action with a name and a date attached. "Ask Sarah to own the weekly client report starting next Monday." Do that one thing. Then do the next one.

The full protocol is free to read, and it’s the version you can actually run on a Sunday.

Six steps: pull the real calendar for the last fortnight, sort every block by energy and impact, add up the percentages, tag the bottom quadrant delegate, eliminate or automate, protect the top quadrant, then rebuild the next two weeks around your best work. Plus what changes if you’re solo, if you’re a co-founder pair, or if you’re past fifty people.

The Time Audit, in the Source Code

Adapted from the Mochary Method ([Time Audit](https://docs.google.com/document/d/1hCxvdAi8aMtJ95are02AZO2fjvkNe0rDGzNhhmbUSqQ), [Energy Audit](https://docs.google.com/document/d/1HmaRdtk8R5GQtMj72Y6XhHTru5SQAiiqDfDP3qy73k4)) with the Eisenhower Matrix overlay. The Mochary Method treats these as separate exercises. This protocol combines them because founders don't have time to do two audits — and the real insight lives in the overlap.

So what do we do when a team underperforms? The same thing we always do. We send someone to a course. We hire a coach. We build a performance improvement plan. We replace the person and hope the next one is better.

The leadership development industry is worth an estimated $366 billion (Training Industry, 2024). That's not a typo. Three hundred and sixty-six billion dollars a year, spent on the same thing: the individual. Make the leader better. Make the manager sharper. Make the salesperson more resilient. The assumption underneath all of it is that the person is the problem, and therefore the person is the solution.

It feels obvious. It feels right. And that's exactly why it's dangerous.

Consider an experiment. Participants watched a quiz show where questioners and answerers were randomly assigned. The questioners wrote their own questions — drawing on whatever they happened to know. The answerers had to guess. Afterwards, observers rated the questioners as significantly more knowledgeable. Even when they knew the roles were assigned by coin flip. Even when the structural advantage was transparent, people couldn't see past the individual.

In 1977, psychologist Lee Ross gave this error a name: the Fundamental Attribution Error. We are hardwired to see individuals as causal agents. When something goes well, we credit the person. When something fails, we blame the person. The situation — the structure, the rules, the environment surrounding the person — is invisible to us. Not because it's hidden, but because our brains aren't built to see it.

That's not a footnote in a psychology textbook. It's the operating assumption of modern management.

"She's the best hire we ever made." Is she? Or is she inside a system that makes most people look great? You've seen the reverse. Someone brilliant in one company, mediocre in the next. Same person. Different system. We call it "culture fit" and move on, as if that explains anything.

The leadership development industry runs on this error at industrial scale. You identify a high-potential leader. You send them to a program — two days, maybe a week, somewhere with good catering and a keynote speaker. They return energised. New vocabulary. New frameworks. A binder full of notes they'll never reopen.

The environment they return to hasn't changed. Same meeting rhythms. Same decision-making bottlenecks. Same incentive structures. Within weeks, the old patterns return.

For much of that industry, the ROI isn't in the outcome. It's in the feeling. The company feels like it invested in its people. The leader feels like they grew. Everyone feels good. Nothing changes.

That's not development. That's theatre.

I'm a coach. My livelihood depends on individual development mattering. That makes me the last person you should trust on this point. I have a financial incentive to tell you that coaching changes lives — and it does, I've seen it. But I should be the first to interrogate that belief, not the last. So here's what I've also seen, over and over: individual growth without system change is a candle in a wind tunnel.

Here's proof that doesn't come from coaching. Kahneman and Tversky identified the planning fallacy in 1979: people consistently underestimate how long projects will take, how much they'll cost, how much can go wrong. The interesting part isn't that people are bad at forecasting. It's that expertise doesn't fix it. Experienced project managers blow deadlines at the same rate as novices. Bent Flyvbjerg's analysis of major infrastructure projects across decades found the same pattern repeating regardless of who was in charge. The most effective correction is structural — comparing your project against the historical distribution of similar projects, a reference class that overrides individual judgment. You don't fix the planning fallacy by getting smarter people. You fix it by building a process that ignores how smart the people think they are.

The same logic holds beyond forecasting. Daniel Kahneman's final major work, Noise (2021), drove the point further. Structured decision environments — clear criteria, independent evaluation, consistent process — categorically outperform unstructured individual judgement. What Kahneman showed is that professional judgement contains far more unwanted variability — noise — than anyone expects. Structure reduces that noise, often dramatically. But the signal still comes from expert judgement. The structure organises the work that individuals do; it doesn't replace it. Decision hygiene beats decision talent. Reliably. Across medicine, law, hiring, strategy — every domain they studied.

Two different findings. One consistent conclusion: structure corrects for what individuals cannot correct in themselves.

I worked with a founder who came back from an intensive program having genuinely rethought how she ran her Monday leadership meeting. New questions. Better listening. A real shift. Two weeks later, I sat in on that meeting. Same room. Same chair layout. Same agenda template. Same team members waiting for her to speak first so they could calibrate their answers. Every cue in the environment told her to revert. She did. Not because she forgot what she'd learned. Because the system she returned to was the same system that produced the problem in the first place.

I caught the reversion. I didn't fix it. The environment won.

The uncomfortable truth is that we've built a $366 billion industry around the smaller variable. We keep upgrading the people and leaving the system untouched. And then we wonder why nothing changes.

You've watched this happen.

A team that was shipping. Fast, clean, decisive. The kind of team where problems surfaced early and got solved before they spread. People talked to each other — not because a standup forced them to, but because the work demanded it and the environment made it easy.

You could hear it in the hallway. Two engineers at a whiteboard. A designer leaning over someone's shoulder. Decisions happening at the edges, where the information lived. You looked at this team and thought: we've cracked it.

Then something shifted. A reorg. A new reporting line. A layer of approval that didn't exist six weeks ago. The team got split across two floors — and that single change did more damage than anyone expected. Decisions that used to happen in a hallway now needed a calendar invite and a slide deck.

Same people. Same skills. Same intentions.

Dramatically worse outcomes.

The hallway went quiet. The whiteboard dried out. You'd walk through the office and feel it — a stillness where collaboration used to be. Not tension. Absence. The sound of a team that stopped reaching for each other.

Then the process language arrived. Silos. Checkpoints. Escalation paths. The people who used to solve problems started routing them instead. Not because they forgot how. Because the system told them to.

Of course it's never this clean. Multiple things break at once. But this piece matters more than we think.

You know the instinct that kicks in. You've felt it. The senior team sits in a room and someone says: "We've lost our edge. We need to upgrade the team." Heads nod. HR starts drafting job specs. The story writes itself — the talent degraded, so you fix the talent.

But nobody left. Nobody got worse. The same people who built the thing that worked are now building something that doesn't. And nobody in the room is asking the obvious question.

What if the intelligence lived in how those people operated together — and you just broke the conditions that made it possible?

The Problem You read Radical Candor. You read High Output Management. You know that as a founder, you are supposed to give “clear, direct feedback.”

So, you sit your Head of Marketing down. You use the scripts. You say the right words. You are “hard on the problem, soft on the person.”

And yet... they shut down. They get defensive. They gloss over.

You walk away thinking, “Why are they so fragile?”

The Physics of Feedback They aren’t fragile. You just ignored the physics of the relationship.

Think of your relationship with your direct report like a guitar. Think of the feedback you want to give (the critique, the correction, the hard truth) as a complex song—let’s say, Stairway to Heaven.

Most founders obsess over the Song. They practice the notes. They focus on their finger placement (the words they use). They try to play with passion.

But they forget to check if the guitar is Tuned.

The Tuning Principle If a guitar is out of tune, it doesn’t matter if you are Jimmy Page. It doesn’t matter if you hit every note perfectly. The sound coming out will be noise.

In a startup:

• Tuning = Psychological Safety (Trust Capital).

• Playing = Critical Feedback.

If you try to play a “High Tension” song (critical feedback) on a “Loose String” (low trust), the string doesn’t make music. It snaps.

The Protocol: Tune First, Play Second Before you walk into your next 1:1 to deliver bad news, stop rehearsing your script. Instead, audit the instrument.

Ask yourself: Is this string tuned? Do I have enough “Marble Jar” capital with this person to play this song?

The 3 Stages of Tuning

1. The Audit (Check the Tension) Can you answer the “5 Questions” about this person? (Do you know their partner’s name? Do you know their 2-year goal?). If not, the string is loose. Do not play the solo yet.

2. The Calibration (Turn the Peg) If the trust is low, spend the next 3 interactions doing nothing but listening.

• Ask: “What’s the biggest blocker you have right now that I’m not seeing?”

• Action: Remove the blocker.

• Result: You just tightened the string. You built credit.

3. The Performance (Play the Song) Once the trust is established, you can play the hardest, fastest, most complex feedback possible. They won’t snap. They will resonate.

The “Source Code” If you don’t know how to “Tune” the instrument, you need to use the Marble Jar Protocol. I broke down exactly how to build this trust in my previous post.

Summary Stop obsessing over your delivery. Start obsessing over the reception. You can’t play a masterpiece on a broken instrument.

In October 1806, the Prussian army—the most feared military machine in Europe, the disciplined heirs of Frederick the Great—marched out to meet Napoleon at Jena-Auerstedt. They were, by every standard metric, perfect. Their drills were precise. Their uniforms were immaculate. Their chain of command was absolute.

And they were annihilated.

It wasn’t just a defeat; it was a systemic collapse. The Prussian generals, waiting for orders from a centralized command that couldn’t keep pace with the chaos of battle, froze. Napoleon, meanwhile, didn’t just have a better army; he had a different kind of army. His corps commanders could improvise. They could see a gap and take it without asking for permission.

The Prussians had designed a system for robustness—rigid, strong, and unbreaking until the moment it shattered. Napoleon had designed a system for anti-fragility—one that actually gained speed from the chaos of the fight.

I’ve been thinking about the Prussians lately because I spend my days studying the physics of the modern high-growth startup. In my work developing [The Open Source Code](Link to: Source Code Library)—my library of frameworks for founders—I’ve found that every successful company eventually faces its own “Jena Moment.”

The Growth Paradox

It usually happens around employee number 50.

Up until that point, growth feels linear: you add a person, you get more output. But then, you cross an invisible threshold. You add a new engineer, and shipping speed slows down. You hire a VP of Operations, and suddenly everyone is in more meetings.

I call this the “Death Cross.” It is the moment where your organization’s internal friction—managing people, coordinating schedules, writing reports—begins to exceed its external velocity.

The Scaling Productivity Guide

The data I’ve collected is counter-intuitive. We assume that bureaucracy is what happens when organizations get lazy. But the reality is the opposite: bureaucracy is what happens when smart, well-meaning people try to fix chaos with rules.

We add a process to prevent a mistake. We add a manager to coordinate the process. We add a report to update the manager. We are trying to be robust, just like the Prussians. But in doing so, we unintentionally design a system that is allergic to speed.

So, how do you avoid the fate of the Prussian army?

The Strategy of “Via Negativa”

The answer lies in a concept that Nassim Taleb calls Via Negativa—improvement by subtraction.

Most of the founders I coach are additive problem solvers. When we see a problem, our instinct is to add something: a new role, a new tool, a new meeting. But the most effective scaling organizations are ruthlessly subtractive.

THE ANTIFRAGILE MANIFESTO.

Consider the case of Linear, the software unicorn. They are valued at over a billion dollars, yet they operate with a tiny headcount and, famously, zero product managers.

This seems impossible. Who writes the tickets? Who manages the backlog?

The answer is: nobody. They subtracted the layer of translation between the problem and the code. Engineers speak directly to designers. They work in “cycles,” not sprints, and then they have mandatory “cooldowns” to recover. By subtracting the “management” layer, they increased the “execution” layer.

They didn’t build a better process. They deleted the need for the process.

The Warning: The “DOGE” Trap

However, there is a dangerous way to misinterpret this philosophy.

When we talk about subtraction and efficiency, it is easy to look at Elon Musk’s approach—slashing 80% of Twitter’s staff or the aggressive mandates of the “Department of Government Efficiency” (DOGE)—and think, “Yes, that’s the goal.”

It is not.

What Musk engages in is often a chainsaw massacre disguised as surgery. While it effectively reduces cost, it frequently destroys capacity. It creates a culture of fear, and fear is the enemy of anti-fragility. When people are terrified, they don’t improvise; they freeze. They become Prussian generals waiting for permission.

In The Open Source Code, we distinguish between “Anorexia” (starving the system) and “Leanness” (removing the fat). To avoid the Musk trap, you must follow two critical guidelines:

1. Respect Chesterton’s Fence: There is a famous parable about a fence in the middle of a road. The reckless reformer says, “I don’t see the use of this; let’s clear it away.” The wise reformer says, “If you don’t see the use of it, I certainly won’t let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it.” Never subtract a process until you understand the value it was built to protect.

   The Values Discovery Protocol

2. Subtract Friction, Not Muscle: The goal is not to have fewer people doing more work; it is to have the same people doing less “Ghost Work”—the work that looks like work but creates no value.

The Scream Test

This brings me to the tool we use to distinguish between the two: The Scream Test.

It is a technique for detecting that “Ghost Work”—reports that nobody reads, servers that run for no reason, recurring meetings that have lost their purpose.

The test is simple: you stop doing it. You turn off the server. You stop sending the weekly status report. You delete the recurring meeting.

And then you wait.

If nobody screams—if nobody complains—then that work was waste. It was friction masquerading as value. If they do scream, you turn it back on immediately.

Unlike a layoff, the Scream Test is reversible. It is “Organizational Chaos Engineering.” Just as Netflix randomly shuts down servers to ensure their system can survive a crash, we intentionally break our own processes to see which ones are actually load-bearing

Why Simplicity Scales

The New Prussianism

After their defeat in 1806, the Prussians didn’t just buy better muskets. They rewrote their operating system.

They introduced a concept called Auftragstaktik, or Mission Command. The idea was radical: the General defines the intent (the “what” and “why”) but is forbidden from dictating the method (the “how”).

This is the antidote to the Death Cross.

In a scaling startup, you can no longer make every decision. The “knowledge gap” is too wide. You have to push decision-making authority to the “edge,” to the people who are actually talking to the customers and writing the code.

But you can’t just tell people “do whatever you want.” That’s anarchy. You have to create a culture of “Thinking Obedience.” You have to build a system where people are rewarded not for following the plan, but for achieving the outcome—even if it means breaking the plan.

The 90-Day Challenge

This is why I often start my engagements with a 90-day roadmap designed to shock a company out of its inertia.

It starts with a “Ritual Purge.” We audit every meeting on your calendar. If a meeting doesn’t have a clear decision output, it dies. We look at your projects and kill the “zombies”—the initiatives that are walking around but not actually alive.

It feels dangerous. It feels like you are losing control. But that is the paradox I want to leave you with.

To gain speed, you have to let go of the handlebars. You have to trust the physics of the system you’ve built. You have to stop trying to be the perfect Prussian General, and start building an army that can think for itself.

Need to install this operating system?

All the frameworks mentioned here—from the Ritual Purge to The Values Discovery Protocol—are available in

The open source code

The Executive Summary

Estimated Reading Time: Summary (2 min) | Full Article (8 min)

The Problem: You spend hours at events, on LinkedIn, and in DMs. Your contact list grows. Your actual leverage does not. When you need a real favour, a real introduction, or a real partner, the room goes quiet.

The Misconception: Most people believe that networking—collecting connections, being “visible,” and staying “top of mind”—is how you build influence. Weak ties provide optionality — many low-cost bets where one Black Swan connection could change everything. In a fat-tailed world, that matters. But most people treat networking as the only strategy, building breadth without depth. When crisis hits, these networks are Fragile. Research on 20 million LinkedIn profiles shows weak ties create opportunities, but strong ties are individually more valuable when stress arrives.

The Solution: You need both. Keep your weak-tie network for optionality. But build a small number of Robust alliances with skin in the game — relationships where both parties bear downside risk if the other fails. Not friendship alone. Structural interdependence. When your success depends on theirs and theirs depends on yours, the relationship holds under pressure. The difference is not semantic. It is structural.

For those with more time, the full analysis follows below.

The Inklings: Friendship and Shared Purpose

In 1930s Oxford, J.R.R. Tolkien and C.S. Lewis were not hunting for clients. They were friends who shared a cause: they believed in the power of story to carry truth, and they were both trying to write the kind of work that could do that. They met weekly with a small group—the Inklings—to read drafts aloud, tear them apart, and push each other to finish. Lewis is the one who kept demanding Tolkien stop revising and actually complete The Lord of the Rings. Tolkien’s depth and myth-making sharpened Lewis’s own fiction. Neither was “networking.” They were adding value first: showing up for each other’s work, offering critique and encouragement, with no contract and no expectation of payback. The alliance was built on mutual values—faith, craft, the belief that certain stories matter—and aligned interests: they wanted to make something meaningful, and they did it with each other. When things were hard, they showed up. That is the model. Alliances like that are Robust because they have skin in the game — Tolkien’s reputation depended on Lewis’s honest feedback; Lewis’s time investment was wasted if Tolkien never published. Both had something to lose if the other failed. This is not friendship alone; it is structural interdependence. The best alliances are the people you’d be there for when things go wrong—and who’d be there for you—because you care about the same things and you’ve already been building something together.

Fragile Networks, Optionality, and Robust Alliances

Modern “networking” is not useless — it provides optionality. Weak ties are many low-cost exposures with limited downside and potentially unlimited upside. In a fat-tailed world, the 500th LinkedIn connection could be worth more than all 15 close alliances combined. That is how power laws work. Research analyzing 20 million LinkedIn profiles over five years confirms this: weak ties drive volume of opportunities. That volume includes outliers — the Black Swan connection you cannot predict but that could change everything. Optionality matters. But most people treat networking as the only strategy, building breadth without depth. Your network is Fragile. Under stress—a layoff, a pivot, a crisis—it thins out fast. During COVID-19, German SMEs with strong relational investments in partnerships survived better than those with purely transactional arrangements. Why? Because there is no shared downside risk. No structural interdependence. You have breadth. You do not have depth.

Alliances are different. They are Robust — they withstand stress because they have skin in the game. Shared downside risk. When your success depends on theirs and theirs depends on yours, the relationship holds when things go wrong. Roy Keane and Teddy Sheringham did not speak to each other for three and a half years at Manchester United, yet they played through the 1999 Treble together. They were not friends. But if the team lost, both lost. That is skin in the game. Steve Jobs and Steve Wozniak built Apple the same way: neither could have done it alone. Mutual dependency, not just mutual values. The Ford-ABB partnership moved beyond adversarial supplier practices to a mutual value creation model — both parties had something to lose if the other failed. Taleb’s framework clarifies this: weak ties provide optionality — many cheap bets where you cannot predict which will pay off, but one could change everything. Alliances provide robustness — deep relationships with skin in the game that hold when things go wrong. These are not substitutes. You need both. The error is treating networking as sufficient, or abandoning optionality entirely for concentration risk.

The Alliance Audit

You cannot fix this by “networking better.” You need a protocol. Use this one.

Step 0 — Subtract First. Before adding anything, subtract. Via negativa: remove what harms you. List the 10-15 relationships that drain your time, misalign with your values, or create obligations without reciprocity. Stop attending their events. Stop responding to their requests. Stop investing energy. Subtraction is more powerful than addition — these toxic ties are preventing real alliances from forming.

Step 1 — Inventory. List the people you currently treat as “key relationships”—advisors, peers, potential partners, past collaborators. Not your whole Rolodex. The 15–25 you would actually call when something serious is on the line. Research on effective networks suggests 15–25 aligns with Dunbar’s number—the cognitive limit of ~150 stable relationships humans can maintain. Relationships organize in nested layers: 5 most intimate, 15 close friends, 50 friends, 150 total stable relationships. The 15–25 range sits between your close friends and broader friend circle—your meaningful inner circle of alliances. The strongest alliances have complementary resources — each person brings something the other lacks. Steve Jobs and Steve Wozniak built Apple this way: Wozniak was the brilliant engineer who designed the computers; Jobs was the visionary who saw the market and knew how to sell. Wozniak called it “an unbelievably fortunate partnership.” Neither could have done it alone. The Airbnb founders followed the same model — two designers from RISD paired with an engineer who could build the platform. Design vision plus technical execution, held together by a shared mission to reimagine hospitality. When you look at your 15–25, ask not just do we share values? but what do they bring that I do not — and what do I bring that they need?

Step 2 — The Skin in the Game Test. For each person, ask two questions:

First: Do we have skin in the game — shared downside risk where we both lose if the other fails? This is structural. Are our fates linked? Examples: Co-founders — if company fails, both lose. Keane/Sheringham — if team loses, both lose (this is why they performed despite hatred). Jobs/Wozniak — neither could build Apple alone; mutual dependency.

Second: Do we have soul in the game — do we care deeply enough about the same cause that our identity is at stake? This is values-based commitment. Martin Luther King’s civil rights volunteers put their lives on the line for the cause. Nike’s “Ekins” got swoosh tattoos on their bodies — cult-like devotion to the brand’s mission. When people unite around values they’d sacrifice for, the bond runs deeper than contract or career.

The strongest alliances have both: shared material risk and shared values commitment. Mark each relationship: “Skin + Soul,” “Skin Only,” “Soul Only,” or “Neither.” Those with neither move to periphery. Those with one or both are your true alliances.

Step 3 — Reallocate. Everyone marked “Neither” moves to the periphery. You do not delete them. You stop over-investing. Your calendar, your energy, and your follow-ups shift to those with “Skin + Soul,” “Skin Only,” or “Soul Only.” For “Skin Only” alliances, ask: What shared cause could we unite around? For “Soul Only” alliances, ask: What projects can we work on where both parties bear downside risk? For “Skin + Soul” alliances — those are your core. Protect them. This audit is a starting point, not a system. Human relationships are nonlinear and path-dependent. The person marked “Neither” today may become your most important ally after a shared crisis next month. Use this as a heuristic, not an algorithm. Real robustness emerges from repeated interactions with skin in the game and soul in the game — not from yearly spreadsheets.

Tolkien and Lewis built their alliance with skin in the game: their reputations and time were mutually at risk. Companies like Ford-ABB and HP-Cisco did the same — mutual dependency, not just mutual values. Research across 93,000+ firms confirms that alliances with complementary resources and shared downside risk outperform transactional networks.

You do not need to abandon your weak-tie network — it provides optionality in a fat-tailed world. But stop confusing a long contact list with real leverage. Run the Alliance Audit. Start with via negativa: identify the 10-15 relationships draining your energy and stop investing in them. Then ask: of the people left, who has skin in the game with you? If the number is small, that is clarity. Build from there — by finding projects where both parties bear downside risk, where failure for one means failure for both.

FAQ

Time-poor / optionality vs overload – “How do I keep optionality without spreading myself thinner?” Reallocate via Step 0; optionality = low-touch; depth comes from shared stakes, not volume.

No co-founder – “Can I still have skin in the game?” Yes: advisors, peer founders, strategic partners; defined by shared downside, not legal structure.

Audit as another spreadsheet – “Won’t this become a spreadsheet I ignore?” Framed as a heuristic and reallocate step; use when something material changes, not rigidly once a year.

Mostly “Skin Only” or “Soul Only” – “How do I deepen them?” Skin Only → add shared cause; Soul Only → add structure (project/commitment with real downside).

Board and investors – “Where do they fit?” Only count as alliances if they pass the skin-in-the-game test; otherwise keep them in a different bucket.

But the team member says “No.” Or they get defensive. Or they “Quiet Quit.”

You think: “They are lazy.” You are wrong.

They aren’t lazy. They are unsafe.

They are overwhelmed, but they don’t feel brave enough to tell you. They fear that if they admit vulnerability, you will see them as incompetent and remove their opportunities.

The Solution: The Marble Jar Trust isn’t built in the big “Town Hall” speeches. Trust is capital. As Brené Brown explains, trust is built in micro-moments. It is built like a “Marble Jar”.

Every time you remember their partner’s name, you put a marble in. Every time you ask about their grandmother’s surgery, you put a marble in. Every time you “scoot over” to make space for them at the table, you put a marble in.

When the jar is full, you have enough Trust Capital to have difficult conversations. When the jar is empty, every request feels like a threat.

The Trust Audit Do not assume your jar is full because you pay them well. Pass this audit. Can you answer these 4 questions about your direct reports right now?

1. The Goals: Do you know their specific career goals for the next 2 years? (Do they want to be a founder one day?).

2. The Tribe: Do you know the name of their partner or their children?.

3. The Context: Do you know the biggest stressor in their life outside of work right now?.

4. The Soul: Do you know who they are at their deepest level? (Are they religious? Are they a kite-surfer? What drives them?).

The Outcome If you scored 0/5, you don’t have a team. You have staff. Start filling the jar today. The ROI on trust is higher than any software you will ever buy.

I only want to be sending stuff to you that you find valuable. If you’re not interested in this, please feel free to unsubscribe using the link below

Unsubscribe

1. The Core Philosophy: Trust is Investment Capital

Most leaders view trust as a “soft” metric—a nice-to-have byproduct of a happy culture.

This is false. In an Anti-Fragile system, Trust is Capital.

You do not hoard capital; you accumulate it so you can Invest it.

• The Deposit: A micro-moment of connection (A marble in).

• The Investment: A hard conversation, a sudden deadline, or a critical feedback session (A marble out).

If you try to make an investment when the jar is empty, the transaction fails. The employee shuts down, goes to HR, or quits. You are writing checks that your culture cannot cash.

2. The Diagnostic: The “Bandwidth” Bluff

The Scenario:

Matt (a Senior Manager) asks a team member to take on a strategic market research project.

The answer is an immediate: “No. I don’t have the bandwidth.”

Matt knows this is false. He knows the workload. He knows this project is within scope. He suspects the team member is “quiet quitting” or lazy.

The team member suspects Matt is trying to exploit them. They imply that asking for more work is unreasonable.

The Diagnosis:

This is not a capacity issue. This is a Safety Issue.

The team member isn’t actually busy; they are defensive. They are afraid to say: “I don’t know how to do this efficiently,” or “I’m scared I’ll fail.”

Because Matt hasn’t filled the Marble Jar, the team member cannot be vulnerable. They default to the safest corporate lie: “I’m too busy.”

3. The Methodology: What is a “Marble”?

We often assume trust is built in the big moments—the town hall speech, the promotion, the bonus.

Research by Brené Brown proves the opposite. Trust is built in the granular, invisible moments.

Brown explains trust using the metaphor of a Marble Jar, inspired by her daughter Ellen’s teacher. The class earned marbles for good behavior; when the jar was full, they got a party.

When Brown asked her daughter how her friends earned marbles (trust), Ellen didn’t describe grand gestures. She described micro-moments:

• The Half-Heinie Seat: “If there’s not a seat for me at the lunch cafeteria, she’ll scoot over and give me half a heinie seat.”

• The Context: “Hannah looked over, and she saw Oma and Opa [my grandparents]... and she said, ‘Look, your Oma and Opa are here.’... It was so nice to me that she remembered their names.”

The Insight:

Brown went back to the data and confirmed it: “Trust is built in very small moments.”

4. The Mechanics: Building the Asset Class

For a leader like Matt, “filling the jar” isn’t about being best friends. It is about signaling Attention and Care.

What a Marble looks like in Business:

• The Dentist: Remembering their kid had their first appointment this morning and asking, “How did it go?”

• The Slack: Giving them Friday afternoon off because you know the nanny is sick, without them having to beg.

• The Connection: Asking “How was the weekend?” and actually listening to the answer, rather than looking at your phone.

These are not “niceties.” These are Deposits.

5. The ROI: Buying Bravery

Here is the critical shift. When you have filled the jar, you don’t just “spend” the trust; you trade it for something more valuable.

When you make a withdrawal, what you are buying is their Bravery.

Let’s replay Matt’s scenario, assuming he had a full Marble Jar.

The Investment:

Matt asks for the project. Because the trust capital exists, he can push past the initial “No.”

The Yield (Bravery):

The Team Member feels safe enough to drop the shield. They admit:

“Matt, honestly, I’m drowning. It takes me two days just to do the pitch deck, so I can’t add this on.”

Matt has just successfully purchased the truth. The employee was brave enough to admit a weakness (inefficiency) rather than hiding behind a bluff (bandwidth).

6. The Multiplier: The 10x Return

This is the “Sliding Door” moment. Matt has withdrawn trust to get the truth. How he responds now determines if the account goes to zero or compounds 10x.

Scenario A: The Crash (Smashing the Jar)

Matt says: “Well, you’re just taking too long. You should know how to do this by now.”

• Result: He punished their vulnerability. The jar is smashed. They will never tell the truth again.

Scenario B: The Compound (The 10x Investment)

Matt says: “Wait, two days? That should take three hours. Let me sit down with you right now and show you the framework I use to build these fast.”

• Result: He rewarded their bravery with coaching.

The Outcome:

By meeting their vulnerability with support, Matt has exponentially increased the trust level.

• The employee feels seen, not judged.

• The skill gap is closed (Anti-Fragility).

• The next time Matt asks for the impossible, they will say “Yes.”

7. The Execution Standards: Connection Before Content

We do not need complex scheduling hacks. We simply need to prioritize the human over the task.

Standard A: The “Connection First” Meeting Rule Most leaders rush into the agenda to “save time.” This is a mistake.

• The Rule: Start every official meeting with 5–10 minutes of genuine human connection.

• The Logic: You are tuning the frequency of the room. By spending 5 minutes on “marbles” (How is the family? How was the weekend?), you lower the threat response of the room.

• The Result: When you pivot to the hard work, the team is neurologically regulated and ready to engage, rather than defensive and cold.

Standard B: The “Slow Walk” Rule When you move through the office (or the Zoom calls), stop rushing.

• The Anti-Fragile Mindset: “Never run for a train.”. If you are rushing to your next task, looking at your phone, and ignoring your team, you signal anxiety and self-absorption.

• The Practice: Walk slowly. Lift your head. Make eye contact.

• The Action: If you see someone, stop. Spend two minutes filling their jar. The email can wait; the relationship cannot.

8. The Meta-Protocol: Empathy is the Engine

Let’s be honest: You don’t really need a protocol for this.

You don’t need a checklist to be a decent human being. You simply need to cultivate deep empathy and genuine care for the people you are in the trenches with.

• Protocols are just training wheels for character.

• The goal is not to “hack” trust; the goal is to actually give a damn.

The Ultimate Test: The Exit The highest ROI of the Marble Jar is not seen when you hire someone; it is seen when you fire them.

One day, you may have to let a team member go because they aren’t the right fit. This is the ultimate “Withdrawal” of capital.

• Empty Jar: If you fire them without trust, they leave bitter, they sue, and they poison your reputation in the market.

• Full Jar: If you have built deep empathy, you can have a hard conversation with dignity. You can say, “I care about you, but this role isn’t right.”

The Consequence: If you execute this with love and a full jar, that person will leave and tell the world what a great experience it was working with you. They become Alumni, not enemies.

Summary: Fill the jar. Not because it’s a tactic, but because it’s the standard of a leader who leads people, not just spreadsheets.

This post is the idea. The full protocol is how you run it, and it’s free to read.

It has the bandwidth bluff diagnostic, the connection first meeting rule, the slow walk, and the exit test for knowing whether the jar was ever full. Plus what changes when the team is remote, when it’s contractors, or when you’re too big to make the deposits yourself.

The Micro-Trust Protocol, in the Source Code

I have a secret.

If you know me, you know I am a massive advocate for morning routines. I talk about intention, about setting the tone, about owning your day before the world owns you.

But since Christmas, I have completely fallen off the wagon.

The discipline that usually anchors me has slipped. Lately, when I wake up, the room is quiet, the light is soft, and instead of reaching for my journal, I reach for my phone. Just to check the time. Just to check the weather.

And instantly, I am pulled into the vortex.

The other day, I hit rock bottom with it. I opened my phone and saw the headlines coming out of America—the chaos, the outrage, the endless cycle of “breaking news.” I didn’t mean to stay there. I just wanted to know what was happening.

But I got gripped. I hunted for clarity. I scrolled for a resolution. I looked for someone, anyone, to make sense of the noise.

When I finally looked up, I had lost three hours.

The day was in full swing, and I hadn’t done a single thing to move my life forward. I hadn’t spent time with my family. I hadn’t connected with my community. I hadn’t done anything to advance my actual mission in life.

I felt hollow. And worse, I felt helpless.

Yes, what is happening in the world is important. But paying attention to the outrage machine for three hours didn’t fix the world. It just broke my morning. It created a paralysis that drained the energy I needed to do the work that is within my reach.

The Ancient Mind in a Modern Cage

Why do we do this? Why does a rational person—someone who knows the value of a morning routine—spend the most valuable hours of the day paralyzed by events they cannot change?

The answer isn’t a lack of discipline. It is a matter of biology.

In evolutionary terms, we are still hunter-gatherers. Our hardware hasn’t been updated in 100,000 years. We are designed to be trackers. When you are tracking an animal through the woods, your survival depends on noticing disruptions in the environment. A broken twig, a sudden silence, a flash of movement—these are anomalies. They signal danger.

Psychologists call this the Negativity Bias. Research shows that “bad is stronger than good.” To a hunter-gatherer, missing a patch of berries is a mistake; missing a predator is death. Therefore, our brains are evolved to prioritize the negative, the threatening, and the outrageous.

The problem is that we no longer live in the woods. We live in an information environment that has been engineered to hack this specific vulnerability. The news feed is not a forest; it is a landscape of manufactured predators. When you wake up and look at your phone, you are engaging the amygdala—the fear center of the brain—before you have engaged the prefrontal cortex, the seat of reason.

This brings us to a piece of biology known as the Reticular Activating System (RAS).

The RAS is a bundle of nerves at our brainstem that filters out unnecessary information so the important stuff gets through. It is the reason you can hear your name mentioned in a noisy party, or why, after you buy a red car, you suddenly see red cars everywhere. The RAS is the “tracker” mechanism of the brain. It asks: What are we hunting for today?

When we doomscroll, we inadvertently program the RAS to hunt for threats. We tell our brain: “The world is dangerous; find me proof.” And because the RAS is an obedient servant, it complies. It filters out the beauty, the opportunity, and the solutions, and highlights only the despair.

We become hopeless not because the world is entirely broken, but because we have lost the ability to see anything else.

The Return to the Mission

So, how do we reset the tracker?

Research into Self-Affirmation Theory, pioneered by Claude Steele, offers a solution. Studies have shown that when individuals spend just a few minutes affirming their core values, their cortisol levels (the stress hormone) drop, and their problem-solving abilities increase. Priming the mind with a “mission” doesn’t just make you feel good; it physically shifts neural activity away from the reactive “fight or flight” centers and back toward the executive functions of the brain.

This is why I am back on track with my routine. It is why, despite the pull of the digital vortex, I must fight to return to my ritual: reading my mission, my vision, and my values every single day.

I have a mission: To build cultures where people thrive, to birth solutions to problems that move us towards a better future.

When I woke up the other morning and lost three hours to the news, I was tracking the wrong beast.

By reading my vision, I am giving my Reticular Activating System a new set of coordinates. I am telling my brain: Do not look for lions. Look for opportunities to build.

When I lock into my mission, the chaos of the world doesn’t disappear. The reality remains harsh. But my role in it changes. I stop being a passive victim of the outrage cycle and become an active participant in my own life. I move towards the future I want to see.

I become the man I want to be—not because the woods are safe, but because I finally remember what I am tracking.

1. The Executive Summary

Estimated Reading Time: Summary (2 min) | Full Article (6 min)

• The Problem: High-stakes environments (critical investor pitches, championship finals, boardrooms) trigger a biological “survival mode” in the brain. This forces you into rigid, analytical thinking exactly when you need fluid, creative execution.

• The Trap: Most leaders view rituals (like Nadal’s water bottles or Steve Jobs’ uniform) as eccentricities or superstitions. They are neither.

• The Solution: These are acts of Cognitive Tuning. They are manual overrides for the brain’s “feelings-as-information” system, shifting your neural state from “Danger/Analyze” to “Safe/Flow.”

• The Outcome: By engineering a “Benign Micro-Environment,” you can decouple your internal state from external chaos.

For those with more time, the full analysis follows below.

The Geometry of the Gladiator

Imagine the clay courts of Roland Garros. Rafael Nadal stands at the baseline. The stakes are in the millions; the historical legacy is incalculable.

Before the first serve, the ritual begins. It is rigid, neurotic, and absolute.

He places two water bottles at his feet. One water, one energy drink. He sips one, then the other. He places them back on the ground, aligning them diagonally, labels facing the court, creating a perfect vector toward the baseline. He adjusts his socks to equal height. A tug of the shorts, a touch of the shoulders, a brush of the nose.

Observers call it OCD. Commentators call it gamesmanship.

Nadal calls it something else: “It’s a way of placing myself in a match,” he says, “ordering my surroundings to match the order I seek in my head.”

Shift scenes to Bangor, Maine. Stephen King sits down to write the nightmares that captivate the world. He does not wait for inspiration. He swallows a vitamin. He blasts Metallica or AC/DC—a sonic wall of hard rock. He sits in a specific chair, papers arranged in a specific geometry.

These are not superstitions. These are not quirks.

Nadal and King are not merely creatures of habit—they are Architects of State. They are engaged in the precise neurological engineering of Cognitive Tuning.

The Thermostat of Survival

Here is the flaw in modern business thinking: We believe we are computers.

We think: Input Data → Process Logic → Output Decision.

But the research of psychologist Norbert Schwarz proves we are not calculators; we are biological thermostats. We constantly sample the emotional temperature of our environment to decide how to think, not just what to think.

The brain has two primary gears based on this temperature:

1. The Problematic Signal (Bad Mood/Anxiety): Evolutionarily, this means “Threat.” The brain shifts into Systematic Processing (Bottom-Up). You become vigilant, analytical, and risk-averse. Great for auditing a balance sheet; fatal for playing tennis or navigating a market crash.

2. The Benign Signal (Good Mood/Safety): Evolutionarily, this means “Safe.” The brain shifts into Heuristic Processing (Top-Down). You rely on intuition, muscle memory, and “flow.”

The Performance Paradox This is where the fragile leader fails. When you walk into a boardroom crisis or a Critical negotiation, your environment screams “Problematic!” Your brain naturally shifts into Systematic Processing—fear, rigidity, paralysis by analysis.

But to perform at you best, you need Heuristic Processing—the ability to see the big picture, take an asymmetric risk, and act without hesitation.

The environment signals “Freeze,” but success demands “Flow.” This is the neurological definition of choking.

Nadal’s bottles and King’s Metallica are not magic. They are Manual Overrides. By ordering the immediate physical environment (the bottles), Nadal signals to his ancestral brain that order exists. He manufactures a “Benign Micro-Environment” in the middle of a chaotic war zone. He hacks the thermostat.

The Cognitive Tuning Protocol

You do not need to line up water bottles, but you do need a system to gate out the noise and protect the signal. Use this three-step protocol to build your own “Benign Micro-Environment” before high-stakes execution.

1. The Bounding Box (Limit the Input) You cannot control your team or the competition, but you must control the immediate geography.

• The Action: Define a physical or temporal boundary.

• The Example: Paul Tudor Jones, the legendary macro trader, used a “Power Room” where no news was allowed—only price action.

• The Application: Before deep work or a negotiation, create a “clean desk” policy or a specific location where phones and WiFi are banned. If the environment is chaotic, the brain stays in “Threat” mode.

2. The Benign Signal (The Safety Cue) Introduce a familiar, orderly stimulus to downregulate the threat response.

• The Action: A repetitive, low-friction task or sensory input that signals “Normalcy.”

• The Example: Stephen King’s vitamin pill and specific paper arrangement. Nadal’s sock adjustment.

• The Application: Develop a pre-game sequence. A specific playlist (Auditory Prime), a specific breathing pattern (Physiological Prime), or a review of a “Core Principles” document (Semantic Prime) rather than the news.

3. The Anchor (The Trigger) Borrowing from NLP, you need a physical trigger to lock the state in.

• The Action: A distinct physical gesture or sensation that marks the transition from “Analysis” to “Execution.”

• The Example: Tiger Woods utilized the sound of Velcro-ing his glove. That ripping sound was the switch from the “Thinking Box” (Analysis) to the “Play Box” (Execution).

• The Application: Use a somatic trigger—putting on a specific watch, drinking a specific coffee, or a physical phrase you say internally—to mark the threshold. When this happens, we go.
  
  

The “Real World” creates noise—anxiety, fear, distraction. This noise consumes your cognitive bandwidth, forcing you into a defensive crouch.

If you do not tune your instrument, the environment will tune it for you. And the environment is almost always playing a song of chaos.

Be the architect, not the victim. Line up your bottles.

Frequently Asked Questions (The Architect’s Dilemma)

1. “We just raised Series A and the board wants velocity. I don’t have time for rituals. Won’t this slow us down?” This is the “Efficiency Trap.” You don’t have time not to tune. A Founder in a “problematic” cognitive state makes fearful, rigid decisions (hiring the “safe” candidate, avoiding the hard pivot) that cost months to fix. The 10 minutes spent tuning buys you the cognitive clarity to execute the next 10 hours without error. Speed is useless if you are running in the wrong direction.

2. “I’m an engineer, not an athlete. Is ‘Cognitive Tuning’ just a fancy word for mindfulness?” Mindfulness is about accepting the present moment; Cognitive Tuning is about hacking it. It is an engineering protocol for your biological operating system. Just as you wouldn’t deploy code without a staging environment, you shouldn’t deploy a high-stakes decision without a “Benign Micro-Environment.” It is not spiritual; it is mechanical.

3. “My team has grown past 30 people, and the culture is ‘drifting.’ Can I scale this beyond myself?” Absolutely. The “Drift” happens when the collective nervous system of the company becomes “Problematic” (anxious, political, reactive). You can engineer organizational rituals—like “No Meeting Wednesdays” (Bounding Box) or specific “All Hands” formats (Benign Signal)—that tune the group mind just as effectively as the individual mind.

4. “I’m looking for a strategist, not a therapist. Is this coaching?” Therapy explores why you feel a certain way (historical analysis). Strategic Performance explores how to execute despite how you feel (systems design). We are not here to validate your feelings; we are here to prevent your feelings from distorting your data processing. We are building a “Sparring Partner” relationship, not a supportive one.

5. “How do I measure the ROI of a ‘Benign Signal’?” You measure it in “Unforced Errors Avoided.” In tennis, the player with the fewest unforced errors usually wins. in Startups, it is the same. The ROI comes from the bad hire you didn’t make because you weren’t operating from a place of scarcity, or the negotiation leverage you didn’t lose because you weren’t projecting anxiety.

References

1. King, S. (2000). On Writing: A Memoir of the Craft. Scribner.

2. Nadal, R., & Carlin, J. (2011). Rafa: My Story. Hyperion.

3. Schwarz, N., & Clore, G. L. (1983). Mood, misattribution, and judgments of well-being. Journal of Personality and Social Psychology.

4. Schwarz, N. (2002). Situated cognition and the wisdom in feelings. The wisdom in feelings: Psychological processes in emotional intelligence.

5. Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.

6. Schwager, J. D. (1989). Market Wizards. HarperCollins.

7. Douglas, M. (2000). Trading in the Zone. Prentice Hall Press.

The Executive Summary

Estimated Reading Time: Summary (2 min) | Full Article (6 min)

• The Problem: Leaders often impose complex, rigid systems (”The System”) onto high-performing teams in an attempt to control outcomes. This increases cognitive load and suppresses natural talent.

• The Case Study: Manchester United’s recent victory over Manchester City wasn’t tactical genius; it was a return to simplicity. By removing Ruben Amorim’s complex 3-4-3 and installing a simple 4-4-2, the team stopped thinking and started playing.

• The Solution: Clarity is a competitive advantage. When performance dips, do not add more processes. Use “Via Negativa”—improvement by subtraction.

• The Protocol: A 3-step audit to strip away the noise and return to your “Base Code.”

For those with more time, the full analysis follows below.

The Micro: The Blue Jacket

My favorite Christmas present this year was a gift from my daughter. A carefully chosen artifact from the early 2000s that she knew would mean something to me.

It was a blue track jacket with the Manchester United crest. When I wear it, I don’t just see a logo. I feel the nostalgia of home. I remember living fifteen minutes from Old Trafford. I remember my father. Football was the language we spoke; it was the glue of our bond.

Living in Australia, the obsession naturally waned. But I still kept myself updated as much as I could. This weekend, I felt a familiar pull. The chaos of losing a manager usually signals a funeral, but I was desperate to see a glimpse of life. I wanted to see the DNA of the team that won 13 Premier League titles—the team that didn’t just play matches, but owned them.

The narrative was written before a ball was kicked. City is the machine—the undisputed hegemon of the last decade. United is the fallen giant, currently in chaos following the exit of Ruben Amorim. The new man in the dugout, Michael Carrick, is a club legend, but he inherited a broken squad.

I expected a loss. I hoped for a glimpse of dignity.

Instead, I read about a resurrection.

United didn’t just beat City; they dismantled the narrative. City held 70% of the possession—they had the ball, the territory, and the “system.” But United had the clarity. They played fast, attacking, intuitive football. It was a glimpse of the Old United—the one from my youth, the one that struck fear into teams before they even stepped off the bus.

Gary Neville, a man who shared a dressing room with Carrick, explained it perfectly: “It’s the return of at least something that looks like the club.”

But what does that actually mean? It isn’t just nostalgia. It is physics.

The Homogenisation Trap

Why did a team that looked lethargic and incompetent weeks ago suddenly look lethal?

The players didn’t change. Their fitness levels didn’t change. The only variable that changed was the Cognitive Load.

For the last two years, Ruben Amorim forced a rigid ideology onto this squad. Amorim is an astute student of the game; his system (a complex 3-4-3 formation) worked miracles at Sporting CP. But it is a “System” with a capital S. It requires precise positioning, triggers, and choreographed movements.

We often mistake complexity for strategy. We think that if a plan is hard to understand, it must be smart. But as Neville pointed out in his post-game analysis, high performance isn’t about doing complicated things. It is about sequencing simple things together perfectly.

Neville broke it down to the fundamentals: “It’s about the combinations of pairs... It’s a left winger and a left back. It’s a right winger and a right back. It’s two central midfield players... And then you might have your left-sided center back with your left back... and how they’re compact together so that they can play with each other.”

Neville is describing the power of local coherence. In Amorim’s complex system, every player had to understand the entire map of the pitch—a global network of moving parts. In Carrick’s system, you only need to understand your partner. The Left Back doesn’t need to calculate where he should be; he just needs to lock in with his Winger. By reducing the scope of responsibility to simple “pairs,” you dramatically reduce the cognitive load. You stop trying to solve the entire equation and just solve the problem standing right next to you.

Take Luke Shaw as the prime example. For months, he has looked stifled, often deployed as a makeshift center-back, caught between two minds. Neville noted the transformation: in previous weeks, Shaw was “holding back,” paralyzed by the system’s demands. In this game? He was sprinting. When the ball went wide, he didn’t calculate the structural implications for the rest of the team; he just supported his winger. He returned to his natural game because the instruction was liberated from complexity: If he goes, you go.

To an outsider, a counter-attack looks chaotic. To an insider, it is a series of “one-way door” decisions made at high speed. Pass forward. Overlap. Shoot. When you have clarity, you have the energy to execute these sequences. When you are burdened by a complex system, you hesitate.

Amorim fell into a classic leadership trap: Valuing the model over the reality.

When you force a genius to overthink, you make him average. When Bruno Fernandes has to calculate where to stand based on a complex algorithm of player movements, he cannot use his instinct to kill the opposition with a single pass. The goals United conceded under Amorim weren’t due to a lack of skill; they were “stupid mistakes” born of confusion. Confusion creates hesitation. In elite sports—and elite business—hesitation is death.

Carrick’s brilliance was not in adding a better strategy. It was in subtraction.

He reverted to a 4-4-2. He told them to play the “United Way”—play the ball forward, sprint, be aggressive. He removed the shackles of complexity. He realized that as an underdog with 30% possession, you don’t have time to think. You must act. Simplicity isn’t a finish line—they could still get thrashed by Arsenal next week—but you cannot climb the mountain if you are tripping over your own feet.

Clarity is not the absence of strategy. Clarity is the absence of noise.

Unlocking potential by making strategy simple is not a new phenomenon. We saw this decades ago with Brian Clough and John Robertson at Nottingham Forest.

When Clough arrived, Robertson was on the scrapheap—unfit, overweight, and considered “difficult.” Previous managers tried to force him into complex fitness regimes and defensive systems. Clough did the opposite. He ignored the weight. He ignored the tracking back. He reduced Robertson’s role to a single, crystalline instruction: Get the ball. Hold it. Cross it to the big man.

By stripping away the complexity of expectations, Clough unlocked one of the greatest creative forces in European history. Robertson didn’t need to be an athlete; he just needed to be a genius. (I wrote a deep dive on how Clough built a championship team from “average” parts here:

The Baseline Regression Protocol

When your business, your team, or your life feels stalled, the instinct is to add. Add a new tool. Add a new hire. Add a new meeting.

Stop.

If you are not getting the results you are capable of, you are likely suffering from “System Fatigue.” You need to strip the machine down to the chassis. Use this protocol to manufacture clarity.

1. Identify the “Unnatural” Friction

Look at your team. Where are the “stupid mistakes” happening?

• Are sales teams failing to close because they are filling out CRM data?

• Are engineers shipping slowly because they are arguing about ticket syntax?

• The Signal: If high-performers look confused or hesitant, you have a process problem, not a people problem.

2. The Via Negativa Audit (The Carrick Move)

Ask this question: What can I remove that will immediately increase speed?

• Eliminate the standing meeting that has no agenda.

• Remove the approval layer that adds 48 hours to a two way decision.

• Scrap the complex strategy document nobody reads for an Inconsequential decision and replace it with three bullet points.

• The Goal: Return to the “Base Code”—the simplest version of operations that allows the talent to function.

3. Optimize for Outputs, Not Inputs

Amorim optimized for inputs (positioning, structure, possession stats). Carrick optimized for outputs (speed, goals, winning).

• Stop measuring how many hours your team works (Possession).

• Start measuring the impact they deliver (Goals).

• Give them a simple objective and get out of their way.

Micheal Carrick’s first game as manager at United wasn’t just a football game. It was a mirror for every business that has lost its way.

When a company stalls—when it struggles to unlock the potential of its people or break through a growth ceiling—the instinct is always to complicate. We add layers. We add metrics. We add “systems” to manufacture control over an uncertain future.

But complexity is often just a hiding place for insecurity.

Manchester United didn’t need a new strategy to unlock their world-class talent. They just needed to remove the interference. They needed to return to the basics: clear roles, high speed, and absolute trust in instinct.

If you are stuck, do not build a better machine. Stop trying to code-switch your best people. Strip the operation down until all that remains is the mission and the talent.

The next level of growth is not found in the new. It is found in the foundation you forgot.

Simplify. Then watch them fly.

The Executive Summary

Estimated Reading Time: Summary (2 min) | Full Article (6 min)

• The Problem: Founders eventually hit a “Complexity Wall.” You are the sole router of information, meaning every decision waits for you. You become the bottleneck that slows down your own company.

• The Misconception: You try to solve this by hiring an Executive Assistant (EA) to buy back time. But an EA usually only defends your schedule. They cannot scale your judgment.

• The Solution: You need to adopt the “Two Chiefs” model—not two CEOs, but a partnership between the Chief Executive Officer and a Chief of Staff (CoS).

• The Mechanism: The CoS acts as a proxy, a router, and a force multiplier, allowing the CEO to focus purely on high-leverage strategy while the CoS ensures execution and follow-through.

For those with more time, the full analysis follows below.

The Ferguson Paradox

When Alex Ferguson arrived at Manchester United in 1986, the club was a sleeping giant with a culture of mediocrity. His first few years were a grind of rebuilding foundations. But as the club entered its golden era in the 90s, Ferguson made a decision that baffled pundits: he stopped leading training.

While his assistant Archie Knox, ran the drills, blew the whistle, and screamed instructions, Ferguson stood on the sidelines. He wore a heavy wool coat, hands deep in his pockets, watching.

He wasn’t lazy. He was seeking Asymmetry.

“When you are in the middle of the training session, playing the referee, you can’t see,” Ferguson later explained to Harvard Business School. “You can’t see a player’s body language change. You can’t see the energy levels drop.”

By stepping out of the noise of execution, he gained the signal of strategy. He understood that you cannot effectively manage a system if you are a cog within it. He needed a “Chief of Training” so he could be the “Chief of Winning.”

The Two Chiefs Model

Most modern CEOs are stuck playing player-coach. You are trying to be Alex Ferguson (Vision) and the assistant coach (Execution) simultaneously.

You run the board meeting, then rush out to debug a process failure in Sales. You call this “hustle.” In reality, it is a structural failure. You have created a Single Point of Failure: Yourself.

The flaw in most executive offices is the rigid distinction between “admin” and “strategy.” We often think an Executive Assistant (EA) handles logistics and a Chief of Staff (CoS) handles high-level thinking. This is a mistake.

In the early stages, the lines must be blurry. A great CoS often starts by managing your calendar. Why? Because managing your time is the fastest way to understand your Algorithm. They cannot control the flow of your strategy until they control the flow of your time.

This is where the Two Chiefs concept enters.

The “Two Chiefs” are the CEO and the Chief of Staff.

• The CEO is the directional force (The Telescope).

• The CoS is the integrating force (The Microscope).

The Authority Trap: A warning. If you do not define this relationship clearly, the team will get confused about who to please. You must clarify that the CoS speaks for you, not over you. The CoS creates efficiency, but you (the CEO) set the culture and the vision.

The Mochary Mandate

This structure is not just a preference; for elite operators, it is a prerequisite.

Matt Mochary, the legendary executive coach who advises Sam Altman (OpenAI) and Brian Armstrong (Coinbase), is famous for his rigid adherence to this principle. In fact, Mochary generally refuses to work with a CEO unless they have a Chief of Staff.

Why such a hard line? Because without a CoS, coaching can end up being just conversation. Strategy dies in the room without an implementation layer.

If you are hiring a CoS, Mochary suggests three non-negotiable responsibilities to include in the Job Description:

1. Preparation & De-brief (The 30-Minute Rule)

The CoS ensures you are prepared before the meeting (materials read, agenda set). More importantly, they capture the action items during the meeting and send the follow-up email within 30 minutes of the meeting ending.

2. Level 10 Meetings (The Referee)

The CoS should run your weekly leadership meeting. They keep the time. They police the agenda. They stop people from rambling. This allows you to participate in the debate without having to referee it (just like Ferguson).

3. Fear & Anger Sensor (The Emotional Radar)

The CoS acts as a sensor for the team’s emotional health. They check in with your direct reports: “How are you feeling? You seemed frustrated in that meeting.” They bring that data back to you so you can fix relationships before they break.

The Imbach Protocol: Lessons from LinkedIn

The most potent real-world example of this dynamic comes from Mark Organ (CEO of Influitive), writing in First Round Review.

Organ was drowning in operational noise. He was looking for help, assuming he needed a better admin. Then he witnessed Sarah Imbach, the Chief of Staff to Reid Hoffman (LinkedIn’s co-founder), in action.

He watched her run a high-stakes meeting. She wasn’t just taking notes or fetching coffee.

• She managed the energy of the room.

• She ensured every voice was heard, preventing groupthink.

• She synthesized complex arguments in real-time.

• She drove the group to a decision so Hoffman didn’t have to force it.

Organ realised: “I didn’t just need someone to book travel. I needed someone like Imbach. Someone who could substitute for me in meetings. Bring me the inside scoop from other departments. Take over projects I was too busy to do.”

This is the gold standard for the CoS role. They are a Proxy.

How to Implement the “Proxy” Protocol

To replicate the Hoffman/Imbach dynamic, you must empower your CoS with three specific mandates:

1. The “Shadow” Mandate (with The Debrief Ritual)

For the first 30 days, the CoS shadows you everywhere. But shadowing without feedback is just watching.

• The Ritual: You must hold a daily sync (15-30 mins) at the end of every day. The CoS asks: “I saw you do X in that meeting. Why didn’t you do Y?”

• The Goal: This is how they download your brain. If you don’t make time to explain the why, they will never learn to be your proxy.

2. The “Whisperer” Mandate (Systemic Candor)

While every team member should be paid to speak the truth, the CoS is the architect of candor.

• The Protocol: The CoS monitors the flow of information. If a VP is sugarcoating a report to the CEO, the CoS intercepts it.

• The LinkedIn Example: Just as Imbach guided the room for Hoffman, your CoS serves as a mirror for the group, signaling when the team is drifting into consensus-seeking rather than truth-seeking.

3. The “Router” Mandate (The Agreement Tracker)

The CoS is not just a gatekeeper of decisions; they are the keeper of the Agreement Tracker.

• The Problem: Most teams suffer from Amnesia. Decisions are made, but implementation drifts.

• The Fix: Every time you or a team member says “I will do X,” the CoS writes it down. They ensure that what was decided actually happens. This shifts the role from just “decision support” to “execution guarantee.”

The tragedy of the modern founder is that they think “letting go” means losing control. Sir Alex Ferguson didn’t lose control when he stepped off the training pitch; he gained total control.

By installing a Chief of Staff—a second Chief—you are not abdicating your throne. You are securing it. You are acknowledging that to see the whole field, you cannot be chasing the ball.

Stop trying to be the hero who touches everything. Build an office where you have a Chief who runs the plays, so you can be the Chief who wins the game.

This post is the argument. The full protocol is the playbook, and it’s free to read.

It has the parts I left out here: the 30 day shadow, the debrief ritual, the agreement tracker, and how to run the whole thing differently when you’re early stage, when you’ve got a co-founder, or when the team is remote.

The Ferguson Protocol, in the Source Code

In 1979, Herb Brooks stood on the ice in Colorado Springs, staring at a list of the best college hockey players in America. He had a task that was statistically impossible: build a team of college kids to beat the Soviet Union—a machine that had won the last four Olympic gold medals and hadn’t lost an exhibition game to an NHL team in years.

During the tryouts, Brooks did something that baffled his assistant coach, Craig Patrick. He started cutting the most talented players. He cut players who were statistically superior, players who were stronger skaters, players who were “consensus picks.”

When Patrick challenged him, asking why he was sending the best talent home, Brooks delivered a line that should be burned into the mind of every founder:

“I’m not looking for the best players, Craig. I’m looking for the right ones.”

Brooks wasn’t building a collection of individual stats; he was building a system. He knew that to beat the Soviets, he didn’t need individual brilliance—he needed a specific style of weaving, passing, and conditioning that required total ego-death. He needed players who fit the architecture of his game plan, not the archetype of a star.

Six months later, that group of “inferior” players pulled off the Miracle on Ice.

The “Best Player” Fallacy

Most founders recruit like Craig Patrick, not Herb Brooks. They fall into the trap of “Voodoo Hiring.”

They look for the “Best Player.” They hunt for the impressive resume, the big brand names, the shiny pedigree. They write Job Descriptions that list generic inputs: Must manage sales. Must know Python. Must have 5 years experience.

This is fragile thinking. It assumes that talent is a universal currency that works in every environment. It doesn’t.

When you hire for generic “excellence” or “culture fit,” you end up with a team of individuals playing their own game. You get a group of people who are busy, who are talented, but who—when the pressure mounts—revert to their own instincts rather than the system’s needs.

To build an antifragile business—one that grows stronger under stress—you must stop writing Job Descriptions and start building Scorecards.

The Scorecard: Your Blueprint for Anti-fragility

A Job Description is a wish list. A Scorecard is a business plan for a role.

Just as Brooks defined the specific outcome (beat the Soviets) and worked backward to find the specific traits required (conditioning, unselfishness, speed), you must define the victory before you look for the soldier.

Here is the protocol for building a team that fits your game.

1. The Mission (The North Star)

Stop listing tasks. Define the essence of the role in one sentence.

• The Trap: “The Sales Manager manages the team and reports numbers.”

• The Fix: “The Sales Manager builds a predictable revenue engine that scales ARR from $5M to $10M in 18 months.”

If the candidate cannot look at that mission and say, “I have done exactly this before,” they are a gamble. And you cannot afford to gamble.

2. The Outcomes (Binary Success)

Brooks didn’t care if his players looked good; he cared if they could keep up with the Soviet pace. In business, you need 3-5 specific, binary outcomes.

• Revenue: “Close $1M in new business by Q4.”

• System: “Reduce onboarding time from 6 weeks to 2 weeks.”

• Culture: “Hire 3 A-Players who stay for 12+ months.”

At the end of the year, there should be no debate. Did they hit the number? Yes or No. This clarity removes the emotional weight of management.

3. The “Near Enemy” Filter

This is the most critical step. Every virtue has a “Near Enemy”—a negative trait that mimics a positive one.

• You want Ownership, but you might hire a Control Freak.

• You want High Standards, but you might hire someone with Paralysis.

• You want Speed, but you might hire Recklessness.

Brooks needed aggression, but he couldn’t afford penalties. He filtered for the trait (grit) and filtered out the near enemy (undisciplined rage). Your Scorecard must explicitly name these enemies so you can spot them in the interview.

Need to go deeper check out the co founder protocol here:

The Name on the Front of the Jersey

The reason the 1980 US Olympic team won wasn’t a miracle. It was a design. It was the result of a leader who ignored the noise of “talent” and focused on the signal of “fit.”

When you strip away the Voodoo—the gut feelings, the resume biases, the “I just like him” rationale—you are left with the cold, hard truth of the Scorecard. It forces you to ask: Can this specific person achieve this specific outcome in this specific environment?

If the answer is yes, you hire. If the answer is maybe, you pass.

Herb Brooks famously told his players:

“The name on the front of the jersey is a hell of a lot more important than the name on the back.”

Stop hiring names for the back of the jersey. Start hiring for the mission on the front. That is how you turn a group of misfits into a team that can beat the world.

Note: This Document was drafted with AI support. I leverage technology to structure my thoughts efficiently, ensuring you get my best thinking with zero friction.

This post is the case. The full protocol is the build, and it’s free to read.

It has the Scorecard itself: the mission line, the three to five binary outcomes, and the Near Enemy filter for spotting the shadow version of the trait you actually want. Plus how to run it when you’re under ten people, and how to build a Scorecard library when you’re hiring five a quarter.

The Herb Brooks Protocol, in the Source Code

1. The Core Philosophy (The “Why”)

The Trap: “Voodoo Hiring”

Most leaders hire based on “Gut Feel,” generic job descriptions, or “Culture Fit.” With out defining what the culture is.

• The Job Description Error: Lists tasks (”Must manage sales”), not results. It attracts people who want to “do things,” not people who want to “own outcomes.”

• The Culture Fit Error: We hire people who “feel like us.” This creates fragility because it prioritises comfort over challenge.

The Shift: The Scorecard

The Scorecard is not a job description; it is a business plan for a person.

It operates on the principle of Anti-Fragility. We are not looking for someone to fill a seat; we are looking for someone who can navigate chaos and strengthen the system.

The “Double Duty” of the Scorecard:

Geoff Smart and Randy Street emphasize that the Scorecard is not just a hiring filter; it is a management tool.

• In Hiring: It predicts who can do the job.

• In Management: It measures if they are doing the job.

The Rule: If you hire against the Scorecard, you must manage against the Scorecard. It replaces the vague “Annual Review” with a binary check: Did we hit the outcomes defined in the blueprint?

We do not hire for “Potential” (a gambling term). We hire for Patterns of behavior that match our specific DNA.

2. The Protocol (The “How”)

Phase 1: The Mission (The North Star)

Goal: Distill the role into a single, high-clarity sentence. This is the “Headline.” It must answer: Why does this role exist?

• The Trap: “The Sales Manager manages the sales team.” (Task-based).

• The Protocol: “The Sales Manager constructs a predictable revenue engine that scales from $5M to $10M ARR within 18 months.” (Outcome-based).

Phase 2: The Outcomes (The “What”)

Goal: Define the 3-5 specific victories that constitute success.

These must be binary. At the end of the year, we should be able to look at this list and say “Yes” or “No” without debate.

• The Rule: Avoid “activities” (e.g., “Make cold calls”). Focus on “yields” (e.g., “Generate $2M in net new pipeline”).

Note: Every scorecard must include one outcome related to System Improvement. We don’t just want them to execute the process; we want them to break and rebuild the process to be stronger.

Structure each Outcome as:

“From

Current Reality

to

Desired Reality

by

Date

.”

Phase 3: The Competencies (The “How”)

Goal: Define the behaviors required to achieve the outcomes. Here is where we integrate your

Values Discovery Protocol. We split competencies into two categories:

A. The Hard Skills (Table Stakes)

• Example: Strategic Planning, Python, P&L Management.

B. The Cultural DNA (The Values Alignment)

We do not use generic buzzwords like “Integrity.” We use your specific Core Values and filter for “Near Enemies”.

The Concept of Near Enemies:

A “Near Enemy” is a trait that looks like a virtue but is actually a vice in disguise. It is the shadow side of a strength. When defining competencies, you must be aware of these traps:

• Ownership (Virtue) vs. Control Freak (Near Enemy).

• High Standards (Virtue) vs. Perfectionism/Paralysis (Near Enemy).

• Empathy (Virtue) vs. Pleasing/Conflict Avoidance (Near Enemy).

Ensure your cultural competencies explicitly describe the healthy virtue, not the shadow.

3. The Execution: The “Draft-to-Craft” Workshop

Do not try to write the perfect scorecard alone. The Who methodology explicitly warns against “Phantom Requirements”. Where different stakeholders have secret expectations that are not on the page.

Step 1: The 15-Minute Flash Draft (The Hiring Manager)

• Owner: The Hiring Manager (You). Do not outsource this to HR.

• Action: Set a timer. Write down the “Shitty First Draft.” Focus on the raw outcomes required to support the top 3 goals for you business

• Review it and edit it into shape

Step 2: The Alignment Cycle (The Smart & Street Requirement)

• Context: You must gather input before you interview. If you don’t align now, you will argue later.

• The Who: Send your draft to:

1. The Boss (To ensure it hits strategic goals).

2. The Peers (To ensure it doesn’t step on toes).

3. The Subordinates (To ensure they know what leadership looks like).

The Script: “I am drafting the blueprint for this new role. Please look at the Outcomes section. If they achieve these 5 things, is that a win? Is anything missing? Is anything unrealistic?”

Step 3: The Calibration (The Review)

• Review the feedback. Sharpen the language using the “So What?” test.

• Draft: “Run weekly meetings.” -> So What? -> “So the team is aligned.” -> So What? -> “So we don’t miss product ship dates.”

• Final Outcome: “Ensure 100% on-time product delivery through rigorous weekly alignment.”

4. The Tool: The Scorecard Template

Role: Insert Title

Mission: One sentence summary of the role’s purpose

Outcomes (The “What”):

(The specific, binary results used for Hiring and Performance Reviews)

1. Outcome 1: From X to Y by Date

2. Outcome 2: From X to Y by Date

3. Outcome 3: From X to Y by Date

4. System Outcome: Improve X Process from Y to Z by Date

Competencies (The “How”):

Technical Skills:

• Skill 1

• Skill 2

• Skill 3

Cultural (DNA) Competencies:

(Specific behavioral evidence required)

• Core Value 1: Describe the specific behavior

• Core Value 2: Describe the specific behavior

• Core Value 3: Describe the specific behavior

5. Summary

You are building a filter. A weak scorecard lets 50 people through, and you have to guess. A strong scorecard lets 3 people through, and any one of them can do the job.

We hire for Values Alignment

6. Frequently Asked Questions

Q: What is the primary difference between a Job Description (JD) and a Scorecard?

A: A Job Description typically lists tasks, responsibilities, and generic requirements (inputs). A Scorecard lists specific outcomes and results required for success (outputs). The Scorecard acts as a business plan for the role, whereas a JD acts as a task list.

Q: How does the Scorecard use the “Near Enemies” concept?

A: The Scorecard uses “Near Enemies” to differentiate between a healthy Core Value and its toxic “shadow” trait. For example, it distinguishes between “High Standards” (healthy) and “Perfectionism” (toxic). This ensures we do not hire candidates who mimic our values but ultimately damage the culture.

Q: Who should be responsible for writing the Scorecard?

A: The Hiring Manager must write the first draft of the Scorecard because they are responsible for the hire’s performance. It should not be outsourced to HR or a recruiter. However, it must be refined through the “Alignment Cycle” with peers and leadership.

Q: Can the Scorecard be used for performance reviews?

A: Yes. The “Who” methodology states that the Scorecard serves “Double Duty.” It is the hiring filter and the management standard. Performance reviews become a binary audit: “Did you achieve the outcomes defined in the Scorecard?”

Q: Why is “Alignment” required before interviewing candidates?

A: Alignment prevents “Phantom Requirements”—unspoken expectations held by different stakeholders. If the team does not agree on the Scorecard outcomes before interviewing, they will evaluate candidates against different criteria, leading to hiring failure or internal conflict.

Q: What is the “Draft-to-Craft” protocol for Scorecards?

A: The “Draft-to-Craft” protocol requires the Hiring Manager to write a rough, 15-minute “shitty first draft” of the Scorecard to capture the raw necessities of the role. This overcomes procrastination and perfectionism, allowing the team to edit and refine (Craft) the document later.

Appendix: High-Clarity Examples

Use these examples to calibrate your own drafts. Notice the specificity of the outcomes.

Example 1: Head of Sales (The Revenue Engine)

Mission: Build a scalable, predictable revenue engine that doubles ARR from $5m to $10m by Dec 31st, while maintaining a CAC of <$1k.

Outcomes (The Scorecard):

1. Revenue: Grow Annual Recurring Revenue (ARR) from $5m to $10m by end of fiscal year.

2. Hiring: Hire, onboard, and ramp 6 Account Executives who achieve 80% quota attainment within 4 months.

3. Pipeline: Implement a systemic outbound prospecting methodology that generates $15m in qualified pipeline coverage (3x cover).

4. System Upgrade: Replace the current ad-hoc sales tracking with a fully automated Salesforce dashboard that predicts revenue within 5% accuracy by Q3.

Key Cultural Competency:

• Value: Radical Transparency.

• Behavior: Reports bad news (missed targets) instantly and without fluff. Owns the “miss” and presents the “fix.”

• Near Enemy Watch: The “Spinner” (someone who uses charisma to hide the numbers).

Example 2: Chief of Staff (The Force Multiplier)

Mission: Maximize the CEO’s throughput by handling operational friction and ensuring the Executive Team executes the quarterly strategic plan with 90% completion.

Outcomes (The Scorecard):

1. Meeting Rhythm: Restructure the Weekly Level 10 Meeting to ensure decisions are made in under 60 minutes, reducing executive time-wasting by 30%.

2. Strategic Execution: Manage the “Big Rock” quarterly projects ensuring 90% of agreed initiatives are delivered on time and on spec.

3. CEO Leverage: audit and remove 15 hours of low-leverage administrative tasks from the CEO’s calendar by Month 2.

4. System Upgrade: Build and document the “Company Operating System” (The Wiki) so that onboarding time for new execs drops from 6 weeks to 2 weeks.

Key Cultural Competency:

• Value: Disagree and Commit.

• Behavior: Challenges the CEO privately with data/logic, but supports the final decision publicly with zero hesitation.

• Near Enemy Watch: The “Yes-Man” (agrees to please) or the “Saboteur” (agrees in the room, complains in the hallway).

Example 3: Senior Product Manager (The Value Creator)

Mission: Lead the “Mobile-First” initiative to increase daily active users (DAU) by 40% through rapid iteration and high-velocity shipping.

Outcomes (The Scorecard):

1. Engagement: Increase Mobile DAU from 10k to 14k by Q4 without increasing churn.

2. Velocity: Increase shipping cadence from 1 release/month to 1 release/week (Weekly Sprints).

3. Customer Intimacy: Conduct 50 customer interviews to validate the roadmap, killing at least 2 “zombie features” that users don’t want.

4. System Upgrade: Establish a “Draft-to-Craft” product spec process that reduces engineering rework by 50%.

Key Cultural Competency:

• Value: Anti-Fragility/Resilience.

• Behavior: Treats failed launches as data. Pivots the roadmap based on user feedback without ego or defensiveness.

• Near Enemy Watch: The “Stubborn Visionary” (ignores data to protect their idea).
  
  
  

THE CODE IS OPEN SOURCE.

“These protocols are free to use. You can build the engine yourself. But if you need an expert to install it in your team without breaking the culture...”

Need help with implementation - lets talk

The full protocol is free to read, and it has the workshop this post skips: the 15 minute flash draft, the alignment cycle, and the calibration pass where you run the So What? test over every outcome. Plus what to cut when it’s your first hire.

The A-Player Scorecard Protocol, in the Source Code