I had a twelve-month roadmap pinned to the wall behind my desk. Color-coded by quarter. Dependencies mapped. Milestones named after mountains—Everest was the big launch in Q4. I was proud of it the way you're proud of a diagram that took all weekend. It looked like certainty.
Then a Wednesday morning in February broke it.
Three customers cancelled in the same week. Not angrily. Worse—politely. "We just found something closer to what we need." I asked each of them what that was. Their answers had nothing in common with each other, and nothing in common with my roadmap.
I stared at the color-coded wall and realized I had been building toward a destination nobody asked to visit.
The natural instinct was to defend the plan. I had told my team the plan. I had told investors the plan. I had structured hiring around the plan. Admitting the plan was wrong felt like admitting I was wrong—about my own product, my own market, my own judgment.
So for about forty-eight hours, I rationalized. "Those three customers weren't our target persona." "They churned because of onboarding, not features." "The roadmap addresses their complaints, just not until Q3."
Every excuse pointed in one direction: keep going. That should have been the red flag. When every argument leads to the same comfortable conclusion, you are not reasoning. You are defending.
That Friday, I cleared my afternoon and called ten customers. Not the ones who left—the ones still paying. I asked one question: "What's the most frustrating part of your week that we could fix?"
Eight of them described problems I had never mapped. Not exotic problems. Mundane, painful, recurring friction. The kind of thing you don't put on a roadmap because it doesn't feel ambitious enough.
Two of them described the same problem, nearly word for word, without knowing each other. That was the signal.
I walked back to my desk, took the roadmap off the wall, and folded it into a drawer. The next Monday, I told the team we were changing course. Not pivoting the company—just abandoning the sequence. We would work on what customers told us hurt, in the order they told us it hurt.
The team's first reaction was relief. One engineer told me later he'd been dreading the Q2 milestone because he didn't believe anyone wanted it. He'd kept quiet because the roadmap looked so definitive. Definitive plans silence dissent. That's a cost nobody accounts for.
The second reaction was anxiety. Without a roadmap, how would we know what to build next week? Next month?
We replaced the twelve-month wall chart with a short list. Five problems customers described. Ranked by frequency and severity. Updated every two weeks after a batch of calls. Nothing on the list survived more than six weeks without either shipping or getting cut.
It felt less like strategy and more like triage. That was the point. Early-stage companies are not executing a grand vision. They are searching for the next thing that earns the right to exist.
Within two months, retention climbed. Not because we built anything brilliant. We built small, obvious things—fixes for friction that customers had been silently tolerating. Each one was quiet proof that we were paying attention.
Word-of-mouth referrals started. Customers told peers, "They actually listen." That sentence did more for growth than any feature announcement ever had.
The roadmap in the drawer stayed in the drawer.
I still plan. I'm not arguing for chaos. But the planning artifact changed shape. Instead of a timeline of features, I keep a living list of customer problems ranked by evidence. The backlog is organized around pain, not ambition.
The difference matters. A feature roadmap says, "We know what to build." A problem list says, "We know what hurts, and we'll figure out the fix." The first is a bet disguised as a fact. The second is honest.
Founders love roadmaps because they project competence. Investors like seeing them. Boards like reviewing them. But competence is not the same as correctness. A beautiful plan, executed on schedule, that solves the wrong problem is just expensive furniture.
Your roadmap is a hypothesis. Treat it like one. When evidence contradicts it, update it. When customers describe pain you didn't predict, listen harder than you plan.
The week I killed the roadmap felt like failure. Six months later, it was the clearest decision I'd made. Not because I found some better strategy. Because I stopped pretending I already had one and started earning the next answer, one conversation at a time.
The wall behind my desk is empty now. I like it that way.
Be the first to comment.
0 comments
Loading comments...