Importance of storytelling in designs
The connection
Over time, I've realized that the most impactful designs aren’t just functional, they tell a story. Early in my career, I noticed that designs lacking a clear narrative often felt disconnected with users, or PMs, or myself. Users didn’t just need information—they needed some context, flow, and a sense of purpose.
Marvel's Avengers
Think about how the Marvel's Avengers movies set the stage. Marvel didn’t just drop Endgame out of nowhere. It started with Iron Man, then built a connection across multiple films, giving each character an arc, planting hints, creating anticipation. By the time we got to Endgame, every little moment felt earned. (Sorry. weird example, but you might relate 😅)
The process of design is no different. A great product doesn’t just throw features at users—it guides them through a well-crafted experience.
My experiences
I’ve seen this firsthand. In one project, I was tasked with improving a dashboard that monitored shipments. The product team saw it as just adding filters and graphs, but instead of presenting a list of features, I told a story:
"Imagine you're a supply chain manager rushing to identify delays. You opened a card—overwhelmed with data, struggling to find what matters. Now, imagine if you saw a clear risk summary first, with urgent shipments highlighted, and... only the most relevant data upfront?"
That shift—from a list of features to a real-world scenario, completely changed how the team saw the problem. Now, the PMs weren’t just making Jira tickets; they were helping some manager make faster decisions. They were investing in a solution that directly impacted business KPIs.
My thoughts
Storytelling is about connecting the dots. Making every pixel, every interaction feel like part of a bigger picture. It keeps users engaged, removes friction, and makes the experience feel intentional. Because at the end of the day, no one remembers just a screen—they remember the journey it took them on.