“I want”, “I need”
Implicit in both statements is a crucial word.
“I think I want”, “I think I need”
The fact that we want or need something implies we have thought about it. At least long enough to utter the words. But it doesn’t imply how much thought, nor how rational.
“I want” is much more powerful than “I think I want.” The former implies confidence, the latter implies doubt. Most of the time we’re probably somewhere in between.
User stories are a tool to have a conversation about creating and changing software to meet needs and wants. User stories help us address who, what and why:
As a (who)
I want (what)
So that (why)
There’s no need to enforce this or any other format, so long as who, what and why are discussed. Alternate formats have been proposed, such as the following:
In order to (why)
As a (who)
I want (what)
This example puts why before what. I agree that type of thinking is critical. Much of the value in user stories is the opportunity to discuss the format itself. A chance to reflect about what may be lacking in our normal communication.
I think it may be valuable to alter the format further, or at least talk about it:
In order to (why)
As a (who)
I think I want (what)
Why risk over confidence in (what) we want? So long as we’re fulfilling the purpose embodied in (why) shouldn’t we lean towards encouraging others to have our back. To help us ensure (what) we want will maximize the benefit. To help us question (what) and propose alternatives? To avoid blindly creating something that may not be what we need.