By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
This Product in Practice case study follows Kranthi Kiran, founder of ThoughtFlow, a collaboration tool combining visual mind mapping with data modeling. It opens by framing the risk founders face when they start from an idea: escalation of commitment and confirmation bias make it easy to seek only supportive evidence. Kranthi's earlier build-then-market approach failed, so he switched to talking with prospective users before building. Adopting regular customer interviews, paired with an opportunity solution tree and weekly review of screen recordings and funnels, helped the team replace request-driven prioritization with outcome-focused, evidence-based decisions. The story shows why continuous discovery matters for early-stage teams trying to avoid wasted effort.
01Key takeaways
- Start discovery by understanding customer workflows and pain points rather than validating a preset idea.
- Map user requests to outcomes and opportunities on an opportunity solution tree before committing to solutions.
- Define success criteria using user behavior metrics, not just feature acceptance criteria.
- Practice story-based interviewing and avoid pitching solutions before needs are fully understood.
- Expect continuous discovery to take time; start with small habit changes to build team momentum.
02Key sections
- Why idea-first startups struggle
- Founders who start with an idea tend to frame discovery as proving the idea is good, which invites confirmation bias and escalating commitment. Teresa Torres argues this makes negative feedback easy to miss.
- Early failure and a shift to discovery
- Kranthi's build-then-market approach did not work, so he began interviewing people interested in ThoughtFlow to understand their workflows before building further.
- Stalled conversion and feature sprawl
- Trial users were not upgrading, and the team chased multiple features and the most-requested asks, causing burnout and unclear priorities.
- Building interviews and a weekly review habit
- The team nudged support users into research calls, mapped their motivations to an opportunity solution tree, and reviewed screen recordings and funnels together each week.
- A new use case and evidence-based decisions
- Interviews revealed users wanted to visualize existing board data rather than brainstorm, leading to the Bird's Eye View app and clearer, metric-based success criteria.
03From the post
“Founders have all sorts of reasons for starting companies. Sometimes it’s because they’ve personally experienced a pain point and want to address it. Sometimes they’re dissatisfied with what’s available on the market and think they can do better. And sometimes it’s because they have an”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.