Persona Development & User Archetypes

UX Research
Client
Osprey EV Charging Network
Project type
UX Research
Project year
July 2025 - Jan 2026

Problem Statement

I started working on the B2B proposition but we had no framework for who we were designing for, their needs, frustrations, roles, or context. It was necessary to understand these subsets to develop a product that plugged the gap in the market.

Outcomes

I established a comprehensive set of personas that included different types of users, ranging from drivers to fleet managers and internal administrative roles. These personas provided a nuanced understanding of our customers, guiding and ensuring that the product met the needs of all key stakeholders.
The personas ensured that all design decisions were closely aligned with real user needs, leading to a more intuitive product.
Team Cohesion: The shared understanding of user personas fostered stronger team collaboration and more confident, user-focused decisions.
Improved Engagement: We saw better user engagement and satisfaction because the product flows were tailored to specific user archetypes.

Context

As we expanded into the B2B market, we recognized that our approach needed to evolve to address a new set of users. Unlike our previous focus, this meant understanding the distinct needs of fleet managers, administrative roles, and other B2B stakeholders who would interact with our product. This shift in context drove the need for a new set of personas tailored to these business users.

Constraints

I was limited by the fact that this project was being initiated and so data on fleet manager and fleet drivers was not readily available to use. As a result, this was a close collaboration with the commercial team to gain insights from their business acumen to frame launch.

Primary Challenge

We needed to understand how the tasks that drivers and fleet managers would need to complete would change based on their individual personas. These early development of these architypes meant that some key decisions would begin to create these categories naturally. For example, a driver who had a one to one vehicle relationship or a driver that had a one to many vehicle relationship.

Discovery

  • Research planning
  • Survey design
  • Early pattern identification
  • User interviews
No items found.

Design Goals

  • The goal was to surface siloed knowledge by creating a structured way for teams to share the insights they held independently, so everyone could see the same picture.
  • I wanted to establish a shared source of truth for user understanding that could be developed and iterated on as the product and market evolved.
  • The idea was that the natural evolution of these personas would add value to the product,  deliver alignment without disrupting delivery, operating  iteratively without requiring significant time or budget investment.

Principles

  • User-Centtic. Every design decision was anchored in real user needs from the insights during discovery.
  • Clarity first. We prioritised clear, straightforward interfaces that made it easy for users to navigate based on their needs.
  • Consistency. We worked towards consistent UI, patterns and flows to support users expectations within the platforms.

Design Decisions

Evolving Archetypes

With research learnings in hand, the proto personas development meant these transitioned into detailed architypes that recognised core differences between user tasks, needs and frustrations through real user insights. They actively informed key journeys in the product suck as bulk actions to reduce repeat tasks from an actions panel.

Initial Proto Personas

I began with proto personas based on what reasonable assumptions we could make from commercial knowledge to give us a starting point. This working foundation enabled designing for the core audience from an informed stance and ready t be shaped by data.

Validation Research

We reached out to users and conducted email surveys and ran in depth interviews to validate and direct the proto-personas into being reliable and accurate compasses that would guide the product. These steps helped us gain insights about the users mental models of a day in their life and ultimately enabling us to have a more user centric approach.

The Solution

We facilitated collaborative workshops that allowed each team to contribute their independent knowledge, effectively breaking down silos. We then consolidated this information into a central repository of user personas and insights, which served as a living source of truth. This approach ensured that we aligned everyone’s understanding efficiently and without a heavy drain on resources.

No items found.

Learnings

Bringing teams together early surfaced valuable insights that would not have emerged through research alone. Treating personas as a living artefact, rather than a one-off deliverable, made them far more useful over time. Running the work alongside delivery, rather than as a heavyweight initiative, helped it gain adoption without resistance.

Let's work together

For enquiries about product design roles or collaborations, feel free to get in touch.

Some work is subject to confidentiality and can’t be shared publicly, but I’m happy to discuss further examples on request. I aim to respond within one business day.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.