5 Steps to Writing an Effective User StoryAug 2010
When you are in early stage product development, a user story is one of the most important items that you should consider. A user story is a description of a goal/scenario a (typical) user would want to achieve with the product.
Why is a user story so important?
- Whether you are building a product within an organization or you are a start-up, you have to sell your product to those who are willing to sponsor the development. If your product addresses a very clear or common problem and there is a demonstrable market out there, your job becomes easy. But still it may not be suitably clear to everyone how your product will be of help.
- You want to partner with someone to co-create the product or have them tweak a product of theirs to work with your product.
- Explain clearly to the engineering and quality teams a typical use case and the relationship between the product modules.
- Pitch your product to potential customers.
- Consistency when different members of the product team evangelize the product at separate locations at different times.
Here are some steps that you could consider when coming up with a user story.
- List the product modules and their features (on a whiteboard or anyplace the team can see easily) so it is easier to visualize the relationship between them when writing the story. This is important to ensure that your story includes only what your product offers currently while leaving scope for expansion.
- Identify the user who is going to use the product and make the story compelling for her. It makes no sense to write a story with the CEO in mind when the CFO is the one who will be using the product.
- Identify one problem in an area that the user will be responsible for. Else she’ll not be interested.
- Then show how the product helps identify that problem and solve it. It is important here to cover as much of the product features as possible without reaching novel length. Not all features may be useful for a particular person you are pitching to, but will at least include those that matter to her.
- Link it back to a beneficial outcome solving the original problem to close the loop. If it doesn’t help the user, it doesn’t help you. Period. And the user must realize the benefits.
What are some other considerations for writing user stories? What are some other reasons for wiritng a user story? Do you have an example where a user story failed and what did you learn from it?
[image: Flickr/Anna Gutermuth]