The problem with User Stories as a framework to think about product is that they make too many assumptions and don’t acknowledge causality. When a task is put in the format of a user story — “As a [type of user], I want [some action], so that [outcome]” — there’s no room to ask ‘Why?’. You’re essentially locked into a particular sequence with no context.
A far better framework is what I call Job Stories, an idea from the really smart guys at intercom. Frame every design problem as a Job, focusing on the triggering event or situation, the motivation and goal, and the intended outcome: When _____ , I want to _____ , so I can _____ . For example, “when an important new customer signs up, I want to be notified, so I can start a conversation with them.”
View original post 182 more words