Right idea, wrong moment: why most bad product decisions aren't bad ideas

Most of the product requests I've had to say no to weren't bad ideas. That took me longer to accept than I'd like to admit, because saying no feels like disagreeing with the idea. It usually isn't. Almost every request I've pushed back on turned out to be directionally correct and badly placed — aimed at the right goal from the wrong position. The job wasn't to reject it. It was to find where it actually belonged.

Take a fraud-validation request I once received: run a check every time a customer selects a payment method. The instinct was right — protect the business from fraud. The placement was wrong. Payment-method selection is a browsing moment, not a buying one; most people who tap it never complete an order. Firing a paid fraud check there meant taxing browsers to catch buyers. The fix wasn't to weaken the control, it was to move it — to the moment a customer actually signals intent to purchase. Same protection, aimed at the right point in the funnel instead of the most convenient one.

I've seen the same pattern show up one level up, at the level of whose interest a request actually serves. A team once asked to switch a vendor because they were personally comfortable with an alternative. The comfort was real. But comfort is a benefit that accrues to one team, while the cost of switching — lost platform knowledge, a new ramp-up curve, migration risk — lands on everyone downstream of that vendor. The request wasn't wrong to want ease of collaboration. It was solving for the wrong unit of "who benefits." Once you separate the real benefit from who's asking for it, the right answer sometimes is still no — not because the want was illegitimate, but because it was scoped to a team when it needed to be scoped to a platform.

The version of this that took me longest to sit with wasn't about a funnel or a vendor. It was about timing at the level of an entire organization.

I once built the case for taking a platform that worked well in a single market and making it the standard across the group — the evidence was there: review sentiment analysis, direct market comparisons, a clear operational logic for why one proven approach beats several parallel ones. I took it to executives. It landed. And then the organization restructured, direction changed, and the initiative as I'd pitched it didn't ship.

For a while I read that as a loss, because it's easy to measure an initiative by whether it survived intact. But the analysis didn't disappear, and neither did the standards it produced. They became the operating discipline for the platform I now own outright in the group's flagship market, and they became the basis for how I guide product teams in two other regions today. The initiative didn't fail. It arrived at the wrong organizational moment to ship as originally scoped — and it got relocated instead, into a role built for exactly what it had already proven.

That's the pattern across all three: a fraud check misplaced in the funnel, a vendor request misscoped to a team instead of a platform, a standardization case that was analytically sound but organizationally early. None of them needed to be killed. They needed to be moved — earlier or later, up a level or down one, redirected into whatever structure could actually hold them at the time.

This is, I think, the most underrated skill in product leadership, and it's almost never named directly. Junior instinct treats every request as binary: approve it or reject it. Senior instinct asks a different question first — not "is this right," but "is this right here, right now, for this audience." Most of the time the answer to the first question is yes and the answer to the second is no, and conflating them is where good ideas go to die unnecessarily, and where leaders earn a reputation for blocking things that later turn out to have been correct all along.

The skill isn't saying no well. It's diagnosing where an idea is misplaced — in the funnel, in the org chart, in the calendar — and having the patience to relocate it instead of the reflex to kill it. The ideas that survive that process tend to arrive stronger than they started, because they've been tested against exactly the constraint that was going to break them.