Invention Before Intent Is the Founder Mistake That Costs You Everything

Most growth advice teaches founders to invent faster. That is exactly what breaks companies. The founders I have watched break their companies over the last thirteen years did not fail because they moved too slow. They failed because they moved fast on the wrong thing — and then moved faster to cover for it. A launch that missed. A hire that thickened the org chart without sharpening the decisions. A feature that shipped clean and changed nothing. Each one made the same upstream mistake: it invented before it defined intent. You know the collateral of that mistake because you have paid some of it. Business debt taken to fund a launch that never returned. A leadership team that fractured around a strategy no one on it could describe in the same sentence. Margin thinning quarter over quarter while the top line kept telling a hopeful story. Marriages that stopped hearing about work because work stopped being coherent enough to describe. Prayer time that used to be non-negotiable, quietly moved to the calendar's edge. None of that is the price of ambition. It is the price of building without first naming what the build is for. Let me tell you about one shape of this. Names redacted, but the shape will feel like a mirror. A CEO ran a mid-market company with a leadership development challenge. His managers were coaching their people badly and inconsistently. He decided the answer was a product. He funded a beautifully designed app to structure coaching conversations. His engineering team was excited. His board was excited. The rollout plan looked sharp. Before the build kicked off, I asked one question. What specifically will be different for a manager on your team six months after this ships? He gave the version most founders give. Better conversations. More consistency. Higher engagement scores. The version that sounds like an answer but is actually the same shape as the question. I asked again. What will she do differently on Tuesday morning that she does not do today, and why? He did not have that answer. Neither did his product lead. Neither did the VP of People who had championed the project. What they had was the certainty that the app would be useful. What they did not have was a description of the specific behavior the app would replace, sharpen, or unlock — and, underneath that, a description of what the business would look different because of it. They built it anyway. They shipped it clean. Managers used it for six weeks and stopped. The app got shelved. Two years later the company collapsed for reasons that had nothing to do with an app and everything to do with the pattern the app was a symptom of: a leadership team that had gotten very good at building and very bad at asking what the building was for. This is the shape of invention before intent. It looks like productivity. It is drift. The reason the shape is so hard to catch from inside is that invention feels like the answer to every problem in a growing business. There is always another feature that would probably help, another hire the org chart implies you need, another campaign the market is asking for. Every one of those is a real option. What makes them dangerous is that they all pass the shallow test — the business case sounds fine — while quietly failing the deeper test: does this decision serve an intent we can name on more than one layer. That is the whole point of Intent Before Invent. It is not an instruction to slow down. It is an instruction to interrogate on three layers before you build, because a decision that passes only the business layer is a decision that will look right in the deck and cost you on the ground. Here are the three layers. This is the framework, and it will show up under most of what I write here. Business. What specifically changes in the P&L, the customer's behavior, or the strategic position of the company six months after this ships? "It will help" is not an answer. "It will move our retention from X to Y by removing the friction at week three" is an answer. Team. What does this decision do to the power map, the trust map, and the workload map of the people who have to live with it? A hire that survives the business logic and fails the team logic will still be your problem eighteen months from now. Ask what stops being anyone's job. Ask whose authority just quietly changed. Ask what argument this decision ends and what argument it starts. Personal. What does this decision cost you and the founder or leader closest to it? What will you not do because you did this? What tuition are you paying, and did you sign up for it? The number of founders I have watched wreck marriages, sleep, and health while their business was growing on paper would fill a book I have no interest in writing. That layer is not soft. It is the one that determines whether the business you are building is worth having built. The rule is simple. No decision worth capital, calendar, or people ships until you can write one sentence on each layer. If any of the three sentences will not come, the intent is not ready. The invention is not the problem — the intent is not clear enough to justify inventing yet. This is a hard rule to accept because it looks like it slows you down. In practice it does the opposite. Every founder who has adopted it has told me the same thing: it kills the wrong builds faster than any prioritization framework they have used, and it releases the ones that survive it with unusual clarity. The team stops arguing about the feature and starts arguing about the intent — which is the argument that actually deserved to happen. The CEO with the coaching app never had that argument. He had a build meeting. That is how six figures of engineering time and two years of organizational trust become an app on a shelf. The next big decision on your desk this week is not, in most cases, whether to build. It is whether you can finish three sentences before you do. --- Your Tuesday Intent Check (Business layer): The next big decision you're about to make — hire, launch, feature, partnership — if it succeeds exactly the way you're imagining, what specifically changes in the business six months later? If you can't finish the sentence, you're not ready to spend.