In the engineering biz, people identify "use cases" to justify new designs, meaning specific ways that a design will be used and useful in the real world. Use cases are not invented excuses -- they have to identify real value to real people.
If there's no use case, or only a few, no action should be taken.
For example:
Gaming Use Case
Stakeholders: Casual gamers who like retro games
Situation:
1. Stakeholder is not at home or near laptop -> no access to PC games or gaming console.
Stakeholder wants to play video game, but not some lame phone-based game.
2. Stakeholder takes out Pandora device, boots Linux.
3. Stakeholder uses pen to tap on icon for gaming software, selects game.
4. Stakeholder plays game using built-in controls.
If there's no use case, or only a few, no action should be taken.
For example:
Gaming Use Case
Stakeholders: Casual gamers who like retro games
Situation:
1. Stakeholder is not at home or near laptop -> no access to PC games or gaming console.
Stakeholder wants to play video game, but not some lame phone-based game.
2. Stakeholder takes out Pandora device, boots Linux.
3. Stakeholder uses pen to tap on icon for gaming software, selects game.
4. Stakeholder plays game using built-in controls.