How much should you change your roadmap based on early user feedback?

  • A community for building, creating, and growing with AI.

    Welcome to AI Forums, a community for people using AI to build products, automate workflows, create content, and grow businesses. Discuss vibe coding, AI agents, Claude Code, Codex, automation, AI tools, product launches, marketing, and the latest developments in AI.

    Join the Community (it's FREE)!

curiousBuilder

Starter account
Messages
1
One of the surprises of shipping software is that users request features you never considered, complain about things you thought were obvious, and sometimes barely touch the feature you worked on longest.

How do you distinguish a real product gap from one person's preference? Do you collect requests in a backlog, interview users, watch usage, or just fix whatever hurts the most?
 
When somebody asks for a button, I'd ask what they were trying to accomplish before adding it. Sometimes the actual issue is a confusing label, an extra step, or a missing default. Early feedback is precious but also noisy, especially if you're hearing it from the most vocal few users. I'd look for repeated friction in the core workflow and fix that first. A roadmap should respond to evidence without becoming a list of everyone's favorite features.
 
Back
Top