How do you handle a situation where engineering says a feature is impossible?
Model answer
Model answerWhen engineering says impossible, I first ask: impossible forever, or impossible given current constraints? Then I try to understand what's driving it — technical debt, architecture limits, timeline pressure? I'd reframe around the user outcome, not the feature spec: 'The user needs to accomplish X — are there other ways to get there?' Often there's a simpler technical solution that wasn't obvious when the conversation started with a feature request.
Framework · Communication Framework
- EExplore the constraint
Is it permanent or situational? Time, architecture, or knowledge — each has different solutions - CClarify the outcome
Reframe from feature to user need — engineering can often solve the need differently - PPartner, don't push
Collaborative problem-solving beats advocacy — 'how might we' beats 'you have to' - DDocument trade-offs
Record the decision and why — future team members need to know why the shortcut was taken
Related questions
- What is product-market fit and how would you know if you have it?
- You have 3 features requested by customers and only 1 sprint. How do you decide?
- How would you communicate a feature delay to stakeholders?
- How do you say no to a stakeholder's feature request?
- How would you explain your product roadmap to an engineer who thinks all roadmaps are a waste of time?