The problem: a feature list is growing faster than the explanation
A team can agree on more features without agreeing on what problem matters most. Before the next planning meeting, ask for a recent example of the difficulty the proposed work is meant to address.
One useful framework
Use four headings: observation, explanation, alternatives and next commitment. Put each statement under the heading it belongs to. This can reveal when an assumption has quietly become a requirement.
One illustrative example
Fictional teaching example. Customers call about deliveries. The observation is repeated requests for updates. “We need an app” is one possible explanation or response. Clearer messages, a shared status page and a portal are alternatives worth examining.
One action to consider
Choose one item from your feature list. Write the problem it addresses without mentioning the feature. If you cannot do that yet, use the next discussion to investigate the problem before extending the specification.
This is a sample edition for editorial review. No newsletter has been sent, and this page does not subscribe you to anything.