Spring GDS 25th Anniversary
A logistics company that ships to 190 countries built something to ship to itself.
A user persona is a profile that stands in for a real group of users. It captures who they are, what they are trying to do, and what gets in their way. A good persona has a goal, a context, and a few frustrations that the product needs to answer. A bad one has a stock photo and a favorite coffee order.
A persona is not the same as the research behind it. Research is the raw material: interviews, surveys, support tickets, analytics. A persona is the synthesis, a way to make patterns in that evidence usable for the whole team. The danger is inventing one from assumptions. A persona built without behavioral insights tells you what the team wishes were true, not what users actually do. When a fintech team designs for "Marcus, a freelancer who chases late invoices," everyone can picture who the dunning feature is for and why it matters.
Personas earn their keep when they shape decisions. They settle arguments about features, frame design reviews, and keep edge cases honest. Three or four sharp personas beat a dozen vague ones.
We build personas from evidence, not from a workshop guess. Our UX research and behavioral insights work feeds them: real interviews, real usage data, real patterns. If we cannot point to where a trait came from, it does not go on the page.
Then we keep them in front of the people making decisions. A persona that lives in a slide deck is dead weight. We bring ours into design reviews and prioritization, so when a client asks why a flow works one way, the answer traces back to a user we both understand. As we learn more through user testing, the personas get sharper.
Designing for users you can't quite picture yet? Let's get specific.
A logistics company that ships to 190 countries built something to ship to itself.
Turning a brand into a working business.
Half a million people. One app. Zero chaos.















