On a recent project, I used user personas to improve the design of a web dashboard for support teams. One of our key personas was Anna - a team lead who handles lots of tickets and checks reports daily. She often works under pressure and needs to find information quickly. To build the persona, we used Notion to document user interviews and organise insights. Then I created a simple persona card in Figma, so the whole team could refer to it during design and development. I also used Miro to map out user stories and user flows - this helped connect her goals to real interface decisions. For example, we simplified the layout so that key actions were visible right away, used clear labels, and reduced distractions. The persona helped me stay focused on real user needs, not just assumptions. Having those tools made the process faster and more collaborative, and led to a design that felt more useful and intuitive.
I learned the hard way that user personas need to capture workflow pain points, not just business objectives. When Asia Deal Hub approached me to redesign their dashboard, we initially created personas based on deal sizes—"$100M merger executives" and "startup founders seeking partnerships." But these missed the actual user struggle. The breakthrough came during stakeholder interviews when I finded users weren't just creating deals—they were drowning in complexity. New users would abandon their first deal creation because our 15-step process felt overwhelming. So I redesigned the entire onboarding flow around a single persona insight: "First-time users need to feel successful, not comprehensive." We stripped the initial deal creation down to a simple modal with illustrations showing the process step-by-step. Instead of asking for 15 data points upfront, we focused on just the essentials to get users past that first psychological hurdle. The result was dramatically higher completion rates for first-time deal creation. This taught me that the most valuable personas aren't about who your users are—they're about the specific moment when your users want to quit. Design for that moment, and everything else becomes easier.
I'm Steve Morris, Founder and CEO of NEWMEDIA.COM. Here's how we used personas to guide our UI work for a national coupon platform and a few real-world strategies for making user research drive a real culture shift, not just a new Figma file. Three Personas Drove Segmented, High-ROI UI Decisions First we identified three clear user types: the Budget Couponer, who tries to save as much as possible and is willing to put up with some hassle; the High Value Couponer, who wants top-tier, curated deals that reflect brand reputation or values; and the Convenient Couponer, who prioritizes effortless, digital savings. These weren't just made-up profiles. Each one was supported by interviews and actual user data, such as seeing that Budget Couponers would use multiple apps to maximize rebates, while Convenient Couponers would leave if anything involved more than a couple of clicks. Every persona shaped product and UI features directly. For Budget Couponers, we added features like a "clip all" button and made offers from Walmart and Target more visible, since our data showed these users spent much more time looking at weekly flyers. For High Value Couponers, we built customizable brand filters and sent them email recaps so they could keep track of their best finds. For the digital-first Convenience group, we focused on single-swipe activations and made onboarding ultra-simple, which cut the average time to first savings in half—from four minutes to under two. When the results were analyzed, tailoring the experience to each persona didn't just improve engagement. Repeat coupon usage jumped from 18% to 23% in just six weeks after launch, which matches up with McKinsey's findings that 78% of customers come back if the experience is personalized. We didn't stop at just making personas on paper. The biggest breakthrough internally came from capturing video of real users on grocery runs. When engineers and business teams watched these unfiltered videos, abstract problems became real - people struggling with vague offer rules, getting excited when a coupon loaded in one click, or getting frustrated when paper and digital deals conflicted. Sharing these videos created genuine understanding in a way no persona document ever could. Suddenly, ongoing arguments about unusual cases made sense; they weren't hypothetical anymore. If you want your team to truly empathize, nothing beats showing them real user footage. It's far more effective than heatmaps or survey scores.
At AppMakers, one of the most powerful shifts we made in our web UI design process came from deeply investing in user personas during a wellness app project. We weren't just designing for "users" anymore—we were designing for Jess, a 34-year-old single mom juggling two kids and a side hustle, trying to squeeze in mindfulness without tech overwhelm. Her story wasn't just a paragraph on a board, it lived in our Figma flows, it dictated button placements, onboarding tone, and how we approached feature prioritization. We realized Jess didn't want endless choices. She wanted one calming option that worked now. That insight helped us strip down a cluttered interface into something clean, intuitive, and actually helpful. Our retention numbers improved, but more than that—we stopped designing for edge cases or abstract demographics. Personas made the design personal, and that changed everything. It made the UI not just usable, but empathetic.
We have found that incorporating user personas in the research process before designing is of the utmost importance. In one of our projects, we worked with Tennessee State University to create a mobile app that provides access to jobs and opportunities in the field of agricultural science. Within our research process, we conducted in-person interviews on campus in Nashville with both students and professors at the College of Agriculture. We also explored the school and farm. This real exposure completely changed our initial ideas for the product. It allowed us to pinpoint our target audience's exact needs and pain points. These interviews directly led to the mobile app's success and ensured the importance of serving the intended audience.
In one of our most recent Shopify projects, we redesigned the user interface (UI) for a direct-to-consumer skincare brand aimed at Gen Z consumers using a lot of user personas and user stories. Based on customer information, survey results, and support chat logs, we developed comprehensive user personas. One important character we created was "Leila," a 22-year-old student who mostly shops on her phone, is extremely frugal, and is greatly impacted by peer reviews and social media. Her main complaints were unclear promotions, a lack of trust signals, and the excessive number of clicks required to locate products. We created user stories such as these using Leila's persona: "As Leila, I want to be able to quickly compare the best products on my phone without having to read dozens of reviews." "As Leila, I want to understand if the product is cruelty-free and clean, so I feel good about what I'm buying." These tales assisted us in ranking features such as: A mobile product comparison bar that is sticky Certifications and trust badges above the fold Reviews driven by user-generated content are shown directly on the product listing. As a result, the interface became clearer and easier to use, which increased the mobile conversion rate by 22% and decreased category page bounce rates. It was simpler for the entire team - developers, designers, and even marketers -to remain focused on actual user needs rather than conjectured ones by using personas and stories. It helped us concentrate on what really mattered and firmly rooted the design process in empathy.
The local service client we were building a lead-gen site was just getting unqualified leads. We did not simply adjust the layout or the color scheme, we took a step back and developed two important user personas using real client calls, one was the ideal client that they wanted and the other was a typical but inappropriate lead. We drew the map of what they were interested in, what they were confused about on the existing site, and what they needed to see to come to the decision. This entirely changed the UI approach. On the perfect persona, we placed the primary benefit of the service more prominently on the page and streamlined the contact process. In the case of poor fit persona, we have added a pricing guide and more defined boundaries of service to allow them to self-select out. It was not about being glamorous design. It was all about making things smooth with the right individuals and screening out the others without being callous. That transparency made the site more usable, and more importantly it also enhanced the quality of leads. Less time wasting tyre-kickers, more interested buyers and a far more pleasant time being had by all.
SEO and SMO Specialist, Web Development, Founder & CEO at SEO Echelon
Answered 7 months ago
Good Day, In the redesign of a client's health care site we turned to user personas. We mapped out what a typical patient's journey looks like for example someone in a rush which is in search of quick answers and from that we simplified the interface and reduced the number of clicks to key information. We did this with an eye towards design that is empirical and which creates an experience that is intuitive not overwhelming. If you decide to use this quote, I'd love to stay connected! Feel free to reach me at spencergarret_fernandez@seoechelon.com