The Executive Who Saw a Thing on a Flight and Now Wants It Built

A playbook for handling the pet-feature request from your CEO, CPO, or loudest VP — without burning strategy, without getting fired, and without killing the occasional pet feature that is actually the best idea anyone's had all year.

· · · · ·

The email arrives at 10:47 p.m. The subject line is “quick thought.” Quick thoughts from executives are never quick. The body is two paragraphs long, ends with a link to a competitor's landing page, and proposes that your team ship an entire category of feature by the end of the quarter. The email does not ask a question. It describes a decision that has already been made in the mind of a single person, who now expects the rest of the company to catch up.

Welcome to the final hazard of this dispatch: the pet feature. A senior leader has seen, heard, read, or dreamt up a thing, and now wants it built. It is off strategy. It wasn't in the roadmap. Nobody on the team asked for it. And yet here you are, at 10:48 p.m., wondering whether engineering is going to hate you.

The instinct, which is wrong, is to kill the pet feature with strategy. You will lose this fight. You cannot logic an executive out of an idea they had in the shower, because the idea didn't come from logic. It came from pattern-matching, and pattern-matching is the executive's job. Your job is to convert the pattern into a decision everyone can live with.

The Three Species of Pet Feature

The Competitor-Ate-My-Lunch

Executive saw a competitor ship something and now wants parity. Usually triggered by a blog post, a LinkedIn screenshot, or a sales call. Often backed by real anxiety. Sometimes rational, sometimes a reflex.

The Investor-Said

A board member, investor, or advisor mentioned an idea, and the executive is now relaying it with the full weight of “the board.” Usually less considered than it sounds. The investor said it in passing; the executive heard it as an assignment.

The Shower-Idea

The executive had a flash of insight in a moment of low cognitive load and has been thinking about it during calls ever since. The pet feature is now emotionally invested. Attacking the idea feels, to them, like attacking their judgment. Because it is.

Why Saying No Doesn't Work

New PMs try, roughly in order: (1) explaining the roadmap, (2) explaining the strategy, (3) explaining the opportunity cost, (4) sulking about it in 1:1s with their manager. None of this works because none of it addresses the real thing the executive wants, which is not the feature. The real thing the executive wants is the feeling of forward motion on the anxiety that produced the idea. The feature is the shape that feeling took on the flight home.

Solve for the feeling, and you get to rescope the feature. Argue with the feature, and you fight the feeling.

Contrarian note Here is the honest part. Occasionally the pet feature is the best idea anyone in the building has had in six months. Executives see patterns that PMs can't, because they're in rooms PMs aren't. The worst thing you can do is develop a reflex to reject pet features on principle. The second-worst is to accept them on principle. You have to read each one on its merits — which requires you to not-reject it long enough to find out what the merits are.

The Fix — Four Moves

1. Never say no; say “yes, in this form”

The fastest way to a dead career is to send an executive an email that begins “I don't think we should do this.” The fastest way to a preserved strategy is to send an email that begins “yes — here's the smallest version of it that will tell us whether the instinct is right.” You are not refusing. You are converting the executive's wishful feature into a bounded experiment, which is both cheaper and, crucially, less embarrassing if it doesn't work.

2. Reframe as an experiment with a kill criterion

Write a one-paragraph description of a two-week test. Include: what we'll build, what we'll measure, what result kills it, what result escalates it. Send it to the executive with a single question: “is this the shape of the test you were imagining?” Nine times out of ten they say yes, partly because they weren't imagining a shape that precise, and partly because your test is cheaper than their original plan. The kill criterion is the magic part: it gives the executive a graceful way to walk away from the idea later if the numbers don't support it, without feeling like they were wrong.

3. Hold up the strategy mirror

Pet features die the fastest when the executive themself notices that they conflict with a strategy the executive signed off on. Your job is not to tell them this. Your job is to quote them to themselves. Pull up the strategy doc — “We said Q3 was about retention, not acquisition. This feature is an acquisition bet. Want me to reshape it as a retention play, or want to make the case for shifting the Q3 focus?” You have just handed the executive two options, both of which require them to either adjust the feature or adjust the strategy. Either is fine. What you've avoided is the third option, which was “just build it.”

4. Prove the premise, not the solution

Most pet features are solutions to a premise — “customers are churning because we don't have X” — that has never actually been tested. Before you build X, spend forty-eight hours testing the premise. Three customer calls, a small data pull, a look at the churn cohort. Either the premise holds, in which case the feature becomes a strategic bet and you're glad you're building it, or it doesn't, and you now have data you can use to gently retire the idea. You are not arguing with the executive; you are being a grown-up about the evidence.

Phrases That Work

Love the instinct. Here's the smallest version we could ship in two weeks — it would test whether the underlying hypothesis holds without blocking the onboarding work. Want me to spin it up?

Before we build this, I want to spend 48 hours validating the premise. Three customer calls and a cohort pull — if the signal is there, we go hard. If it isn't, we don't waste the quarter.

I want to make sure I frame this correctly for the team — we said Q3 was about retention. Are we adjusting the strategy, or should I reshape this as a retention bet?

When the Pet Feature Is the Right Call

You will, a few times in your career, get a pet feature that is obviously correct and you need to shut up and build it. Signs: the executive cites three unrelated customer conversations, the idea has been mentioned by the exec more than twice across two weeks, the idea makes sense once you hear it and you feel mildly foolish for not having proposed it yourself. When you see all three signs, stop resisting. Reframe the question from “how do I de-prioritise this” to “how do we build this well.” Your job is not to be strategically pure; it is to be right.

Working rule: pet features are not problems to be refused but ideas to be shaped. Your value as a PM is the difference between the feature the executive first described on the flight and the feature that actually gets built. If those are identical, you didn't do your job. If they're entirely different, you didn't do your job either. Shape, don't block.

← Back to Stakeholder Management