Summary:
Designers are Problem Solvers & Storytellers:
In my opinion, I believe we are both problem solvers and storytellers. In every project, I focus on understanding the user's needs and finding creative ways to meet them. Design helps me share ideas in a way that connects with people. It's not just about how things look, it's about making something useful, meaningful, and easy to engage with.
Designing a user journey with the mindset of a storyteller:

- Act 1: Exposition The beginning, where the characters, setting, and central conflict are introduced. This act sets the stage for the story and engages the audience’s interest.
- Act 2: Confrontation (Rising Action) The middle, where the conflict intensifies, obstacles are faced, tension builds and climax is reached. This act comprises the bulk of the story and keeps the audience engaged.
- Act 3: Resolution (Falling Action) The conclusion, where the central conflict is resolved, loose ends are tied up, and the story reaches its denouement. This act provides closure and satisfaction to the audience.
By thinking of the user journey as a narrative, we can ensure that each stage of the experience is compelling and meaningful, leading users through a seamless and memorable experience.
Story Mountain:
This is also known as Freytag’s pyramid or the hero’s journey.

- Exposition: Introduce the user, their needs, tech skills, and how they found the app. The more details, the more relatable the story.
- Rising Action: Present the challenge, such as getting to a location on time. Introduce obstacles like traffic or time pressure.
- Climax: Reveal the turning point, showing either the app’s success or failure. This could be real-time tracking working or login issues causing frustration.
- Falling Action: Show how the problem is solved. If the app works, the user arrives on time: if it fails, better design or support could have helped.
- Resolution: Conclude with the outcome whether the app succeeded, leading to a recommendation, or failed, leaving the user frustrated.
Designing a user journey this way allows us to better understand the user's needs, the challenges they encounter, and how the app can either solve their problems or create new ones, shaping their overall experience and perception.