Three Interfaces, One Uncomfortable Question
I joined a company building a new user experience with three interfaces for image uploads and moderation. The roadmap was packed, the engineering estimates were scary, and everyone seemed resigned to building three complex systems.
I started asking questions about the requirements: "Do we actually need human moderation at all?" "Are we sure partners and internal users need different interfaces?"
These weren't popular questions. They challenged months of planning and implied that smart people had made wrong assumptions. They also changed the whole plan. We went from three interfaces down to one, delivered faster with fewer resources, and ended up with a better user experience than the original plan would have given us.
Why nobody asks
Most product managers are good at tactical questions: "How should we prioritize this feature?" "What does user research tell us?" Those matter, but they take for granted what we're building and why. We avoid questions like "Should this product exist at all?" and "Are we solving the right problem?" and I understand why. They challenge work that's already in motion. They feel unproductive next to tactical questions that produce neat action items. And sometimes they surface problems that are expensive or politically painful to fix. So we keep building and never seriously consider stopping.
Three systems for a workflow nobody needed
When nobody challenges the assumptions, the team works inside limits it can't see. Failing approaches keep going because the sunk cost fallacy becomes part of how the organization runs.
If I hadn't asked whether we needed human moderation at all, we would have built three separate systems to support a workflow that didn't need to exist. We'd have paid for it in engineering time, and then again in maintenance, complexity, and a worse user experience, all for an assumption nobody had bothered to test.
When a question feels rude
In my experience, a question that makes you uncomfortable is usually pointing at an assumption nobody has examined. The questions that feel threatening often expose beliefs you've never said out loud, and constraints that seem fixed sometimes aren't.
In that image moderation project, the question "Do we actually need human moderation?" felt almost rude to ask. The existing team had spent months on the moderation workflow. That discomfort pointed straight at the assumption most worth challenging.
Try it on your own roadmap
You don't need a formal framework to start asking harder questions. Start by listing the five biggest assumptions underlying your current product strategy. For each one, ask yourself what evidence supports it and what would change if the opposite were true.
The list is easy to write. Saying one of those questions out loud in a planning meeting, with the people who built the plan sitting there, is harder, especially when one of those people is you.