Most stalled initiatives aren't stuck because people disagree. They're stuck because everyone already agrees — and nothing moves. I've watched this for 25 years. The room nods. The strategy deck is beautiful. "Yes, we should absolutely do this." And then a month later it's exactly where you left it. Founders read that as a conviction problem and go hunting for more buy-in. But you don't need more agreement. You have plenty. What's missing is the other two ingredients: momentum and ownership. Agreement is cheap because it costs nothing. It's a nod. Momentum and ownership are expensive because they cost something the moment they exist — a decision that can't be quietly walked back, and a name attached to it. That's exactly why they're the parts that go missing. The organization will happily agree forever precisely because agreeing commits no one. So the job isn't to build more consensus. It's to manufacture the first irreversible step. By irreversible I don't mean dramatic. I mean a step that changes the facts on the ground, so next week can't just be a copy of last week. A few that actually work: Make it public. A private intention dies quietly. An external commitment — a date told to a customer, a launch announced, a demo scheduled with someone outside the building — turns "someday" into "this Thursday, in front of people." Assign one owner, not a committee. Shared ownership is the most sophisticated way to guarantee nothing happens. It has to be one name, with the authority to move and the accountability if it doesn't. A group can hold agreement. Only a person can carry momentum. Spend something you can't refund. Book the venue. Hire the first person. Ship the rough version. The point isn't the size of the bet — it's that reversing it now costs more than continuing. That asymmetry is what makes the step stick. Here's the uncomfortable part: the first irreversible step is uncomfortable on purpose. If it feels safe and fully reversible, it isn't the step — it's more agreement wearing a costume. The discomfort is the signal that you've finally converted a nod into motion. The best builders I know aren't better at getting people to agree. They're better at creating the conditions where agreement has to become action — one owner, one public commitment, one thing that can't be undone. So a question worth sitting with: The initiative everyone agrees on but no one has moved — what's the smallest step you could take this week that you couldn't quietly walk back, and whose name would be on it?

When your customer research keeps contradicting itself, the problem usually isn't the research. It's that you're talking to two different people and treating them as one. I see this constantly. A founder runs a dozen conversations, and the signal is all over the map. One group swears the onboarding is the dealbreaker; another barely notices it and cares only about price. Half describe the product as a time-saver; half call it a status thing. The founder concludes "customers are confused" or "the market is fragmented," and goes hunting for a cleverer message to paper over the noise. But the noise is the finding. Contradictory insights are what a blended audience sounds like. You're not hearing one confused market — you're hearing two or three coherent ones averaged into mush. And you can't message an average. Nobody is the average customer. The reason this stalls companies is subtle: an average feels like data. It has quotes, a deck, a ring of rigor. So you make product and go-to-market bets on it — and the bets keep missing, because you're aiming at a person who doesn't exist. The fix is in how you structure discovery, before you ever synthesize: Segment on the way in, not on the way out. Decide the cuts that might explain different behavior — job to be done, trigger event, stage, buying context — and tag every conversation as you go. If you only segment after the fact, you've already blended. Recruit on purpose, not on availability. A convenient sample is a blended sample. Deliberately fill each segment so a pattern in one group can't hide inside the average of all of them. Read patterns within a segment, never across the pile. The question isn't "what did customers say?" It's "did this segment say the same thing to each other?" Agreement inside a clean segment is a signal. Agreement across a blended pile is a coincidence you'll pay for later. Here's the bar I hold: an insight is decision-grade only when it's consistent inside a segment you could actually go acquire. Anything short of that isn't evidence — it's an anecdote wearing a percentage sign. The uncomfortable part is that this makes your findings messier before it makes them clearer. Two sharp, opposing truths are worth more than one blurry consensus. Consensus is comfortable. It's also where stalled companies go to feel productive. So a question worth sitting with this week: The last time your customer insights contradicted each other — did you treat it as noise to resolve, or as a sign you were listening to more than one audience at once?

"How do I keep from being the bottleneck?" Most founders think they're the bottleneck because of how much they do. They're actually the bottleneck because of what only they're allowed to decide. It's a subtle difference, and it's the one that keeps stalled companies stalled. You can hire more people, delegate more tasks, clear your calendar — and still be the single point of failure. Because the work moved, but the authority didn't. Every real decision still routes back to your desk for a yes. The team isn't waiting on capacity. They're waiting on permission. I've watched this for 25 years across four startups. A founder offloads the doing and keeps the deciding, then wonders why nothing moves when they're heads-down or out of the room. It looks like a delegation problem. It's a decision-rights problem. You gave away the tasks but kept the steering wheel, and a car with one driver can only go one place at a time. The builders I most respect design the opposite way — on purpose, early, before it's comfortable. They treat decision-rights as something you architect, not something that accumulates by default around whoever started the company. Two questions do most of the work: For any recurring decision, who owns it — not who advises, who decides? If the honest answer is "me, eventually," you've found a place the company can only move at your speed. And what does this person need to decide well without me — the context, the constraints, the definition of a good outcome? Authority without judgment is just a faster way to make bad calls. The transfer isn't handing over a decision. It's handing over the thinking behind it, so the call gets made the way you'd make it, whether you're there or not. Here's the reframe I've come to believe: a venture that can't make decisions without its founder isn't a company yet. It's a talented person with help. The moment it can decide well without you is the moment it becomes durable — something built to outlive your involvement instead of depending on it. That's not abandonment. It's the point. You're not designing yourself out because you're leaving. You're doing it because a company that needs you for every decision is fragile in exactly the place that looks like strength. So a question worth sitting with this week: What's one recurring decision that still routes through you by default — and what would the person closest to it need in order to own it outright?

Most people I work with are trying to become indispensable. I spend my time trying to become unnecessary. That sounds backwards, so let me explain the difference — because it's also the difference between me and the operators and agencies a founder might hire instead. An agency is designed to keep you as a client. An operator is often measured by how much runs through them. Both, by design, make you a little more dependent every month. That's not a criticism of their intent — it's the incentive built into the arrangement. The longer you need them, the better it works for them. My job is the opposite. I get handed a hard, ambiguous problem, I build the thing, I set a real foundation under it — and then the win is when a capable operator can take it over and scale it without me in the room. I'm not building a dependency. I'm building something that no longer needs me. Here's why that matters even if you never hire anyone: dependency on a single person is a hidden fragility. It feels like control. It reads like importance. But it's the crack that doesn't show until the load shifts. In M&A, buyers actually price this — a business that leans too heavily on its founder gets discounted, sometimes steeply, versus one that runs on people, process, and structure. The market is telling you something founders don't want to hear: your irreplaceability is a liability on the balance sheet. The fix isn't heroics. It's two disciplines most builders skip. First: document the decisions, not just the outcomes. Anyone can inherit a result. Almost no one can inherit the reasoning — why you chose this customer over that one, why you killed the feature everyone loved, what you'd do if the number moved the wrong way. Outcomes tell your successor what happened. Decisions tell them how to think when you're gone. That's the part that actually transfers. Second: treat the handoff as the test, not the goodbye. A clean handoff is the only honest proof the foundation is solid. If the thing wobbles the moment you step back, you didn't build a company — you built a role, and you're standing in it. The transfer is where you find out whether the structure was ever real. I've come to believe the strongest thing you can build is something that outlives your involvement in it. Not because you're leaving tomorrow. Because durability and dependency are opposites, and you have to choose which one you're actually building. So here's the question worth sitting with: Is your company built to outgrow you — or to need you?

Back in 2007 my mom wrote a book, and no one would publish it. It's called "Butterfly Girl" — the story of a little girl lost in a storm and her long journey home. She wrote it for one reader: my daughter. She wanted her granddaughter to know where she came from, in her own words. The traditional publishers all passed. A beautiful, personal story about one family's journey wasn't a big enough market for them. So I told her not to wait for anyone's permission. We'd do it ourselves. What I didn't fully understand until we were in it: self-publishing back then was brutal. Formatting, printing, distribution, ISBNs, cover files — every step was manual, expensive, and built to make you quit. We pushed through it anyway, and she held her book in her hands. That moment was the whole point. Then Christmas came. And at the table, one relative after another leaned in and said some version of the same thing: "You know, I have a book in me too. How did you do it?" That's when it clicked. The pain I'd just spent months fighting through wasn't my mom's problem. It was everyone's problem. As I put it later: "there's a million other moms out there hundred million other moms you know actually billions of people out there who think they have a book in them and will never publish so it was the business model" That became FastPencil — an online writing and publishing platform. It didn't start with a market analysis or a TAM slide. It started with one person I loved, one urgent human problem, and a Christmas dinner full of people stuck behind the exact same wall. I've come to believe this is one of the most underrated sources of a great idea: proximity. Not brainstorming what the market wants in the abstract, but solving something real for someone you actually care about — then noticing how many other people are quietly living the same frustration. The narrow, personal problem is often the universal one wearing a disguise. So here's my question for you: Is there a version of this in your own story — a problem you solved for someone close to you that turned out to be universal? 🎙️ From my conversation with Julia Lucidi on the Founder Tactics podcast. Full episode: https://youtu.be/M58Dnn2UAlM

Michael Ashley