A roadmap should change when repeated customer calls point to a different urgent job. Keep the slide only if current buyers can still explain why the planned work matters to them now.
In 2006, Evan Williams and Biz Stone were confronting that kind of problem at Odeo. Apple had announced podcasting features for iTunes, placing a large platform directly in the path of the company Odeo had built. The original story no longer had the same future.
Nick Bilton documents the period in Hatching Twitter: Odeo’s team opened the floor for new ideas, and Jack Dorsey’s short-status concept emerged from that process. The outcome was uncertain. A company designed around podcasting was trying to find a reason to keep building after its central assumption had weakened.
That is the uncomfortable work a founder avoids when an investor deck becomes the roadmap. The slide captures a moment when the product had to sound coherent to someone considering a cheque. Customer calls test whether that same coherence survives contact with a buyer’s actual week.
The deck can outlive the reason it was made
An investor deck has a job. It compresses a market, a product direction and a plausible future into a few minutes. It needs a clean sequence: problem, solution, market, roadmap.
A customer call has a different job. It exposes the thing that blocks a purchase, renewal or pilot. The answer is often untidy.
One buyer asks for an audit trail before they will put workflow data into an AI tool. Another has accepted the demo but keeps returning to the manual handoff between two people. A third says the feature sounds useful, then asks who will be accountable when the recommendation is wrong.
None of those comments automatically deserves a sprint. A single loud prospect can pull a small team into expensive custom work. But when the same friction appears across calls, locations and buyer types, it has earned more attention than a promise made six months earlier in a fundraising conversation.
The risk is subtle. The team tells itself it is executing the roadmap. In practice, it is defending a past explanation of the company.
Three months of calls should create a competing roadmap
Before Monday planning, put the deck beside the notes from every customer conversation since the last planning cycle. Do not begin with feature requests. Begin with the moments where the buyer’s process stops.
Look for language that repeats without your prompting. “We need someone responsible.” “I cannot get the data out.” “My team will not use it unless.” “We already have a person doing that.”
Those phrases reveal the job around the product. They also reveal whether the roadmap is aimed at the right constraint.
For a founder building between Accra, Berlin and US customers, the contrast can be especially sharp. An overseas buyer may ask for the integration required by their existing stack. A local customer may need the product to work around a manual approval process first. Neither request becomes truth because it came from a larger market or a more familiar logo. The question is whether it appears in the segment you are choosing to serve.
The useful planning document is a short record of evidence:
- Which customer problem appeared repeatedly?
- Who experienced it, and at what point in their work?
- What did it prevent: a pilot, daily use, payment or expansion?
- What work on the current roadmap would this delay or remove?
That last question matters. A customer-informed roadmap still requires a choice. If everything remains committed, the calls changed nothing.
What Are Paying Users Already Telling Us to Build Next? is useful here because paying behavior gives those conversations a different weight from polite interest.
Replace the story only where the evidence breaks it
The answer is rarely to throw away the whole deck. Some parts may still hold: the customer segment, the distribution path, the team’s technical advantage.
Change the part that no longer survives the calls.
If customers want accountability before automation, build the review path before the autonomous demo. If they cannot reach the data needed for the promised result, solve the access problem before improving the model. If the planned feature answers a question nobody has asked in three months, move it out of the next cycle and say why.
This is less dramatic than a pivot announcement. It is often more valuable. The team keeps its direction while refusing to treat fundraising language as product evidence.
The hard part is emotional. The roadmap may contain the feature that made the round feel inevitable. It may be the work the engineering team wants to show. It may be the thing that sounds strongest in a pitch. Customers do not owe that feature their attention.
Monday planning needs a visible decision
By Monday, write one sentence the team can use to decide what enters the sprint: “For this segment, the next product risk to remove is ___ because ___ customers have shown us ___.”
Then name the work that will wait.
Odeo did not discover Twitter by polishing its old answer to Apple’s move. The team made room for an idea that addressed a different future. Your customer calls may not require a company-defining pivot. They may require a smaller, harder act: deleting a roadmap item that still looks convincing on slide 12.
Comments
No comments yet.