Tell me about a time when you had to reject a popular idea or project.

Illustrative answer

This is a fictional example of rejecting a popular proposal within a defined decision role.

As product owner, I had to decide whether to add a public activity feed. The team liked the prototype, and several enthusiastic customers had requested it. However, our current objective was to make a core reporting workflow dependable, and the feed would consume the same engineering and support capacity.

I asked the proponents to explain the customer problem and the expected benefit, then compared it with evidence from a broader set of customers and the unresolved reporting failures. We estimated development and ongoing moderation effort, identified uncertainty and considered a smaller alternative. The prototype's popularity was useful input, but it did not establish enough value to displace the committed work.

I decided not to add the feed to that release. I explained the criteria, credited the team's exploration and recorded what evidence would justify reopening the decision. We kept the research so the effort was not lost, and I made the resulting reporting priorities explicit.

The team completed the agreed reporting fixes and verified the known failure cases. That outcome supported the chosen focus; it did not prove that the rejected feed could never succeed. I learned to separate respect for an idea and its authors from the decision to fund it now.

Follow-up to practice

If you could only recommend rather than decide, how would you present the same evidence to the accountable owner?