Features Do Not Exist (Only Benefits)
Filed Under Human Factors
A bit of a rant, that we really need to quit thinking and speaking in terms of features, and start talking to our clients in terms of the benefits that they will gain.
Comments
7 Responses to “Features Do Not Exist (Only Benefits)”
Nicely done.
In BDD, I tend refer “benefit” as “experience”. When I write executable specs, I write them to describe the experience rather than the implementation.
I’m reticent to conclude that I’m delivering benefit at the time I’m writing specs. We believe or suspect that there’s benefit, but we only really know this at a later time.
Similarly, I don’t refer to a user story template as “As a , I want to so that “. My preferred template is “As a , I want to so that “. There may or may not be business value involved. That often remains to be seen as well.
@Scott,
I understand why you would write specs to describe an experience, but is there a fine difference between application “behavior” and user “experience” besides from which direction you are viewing?
From one point of view they seem to be the same thing, from another potentially different…
[…] Features Do Not Exist (Only Benefits) (Max Pool) […]
LOL I’m glad to see I’m not the only one that finds small irritants in society that hint to large scale fundamental issues. I would of thought the exact same thing…60% lighter…well whoopty doo..what the @#$$ does that mean? enjoyed the post 🙂
[…] Features Do Not Exist (Only Benefits) – Max Pool Happy to see Max continue his video messages. This time a good example of why we ‘ need to quit thinking and speaking in terms of features, and start talking to our clients in terms of the benefits that they will gain ‘ […]
Max, I almost forgot, my reply to this post is here…
http://www.noop.nl/2008/07/oh-my-god-they-fixed-the-bug-you-bastards.html
Well said! Brilliant.
Or perhaps Paula Bean Brillant? ;D