That story is true. It’s also incomplete.

The part that gets less attention is what happens on the other side of that collapse. When the cost of producing something falls to near zero, the ability to produce that thing stops being rare. Something else becomes rare instead. And in a world where anyone can write anything, generate anything, personalize anything, the thing that becomes scarce is trustability (being worthy of someone’s trust).

Over the last few months, thanks to Founder Real Talk, we’ve talked to founders across completely different industries who’ve independently landed on the same conclusion. AI matchmaking. AI-powered websites. Sales enablement. Agency work. AI safety infrastructure. None of them talk to each other. They’re solving different problems for different customers. And they’ve all arrived at the same thesis.

Trust is the new moat.

Why this is happening now

There’s a version of the “AI is coming for everything” argument that treats every industry as headed toward the same commodified endpoint. Content is commodified. Code is commodified. Design is commodified. Sales outreach is commodified. Everything gets cheaper, faster, and less differentiated, forever.

That framing is missing something important. When a category commodifies, buyers don’t stop caring. They start caring about something else.

You’ve probably heard people in Silicon Valley say, “Taste Is the New Moat.” Their argument: as generative AI collapses the cost of production, the real value comes in curation. Editorial judgment. Point of view. Knowing what’s worth making rather than what can be made.

We think trust is the second half of that same shift. Taste is what someone brings to the work. Trust is what other people extend to them. Both are human. Both are hard to fake. Both become disproportionately valuable in a world where output is free.

Here’s the mechanical version. AI has done two things at once. It has made it much easier to produce content that looks credible. And it has made it much harder to tell whether the credible-looking thing is actually credible. That gap, between what looks trustworthy and what is trustworthy, is where value is now concentrating.

Ben Gusberg at CAPE puts it in the sharpest form. Cold email conversion is collapsing because everyone has the same AI tools. In his words, “everyone is sending 10,000 emails a day that are perfectly personalized to you, and the conversion for those messages is going way down.” His numbers on the alternative are striking. Warm intros convert 34 times higher than cold email.

His framing: “In a world with all noise, how do you find signal? Ironically, we think that signal comes from humans.”

That’s the shape of the argument in one line. As synthetic communication floods the channel, the signal buyers actually respond to is human.

Check out Ben’s full episode on our YouTube channel here

What this means

The founders we talk to who are winning right now are betting on a specific set of things that AI can’t easily replicate.

Real relationships. The kind you build over years, with people who’ve watched you handle the hard version of something and stuck around. This is why in-person is resurgent. In-person can’t be automated or faked. Presence is a costly signal in a way that a cold email will never be, no matter how well-personalized.

Genuine thoughtful voice. Not a brand voice generated by a prompt. A perspective that comes from an actual human who’s spent enough time in a specific problem to have earned an opinion about it. The blog post that took someone twenty years of hard experience to write reads different than the one that took a language model twenty seconds, even when the surface content is comparable.

Reputation over time. In a world where anyone can spin up a plausible-looking company overnight, the founders who’ve been building the same thing for five years, showing up in public, taking responsibility for outcomes, have an advantage that new entrants can’t buy. Longevity is a form of trust that money can’t manufacture.

Safety and audit-ability. The regulatory version of trust. As AI gets deployed in high-stakes domains, the ability to prove your system won’t fail in the ways that matter becomes a hard requirement. The EU is already pushing regulation into force that requires companies deploying AI to demonstrate compliance. Trust is being written into law, not just competitive strategy.

All of these have one property in common. They can’t be produced at zero marginal cost.

What this looks like practically

If you’re a founder trying to decide what to build, or what to invest your reputation in, the takeaway is fairly specific.

Prioritize the parts of your business that can’t be commoditized. The customer relationships. The domain expertise. The judgment that tells you what to bother building and whether what you’ve built actually serves the customers you want. These are the parts that will still be worth something in five years, whatever else changes.

Be skeptical of building anything that depends on a temporary advantage in AI-generated volume. Cold outreach at scale, content flooding, spray-and-pray outbound. These tactics are already declining and will decline further. If your business model requires them to work, your business model is on borrowed time.

Invest in in-person more than the current defaults would suggest. Events, dinners, actual meetings. The economics have quietly shifted. In a world where the cost of digital contact is near zero, the value of physical presence is going up, not down. A dinner with ten of the right people is now doing what a thousand LinkedIn connections used to do.

Build your public presence on the assumption that trust will be the scarce resource for the rest of your career. Not audience. Not reach. Trust. Which means being right when you make a public call, admitting when you’re wrong, and being consistent about what you stand for. That’s a five-year game, and the people who started playing it three years ago are already ahead.

The reframe

The narrative about AI has spent two years focused on what it can do. The interesting question, and the one the founders we talk to are quietly answering, is what AI can’t do.

It can produce output. It can’t produce trust.

It can generate credible-looking content. It can’t give that content the weight of a human being who poured their heart into it.

It can automate the cheap parts of a relationship. It can’t automate the parts that make a relationship worth having.

The founders betting on the human side of that split are the ones we’d bet on. Not because AI is going away. Because the more powerful AI gets, the more valuable the thing it can’t do becomes.

Trust is the new moat. It always has been, actually. The change is that everything else just got a lot easier to imitate.

Subscribe now

They think they’re selling their technology. They spend fifteen slides on how the sausage gets made. They dive into the architecture, the algorithms, the technical breakthroughs. They’re proud of what they’ve built. They assume the investor will be equally impressed.

Or they think they’re selling their product. They walk through the feature set, the customer testimonials, the product roadmap. Everything is about how amazing the thing they’ve made is. They love their product. It’s their baby. Surely, the investor will love it too.

Or they think they’re selling an idea. This thing will change the world. This category is about to explode. This vision is huge and inspiring and could be the next Google.

Or they think they’re selling themselves. They lead with the resume. Where they went to school. Where they worked. The impressive brand names in their background. Sometimes investors even encourage this framing. “We invest in founders, not ideas.” So the pitch becomes a beauty pageant.

All of that is wrong, and often it results in pitches that don’t close

What you’re actually selling

You are selling part of a business.

Literally. That’s it.

When you close a round, the transaction is that an investor gives you cash and you give them shares. They now own shares of your company. Five percent, ten percent, twenty percent, whatever the number is. They will own that many shares until the business gets acquired, until they get bought off the cap table, or the whole thing collapses.

That is the transaction. Everything else in your pitch is in service of that transaction, or it shouldn’t be in the pitch. Once you internalize this, everything about pitch strategy shifts.

• If you’re selling technology, you’re basically applying for a grant. That’s a different transaction with different buyers.

• If you’re selling a product, you’re pitching to customers. That’s also a different transaction with different buyers.

• If you’re selling an idea, you’re a novelist. Ideas without execution don’t have investable value.

• If you’re selling yourself, you’re running for office. Investors may be flattered to be pitched this way, but they will probably not write the check.

Investors are buying part of a business. Your pitch deck exists to answer the question “is this business worth owning a piece of.”

What the pitch actually has to prove

Once you’re clear on what you’re selling, the pitch structure follows.

You need to prove that this is a real business. Not a cool project. Not an interesting technology. Not a founder with a good story. A business. Something that generates revenue, scales that revenue, and eventually becomes valuable enough that someone will want to buy it or take it public.

That means the pitch has to answer specific questions.

• How does this business make money? Not eventually. Now, or with a credible path to now.

• How will the revenue grow? What’s the go-to-market motion? What’s the acquisition cost, the retention curve, the expansion story?

• What does traction actually look like today, and what will it look like six months from now? Traction is not just what you’ve done. It’s what your existing progress predicts about what you’ll do next.

• Why can you specifically build this into a big business? This is where your background and skills become relevant. Not as a beauty pageant, but as evidence that you can execute on the specific plan you’re proposing.

• How does the investor get their money back? Eventually, the shares they’re buying need to convert into cash. That happens through acquisition, IPO, or secondary sale. Your pitch needs to make the exit path plausible without pretending to know exactly what it will be.

The product, the technology, the team, the idea. All of that is still in the deck. It’s just in service of a different central question. Instead of “look how amazing this is,” everything becomes “here’s why this can be a business that returns capital.”

We wrote a whole post on the 10 common pitch deck mistakes that come from misunderstanding this. It’s the tactical companion to this one.

The founder identity trap

There’s a second reason this reframe matters, and it has nothing to do with fundraising success. It has to do with what happens if the business fails.

When founders confuse themselves with the company, they set themselves up for a very specific kind of collapse. If the business fails, they conclude that they failed. With every threat to the business, they feel threatened in their core human value. The identity and the entity have merged. There’s no way to separate the two.

You’re not selling your self when you take investment. You’re selling shares in a specific business you’re building right now. The investors do not own you. They do not own your future ideas. They do not own your next company. They own a portion of this company, for as long as it exists in its current legal form.

If this business succeeds, great. If it doesn’t, you’re still you. You still have your capabilities, your relationships, your experience, your future. The investors don’t have any claim on those things.

Founders who understand this early tend to weather the hard parts of the journey better than founders who don’t. When things get bad, they can look at the situation honestly, because they aren’t personally dying with every piece of bad news. Founders who’ve merged their identity with the company can’t do this as well. Every setback feels existential because they’ve made it existential.

Separate the two. You’re a founder building a business. The business is a legal entity that produces goods or services and generates cash. You are a person. They are not the same thing. Investors are actually buying into the entity, not the person.

The reframe

The next time you sit down to work on your pitch deck, ask yourself one question at every slide.

Does this slide help someone decide whether they should own five percent of my business?

If yes, keep it.

If it’s just there because you love the technology, or you’re proud of the product, or you want the investor to like you personally, cut it.

Your pitch is not a demo. It’s not a resume. It’s not a manifesto. It’s a business case for why owning part of your company will produce a return.

Build the pitch around that transaction, and the rest of it gets easier.

Subscribe now

The meetings that produce the biggest leverage are also the hardest to sustain. Here’s why, and what to do about it.

HPMs are simple to set up. They’re genuinely challenging to maintain. Almost every founder who tries them lets them slip within a quarter or two, drifts back into the old rhythm, and then feels bad about it.

The slippage isn’t a discipline failure. It’s a design feature. HPMs are hard on purpose. The difficulty is actually where the value is.

The core reframe: HPMs are the end of a process, not the beginning

The single most important thing to understand about a high-performance meeting is that the meeting itself isn’t the real work.

The real work happens before the meeting. Owners prepare written material. Everyone reads it in the first fifteen minutes. The remaining forty-five are spent on the things that actually need discussion. If the meeting feels efficient because there’s nothing interesting to say, you’re doing it wrong. If it feels efficient because everyone came prepared and the meeting is where you collect the value of that preparation, you’re doing it right.

That distinction is why HPMs are hard. The default mode for how meetings work in most companies is the opposite. You show up. You riff. You improvise for an hour. You leave without much to show for it, but you also didn’t have to prepare, and neither did anyone else.

An HPM demands preparation from everyone. That’s expensive. It feels especially expensive at the beginning, before people have felt the payoff. If you’re a founder who runs on charisma and in-the-moment thinking (which many founders are), you’ll find HPMs deeply uncomfortable at first. They take away the improvisation you’re good at and force a discipline that doesn’t come naturally.

Key 1: The agenda is the actual product

The single biggest predictor of whether an HPM culture takes root or not is whether the founder sat down and did the hard work of designing a high quality agenda.

Not once. Every quarter. With each person who owns a section of the meeting.

That work looks like this. You sit down with the person who owns a function or a project. You talk through what success looks like for them. You agree on what they should report on, how they should measure it, and what kind of updates matter. You make it specific. You make it real. You leave with an understanding that will hold for at least a few months.

That is a lot of upfront time. But if you don’t invest this prep time, you end up with meetings where people just report vanity metrics and phone it in. Founders who do invest it end up with meetings that unlock genuine leverage.

Key 2: It’s on your team to prepare, and they’ll resist at first

The unlock for CEOs, once they get this, is enormous. In a functioning HPM culture, it’s your reports’ job to make sure the meeting is good, not yours.

You show up. You read the prep. You engage. You leave. The responsibility for the meeting being useful sits with the person reporting, not with you.

That is the great CEO relief. If you’re the founder currently drowning in requests of “Can you just look at this real quick?”, it can feel like getting swarmed by piranhas. Each request is tiny, but the compounding effect eats you alive.

Imagine those requests batching into a weekly forum where the person has prepared, thought it through, and is coming to you with a real ask. Every small interruption is redirected into a scheduled, contained conversation. The piranha bites stop.

But there’s a catch. Your team will resist this at first. Almost every implementation we’ve watched includes at least a few people who think the prep work is busywork. They’ll grumble. They’ll do the minimum. They’ll try to phone it in.

What you’re looking for, within a meeting or two, is the shift. You’ll hear someone say “I can’t believe how much we got done today.” That’s gold you’ve been working toward. Once they realize that putting real information into the prep gets them real help in the meeting, they lean in. Before that moment, you’re pushing a rock uphill. After it, they push it themselves. You just have to survive the first weeks.

Key 3: You have to resist taking over

The temptation, when your team’s first HPM prep isn’t very good, is to take over.

Don’t.

The failure mode is easy to fall into. Someone reports on their section. It’s shallow. It doesn’t cover the actual issue you know they’re facing. So you jump in, redirect the conversation, start driving it yourself. Now you’re the one running the meeting, they’re the one being interrogated, and the ownership dynamic you were trying to build has quietly collapsed.

The better move is to ask a pointed question. You know what’s actually going on. Use that knowledge to ask something specific that surfaces the real issue rather than lecturing them into it.

But here’s the part most leaders get wrong. The pointed question is only half the skill. The response to the answer is the other half, and arguably the more important half. When someone finally gets vulnerable and admits the thing they were dodging, what you do next determines whether they ever do that again. If you punish them, or turn it into a lecture, or use it as an occasion to demonstrate how much more you know than they do, you’ve just taught them to hide the next hard thing. On the other hand, if you say, “It’s great that we’re talking about this. How can I help?” then you’ve just built the muscle of honest reporting.

Key 4: Figuring out what to report on is genuinely hard in a startup

One of the recurring struggles for early-stage founders trying to run HPMs is knowing what to have people report on. The default answer, borrowed from bigger companies, is KPIs. Report on your metrics. Show the numbers.

The problem is that in a startup, the numbers are often too volatile or too small to be meaningful week over week. Ten customers becomes eleven becomes nine becomes twelve. Reporting on that in isolation tells you nothing.

The frame that tends to work better is unlocks. What are you trying to unlock next? Product-market fit. The next fundraise. The first repeatable sale. The tenth customer that lets you build a system around a real cohort. Every function in a startup is oriented around unlocking the next thing. If you organize reporting around what each owner is working to unlock, you get much more useful conversations than if you organize around fixed metrics that don’t yet mean much.

The unlock frame also protects against the demoralization problem. If you set a quarterly target of “10x sales” and miss it four quarters in a row, your team stops trusting the goal-setting process. If you say “The unlock this quarter is repeatable systems, which requires at least ten customers,” then you’re pointing at a real threshold. Hit it, and something opens. Miss it, and you know what you didn’t get to.

Key 5: You have to blow it up periodically

The last reason HPMs are hard is that, even when they’re working, they eventually stop working.

Humans are naturally good at optimizing. Once people get used to the format, they optimize for it. They report on the same things in the same order. The prep becomes easier because it’s routine. And routine, in the context of an HPM, is death.

The whole point of the meeting is the developmental stretch. If it’s easy, it’s not doing its job. The zone of developmental challenge, the middle band where things are hard but achievable, is where humans actually grow. Too much challenge and people give up. Too little and there’s nothing to push against.

The move, roughly two or three times a year, is to blow up the agenda. Destroy the format you’ve built. Design a new one that stresses the thing your team most needs to stretch on right now. Then, run that for a few months until it, too, becomes comfortable, and blow it up again.

It’s exactly like an exercise program. Do the exact same workout for three months, and it stops helping you. Same principle applies here.

One last thing: HPMs surface politics fast

There’s one more reason HPMs are hard to maintain, and it’s worth flagging separately. HPMs surface political dynamics very quickly. In a healthy team, that’s a feature. In an unhealthy one, it’s a threat.

The whole point of the meeting is that people show up and say the thing that needs to be said. If your organization has developed norms around not talking about the difficult things (the underperforming leader, the misaligned strategy, the customer who’s about to churn), the HPM becomes uncomfortable, and people find ways to route around it. They talk offline. They soften what they report. They hide behind vanity metrics.

That drift is your signal that something has gone off in the culture. The HPM didn’t cause it. The HPM revealed it, which is exactly what a good meeting should do.

If yours is drifting, the question isn’t how to fix the meeting. It’s what conversation your team no longer feels safe having, and what you’re going to do about that.

HPMs are hard because they demand the things most meetings let you avoid. Preparation. Ownership. Honesty. Discomfort.

The founders who stick with them do it because they’ve felt the payoff. The team is more aligned. The CEO is less drained. The important issues surface faster. The politics stay in check. All of those benefits are downstream of the hard work of building a good meeting.

The meetings aren’t the work. The meetings are where the work pays off. Keep the work going upstream, and the meetings take care of themselves.

Subscribe now

That number feels strange to write. We started the podcast in February, not entirely sure what it was going to be, not entirely sure we could sustain it. Two or three episodes a week. Four dozen founders. Roughly ten months of conversations we didn’t have when we set out to have them.

There’s a version of this post that would summarize the fiftieth episode. We’re not going to do that. The episode is already up, and it’s worth listening to (check our 50th episode special here). What we want to do instead is sit with what it’s been like on our side of it, and share some of what we’ve learned that only really surfaces when you look at the whole thing at once.

Starting something new is always a little disorienting

We work with a lot of founders. We coach them, advise them, help them build the companies they’re trying to build. That’s the day job.

Starting a podcast wasn’t the day job. It was closer to what we spend our time helping other people do. You have an idea. You aren’t sure who it’s for. You aren’t sure what the format should be. You don’t know if anyone will listen. You publish the first one anyway. Then you publish the second. Then you’re twenty deep and starting to see the shape of the thing you’re actually making.

That process turned out to be a useful exercise in a way we didn’t fully anticipate. We spend a lot of time talking about the founder journey. We got to live a very small, low-stakes version of it, again. The uncertainty at the beginning. The private “is anyone actually paying attention” phase. The moment where you stop asking whether it’s working and start asking how to make it better. It’s a very different feeling from the outside.

We came out of it with renewed empathy for what we’ve been asking our clients to feel their way through for years. Advice is easier than execution, which we already knew, but it’s one thing to know and another to be reminded.

The founders we met

The best part of the last eight months of podcasting has been the founders themselves.

Some of them are our clients. Some are people in our network. But a real portion of them are founders we would never have crossed paths with any other way. Different industries. Different geographies. Different stages. Some are ex-corporate operators who left a comfortable job to build something. Some are second-time founders who lost the first company and came back for another try. Some are running businesses that don’t look anything like the venture-backed, unicorn-chasing stereotype the tech press tends to focus on.

That range has been the gift. Founder Real Talk pulled us into a bigger picture of the founder journey. And what became obvious pretty quickly is that the core experience of being a founder rhymes across almost every industry, stage, and geography we’ve seen.

Which brings us to the three themes.

What kept showing up

Three patterns emerged across the fifty episodes, and they’ve reframed how we think about the work.

The first is loneliness. We knew this going in. We’ve written about it. We’ve built coaching materials around it. But hearing it from forty-nine founders in a row, in their own words, is a different thing than knowing it in the abstract or from our own experience. The specific quality of the loneliness surprised us. It isn’t the loneliness of being physically alone. It’s the loneliness of carrying something the people around you can’t fully carry with you, either because they work for you, or because they love you too much to be objective, or because they simply don’t have your context.

Almost every founder we talked to described some version of that. Different words, same experience. It made us more certain than ever that the actual product we can offer isn’t advice. It’s someone in the room who understands what you’re carrying and isn’t compromised by their proximity to it.

The second is that the hardest work of running a company is the people work. Specifically the firing. This one came up so often it stopped surprising us. Founder after founder told us they held on too long. They knew something was off, they hoped it would resolve, they didn’t want to have the hard conversation, and by the time they finally acted, the damage had compounded.

Nobody who talked about this said they wish they’d waited longer. Every single person said they wish they’d moved faster. That kind of consensus is rare. When you hear the same regret from fifty different people who otherwise share almost nothing in common, you start to believe it’s a real pattern rather than an anecdote.

The third is that the founder can’t be separated from the company. As one of our guests, Giulia, put it: “I am the nervous system of my business.”

Whatever the founder is carrying, the company is feeling. Anxiety, avoidance, unresolved conflict, unclear priorities. None of it stays in your head. It shows up in your team’s behavior, your product decisions, the culture that grows around you.

This is the theme that hits closest to what we do every day. It’s also the one that founders tend to resist the most, because the implication is that some percentage of the problem is always inside you. That’s a hard thing to hear when you’re already working eighty hours a week and doing everything you know how to do.

But it’s true. And the founders who make peace with it are the ones who tend to make it.

The gratitude part

We want to pause on something that’s not framework and not analysis. Just gratitude.

Every founder who came on the show gave us something. Their time, obviously. But also their honesty. Founders are trained to project confidence. It’s part of the job. Investors want to see it. Employees need it. Customers respond to it. Sitting down with a microphone and telling the truth about the hard parts of the last three years is not something founders are practiced at.

The forty nine people who did it anyway gave us something rare. We’re not going to pretend we’ve done anything heroic by hosting the conversations. The heroism was theirs, in being willing to say the thing they usually don’t say.

For our part, this project has become something we didn’t expect. It started as a way to help founders feel less alone. It’s turned into a way for us to feel more connected to the broader community of people doing this work. Every conversation reminds us why we started Wisdom Partners in the first place. Every episode is a small correction against the myth that founders are supposed to have it all figured out.

The next fifty episodes are going to be more of what’s worked and some things we haven’t tried yet. Deeper dives into some of the themes above with founders who’ve lived them at unusual scale or in unusual industries. We’ve got a full lineup of guests already scheduled and we’re going to keep pushing what these conversations can be.

If you’ve been reading the blog and haven’t listened to the podcast yet, go subscribe. Every episode is a conversation with a founder telling the truth about something the rest of the ecosystem tends to gloss over. It’s the same voice, the same worldview, the same commitment to the honest version of the founder journey that we bring to everything else we do.

You can find Founder Real Talk on Spotify and YouTube. Two to three new episodes every week. If something in an episode resonates, tell us. If you know a founder whose story deserves to be told, send them our way. This show works because founders keep showing up for each other.

Thank you to every founder who’s been part of the first fifty episodes. Thank you for trusting us with the hard parts. There’s a proverb that has meant a lot to us: it is an honor to receive an honest reply. You’ve all honored us and our listeners with your honesty.

Here’s to the next fifty.

Subscribe now

The top-down approach is what most people learned in enterprise. The executive team disappears for a week, comes back with five to seven company goals, and cascades them down. Each layer sets goals that supposedly ladder up to the layer above. It’s clean on paper. In practice, the people closest to the work weren’t consulted. The goals feel handed down. Nobody owns them; they just try to comply with them. And by the time everything cascades through all the layers, the quarter is a third over.

The bottom-up approach sounds like the fix. Ask each team what they think their goals should be. Roll them up. The executive team synthesizes and refines. This is the ideal model in a world with infinite time. In practice, it burns an entire quarter on planning itself. Almost nobody actually does it, and the ones who try usually give up halfway through.

The middle path isn’t a compromise between these two. It’s a different sequence.

The core principle is the one we’ve written about before. [@Luis Pieruzzini - include title and link to this article here.] It’s much easier for you to course-correct the team’s thinking than for the team to reverse-engineer yours. Planning should be designed around that reality.

The full sequence

Here’s what a well-run quarterly planning process actually looks like when you compress it. In practice, this is roughly two working days of actual meeting time, spread across a week to allow drafting in between.

Step 1: The framing group drafts directional guidelines. (Half a day)

Get two or three people in a room who have their pulse on where the business needs to go. This is not necessarily the CEO plus the org chart. It’s the people with actual context, wherever they sit. Sometimes it’s the CEO, a founder, and a senior operator. Sometimes it’s a CEO and a couple of function leads. The composition matters less than the caliber of thinking.

The job of this group is to draft directional guidelines. Not full OKRs. Not target numbers. Just the qualitative priorities for the quarter.

Something like: “Our biggest issues this quarter are increasing retention, growing sales in the enterprise segment, and reducing interest payments on our debt facility.”

That’s it. No percentages. No specific KRs. If you have strong feelings about a specific number, don’t hide the ball, name it. But mostly, this stage is about scoping, not committing. The goal is to give the rest of the organization enough guidance to think clearly, not to hand them a finished plan.

This is the phase where focusing on inputs matters more than outputs. What you produce here is a set of inputs to the team’s thinking. You’ll get outputs back from them in the next steps.

Step 2: Executive alignment on scope and ownership. (Half a day)

Bring in the executive team, or the layer of leaders who own each functional area. Walk them through the directional guidelines. Get their feedback. Refine as needed.

The critical part of this meeting is claiming ownership. By the time everyone leaves the room, each priority has a leader whose name is on it. Not shared ownership. Not “the marketing team.” A specific human who will come back with the OKRs for their area and be accountable for delivering them.

You also want to leave with rough agreement on the guidelines themselves. Not perfect. Rough. The point of this meeting is to give people enough scope to think inside the broad shape of the plan, not to lock the details of the plan.

Step 3: Owners draft OKRs with their teams. (One week, mostly async)

Each executive takes their area of responsibility and drafts real OKRs. Targets, guards, and diagnostics for each priority. (If those terms are new, we wrote about them in “Measuring What Actually Matters.”) [@Luis Pieruzzini include link here.]

For smaller teams, the executive can often just pull three or four people into a room and draft it collaboratively. For larger teams, most managers do this through one-on-ones. They draft, share, iterate. A lot of team members won’t have the context to make good top-down contributions, but they’ll have sharp opinions on the pieces that touch their work.

This step takes about a week. It’s mostly async. The leader is doing the driving.

Step 4: Executive review and dependency mapping. (Half a day)

The executive team reconvenes. Each owner presents their OKRs, what they’re going to achieve, how they’ll measure it, and, critically, what they need from the rest of the company to succeed.

This last piece is the one most companies leave implicit and then regret. If the sales lead’s plan assumes engineering will ship a specific feature by mid-quarter, that dependency has to be surfaced now, in the room, with the engineering lead present to confirm or push back. Otherwise, you’ll discover the misalignment in week eight, and it’ll be too late.

Expect a few iteration loops. The CEO gives feedback. Owners refine. Sometimes, it takes two or three passes across different meetings. That’s fine. What matters is that everyone leaves this stage with OKRs that are actually owned, with dependencies mapped and agreed upon.

Step 5: Publish via all-hands. (One meeting)

Roll out the quarterly plan in an all-hands meeting. The CEO frames the quarter at the beginning and closes at the end. Everything in between is the executives presenting their own OKRs. Not the CEO reading them out. Not the deck someone else built. Each owner gets up and says, “Here’s what I’m committing to, and here’s what I need to make it happen.”

That’s the sequence. Two working days of actual meeting time, spread across roughly ten calendar days. Some drafting and thinking in between. A published plan at the end.

Why the sequence works

The design of this process is doing two jobs at once.

Job 1 is producing a coherent set of quarterly goals. That’s the obvious thing.

Job 2 (less obvious but more important) is producing goals that are actually owned by the people who have to deliver on them. The reason the sequence starts with directional guidelines instead of specific OKRs is that specific OKRs handed down feel like assignments. Directional guidelines that owners then translate into OKRs feel like commitments. Potentially the same content on paper, but a wildly different psychological experience.

The core principle that runs through the whole sequence: you never set the goals in the final form yourself. The goals are always the summarization of what the people who own them decided. Your job is to shape the direction upstream and course-correct downstream. The middle part belongs to them.

How the cadence adapts down the org

The sequence above describes what happens at the top of the company. There are similar mechanics apply as you push it down through the layers, with one important adjustment.

The more junior the employee, the more directive their manager needs to be. A senior VP will draft their own quarterly goals and defend them. A mid-career manager usually needs some framing from their leader before they can draft. A junior individual contributor often needs to be told what the priorities are, not asked what they think they should be.

That’s not a violation of the principle. It’s the principle applied to reality. Ownership requires the context to make good decisions. When someone doesn’t have that context yet, forcing them to invent goals is not empowerment, it’s abdication and lack of support.

The middle manager’s job near the bottom of the cascade isn’t primarily to set goals. It’s to make sure their team has internalized ownership of the goals that got set. That happens in the invitation-to-challenge conversation. “Here’s where we’re going this quarter. You said you want to own X. Here’s what I think success looks like. What do you think? What am I missing?” The lower you go, the more developed of a plan you’re bringing to the person. But you still bring it as an invitation, not a decree.

One more thing to include: The executive hiring test

A useful tell for whether a senior hire is going to work out. When you’re at the final stage of hiring an executive, have them do exactly this planning process for themselves, for their first six months.

Draft directional guidelines. Propose OKRs. Identify dependencies. Present it back to you.

You get three things out of that exercise. (1) You see their analytical thinking. (2) You see whether they actually understand the mission and can translate it into priorities. And (3) when they start on day one, they know exactly what their job is (after you’ve helped them refine their perspective).

That’s more useful than any interview loop.

The bigger point

Most planning processes fail not because the goals are wrong, but because the process didn’t produce ownership.

You can write beautiful OKRs and cascade them cleanly and still end the quarter with a team that never really committed to them. Or you can produce slightly rougher OKRs through a process that made people co-authors of what they’re committing to, and watch the same team overdeliver.

The plan matters, but the way you produce it matters more.

Two days of well-designed meetings, spread across a week, will get you further than a month of the wrong ones. The trick is knowing which meetings actually count and running those well.

Subscribe now

That is not what most employees mean when they say they want autonomy.

What they actually want is the freedom to execute on your vision without having to come back to you for every decision. They want to achieve the outcome you’re trying to achieve, in the direction you’d choose, using the judgment they’d apply if they had your context. What they’re asking for isn’t independence from you. It’s the ability to represent you when you’re not in the room.

That distinction is nearly the whole game. Miss it and you’ll either micromanage a team that resents you, or over-delegate to a team that quietly drifts away from what you actually wanted.

The three layers

Every decision inside your company happens across three layers.

The why. Why are we doing this at all? What outcome are we ultimately after? What’s the mission we’re trying to serve?

The what. What specifically are we going to build or ship or do this quarter? What does success look like? How will we measure it?

The how. What tactics are we going to use? What tools? What sequence? What compromises are we going to make when reality doesn’t fit the plan?

These are not the same layer, and they shouldn’t be owned the same way. Real autonomy is a slope across these three, not a single toggle.

Layer 1: the Why (You drive 80 to 90 percent)

This layer belongs to you.

Your team wants you to own the Why. That’s why they took the job. They want to be part of something bigger than themselves, and they want you to tell them what the bigger thing is. Imagine how they would feel if you show up to the Monday all-hands and say, “So … what do you all think we should be trying to accomplish?” You have not empowered them. You have destabilized them.

They will contribute some to the Why—especially senior leaders, who should have real influence at this layer. But even the strongest senior leader wants to know that the founder has a view, believes in it, and is willing to defend it. A senior VP will happily help refine a Why, but they want it to be a real thing they’re reshaping, not a blank canvas.

The more junior an employee is, the more they want the Why to come from you, whole and unambiguous. This is the layer where founder clarity matters most.

Layer 2: the What (Roughly split: they draft, you refine)

This is where most leaders get it wrong, in either direction.

The command-and-control mistake is to hand your team a fully specified what. “Here are our quarterly goals. Here are the KRs. Go execute.” You’ve saved yourself a week of team-based planning … and destroyed any sense of ownership in the process. Your team is now compliant (hopefully), but not aligned.

The hands-off mistake is to say, “Figure out what we should be doing this quarter.” Then, you get frustrated when they come back with something that isn’t what you had in mind. You didn’t share your view. They aren’t mind readers.

The right move is a feedback loop. You share the Why in specific enough terms that direction is clear. You ask them to come back with What they think the what should be, given that Why. They draft it. You react, ask questions, push back where you disagree, help them see what they missed. You iterate until you’re both aligned.

At the end of that process, they’ve done maybe 60 percent of the driving on the What. You’ve done 40 percent, mostly through course-correction rather than dictation. And critically, they now own the What because they proposed the majority of it, even though your fingerprints are all over the final version.

This is the layer that carries the most weight, because it’s where alignment actually gets tested. If you get this layer right, the layer below almost takes care of itself.

Layer 3: the How (they drive 80 to 90 percent)

Once you’re aligned on the What, the How belongs to them.

You are not the tactician on their function. You hired them because they know things about execution that you don’t, or because you don’t have the time to be in the details. Either way, the How is their zone.

Your job at this layer isn’t to prescribe. It’s to observe. You look at how they’re executing not to correct their tactics, but to check whether their alignment on the What and the Why is actually solid.

Here’s the reframe. When an employee’s How is off, the problem is almost never that they’ve chosen bad tactics. The problem is almost always that you weren’t as aligned on the What or the Why as you thought. Their tactics are the diagnostic. What they choose to do reveals what they think you’re actually trying to accomplish.

If a new sales leader comes back with a hiring plan that focuses on a region you never intended to prioritize, the right question isn’t: “Why are you hiring in the wrong region?” The real question is: “What do we not agree on about where our sales team should focus?” Their How is telling you that your What wasn’t actually shared.

Fix that upstream, and the tactics correct themselves.

The shape of the slope

Put together, autonomy across a healthy leader-employee relationship looks like a curve rising from left to right.

At the Why, they have a voice, but you’re driving. At the What, they draft, you refine, and you converge together. At the How, they’re in the driver’s seat, and you’re watching for signal.

That’s the slope of autonomy. That’s what employees mean when they say they want autonomy. Not independence from your direction. Ownership over the parts of the work where their expertise is the point.

The founders who get this right report something interesting once it clicks. Their team starts spending real cognitive effort building a mental model of them. What would the founder say about this? How would they weigh these two options? What would they push back on? It’s like your personal chatbot within their minds.

Your team is doing this whether you want them to or not. Most founders don’t realize how much of their team’s time gets spent on this specific kind of prediction. The move is to shape that prediction deliberately, so the version of you living in your team’s heads is accurate enough to answer questions when you’re not there.

That’s the actual mechanism of scaled leadership. Not more meetings. Not more oversight. A team that can predict your judgment because you gave them enough alignment to build a working model of it.

The slope is a diagnostic. Wherever your team feels stuck, look at the layer before and ask whether you actually did the alignment work there. Almost every time, the answer is that you didn’t do enough of it.

Build the slope. The autonomy follows.

Subscribe now

That’s the entire craft of coaching in 20 seconds.

When you’re advising a founder or an executive, the temptation is to give them the answer. You’ve probably seen this problem before. You have a view. It would be faster to just tell them what to do. And sometimes that’s the right move. But most of the time, the version of the answer they arrive at themselves is more useful than the version you hand them, even when the content is identical.

The reason is simple. An answer you’re given is information. An answer you arrive at is understanding. The first one you follow. The second one you own.

The mechanics of coaching through questions

The move isn’t to pretend you don’t have a view. You often do have a view, and that view is exactly what should be driving the conversation. The trick is to use it to shape the questions, not to shortcut past them.

If you think a founder is undervaluing their product, you don’t say “you’re undervaluing your product.” You ask, “What’s the highest price you’ve ever heard a customer object to?” … and then “What happened when they objected?” … and then “How many of those customers still bought?” You’re guiding them toward the conclusion you already reached, but they’re doing the reasoning. When they arrive, they arrive with conviction because they built the argument themselves.

The compliment above is the giveaway that this is working. The founder feels like they figured it out. In some real sense, they did. What you contributed was the direction of the inquiry, not the answer at the end.

Most people who try to coach skip this step. They see the answer and jump to it, and the person on the other side of the table complies but doesn’t internalize. Six weeks later, the same problem is back in a slightly different form.

The same skill makes you effective with AI

Something interesting has happened as language models have gotten better. The people who get the most out of them are the people who already had this skill from coaching or leadership. The parallel is almost exact.

If you sit down at ChatGPT or Claude and tell it exactly what you want it to produce, you’ll get something reasonable. You’ll also get roughly what you were already thinking. The model is doing a competent job of predicting the output that fits the request you gave it. You’ve used it as a smart typewriter.

If instead you ask it good questions, you’ll often get answers that are better than what you were thinking on your own.

As a concrete example, Charles was working on a customer development pitch deck. The first pass from the model was flat. It missed the customer pain points that mattered most. The easy move would have been to say, “No, do it this way instead,” to describe what he already had in mind, and get back a deck that matched his existing thinking.

Instead, he asked the model a question: “What the customer actually cares about is X and Y. How would we design a deck that solves for those?”

The response came back with features and framings he hadn’t considered. Some of them were better than what he’d been thinking. The model didn’t just validate his direction. It extended it.

Why the question format beats the instruction format

There are two reasons this works.

The first is that questions activate the model’s reasoning in a way that instructions don’t. When you tell a model, “Write me a section that says X,” it optimizes for producing X. When you ask it “Given these constraints, how would you approach X?”, it has to reason through the constraints and generate an answer. This often surfaces considerations you didn’t know to include.

The second reason is the sycophancy problem. Large language models are trained to be helpful, which often means trained to be (overly) agreeable. If you tell the model your view and then ask it to help you execute on that view, it will mostly agree with you because agreement is what it’s rewarded for. You’ve built a fancy echo chamber.

Questions cut around this. When you ask the model to reason through a problem rather than execute on your conclusion, you get less flattery and more actual thinking. It’s the same reason a good coach asks questions rather than validating. Validation is comfortable. Thinking is useful.

The practical implication

Most founders using AI tools are getting a fraction of the value available to them, because they’re using the tools the way they’d brief a junior employee. They give it instructions. They accept what comes back. They edit for polish. This is helpful, but not transformative.

The expert move is to treat the model more like a peer with whom you’re thinking out loud. Actually talking to the model with the voice-to-text function helps create this more natural dialog. Describe the situation. Describe what you’re trying to solve for. Ask how it would approach the problem. Ask what considerations you might be missing. Ask what a smart person who disagreed with your framing would say. Ask what you’d need to be true for your current plan to fail.

Every one of those questions produces a better response than: “Write me a plan for X.”

The same is true of your team. The same is true of your board. The same is true of yourself.

The people who get the most out of any thought partner, whether human or machine, are the ones who learned to ask before telling. That skill compounds across every high-stakes conversation you have. It’s worth developing on purpose.

Because in a world where information is cheap and answers are everywhere, the differentiating move is knowing which questions to ask. That’s true whether you’re sitting across from a founder or opening a new chat window.

Subscribe now

• Should I raise another round?

• Should I replace my cofounder?

• Should I take the acquisition offer?

• Should I hire the executive?

• Should I keep pushing for growth, or slow down before my family pays the price?

But after years of working with founders, I’ve come to believe these aren’t primarily business decisions.

They’re leadership decisions.

And leadership decisions are rarely just business decisions. Every significant decision a founder makes is shaped not only by market conditions, financial projections, and competitive strategy, but also by fear, ambition, identity, relationships, values, the kind of life they hope to build, and the kind of world they want to help create.

That’s why the hardest founder decisions rarely feel straightforward. They’re tensions to navigate.

What founders actually ask for

People don’t usually come to Wisdom Partners saying they want better judgment.

Instead, they say things like:

• “I’m stuck between two bad options.”

• “I can’t tell whether I’m fooling myself.”

• “I don’t know who I can trust.”

• “My board wants one thing, but my gut says another.”

• “I think I’m becoming the bottleneck.”

• “I don’t know whether to raise, sell, or keep going.”

• “Everything feels blurry.”

On the surface, those sound like different problems, but they’re all moments when the stakes are high enough that thinking clearly becomes difficult.

The founder’s real challenge

Recently, I worked with several founders whose situations couldn’t have looked more different.

One wanted help creating an ownership culture so she could stop being the bottleneck in two growing companies. As we worked together, it became clear that the deeper question wasn’t organizational design. She wanted to build a company that wouldn’t consume the life she hoped to create as she prepared to become a mother.

Another founder came to us after losing a cofounder in the middle of fundraising. We spent plenty of time discussing strategy, but what he needed most was someone to think with as he carried the weight of leading alone.

A third founder wanted help preparing for the next stage of growth. We talked about strategy, but we also explored how his own assumptions, pace, and patterns of thinking were quietly shaping the company’s future.

Different industries. Different companies. Different questions. Yet the work was remarkably similar.

None of these founders lacked intelligence. None lacked information. All had capable advisors. What they needed was a trusted partner who could help them think clearly when business strategy, leadership pressure, and personal consequences became impossible to separate.

Better decisions require better judgment

People often ask whether Wisdom Partners provides coaching, consulting, or executive advising. Those sorta-kinda describe the format of the work, but not its purpose.

The purpose is to help founders make better decisions when the stakes are highest. We believe the way to do that is by strengthening judgment.

By judgment, I don’t mean instinct or intuition alone. I mean the ability to perceive reality clearly, weigh competing priorities, recognize tradeoffs, and make wise decisions under conditions of uncertainty.

The hardest founder decisions rarely come with clear answers. They require balancing short-term and long-term consequences, company needs and personal values, courage and caution, conviction and humility.

Pressure makes those decisions even harder. Urgency, uncertainty, responsibility, and isolation narrow our perspective, making it difficult to distinguish what is really true from what merely feels true.

No framework can make those decisions for you. No AI model can fully understand your context. Even as decision-making becomes more distributed, the founder’s judgment continues to shape the company’s highest-consequence decisions—and the culture in which everyone else makes smaller decisions.

How judgment grows

Founders face a difficult paradox. Good judgment is developed through experience and reflection. But surviving long enough to gain that experience requires enough judgment to navigate the hardest decisions along the way.

Developing good judgment is never finished. It grows through disciplined examination of difficult decisions and thoughtful partnership. That often means slowing down long enough to ask questions that are easy to miss when you’re operating at startup speed.

• What assumptions am I making?

• What is the forest I am not seeing because I’m surrounded by trees?

• What fears or ambitions might be distorting my perspective?

• What are the immediate, longer-term, and second-order consequences of this decision?

• Which option best aligns with the kind of company—and the kind of leader—I want to become?

We talk about all kinds of things with founders. Sometimes we discuss fundraising. Sometimes hiring. Sometimes organizational design. Sometimes conflict. Sometimes the conversation is deeply personal. More often than not, it’s all of those at once.

Authenticity and empathy create the trust required to examine difficult decisions honestly. Business experience keeps those conversations grounded in the realities of building a company. Together, they create the conditions for better thinking when it matters most.

Why this matters

As information, strategic frameworks, and AI-generated recommendations become increasingly accessible, actual judgment becomes even more valuable. In fact, good judgment is your most valuable asset as a founder. In many ways, your shrewd judgment is what you and your investors are betting on. (Judgment is the new moat.) The problem is that judgment gets clouded under pressure and entangled with all kinds of internal and external variables.

Technology can expand our options. Capital can accelerate growth. Talent can improve execution. But leaders still decide what to pursue, what to ignore, what to change, what to protect, and when to act. Those are judgment calls. They are immensely important, and they compound over time.

Small improvements in judgment don’t simply produce better individual decisions. They influence the people you hire, the culture you create, the risks you take, the opportunities you recognize, and ultimately the kind of company you build.

The work of Wisdom Partners

For years, I described our work as founder coaching. Today, I think there’s a better description.

Wisdom Partners exists to be the trusted thought partner founders turn to when the stakes are highest. When the biggest decision of your year arrives, you shouldn’t have to think through it alone. When the heat is highest, you want us in your corner.

You need someone who understands the realities of building companies, who genuinely cares about you as a leader, and who can help you see through the clouds of intense pressure. Better judgment is the result. Better decisions follow.

Because founders don’t have business problems and personal problems. They have leadership challenges that appear in both places.

And the leaders who learn to navigate those moments with wisdom don’t just build stronger companies. They build companies that contribute to lives worth living—for themselves, their teams, and the people they serve.

Subscribe now

The framework we use for this comes from Stephen Covey, who introduced it in The 7 Habits of Highly Effective People under Habit 1: Be Proactive. He called them the Circle of Concern and the Circle of Influence. Later leadership writers expanded it into a set of concentric rings, which is the version we teach because it maps more cleanly to how a founder’s day actually looks.

The idea is simple. Lots of things affect you. You don’t have a corresponding ability to affect all of them. Most people spend their emotional energy in inverse proportion to their actual leverage.

Here’s what the circles look like, from the inside out.

Most influence: your thoughts, attitudes, and actions

The innermost circle is you. What you think. What you feel. What you do. This is where your leverage is highest and where, paradoxically, most founders spend the least time.

Even here, control isn’t total. Nobody controls everything they think. Nobody controls every reflex reaction to a hard email or a bad meeting. The self-aware founder controls more than the reactive one, but nobody controls all of it. Triggers are called triggers for a reason.

But you have more control here than anywhere else in your life. You can change how you frame a setback. You can change what you decide to focus on tomorrow morning. You can change how you show up in a hard conversation. You can decide whether to send the email or sleep on it.

Most of your leverage lives here. Most founders barely tend to it.

Some influence: family, team, business, health

The next circle out is where you have real but partial influence. Your immediate family. Your friends. Your co-workers. Your home. Your business. Your health.

Your business belongs here, not in the innermost circle, and it’s worth pausing on that. You don’t fully control your business. You influence it heavily. You decide what to build, who to hire, how to spend, what to say yes and no to. But customers make their own decisions. Team members make their own decisions. Investors make their own decisions. You are the largest single influence on your company, and you are still not in control of it.

Same for health. You control what you eat, how you sleep, whether you exercise. You do not control cancer. You do not control accidents. You optimize possibilities. You never eliminate risk.

This is the second-highest leverage zone. If you’re doing the work in the innermost circle, this is where most of the visible output shows up.

Minimal influence: extended family, neighborhood, government

The next ring out is where you have some influence but not much. Your extended family. Your neighborhood. Your local government. Your industry ecosystem.

You vote. Sometimes your candidate wins. Sometimes they don’t. You can pick up trash on your street. You can’t paint your neighbor’s house. You can attend a founders’ meetup. You can’t rewrite how your city funds infrastructure.

Founders often get pulled into this ring by frustration. The industry should be different. The city should support startups better. The tax code should favor small companies. All might be true. None of it is where your leverage sits.

Contributing to change at this level can be meaningful and worthwhile. It should not be where most of your attention lives.

Almost no influence: macro trends, the economy, the climate

The outermost ring is where you have almost no influence at all. The price of oil. Interest rates. The venture funding climate. The broader economy. Weather. Climate. War and peace. The general vibe of the market.

You have some second-order influence. You recycle. You vote. You choose what to consume. Your individual actions do matter in an aggregated sense, and you should still do them. But the amount of attention founders spend here (in the form of anxiety, reading, doomscrolling, and comparing themselves to a market they can’t control) is wildly disproportionate to their ability to move anything in it.

This is the ring where founder attention gets destroyed the fastest.

Where founders actually lose the game

The specific application to founder life is worth calling out.

You cannot control the venture landscape. You cannot control whether capital is loose or tight this quarter. You cannot control which competitor closes a round next week or how much they raise or which fund led it. You cannot control interest rates, the IPO market, or whether the AI hype cycle inflates or pops.

The number of founder hours lost each year to obsessing over these things is staggering.

What you can control is your pitch deck. Your product. Your sales process. Your team. What you spend time on tomorrow morning. The email you send tonight. The conversation you have with your co-founder about what’s actually working. The people you choose to spend your remaining attention on.

Every hour you spend refreshing TechCrunch is an hour not spent on the circle where you have leverage.

The reframe

This is an attention allocation problem. If you spend 70% of your attention on the outer rings, you get almost no return on it, because your leverage there is close to zero. If you spend 70% of your attention on the innermost two rings, you get most of the possible return, because your leverage there is high.

Same amount of energy. Radically different outcomes.

The founders who endure are those who figure this out. They stop trying to control the macro. They stop measuring themselves against news headlines. They let the ecosystem be the ecosystem and put their finite attention into the tight core of things they can actually move.

That doesn’t make the outer rings go away. The economy still shifts. Competitors still raise. Markets still turn. All of that keeps happening whether you obsess over it or not.

The question is whether your response to those things is going to come from a place of leverage or from a place of reaction.

Focus on the center. Let the edges do what they’re going to do.

Subscribe now

You have eight to twelve productive hours in a day. The question is which of those hours are you doing the work that only you can do, and which are you doing work that is quietly draining you while producing very little. Most founders can’t answer that cleanly. Until you can clearly identify which work produces the best returns, no amount of productivity hacking is going to help very much.

The framework we use for this comes from Dan Martell’s book Buy Back Your Time. If you haven’t read it, it’s worth the time and money. The core tool is a simple 2x2 that maps everything you do against two axes: how much money it makes you, and how much energy it gives you.

Every task in your life sits somewhere on this grid. Where it sits tells you what to do with it..

The delegation zone: the easiest place to start

The bottom left is where most founders should start because it has the lowest stakes and the highest immediate payoff.

The rule is simple. If a task drains you and doesn’t produce revenue, either delegate it, automate it, or stop it entirely.

The elimination path is underrated. Lately, I have been unsubscribing from newsletters I kept “meaning to read” that just built emotional debt in my inbox. If you’re not reading it and it isn’t valuable most of the time, unsubscribe. The same principle applies to meetings that no longer need to exist, reports nobody reads, and processes that persist because nobody bothered to kill them. Cutting is often better than delegating because delegating still requires oversight.

The delegation path is where most founders leave money and hours on the table. The reason is usually that they haven’t tried, or they tried once with a bad hire and gave up.

The virtual assistant unlock

The single highest-leverage move for most founders in the delegation zone is hiring a virtual assistant. Even part-time. Even ten hours a week.

Here’s what it actually looks like in practice. You get an idea for something you want to send out. Normally you’d sit down and spend an hour and a half writing it, formatting it, finding the right people to send it to, personalizing the send. Instead, you spend five minutes explaining the idea to your VA. They come back with a draft that’s 80 to 90% of the way there. You spend fifteen minutes polishing. Total time from you: twenty minutes instead of ninety.

That’s a 4x multiplier on your output for the same amount of your time. Sometimes it’s 10x, depending on the task.

The math gets more interesting when you consider what you do with the freed hours. If you spend them in the production zone, you’re compounding the value. If you spend them on sleep, exercise, or family, you’re compounding a different kind of value that turns out to matter just as much for whether you last as a founder.

We’ve placed fifteen to twenty VAs from Latin America for founders in our network. Why do we recommend LATAM specifically?

• The time zones are close to US business hours

• The cultural context is closer to a US working environment than most alternatives

• The English quality is often stronger than what you get from Eastern Europe or Asia.

• Rates typically run $8 to $15 an hour depending on the level of the role.

The roles range widely. Straight administrative VAs. Video editors. Customer service. Business operations. Sales development. Whatever’s sitting in your delegation zone is likely something you can hire someone in LATAM to do for a fraction of what a US hire would cost, and often at a higher quality than you’d expect.

If this is something you want to explore, talk to our team here. We’ll help you scope the role, figure out what to hand off first, and match you with someone from our network.

The replacement zone: the harder work

Once the delegation zone is under control, the harder work begins.

The replacement zone is where founders get stuck. This is the top-left quadrant, the work that makes money precisely because you do it. Maybe you’re the best salesperson in the company. Maybe you built the marketing engine, and it runs on your intuition. Maybe your product intuition is the reason the roadmap doesn’t drift.

The instinct here is to hold on. “Nobody else can do this as well as I can” is technically true and strategically fatal. If the work drains you, holding it means you’ll eventually burn out while doing good work for your company. That’s a worse outcome than an imperfect handoff.

The move is replacement, not delegation. The distinction matters. Delegation is handing off a task and letting the person run with it. Replacement is a slower, deliberate transfer. You document your process, you train someone into it, you stay closely involved during the handoff, and you gradually pull back as they demonstrate competence.

One founder in our network was a marketing genius who decided to hand off marketing entirely. She hired a fractional executive, briefed her, and stepped away. Months later she realized the fractional exec was operating out of alignment with the company. Not because the hire was bad, but because the handoff had been too fast. The job wasn’t just tasks. It was judgment calls the founder had been making implicitly, and nobody had captured them explicitly.

The fix wasn’t to fire the executive. It was to re-engage. Regular check-ins. Explicit conversations about brand voice, positioning, priorities. Slower transfer. What she called delegation had actually needed to be replacement.

If the work makes real money for the company, don’t just hand it off. Replace yourself out of it. That means SOPs, close oversight, and a gradual widening of the trust zone as the new owner earns it.

The order of operations

Most founders try to do this backwards. They obsess over their production zone (which usually doesn’t need optimization because it’s already working), procrastinate on their replacement zone (which is the hardest), and let their delegation zone fester (which is the easiest to fix and the fastest to pay off).

The right order is the opposite. Start with the delegation zone. Get the drain off your plate first. Use the reclaimed hours to properly set up the replacement zone. Protect the production zone with everything you have. Don’t neglect the investment zone because it’s what keeps you functional over the long run.

The whole framework is a tool for one question? Are you using your time wisely?

Most founders find out, when they honestly map it, that the answer is no. And that gap between where their time is and where it should be is where the leverage lives.

Subscribe now

They’re comparing.

There’s a specific kind of comparison problem founders fall into, and it’s the most common psychological tax in startup life. The myth is that the only successful outcome is the unicorn outcome. Anything less than a billion-dollar valuation is a participation trophy.

This is wrong on two levels. It’s wrong about what makes a successful business, and it’s wrong about what changes your life.

The math nobody talks about

Run the numbers on a few exit scenarios and the unicorn obsession starts looking strange.

You hold 30% of a company that exits for $10M. You take home $3M.

You hold 30% of a company that exits for $50M. You take home $15M.

You hold 30% of a company that exits for $150M. You take home $45M.

Now ask the honest question. Is your life meaningfully different at $15M versus $45M? At $3M versus $15M? At any point along this curve, you’ve crossed into territory most people will never see in their lifetime. You’ve solved the question: “Do I ever have to work again?” You’ve solved your kids’ college, your parents’ retirement, your own peace of mind.

The marginal value of additional millions past a certain threshold is real but small. The marginal cost of chasing them, in years of your life, in stress, in time with the people you love, in health, is not small. It’s often enormous.

A $20M exit, the kind that gets zero headlines and doesn’t make anyone’s “founder to watch” list, lands you $6M if you held 30%. Most people would call that winning the lottery. Founders chasing unicorns somehow file it under failure.

Why this myth persists

Rob Walling at Tiny Seed Capital and the excellent podcast Startups for the Rest of Us, have been making this argument for years. A $10M or $20M or $50M exit can be fundamentally life-changing for a founder. They’re right.

But the louder voices in the ecosystem are big venture funds, whose business model only works if a small number of their bets become enormous. They need unicorns. Their math literally doesn’t function without them. So the narrative they push, intentionally or not, is that the only outcome worth pursuing is the unicorn (which coincidentally lets them return their fund).

That narrative is correct for them. It is often wrong for you.

You are not a venture fund. You don’t need a portfolio of bets where one wins and the rest die. You need one company. You need it to work. And “work” can mean a lot of things that don’t involve being on the cover of Fortune or Inc.

The comparison tax

There’s a second cost to chasing unicorns, beyond the math. It’s the constant low-grade misery of measuring yourself against outcomes that were never available to you in the first place. LinkedIn is to founders as Instagram is to teenage girls. It can foster unhealthy comparisons.

Your business is different. Your market is different. Your timing is different. Your team is different. The founder who raised $50M last quarter is solving a different problem in a different market with different investors and a different cap table. Their fundraise tells you almost nothing about whether you should be raising, what you should be raising, or whether you’re succeeding.

And yet most founders compare anyway, because comparison is the default human response to ambition. Don’t stop being ambitious; just be ambitious about the right thing.

What ambition can look like instead

None of this is an argument for being unambitious. If you’re a missionary founder who genuinely needs to see this thing through, who’s trying to solve a problem at massive scale, who would rather die on the hill than sell early, that’s a real and respectable path. Build the unicorn. Some people are wired for it, and the world is better for them existing.

This argument is against chasing unicorns by default. Against assuming that because the headline outcomes are the unicorns, the only outcome worth pursuing is one.

The alternative is to build a real business. A company that becomes profitable. A company that compounds over time. A company that, if it never gets acquired, you’d still be glad to be running in ten years. A company where your life is sustainable, where you’re not destroying yourself to hit the next milestone, where the work itself is the point.

If that company grows into something acquirable, great. If the right offer comes along at the right time, take it. $20M, $50M, $100M. Any of these probably changes your life. None of them will get your name on a billboard, and that turns out to matter much less than founders think.

The reframe

Stop chasing unicorns just because everyone else is. Stop assuming the only valid exit is the one that gets headlines. Stop measuring your trajectory against companies that got lucky in a different market at a different time.

Build the thing that makes sense for you. Build it in a way that doesn’t break you. And when an outcome arrives that would change most people’s lives forever, recognize it for what it is.

Winning doesn’t always look like a unicorn. Most of the time, it looks like a real business that quietly made its founders wealthy and their customers better off. That’s the actual game.

Subscribe now

His piece is worth reading in full. The data is striking. Salaries for specialized AI trainers have climbed past $180K at the top end. Demand for these roles has grown more than 150% in two years. As the machines got smarter, the value of human expertise went up rather than down.

The line from his piece that stuck with me most: “You can scale the production of answers. You cannot scale taste.”

I want to take Gangesh’s argument and apply it somewhere specific. If human judgment is the scarce input for training the most advanced AI systems on the planet, what does that say about the messier, higher-stakes problem of running a company?

The encyclopedia problem

Here’s how I think about using AI as your business advisor.

In 1985, having an encyclopedia at home was a real advantage. You could look things up. You could answer questions your neighbors couldn’t. It was a genuine information edge.

By 1995, every middle-class household had one. By 2005, physical encyclopedias had mostly migrated to software. By 2015, Wikipedia made the entire genre obsolete. The encyclopedia didn’t get worse. The moat just evaporated, because everyone had it.

That’s where AI sits in 2026 as a business advisor. ChatGPT and Claude can give you a credible answer to almost any general business question. They can frame your strategy. They can pressure-test your reasoning. They can role-play an investor objection or draft a board update. All of that is genuinely useful, and you should be using these tools.

But it isn’t a moat. Every founder you’re competing with has the same tools. The same access to the same models. The same ability to ask the same questions and get the same well-reasoned, slightly-too-polished answers.

If your competitive edge is “I regularly use an LLM,” you don’t have an edge.

What AI cannot do for you

A model can tell you what other founders in your situation have done. It can synthesize the conventional wisdom. It can list the seven frameworks for thinking about your hiring problem. What it cannot do is look at you, in your specific moment, with your specific blind spots, and tell you which framework is actually wrong for you. It also can’t tell if you’re not really being honest with yourself or with it.

That requires three things AI doesn’t have:

1. It requires reading the room. Not the room in a strategy doc, but the actual room. The way you said something, the thing you didn’t say, the place you got defensive. A good coach catches the half-sentence you backed away from.

2. It requires having watched a hundred other founders navigate the same problem and remembering which ones got it right and which ones flamed out, and why. That’s pattern recognition built from experience, not from training data.

3. And it requires the willingness to disagree with you in a way that actually lands. AI is trained to be helpful, which often means trained to be agreeable. A coach worth paying for is willing to tell you that you’re wrong, and to keep telling you until you actually hear it.

The deeper thing

There’s something even harder to name that gets lost in this conversation, which is that humans only get really honest with other humans.

I sit across from founders every day. The things they actually need to work on, the real questions underneath their stated questions, almost never come out in the first five or even 20 minutes. They come out when there’s enough trust in the room that the founder is willing to stop performing competence.

The moment someone stops performing and starts actually thinking (with both the mind and the heart) is the moment coaching becomes valuable. And it doesn’t happen with a chatbot. It happens with another human, present, paying attention, who has earned the right to ask the next question.

This is simply how humans are built. We’re a social species. Our deepest cognition happens in dialogue with other humans we trust. You can simulate a form of that with AI. You cannot replicate the impact.

What this means for you

Gangesh’s bet is that the next decade goes to companies with the best people wielding the tools, not the ones with the most tools. I think that scales down to the individual founder too.

The AI tools are a commodity. You have them. So does your competition. The differentiator now is the judgment you bring to using them, which is itself sharpened by working with people who have judgment sharper than yours.

Use the tools. Use them aggressively. Let them handle the analytical, repetitive, synthesize-able work so you have more bandwidth for the work that actually moves your company forward.

But don’t confuse access to information processing power with access to wisdom. They’re not the same thing. They were never going to be the same thing. The data is now confirming what the best founders already knew.

The machines are getting smarter. Your need for a real human across the table is getting more important, not less.

Subscribe now

It’s useless because most of the work people do every day looks like effort, not outcome. Calls made. Code committed. Features shipped. Meetings held. Documents drafted. If you only measure the outcome and pretend the work doesn’t exist, you can’t tell whether your team is on track until the quarter ends and the number is already in. By then it’s too late to do anything about it.

The honest version of the advice is more useful: measure outcomes primarily, but build the rest of your dashboard to explain why the outcome is or isn’t happening.

The framework we use breaks every metric a team owns into three buckets: Targets, Guards, and Diagnostics. Each does a different job. Get the split right, and you have a real operating system. Get it wrong, and you end up with either a vanity dashboard or a guilt trip

.

Targets: the outcome you’re actually trying to produce

A target is the metric that shows you won. It has to be objectively measurable. It has to be the thing itself, not a proxy for the thing.

A sales team’s target is not calls made, or even “qualified meetings held with prospects who showed up.” It’s dollars and deals closed. A growth team’s target is not “campaigns shipped.” It’s “new users retained at 30 days.” An engineering velocity team’s target is not “commits per week.” It’s “features shipped that either turned up because they worked or turned off because they didn’t, with the learning captured.” The distinction sounds pedantic until you watch teams hit their proxy metric for four quarters in a row while the actual outcome flatlines.

The rule for choosing a target: if a robot could maximize this number without producing the result your business needs, it’s the wrong target. Calls made can be maximized by dialing nonsense. Qualified meetings can basically be bought. Dollars closed is the real thing.

Targets should be small in number. Two or three per team is usually right. The instinct to add more is almost always wrong. Every additional target dilutes focus on the ones that matter most.

Guards: the boundaries that keep the target from becoming a loophole

The reason most outcome metrics fail isn’t that they’re wrong. It’s that they create incentives to game them.

If your target is four qualified meetings (for a BDR team), a rep might book fourteen meetings of which only four are qualified, hit the number, and call it a week. The target was met. The system was abused. That’s where guards come in.

A guard is a boundary you’re not allowed to cross. “Qualified meetings must be at least 60% of all meetings booked.” “No more than two no-shows per week.” “Customer churn below 5%.” “Bug count not rising quarter over quarter.”

Guards protect quality, efficiency, and the integrity of the target. They’re the answer to the question: “What would have to be true alongside this target for it to actually mean we’re winning?”

Most teams skip guards entirely and then wonder why hitting the target didn’t feel like winning.

Diagnostics: the activity metrics, in their proper place

This is where most of the work-done numbers belong. Calls made. Hours logged. Outreach sent. Lines of code committed. Cycle time. Lead response time.

Diagnostics aren’t goals. You don’t hit them or miss them. Their job is to tell you why the target is or isn’t moving. If qualified meetings are down this week, diagnostics tell you whether the problem is too few calls (an activity problem) or the same calls converting at a lower rate (a quality or targeting problem). One requires more effort. The other requires better aim. The diagnostic is what tells you which.

You can have as many diagnostics as you want. They cost almost nothing to track and they make the targets legible. The mistake to avoid is letting any diagnostic creep into your performance review and become a target by accident. Once “calls per week” becomes something the team is evaluated on, it stops being a diagnostic and starts being a number that gets gamed.

The trickier cases: roles where the outcome is hard to name

Sales is easy. Dollars closed is the target. Marketing is usually easy. Pipeline generated, attributed to specific channels.

The harder cases are the ones where the output isn’t directly tied to revenue. Engineering. HR. Operations. C-suite roles like CTO or COO.

The move for these roles is the same; it just requires more thought. Find the outcome that, if achieved, would mean the function is doing its job. For a CTO, that might be “ship the three roadmap features in the quarter, with uptime above 99.9% and bug count not increasing.” Target: three features shipped. Guards: uptime threshold, bug count ceiling. Diagnostics: average time to close a bug, deploy frequency, on-call alert volume.

For an HR function, the target might be “key roles filled within X weeks of opening, with first-year retention above Y%.” For ops, “monthly close completed by the fifth business day with no material errors.” None of these are revenue numbers. All of them are outcome numbers, in the sense that achieving them means the function did what it was supposed to do.

The trick is to stop looking for the exact equivalent of a sales quota and start looking for the result the function exists to produce.

One last principle: Keep the list short

Cascading goals down to every level of the organization sounds great in theory. In small companies, it’s usually a mistake.

A small company runs on focus. Two or three top-level targets that everyone is aware of and working within will outperform a system where every team has its own pyramid of objectives rolling up to the company OKRs.

Cascading becomes useful once you’re large enough that teams can actually operate independently on different problems. Until then, a few focused goals, with everyone pulling in the same direction, beats a complete OKR architecture every time.

The bigger principle underneath all of this is that measurement is itself a design problem. Every metric you choose is a behavior you’re incentivizing. Every metric you don’t choose is a behavior you’re either tolerating or trusting to take care of itself.

Targets define the win. Guards keep the win clean. Diagnostics explain the score. Get those three buckets right, and you’ll finally be doing more than just looking at numbers.

Subscribe now

The question we wanted to answer: how does a founder actually move beyond founder-led sales? Most founders try and fail. The pattern is pretty consistent. They hire an account executive, set a quota, and six months later the AE is frustrated, the founder is back doing sales, and twelve months of payroll have evaporated.

Step 1: Realistic Goal

Most founders hire a salesperson with an expectation calibrated to themselves. They’re closing one deal a week, so they expect the new hire to close one a week too. That’s the first mistake.

When you, the founder, pull in a lead a day through LinkedIn, that’s happening because of who you are. You’re the founder. You have title authority. People take meetings with you that they wouldn’t take with a junior account executive.

If you hand the new hire your outbound process and hold them to your numbers, you’re going to be disappointed. Their conversion will be lower. Their lead flow will be thinner. That doesn’t make them a bad hire. It makes the expectation wrong.

The fix is to start at the desired outcome and work backwards. If you want this person closing $300K in sales in their first year, what does that actually require? How many calls? How many meetings? How many leads in the top of the funnel? What’s a realistic ramp? Is the quota a fair reflection of what the data says is achievable for someone with their experience, in your market, with the resources you’re giving them?

Skip this step, and the whole hire is built on a number you made up.

Step 2: Enablement

This is one most founders underestimate, and it’s where most sales hires actually fail.

When you hire a salesperson, you’re not just paying their salary. You’re also signing up to buy the entire infrastructure they need to do the job. A CRM (Customer Relationship Manager) if you don’t have one. Marketing materials. A repeatable outbound methodology. Tools to find and enrich your ICP (Ideal Client Profile). LinkedIn Sales Navigator. Maybe a marketing partner. Maybe a couple of BDRs (Business Development Representatives)feeding them leads.

The reason this matters: a salesperson’s KPI (Key Performance Indicator) is the act of speaking to a prospect. Demos, discovery calls, presentations, actual conversations. If they’re spending their day building lists, writing cold email templates, and figuring out CRM workflows from scratch, they’re not selling. They’re doing the work you should have done before you hired them.

When you send a rep out to sell your product or service, they should be able to explain that client’s value proposition to their grandmother. They need to make it simple and non-technical. That requires real onboarding. Real materials. Real conversations with existing customers so the new hire knows what good looks like.

Step 3: Purpose, Motivation, and Direction

The third piece is the part most founders eventually grow into, but rarely start with. The US Army teaches leaders to clarify purpose, motivation, and direction.

The salesperson needs to know why they’re selling what they’re selling. They need a reason to push through rejection, because sales is a job lived in rejection. And they need direction when they hit something they haven’t seen before.

This is the leadership piece. The piece you can eventually delegate to a head of sales, but at the first-hire stage, it’s the founder’s job. You’re the one who knows why this company exists, why this product matters, and what good looks like when things go sideways.

If you’ve nailed steps one and two, step three is what unlocks performance. If you’ve skipped steps one and two, no amount of inspiring leadership saves the hire.

Inbound or outbound? Hunter or farmer?

A quick aside before the punchline. Founders also need to be clear about what kind of salesperson they’re hiring. Inbound and outbound sales are different jobs that happen to share a title.

An inbound salesperson is closer to a customer success role. People are already interested. The work is helping them understand how the product solves their problem. It’s a farmer’s job.

An outbound salesperson is a hunter. They have to convince people who weren’t thinking about your product to give you twenty minutes. That requires a totally different temperament and skill set.

The diagnosis is simple. Wake up tomorrow and check your inbox. If you have three prospective leads waiting for you, you probably need a farmer. If you have to beat the bushes to get a single meeting, you need a hunter.

Most early-stage companies need a hunter, but they hire a farmer because farmers are easier to find and cheaper to pay. Then, they wonder why pipeline isn’t growing.

The mistake most founders make

Most founders hire a driver and then tell him to build his own car to race in NASCAR.

That move almost never works. The driver is good at driving. He’s not a mechanic. He’s not a pit crew. He’s not the team owner. If you hand him a pile of parts and tell him to figure it out, you’re going to lose the race and the driver.

A better approach is to build the car first. Or get help building it. Learn how to drive it. Get the foundation in place. Then, hire the driver who can actually race.

In practical terms, that usually means starting with the business development side of the operation before you hire a closer. Get a BDR or two seeded, get the lead flow stabilized, get the CRM and the materials and the outbound methodology working. Then bring in the account executive whose job is to take the meetings that BDR motion creates.

The honest version

Hiring your first salesperson is one of the most expensive decisions a founder makes. It’s not just the salary. It’s the year of opportunity cost while you find out whether the hire is going to work, plus the additional cost of all the enablement you didn’t realize you needed.

The founders who get it right do three things. They set an outcome that’s actually achievable for someone who isn’t them. They build the foundation that makes the role winnable. And they provide the purpose and direction that turns a competent salesperson into a committed one.

The founders who get it wrong skip straight to the hire and hope.

Hope is not a sales strategy.

Subscribe now

The standard founder response is to open a spreadsheet. Make a list of every function in the business. Assign a name to each one. Send it around. Done.

Six weeks later, the same things are still falling through the cracks. The spreadsheet doesn’t fix anything because the spreadsheet is a top-down assignment. You’re declaring ownership instead of building it. And declared ownership doesn’t stick.

The opt-in problem

Real ownership has to be chosen, not assigned. If you tell someone, “You own customer support now,” what you’ve actually done is give them a new task on their plate. They didn’t ask for it. They didn’t define it. They might not even agree that it’s the most important thing for them to be doing. You also haven’t agreed on what success looks like.

You’ve created the appearance of ownership without any of the substance. They’ll do it for a while because you said so. They’ll let it slip the first time something more urgent comes along. And when it slips, they won’t feel wholly responsible, because deep down they never opted in.

Compare that to a team member who takes initiative and says “I want to own customer support, here’s how I’d structure it, here’s what I’ll measure.” That person is going to fight for their function. They proposed it. They defined it. They own it.

The difference isn’t the words on the spreadsheet. It’s whether the person on the other end actually agreed to the mission.

Describe the box, draw the box, fill the box

Here’s a helpful framework that Charles has been teaching for years: three steps to handing off ownership of any function or process.

1. Describe the box. This is the leader’s job. You name the high-level functional area. “We need someone owning customer support.” “We need someone owning finance.” Big shapes, no detail. You’ll need to do this for every major function in the company. This becomes the outline of your Area of Responsibility registry.

2. Draw the box. This is where you define the boundaries. What’s in scope, what’s not, how it connects to the rest of the business. Early on, you as the founder may have to draw the boxes yourself because nobody else has enough context. As the team matures, the team draws the boxes.

3. Fill the box. This is the specific detail. What does this function actually do day-to-day? What does success look like? What metrics matter? The leader should never fill the box. That has to be the eventual owner’s work, every time. They may need your help at first, but you should never do it for them.

Most founders mess this up by doing all three steps themselves and then handing the finished package to someone. “Here’s what you own, here’s what’s in scope, here’s what you’ll be measured on.” It feels efficient. It feels like leadership. And it produces zero ownership.

The discipline is to describe, draw if you need to, and then stop. Let the team fill it in. Be ready for their first attempt to be way off. Don’t just fix it for them. Get curious. Ask questions. Help them see what they missed without telling them the answer.

Then comes the hard part

Mapping ownership across the business is a lot of work. Most founders underestimate how long it takes. But the harder part is what comes after. The follow-up.

Without a consistent cadence of review, the Area of Responsibility registry becomes a museum piece. Something that lives in a Notion doc nobody opens. The follow-up takes as much effort as the initial mapping, sometimes more.

The cadence that works is layered: weekly staff meetings, one-on-ones for details, monthly check-ins on the quarterly goals. Quarterly one-on-one performance reviews where each owner walks through how their area is performing against the metrics they set themselves.

OKR-style goal calibration helps here. Aim for around 70% completion on goals. If your team is hitting 100%, the goals are too soft. If the team is hitting 30%, they’re too hard and people get demoralized. 70-80% means everyone is stretching and pushing forward.

The pattern under all of this

We write a lot about ownership culture, and you might be noticing the pattern. Alignment, accountability, autonomy. Mission, metrics, areas of responsibility. Different angles, same core idea.

The work isn’t telling your team what to do. The work is building the conditions where they tell you, and then holding them to what they said.

Describe the box. Let them fill it in. Then check in, every week, every month, every quarter, until the system runs itself.

Subscribe now

That post explained the concept. This one is about what a founder actually does with that knowledge on a Tuesday afternoon.

Because here’s the thing—once you understand alignment, your job changes. You’re no longer the person who tells people what to do. You’re the person who teaches them how to think about what to do. And that’s a much harder (and more important) job than most founders realize.

Stop improving the plan. Start improving the thinking.

When a team member brings them a plan, most founders do one of two things. They approve it, or they fix it. “Yeah, looks good, ship it.” Or “No, you should do it this way instead.”

Both responses are mistakes. Just approving sets you up as the rubber stamp. Fixing teaches them to come back to you for the answer next time, because you have it and they don’t. Either way, you become the bottleneck.

There’s a third option that takes more patience. Instead of evaluating the plan, ask about the thinking that produced it.

“Why did you pick that approach?” “What outcome are you optimizing for?” “What did you consider and rule out?” “What would have to be true for this to be the wrong call?”

The point is not to interrogate them. The point is to surface the reasoning behind the plan so you can coach the reasoning, not the output. A team member who walks out of your office with a corrected plan has a better plan. A team member who walks out with a corrected way of thinking has a better next ten plans.

Build a version of yourself in every team member’s head

The goal of all this on-the-job coaching is not just to make better decisions on the current project. It’s to install your decision-making framework in your team members so they can predict what you’d say.

When alignment is working, you can leave the room, and the team makes the same call you would have made. Not because they got the plan right, but because they understand the underlying thinking well enough to apply it to a situation you’ve never discussed.

The way you build that mental version of yourself in their heads is by externalizing your thinking. Constantly. Repeatedly. Out loud.

Don’t just tell people what to do. Tell them why. Don’t just approve a decision. Walk through the factors you weighed and how you weighted them. Don’t just say “we don’t do that.” Explain the principle that rules it out.

This feels inefficient because … it is … in the short run. You could have just made the call in thirty seconds. Instead, you spent ten minutes explaining how you got to the call. But the next time a similar situation comes up, your team member is better equipped to make the call without you. The time investment compounds.

Ask the team to propose, not to receive dictation

The other thing that changes once you’re coaching for alignment is how decisions get made. The default founder mode is often dictation. You decide what should happen, you tell the team, the team executes. That works fine when you’re five people. It breaks with 15. It’s a disaster at 50.

The mode that scales is proposal. The team member proposes what they think should happen and why. You react, ask questions, and either align with their thinking or help them see what they missed.

This is the hardest mental shift for founders, especially technical founders, because they spent years being the person who knew the answer. Asking “What do you think we should do?” feels like punting, almost like abdicating responsibility. It isn’t. It’s the move that surfaces whether you have alignment in the first place.

When their proposal is a bit off or even wildly off, that’s helpful information. It tells you the alignment isn’t there yet, and now you can do something about it. If you’d just dictated the plan, you’d never have learned that, and the misalignment would have shown up later, in worse form, with bigger consequences.

The leader’s job, revised

Founders usually think their job is to have the answers. The most senior leaders we work with would describe the job differently. Their job is to make sure the team has the thinking that produces the answers, so they don’t need to be in every room.

That shift, from answers to thinking, is the entire game.

Improve the thinking, and the plans take care of themselves.

Subscribe now

How much do you invite your people into your life? And how much do you challenge them to grow?

These two dimensions, plotted against each other, give you a 2x2 that explains more about your organization’s culture than most multi-page values documents ever will.

I learned this framework years ago from some mentors, and I teach it regularly. We’ve never written it down on the Wisdom Partners blog, which is overdue, because it’s one of the most useful diagnostic tools we have. (Shout out to Susan Vick for the prompting to get this published.)

Here’s how it works.

Invitation is the relational dimension. How welcomed do people feel? How much do they belong here? How safe is it to bring your whole self to the work? High invitation cultures feel warm. People know each other. They’re rooting for each other. Low invitation cultures feel transactional. You show up, you do your job, you go home.

Challenge is the performance dimension. How high are the standards? How much are people pushed to grow? Are they expected to do hard things and get better at them? High challenge cultures expect excellence and ask people to stretch. Low challenge cultures don’t expect much beyond showing up.

Cross them and you get four quadrants. Each one is a different kind of company.

Low invitation, low challenge: Apathy. Nobody’s pushing, nobody’s connecting. People show up, do the minimum, and leave. There’s no energy. There’s no growth. Nothing’s really wrong, but nothing’s really right either. This is the quietly dying company. The people who care most are already looking for somewhere else to work.

High invitation, low challenge: Cozy. Everyone’s nice. Everyone gets along. There’s warmth and camaraderie and probably good snacks in the kitchen. But nobody’s getting better. The standards are soft. Hard feedback doesn’t happen because it would feel mean. Underperformance gets absorbed by the team because nobody wants to be the one to call it out. From the inside, this can feel like a great place to work. From the outside, you’re getting passed by competitors who challenge their teams.

Low invitation, high challenge: Stressed. The standards are high but the relationship isn’t there to support them. This is the domineering boss culture. Push, push, push. Hit the number or else. In the short term, it can look productive. People are scared enough to perform. But it isn’t sustainable. The best people leave first because they have options. The ones who stay burn out, or they harden into something cynical.

High invitation, high challenge: Developmental or Coaching. This is the quadrant you want. People know they belong. They also know they’re expected to grow. The relationship makes the high standards understandable, and the high standards make the relationship meaningful. People aren’t just connected; they’re bonded around something hard they’re doing together. This is where the best teams live.

Why this matrix matters

Most founders intuitively understand that pushing your team hard works in the short term. Pressure produces output. The mistake is thinking that’s the whole story.

Sustained performance requires both invitation and challenge. Pull either one out and the system collapses, just in different ways. Without challenge, you get a comfortable team that doesn’t grow. Without invitation, you get a stressed team that doesn’t stay.

The goal is to be the kind of leader who can do both at the same time. Care deeply about your people and hold them to a high standard. Make them feel welcomed and expect them to stretch. Be warm and be honest about what isn’t working.

That combination is rare because the two pulls feel contradictory. High invitation feels like softness. High challenge feels like harshness. Most leaders default to one or the other based on their temperament, and end up in the cozy quadrant (if they’re naturally warm) or the stressed quadrant (if they’re naturally driven).

The work is to hold both at the same time. Care about the person and refuse to lower the bar for them. That’s not a contradiction. It’s the actual definition of coaching and healthy leadership.

Subscribe now

Don’t get me wrong. It’s helpful to have a vision for how you want to change the world. But making actual plans is different. Even one-year plans can feel too far in the future to make much sense for fast-moving startups.

Start with a solid, short mission statement.

A few weeks ago, we wrote about why your mission statement is probably useless. Short version: most missions are too long, too generic, and too forgettable to actually guide decisions. If yours is more than five to seven words and your team can’t recite it from memory, start there.

This post assumes you’ve done that work. You’ve got a mission that fits on one line and actually directs behavior. Now what?

Now you set goals. And this is where most founders fall apart again.

The annual goal trap

Here’s the standard playbook. The founder runs a planning retreat in January. Big whiteboard, big energy. Annual goals get written down. Everyone nods. The team goes back to work. By March, nobody remembers what the goals were. By July, they’re irrelevant because the business looks nothing like it did six months ago.

Annual goals are hard for three reasons.

Predicting twelve months out is nearly impossible at the early stages. Your market shifts, your customers shift, your team shifts. The plan you wrote in January is solving a problem that may not exist by Q3.

Surviving the present overwhelms whatever you wrote down. The fire in front of you always steals your mental energy from the goal in the deck.

And almost everyone on your team forgets the goals anyway. Which means they don’t shape behavior, which means they don’t actually do anything.

Start with quarterly goals instead

Three months is a horizon you can actually see. Pick three or four goals that will move the company forward in the next quarter. Make them SMART. Specific, measurable, achievable, relevant, time-bound. Review them in your staff meetings and 1:1s every week or two.

That’s the system. It’s not complicated. The complicated part is sticking with it long enough to get good at it.

You’re going to be bad at this for a while

Commit to four quarterly cycles before you decide whether it works.

In your first quarter, your goals will not actually be SMART. They’ll be vague aspirations dressed up as objectives. You’ll forget about them halfway through the quarter. That’s normal. Run it again.

Second quarter, change the dynamic. Ask each person on your leadership team to set their own quarterly goals that ladder up to the team goals. The ownership shifts. They’re not getting handed objectives anymore; they’re proposing them. This is also where the accountability piece we talked about in our latest blog post starts to compound. People own metrics they set themselves.

Keep iterating until your leadership team produces good quarterly goals on autopilot. That usually takes a year. Don’t rush it. Be patient with the process. Give yourself and your team grace as you figure this out.

Year two, three, and beyond

Once your leadership team is fluent in the quarterly cadence, you can start expanding the horizon.

Year two, layer on annual goals at a planning retreat, with Q1 goals rolling out from them. Push quarterly goal-setting one level deeper into the organization so the next layer down is doing what your leadership team did in year one.

Year three, you can stretch to three-year goals, with annual and quarterly cascading down. By that point, every person in the organization is setting quarterly goals that ladder up to the mission.

That’s what alignment and accountability actually look like in practice. Not a poster on the wall. A whole organization, top to bottom, setting and reviewing goals on the same cadence, all pointing at the same north star.

Why this works

Most founders try to start with 1-3 year goals because that’s the part that feels like real strategy. But long-range goals without quarterly discipline are just wishful thinking. And annual goals without a team that can execute on a quarterly cadence are just a slower version of the same problem.

You don’t graduate to longer planning horizons by force of will. You earn them by getting good at shorter ones first.

Build the cadence. The strategy comes after.

Subscribe now

So they try to create it in the obvious way. Hire smart people, give them autonomy, and get out of the way.

And then six months later, they’re frustrated. Things slip. Quality drops. They end up pulled back into the weeds, micromanaging the people they hired specifically so they could focus on the bigger picture. Ownership culture isn’t one thing. It’s three, and they have to come in order.

Alignment, then accountability, then autonomy.

Skip a step … and … the whole thing collapses.

Alignment is shared agreement on the outcome. Not just “we’re building X,” but what success looks like, why it matters, and how we’re going to get there. If your team can’t articulate the goal in their own words, you don’t have alignment. You have a memo nobody read. (See Alignment vs. Agreement.)

Accountability is owning that outcome. And here’s where most founders go sideways. Accountability gets confused with consequences. Calling people out, performance reviews, the boss-as-enforcer thing. Real accountability is about whether your team can rely on each other to show up, do the work, and finish what they started.

The mechanics matter too. A real accountability metric has three properties. It’s objectively measurable, it’s simple, and it has a timeframe. And here’s the part I think founders miss most: the person being held accountable should define the metric themselves.

If you hand someone a goal and a deadline, they’re complying. If they tell you what they’re going to deliver and by when, they own it. Maybe the same words, but totally different psychology.

Then, you check in. Regularly. It’s like a military situation report during war. Not because it’s punitive, but because alignment drifts. You and your team need to discuss the actual situation on the ground relating to the key goals. Three months is too long to wait to find out the team is solving a different problem than you thought.

Only then can you give autonomy.

And here’s the uncomfortable part for founders. The number one reason you’re not giving your team more autonomy is rarely that they can’t handle it. It’s that you don’t trust your own systems of alignment and accountability. You’re not sure they actually understand the goal. You’re not sure they’ll deliver on what they said they’d deliver. So you hold on a little too much. You stay involved a little too much. You “just want to be in the loop” a little too much.

That’s a systems problem, and it’s yours to fix.

The good news is the fix isn’t complicated. It’s just sequential.

Get alignment crisp. Then build accountability. Have your team define their own metrics and timeframes. Set up a regular cadence where they report to each other, not to you. Create stability around the goals so people aren’t recommitting every two weeks to a moving target.

Do that, and autonomy becomes the natural output. You’re no longer granting it. You’re just no longer in the way.

Most founders try to start at autonomy because that’s the part that feels like the goal. But autonomy without alignment is chaos, and autonomy without accountability is abdication.

Build the foundation. The freedom comes after. With alignment and accountability, they actually get free-er, and so do you.

Subscribe now

I delegated something, and we agreed on the next step. Then, he did something completely different!

I agreed to the aggressive timeline my boss suggested. Now that there are complications, I feel trapped into working 18-hour days to finish on time.

Sound familiar? These are all symptoms of achieving agreement but not alignment.

Agreement focuses on the actions to be taken. However, alignment ensures everyone shares the same vision, goals, and definition of success.

Let’s start with a social example.

Imagine you ask a friend to help you co-host a party. You agree to have a fun theme: blues music, blueberry smoothies, blue cake. You divide and conquer the responsibilities. You take the food & drinks, and your friend takes the venue and music.

You line up blue cupcakes and a top-notch smoothie maker. But things go off the rails when your friend isn’t able to find a good blues band. He remembers that his brother’s punk band is playing in a nearby bar on the day of the party, so he puts down a deposit on a set of private tables.

The problem is that you were trying to create a slow and gentle vibe to encourage lots of conversation. Although your friend signed on to help, he didn’t get the vision. He agreed, but he wasn’t aligned.

Here’s a common example from startups.

The software development team was tasked with creating a new feature for an app. The team agrees on the timeline, features, and technical approach. However, during development, they encounter an unexpected compatibility issue with the existing codebase.

If the team is only focused on agreement, they might force the original approach, resulting in a subpar or delayed product. But if they are aligned on the end goal—delivering a high-quality, user-friendly feature—they can adapt their approach while still meeting the overall objectives.

To achieve alignment, leaders should:

1. Communicate the “why” behind tasks and ensure the team agrees on the intent. The bigger the project, the more time you need to spend aligning on and clarifying the why.

2. Define measurable outcomes and provide context for their importance. Identify what success looks like and how you will measure it. Depending on how much time you have, this can be a very collaborative process. For more mature individuals or teams, they might take the lead on defining the outcomes and metrics of success. The important part is that everyone is fully aligned on what success is and specifically how you will measure it together.

3. Encourage discussion of potential obstacles and how to handle them. After clarifying the why and the success criteria, you might want to brainstorm the most likely roadblocks or detours. Discuss ahead of time potential solutions or alternatives. Then, make sure the team knows when and how to get your input when there are significant concerns, questions, or risks.

By fostering alignment, leaders empower their teams to make decisions that support the company’s vision, even when faced with unexpected challenges. This creates a foundation for independent work and drives the company forward. Remember, agreement is important, but alignment is essential for long-term success.