Key Takeaway

Feasibility questions are filters, not checkboxes

• Q1 catches hype-driven proposals
• Q2 catches scope-overreach
• Q3 catches integration-blind optimism

A strong requirements engineer kills bad ideas early — before a line of code is written.