BQ-029 · Failure, feedback, and growth
Tell me about an approach you abandoned after investing significant effort.
Illustrative fictional example · Editorial draft, version 1. Use the structure and reasoning to prepare your own experience. Do not present this sample as your personal history.
What the interviewer may evaluate
These are general coaching criteria; interviewers and roles differ.
- Explain the evidence that invalidated an approach, the investment already made, and how you decided what to stop or retain.
- Can you explain the evidence behind representative operators making safe template changes with previewed effects?
- Can you describe testing predictability before investing in broad flexibility without overstating the outcome?
Before you start
- Explain the evidence that invalidated an approach, the investment already made, and how you decided what to stop or retain.
- Separate personal actions from team outcomes.
Choose an experience that answers the prompt
Suitable examples
- Explain the evidence that invalidated an approach, the investment already made, and how you decided what to stop or retain.
- An experience where you can distinguish your decision from the work owned by other people.
Examples to avoid
- We had spent too much time to change direction, so we had to finish it.
- An example whose outcome you cannot distinguish from a plan or an assumption.
Gather your evidence
- Explain the evidence that invalidated an approach, the investment already made, and how you decided what to stop or retain.
- Your decision, the alternative of continuing a general editor primarily to justify effort already spent, and the reason for the choice.
- The observations that support representative operators making safe template changes with previewed effects and their limitations.
Build the answer
- Situation and responsibility. Explain the evidence that invalidated an approach, the investment already made, and how you decided what to stop or retain.
- Actions and reasoning. Explain what you personally changed, who helped, and why you considered continuing a general editor primarily to justify effort already spent.
- Outcome and evidence. Report representative operators making safe template changes with previewed effects. Distinguish observation from an assumption or future goal.
- Reflection and follow-through. Explain testing predictability before investing in broad flexibility. Name one limitation or remaining follow-up.
Full sample answer and paragraph explanations
Read aloud to check pacing. Expand the annotations to see why each paragraph matters and which detail belongs in a follow-up.
Reveal the full illustrative answer
Situation and responsibility
I spent several weeks building a custom rules editor for an operations workflow. The team expected non-engineers to modify routing without code changes, and the prototype supported nested conditions. I owned the editor implementation. In a task walkthrough, operators could complete simple edits but struggled to predict how combined conditions affected existing rules. The flexibility I had built was creating a correctness risk rather than clearly solving their routine task.
Why this paragraph works
Evidence: An investment and an invalidating task observation.
Why it matters: Identifies a relevant situation and your responsibility before describing the solution.
Prepare for a follow-up: Prepare this follow-up: Why not just improve the editor?
Actions and reasoning
I reviewed the observed mistakes with product and operations instead of treating more documentation as the automatic solution. We found that most real changes involved a small set of approved templates. I proposed stopping the general editor and delivering template-based configuration with previews and validation. I documented what code could be reused and what would be discarded, including the time already spent. We compared that path with continuing the editor and absorbing ongoing training and review costs.
Why this paragraph works
Evidence: A future-value comparison with explicit sunk cost.
Why it matters: Makes a decision and its reasoning visible rather than listing activities.
Prepare for a follow-up: Prepare this follow-up: How did you disclose the investment?
Outcome and evidence
The decision owner accepted the narrower approach. I reused validation utilities, removed the unsupported editing surface, and worked with operators on representative template changes. They could preview the affected routes and identify invalid combinations in those tasks. The prior investment was not recovered simply because some code remained useful. I reported the abandoned work as a cost and the new result as a bounded task improvement, not evidence that the original plan had secretly been successful.
Why this paragraph works
Evidence: A narrower delivered capability and acknowledged waste.
Why it matters: Connects the claimed result to observations and acknowledges their limits.
Prepare for a follow-up: Prepare this follow-up: What did the walkthrough show?
Reflection and follow-through
I learned to evaluate the future value of continuing separately from the desire to justify time already spent. I also changed the sequence for future editor work: test whether people can predict the effect of a change before building broad expressiveness. Stopping was useful because it came with evidence, an owned alternative, and a plan to retire the incomplete surface, rather than leaving two half-supported options in the product.
Why this paragraph works
Evidence: A changed discovery sequence and clean retirement.
Why it matters: Turns the experience into a concrete changed habit or mechanism.
Prepare for a follow-up: Prepare this follow-up: Who decided to stop?
Reveal the concise version — roughly 60–90 seconds
I invested several weeks in a flexible rules editor, then observed operators making mistakes with nested conditions during task walkthroughs. I reviewed the evidence with product and found that most changes fit approved templates. I proposed stopping the general editor and delivering template configuration with validation and previews, while identifying reusable code and discarded effort. The decision owner accepted the trade-off. Operators could complete representative template changes and see their effects; I did not pretend the abandoned investment was recovered. I learned to judge the future value of continuing independently of sunk effort and to test predictability before building a broadly expressive editor.
Improve a weak answer
Weak excerpt
We had spent too much time to change direction, so we had to finish it.
Improved excerpt
I reviewed the observed mistakes with product and operations instead of treating more documentation as the automatic solution. We found that most real changes involved a small set of approved templates. I proposed stopping the general editor and delivering template-based configuration with previews and validation. I documented what code could be reused and what would be discarded, including the time already spent. We compared that path with continuing the editor and absorbing ongoing training and review costs.
The improved excerpt explains a specific decision rather than the unsupported claim in the weak version. Complete it with representative operators making safe template changes with previewed effects, and state the limits of what you observed.
Prepare for probing questions
Attempt each response before opening the guidance. Replace fictional details with your own evidence.
Why not just improve the editor?
We compared that with the smaller template approach, including training and correctness-review costs. The observed routine tasks did not justify broad expressiveness at that stage. The decision concerned future value, not discomfort with difficult work.
How did you disclose the investment?
I stated the time and capability already built, what could be reused, and what would be discarded. Hiding sunk effort would prevent the decision owner from understanding the real project cost.
What did the walkthrough show?
Operators could not reliably predict combined rule effects. That was more consequential than visual preference. I used task errors and the required review burden to reassess the approach.
Who decided to stop?
The product and engineering decision owners accepted the revised scope based on the evidence I brought. I owned the recommendation and implementation transition, not unilateral authority over the entire roadmap.
What prevented two incomplete products?
We removed the unsupported general editing surface and gave the template path explicit ownership. Reusing utilities was separate from leaving an abandoned feature accessible and implicitly supported.
Adjust the evidence to your level
Early-career
Use a bounded project, internship, or volunteer example that demonstrates decision courage. Explain guidance you received rather than claiming senior authority.
Mid-level
Show independent responsibility for a defined outcome, including representative operators making safe template changes with previewed effects. Name dependencies and when you sought help.
Senior
Explain trade-offs with affected colleagues, the verification plan, and testing predictability before investing in broad flexibility. Broader scope needs evidence rather than a larger job title.
Staff
Show a mechanism that changed decisions or capability across teams, including who adopted it and what remained outside your authority. Do not describe a local change as organization-wide influence.
Common mistakes
- Listing tasks without explaining why you considered continuing a general editor primarily to justify effort already spent.
- Claiming representative operators making safe template changes with previewed effects without describing how you observed it.
- Claiming sole credit for decisions or work owned by collaborators.
- Treating a proposed follow-up as already completed.
Build your own answer
This worksheet stays in this page’s memory. It is not saved to your account or this device. Copy or download it before leaving or refreshing. Remove confidential details and use only experiences you can defend.
Self-review against observable evidence
This is a coaching checklist, not a company hiring score. Choose one rating per dimension.
Review each dimension to choose one concrete improvement for your next attempt.
Next exercise
Rehearse your own example, then ask a listener to identify representative operators making safe template changes with previewed effects and the decision that led to it.
Prepare a follow-up on continuing a general editor primarily to justify effort already spent. Replace every fictional detail with your own facts and identify one claim that needs more evidence.