Built, Broken, Learned: The Product I Designed Too Early
One of the strangest things about building products is that being right is not always enough.
This was a reply to a friend I made over dinner recently when asked how things were, and it's stuck in my head.
A product can be directionally right, commercially useful, and built around real user problems, and still fail to get traction.
Sometimes the idea is wrong. Sometimes the execution is wrong. Sometimes the timing is wrong.
And timing can be brutal.
Too early looks a lot like unnecessary
This is not theoretical for me. One of the clearest examples was a SaaS platform I built for the print industry, designed to connect workflow decisions more intelligently to what the business actually needed, with a proper view across the customer journey.
It did not really get used.
That was frustrating at the time, but it was also clarifying.
Because the product itself was not solving a fake problem. The problem was real. The issue was that the market, and some of the people around it, were not yet seeing where things were heading.
But I have to be honest: the market's readiness was only part of the story.
I led with instinct. I had a clear picture of the problem in my head, and I moved quickly to design around it, I assumed the business wanted that "special product", however, I did it without properly bringing in the marketing and data teams early enough to validate whether others saw the same thing. There was no structured research phase, no external stress-testing of the proposition. Just conviction, and a deck or two.
That is a difficult lesson when you are close to the idea. Conviction is useful. But conviction without validation is just a bet.
Too early can look a lot like too much. Too early can look like unnecessary complexity. Too early can look like ambition that people cannot yet map onto their current pain.
Sometimes it is all three at once.
What that taught me
1. Product timing is not just about market size
A market can be large and still not be ready.
Readiness is about recognition.
Do people feel the pain clearly enough? Can they picture the new way of working? Do they trust the shift? Can they absorb the operational change? Do they have the internal language for why it matters?
If the answer is no, a product can make sense on paper and still land flat.
2. Bring the data and marketing teams in early, not at the end
This is the mistake I would most want to undo.
Product people, especially those building around workflow or systems, can fall into the trap of treating validation as something that happens after the design. Research becomes a box to tick, not a foundation to build on.
The insight, the instinct, is yours. But the evidence that the market is ready for it? That requires other people, different lenses, and research you probably cannot do alone.
Getting that in early does not slow you down. It saves you from building the right product for the wrong moment.
3. Workflow products need a visible enemy
Workflow problems are often diffuse.
That makes them harder to sell than problems with a clean headline.
If a person can see one obvious thing breaking, they will often pay to fix it. If the issue is really a chain of handoffs, weak visibility, and avoidable friction spread across a journey, that is harder to explain.
Ironically, that kind of problem is often more expensive.
4. People do not always buy the future they say they want
A lot of businesses say they want transformation.
What they often really want is less disruption, less uncertainty, and a clearer return.
That is understandable, but it creates a gap.
Products built around where a market is going can struggle if buyers are still anchored in how they currently think about the problem.
5. Being early is still useful if you learn properly
Designing something too early is not wasted effort if you use it well.
It sharpens instinct. It improves your ability to spot patterns. It teaches you which parts of the proposition were ahead of the market, and which parts were simply unclear. It shows you how industries absorb change, and how slowly some forms of understanding move.
That matters later.
Why it still matters now
The reason this experience still feels relevant is that many industries are now moving into a more connected phase.
AI, automation, orchestration, and better workflow design are forcing people to think more seriously about joined-up systems.
The kinds of problems that once felt too abstract are becoming more visible.
That does not mean every early product idea was secretly brilliant. It does mean timing shapes perception more than many people realise.
Final thought
Sometimes you were wrong. Sometimes the market was not ready. Sometimes both are true.
The important thing is not protecting your ego. It is understanding what actually happened, and being specific about it, not just philosophical.
Failure is fine. Vague failure is wasted.
If you can interrogate what really went wrong, the timing, the validation gaps, the things you assumed rather than tested, being early stops being a source of frustration and starts being one of the most transferable forms of experience you can carry into the next thing.