Let me start with a piece of news that should have been delivered to every operating executive in the country two years ago, and somehow wasn't.
The reason your side project has been stuck is not because you're a bad leader. It's not because your team isn't good enough. It's not because the idea is wrong, or the timing is off, or you "haven't really committed."
It's because you are trying to run two completely different operating systems on the same hardware, and one of them is winning.
Once you see this clearly, the whole thing stops being a personal failure and starts being a problem you can actually solve. So let's see it clearly.
The two operating systems
Operating System One is your existing business. It is tuned for reliability. It rewards predictability, repeatability, and consistency. The KPIs measure uptime, not invention. The people are excellent at running plays, not writing them. The customers expect what they got last quarter. The shareholders expect what they got last year. The whole apparatus, top to bottom, exists to deliver the same thing again, only slightly better.
You hired these people. You designed this system. It works. It is the reason your company has $200 million in revenue and 800 employees. Don't apologize for it.
Operating System Two is what your side project needs. It is tuned for invention. It rewards waste, weirdness, and the willingness to throw away a month of work because you learned the customer wants something different. The KPIs are about learning velocity, not output volume. The people are wired to ask "what if we built this entirely differently" rather than "how do we ship the next sprint on time."
These two systems are not just different. They are in active opposition. The behaviors that make System One excellent are exactly the behaviors that kill System Two. And the behaviors that make System Two excellent are exactly the behaviors that would get you fired from System One.
When you ask System One to also run System Two, System One wins. Every time. Not because anyone is sabotaging it, but because that's what you optimized them for.
This is the physics. Once you see it, you can stop blaming yourself.
Why every fix you've tried so far has failed
You did not get to your job by being passive. So I know you have tried things. Let me list them, in the order most operating executives try them.
Fix one: more meetings. You added the side project to the executive team's weekly agenda. Six weeks in, it stopped getting talked about. Four months in, it stopped being on the agenda. The existing business filled the meeting time, because the existing business has urgent problems and the side project does not.
Fix two: a consulting firm. You hired a name brand. They produced a strategy deck. The deck was, objectively, very good. It is now in a drawer. The strategy did not survive contact with your own operations because nobody inside the company was going to execute on it. They had real jobs.
Fix three: a development shop. You decided to skip strategy and just build. The dev shop asked for a spec. The spec turned out to be the hard part. You spent six months writing it. By the time you finished, the spec was wrong, because writing a great spec for a product that doesn't exist yet is a job that requires customer feedback that you don't have yet because the product doesn't exist.
Fix four: a senior hire. You brought in a Chief Digital Officer or a VP of Innovation. They were good. They were also expensive. They needed a team. The team needed budget. The budget required ROI projections. The ROI projections required customer evidence. The customer evidence required a product. You did not have a product. The CDO eventually left, or was let go, and the strategy went with them.
Fix five: next quarter. This is the most popular fix. It is also the most expensive, because it costs you years of your career and you don't notice the bill arriving.
None of these were dumb moves. They are the moves your job description tells you to make. They just don't fit the actual physics of the problem.
The new math
Here is the part of this essay that I most want you to actually absorb.
In the last 18 months, the cost of building a new digital product has dropped by roughly 90 percent. This is not marketing copy. It is the actual experience of operators in the market right now.
A product that needed a team of six and a year now needs one or two operators and a quarter. The tools that used to be the bottleneck are now commodities. The labor that used to be the bottleneck is now augmentable. The infrastructure that used to be the bottleneck is now rented by the hour.
What this means for your specific side project is that the entire risk equation just shifted. The thing that was once "a six-figure bet on a hunch that distracts the team for a year" is now "a low-five-figure experiment that ships in 90 days and tells you whether the hunch was right."
This is a different decision. You may have rejected this idea three times in the last three years for reasons that no longer apply. That is worth a fresh look.
The right structural fix
Here is what actually solves the physics problem, instead of working around it.
You bring in a single outside operator who is wired for System Two. They own the side project end to end: strategy, build, launch. They do not need a team from inside your company. They do not require headcount. They do not need a CDO above them or a dev shop below them. They are the whole stack.
Their job is to ship a small, real version of the idea in a quarter, get it in front of actual customers, and produce hard evidence about whether the bet is worth scaling. Not a deck. A working product with real users.
If the evidence says go, you scale it, and now you have proof to bring to your board. If the evidence says no, you've spent a small amount of money and saved yourself a year of half-launching it internally and getting nowhere.
Either outcome is better than the doc in the drawer.
The thing I want you to walk away with
You are not stuck because you are bad at this. You are stuck because the structure you have been trying to use cannot, by design, produce the outcome you want.
The fix is structural. It is also, in 2026, much cheaper than it has ever been before.
Your side project doesn't need another quarter of someday. It needs an outside operator and 90 days.
Same core argument, different doorway: the confessional version · the lunch story.
That's exactly what I do. If you want to test whether your idea has legs without disrupting your existing business, book a call. Thirty minutes. No pitch. Just a real conversation about what's in the doc. For the full 90-day build path, we can map that on the call too.