How to answer the feature you decided not to build question
The short answer
Interview Coach asks this question in these words:
Tell me about a feature you decided not to build. How did you decide, and who disagreed?
Pick one feature somebody important wanted and you decided against. Name the feature and who wanted it. Then explain the criteria you used: impact on a goal, the number of customers affected, cost, risk. End with what you built instead, who disagreed, and what happened, ideally with a figure from your analytics or a record of the decision.
Check your own answer in Claude with Interview Coach, free
What the interviewer is checking
Saying no is most of product management. The interviewer wants to see that your no had criteria, and that you kept the person who asked on side. The bank lists three things a strong answer does:
- Names the feature and who wanted it. A custom export for the biggest client, a dark mode the CEO saw at a rival. Name the person or group by role.
- Explains the criteria you used to decide. Written criteria beat taste: the goal of the quarter, reach, effort, risk. Say which one decided it.
- Says what you built instead and what happened. The alternative and its effect, plus what happened to the relationship with the person you turned down.
Avoid a story where the feature was obviously bad. A no to a reasonable request shows more judgment.
A structure that works
Interview Coach describes a decision answer in four parts:
- Options. The choices that were on the table. Here: build the feature, build a smaller version, or build something else.
- Criteria. How you weighed them. Here: the criteria you wrote down before deciding.
- Decision. What you chose and who approved it. Here: what you chose and who agreed, including the person you said no to.
- Consequence. What followed, including the cost. Here: what you built, what it did, and what the no cost you.
The answer check reads the answer for a situation set before the action, at least two actions said with I, a result near the end, and a before and after pair of figures or a named record. It also reads the balance between "we" and "I", the length of a spoken answer, and words that weaken an answer: filler, hedges, weak ownership and vague claims.
Answers as written, and what the check says
Illustrative, not a real client. Each answer below was sent on its own through the answer check of Interview Coach. All of them are also marked short for a spoken answer, because each is one or two sentences; the table shows the other finding, word for word, and one way to fix it.
| Answer as written | What the check says | What to change |
|---|---|---|
| When the largest client asked for a custom export, it was scored against the quarter goal and a standard export was proposed to the account director, and the director agreed to the standard export, per the decision log. | No sentence says what you did yourself, with I. | Say which of these steps were yours, with I. |
| When the largest client asked for a custom export, I scored it against the quarter goal, and the director agreed to the standard export, per the decision log. | Only one first person action found. Say what you did yourself. | Add the second step that was yours, in the order you took it. |
| When a client asked for an export, we scored requests, we sized options, we met sales, we met the client and we ranked the backlog. I scored it and I proposed another, and the director agreed, per the decision log. | Mostly we and the team. The interviewer cannot tell which part was yours. | Give the team's work one sentence, then say which calls were yours. |
| I scored it against the quarter goal and I proposed a standard export to the account director, and the director agreed to the standard export, per the decision log. | No context is set before the action. Add what was at stake. | Open with what was at stake before you acted. |
| When the largest client asked for a custom export, I scored it against the quarter goal and I proposed a standard export to the account director, per the decision log. | No result is named. Say what changed. | Say what changed in the end, and where it shows. |
| When the largest client asked for a custom export, I scored it against the quarter goal and I proposed a standard export to the account director, and the director agreed to the standard export. | No figure and no named record. Name where the result shows, if you have it. | Name where the outcome is recorded, or give the figure before and after. |
| When the largest client asked for a custom export, I scored it against the quarter goal and I proposed a standard export to the account director, and the standard export shipped in 4 weeks. | A figure is given, with no starting point. | Give the starting figure too, or name the record that holds both. |
| When the largest client asked for a custom export, I kind of scored it against the quarter goal and I proposed a standard export to the account director, and the director agreed to the standard export, per the decision log. | Filler words found. | Drop the filler word and say the step plainly. |
The check never adds a figure or a record for you. If the no was later reversed, say what changed.
An illustrative answer
Illustrative, not a real client. Every figure is invented. This answer gets all nine marks of the decision check: length, situation, own action, team versus me, result, evidence, and no vague words, filler or hedges.
When I was the product manager for a scheduling app used by home care agencies, our largest client asked for a custom export of visit data in their own format, and the account director wanted it in the next release. I scored the request against the quarter goal, which was activation of new agencies, and against the other requests in the backlog. The custom export served one client and needed six weeks of work. I proposed a standard export with configurable columns instead: the client could map it to their format, and every other agency could use it too. I took both options to the account director and the client's operations lead, and they agreed to the standard export with a mapping template we wrote for them. It shipped in four weeks. In the quarter after release, 38 percent of agencies used the export against none before, per the product analytics dashboard, and the client renewed.
Why it works. The request has a name and an owner. The criteria come before the decision, the alternative is a real product choice, the people affected agree, and the end has a before and after figure and a business result.
What the check cannot see
The answer check reads the words of your answer, not the judgment behind them. This answer, sent on its own, gets every mark except length:
When a client asked for an export, I scored it and I proposed another, and the director agreed, per the decision log.
Every structural mark but length. An interviewer would still ask: what feature, what criteria, what did you build instead, and how did the client react? The criteria are the answer to this question, and they are missing here.
Choosing your story
- Pick a reasonable request. A bad idea is easy to refuse. A good idea that lost to a better one shows prioritization.
- Pick one with a powerful requester. A big client, an executive, sales. The question is about holding a line under pressure.
- Show criteria you wrote down. A scoring model, the quarter goal, a reach estimate. Taste alone sounds arbitrary.
- Say what happened after. What you built instead and what it did is the proof that the no was right.
Your resume is where an interviewer looks for these stories, and a line such as "owned roadmap prioritization" invites this question. Get a free AI review of your resume and see which lines Reed flags first.
Prepare the follow-up questions
- How did you tell the person who asked that you would not build it?
- What prioritization framework do you use, and where does it fail?
- Have you ever reversed a no? What changed?
Run the free review on your own resume lines.
Check your answer with Interview Coach in Claude
This question is in the product manager track of the Interview Coach question bank. Write your answer the way you would say it and ask for a check.
- It reads the answer for a situation, your own action said with I, a result, and a before and after figure or a named record.
- It flags filler, hedging, weak ownership and vague claims, and says when the answer is short or long for a spoken answer.
- It does not judge whether the story is true or good, and it never adds a figure you did not give.
Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.
Free in Claude, no account. We do not store the text you send through it.
Questions
What if the feature was built later anyway?
That can still be a good answer. Say what changed: new data, a new goal, a different cost. Changing a decision for a reason is part of the job.
Is this question only for product managers?
It is in the product manager track of the Interview Coach question bank, and product owner titles meet it too. Program managers face it as "a project you stopped".
Does Interview Coach know whether my story is true?
No. Interview Coach runs in Claude and checks the structure of an answer by fixed rules: a situation, your own action, a result, a figure or a record. It does not judge whether the story is true or good. You decide what to say.
Keep going
- Interview questions: Product manager interview questions
- Interview questions: Product owner interview questions
- Guide: How to answer the stakeholder conflict question
- Guide: How to answer the influence without authority question
- Guide: How to answer the hardest deadline question
- Guide: How to answer the product metric question
- Guide: How to answer the product discovery question
- Guide: How to answer the failed project question
- Guide: How to answer the scope change question
- Guide: How to answer the project risk question
Last updated: October 14, 2026