The Stories We Tell
Humans are wired for stories. Stories activate our minds. They give us experiences and can influence our way of thinking. We naturally search for meaning in the stories that are told to us. It is the reason we use stories as the drivers for sales, marketing, and design.
Tasks Should Tell a Story
In product design, we find ourselves with many tasks that we must complete to reach our goal. In Scrum, you would have these tasks written out on sticky notes all over the walls. You would then place them in what seems a logical order to move to a Sprint for production.
These simple tasks should be much more than just items to check off. They should tell a story. The story they tell will help better define the purpose and the motivation behind each task. When your team understands the narrative, they make better decisions about implementation because they understand the why, not just the what.
The Three-Act Structure of Every Product
All stories follow the same pattern or story arc. They are broken down into three acts, and you can spot these in every movie, book, or TV show you watch. These three acts can be directly applied to your product planning.
Act one: a character with a problem to solve. This could be a specific user role or function that has found itself with conflict. Act two: the character finds the solution and adapts. This is how your user begins to reach their goal through your product. Act three: the character finds resolve and benefits from the solution. Your user is satisfied with the result.
Understanding this story arc and applying it to every project, product, and task will create a more user-driven experience. The best products do not just solve problems. They take users on a journey that feels deliberate, natural, and satisfying.
Related: How To Create A Losing Product and Product Habits.
