The whole category in one page.
A FEATURE REQUEST IS A PROPOSED SOLUTION TO A PROBLEM NOBODY EXAMINED
Ask what they were trying to do, what happens now, and what is difficult about it. The better solution frequently serves more people than the thing requested.
ASK ABOUT WHAT PEOPLE ACTUALLY DID, NOT WHAT THEY WOULD DO
Past behaviour is evidence; intention is speculation. Keep your idea out of the conversation until you understand their situation.
WORKAROUNDS ARE THE STRONGEST SIGNAL OF A REAL PROBLEM
Nobody builds a spreadsheet to avoid something that does not matter. Look for manual processes and repeated questions.
PRIORITISATION IS DECIDING WHAT NOT TO DO
Every accepted feature costs building, maintenance and complexity forever. Say no clearly with a reason, because vague deferral produces repeated asking.
DECIDE WHAT YOU EXPECT TO CHANGE BEFORE YOU BUILD
Afterwards, any outcome can be justified. Continued use measures value; initial use only measures curiosity.
BUILDING IS THE MOST EXPENSIVE WAY TO TEST AN IDEA
Deliver the outcome manually for a few customers first. A commitment — time, money, a decision — is evidence; expressed interest is free.
RESERVE A STATED PROPORTION OF CAPACITY FOR MAINTENANCE, BECAUSE NEW FEATURES ALWAYS WIN OTHERWISE
TREAT REPEATED SUPPORT QUESTIONS AS PRODUCT FAILURES, NOT DOCUMENTATION FAILURES
AND REMOVE FEATURES NOBODY USES, SINCE THEY COST MAINTENANCE AND COMPLICATE EVERYTHING AROUND THEM
