State the problem to be solved, not the proposed solution.

[jlengstorf]

In large companies, it's easy to lose the original thread.

1. There is a problem with the product
2. A meeting happens
3. A solution is proposed to correct the problem
4. The solution is added to a feature list
5. Work begins
6. Something changes and the feature no longer solves the problem
7. No one remembers what the problem was
8. A feature ships that makes the problem worse

This can be corrected by changing the way we make our todo lists: instead of writing down a feature to implement ("add new header"), write down the problem to be solved ("people can't find the get started button").

Features lock you into a narrow scope of thinking; problems remind you why a feature should exist in the first place and encourage iteration instead of feature-driven deadlines.