Tips on how to practice

4. Dedicate the first few minutes of your rehearsal time for ‘warm ups' such as: right hand Exercises —full bow strokes, 10 up bow strokes, 10 down bow strokes, run the G major scale (2 octaves) wih…


独家优惠奖金 100% 高达 1 BTC + 180 免费旋转

The 3 UX principles behind a powerful user story

Define your type of user, their mission or goal, and what kind of pain points or obstacle s/he might encounter during their journey.
Define your type of user, their mission or goal, and what kind of pain points or obstacle s/he might encounter during their journey.

User, mission, paint points

A user story is a dynamic, fictional narrative that gives the user persona its overarching story. It highlights the type of user, her/his mission, and possible pain points.

User stories complement the user persona. Sometimes, user stories might be referred to as scenarios.

A user story is told as a 3-part sentence. It succinctly unfolds the user’s journey to complement the mission/goal, while encountering pain points/obstacles in so doing.

User stories are accessed by all members of the UX team and stakeholders. They serve to further empathize with the user for whom the product is being designed for. With a user story as a reference, important design decisions can get prioritized throughout the entire development process.

In a fiction, we identify with the hero, her/his goal to be achieved for the story’s conclusion, all the while encountering conflict during the journey of reaching the goal.

The same is true for a user story. In the user story, the user is doing a specific tasks using a product or service to fulfill a need. The user is our hero, engaged in accomplishing a mission or reaching a goal, but dealing with pain points or conflict along the way.

As UX designers, we need to identify the user’s story and tell it in real, yet fictional, form. To phrase such user story in classic short form, we employ a 3-part sentence structure that allows us define the hero, the goal, and the conflict in detail.

First, we define who our type of user, or hero, is. Secondly, we define what action our user needs to take to reach their goal. Thirdly, we define why this action needs to be taken and for what type of benefit.

Add a comment

Related posts:


By reusing blocks in a smart way you can reduce the amount of CSS code you will have to code and look after. If you follow the rules of BEM you can have super effective CSS. It’s all about practice…

The Power of a Daily 20 Minute Walk

How wandering around for a little while can boost your productivity and your creativity.

CMGT 410 Week 1 Project Plan Draft

A project plan is a document created at the beginning of the project lifecycle that gives stakeholders and everyone else involved in a project a clear idea of what a project will entail in terms of…