Case study

Bringing a Complex B2B Product to Mobile

Beneficiary Experience · Pris

Redesigning a complex experience for people who only needed the essentials

  • Product Design
  • Mobile UX
  • B2B2C
  • Financial Experience
  • Information Architecture
Role
Product Designer
Platform
Mobile

Desktop

Administratormanages
  • programs
  • grants
  • rules
  • processes
Context shift

Mobile

Beneficiarytracks and decides
  • reviews
  • understands
  • tracks
  • decides
The same product served very different needs. The main change was not the viewport, but the perspective.
Navigation through the Pris mobile experience across portfolio, programs, progress, and beneficiary profile.
Portfolio, programs, progress, and profile form an experience organized around the beneficiary.

A different user, with different priorities

The desktop product had grown around administration. On mobile, the beneficiary became the primary user, redefining the entry point, hierarchy, and priority tasks.

My role

I defined the mobile experience, reorganized information architecture and hierarchy, and designed access, portfolio, event, and program flows.

What does someone actually need to know and do when accessing their plans on a phone?

The journey began to follow the beneficiary

The sequence started with the current position, moved to upcoming events, and reached programs when there was something to decide.

  1. Sign in
  2. Understand the current position
  3. Track upcoming events
  4. Access programs
  5. Act when needed
The mobile scope gained its own logic. It was not a reduced copy of the desktop product.

Desktop

What does the system allow people to do?

Mobile

What does this person need to know now?

The portfolio became the starting point

What do I have today?

A summarized view of the assets answered the beneficiary’s most immediate need: understanding their current position.

Pris mobile showing total portfolio value, number of shares, access to programs, and upcoming beneficiary events.
The portfolio concentrates the current position and anticipates events that may require attention.

Upcoming events anticipated what deserved attention

After understanding the current position, the beneficiary needed to know “what happens next?”. Upcoming events became prominent so people could anticipate what deserved attention.

  1. Current position
  2. Next event
  3. Attention / follow-up
The app moves beyond being a snapshot of the portfolio and helps the beneficiary track future events.

Programs connected information and action

  1. Portfolio
  2. Upcoming events
  3. Something requires attention
  4. Program
  5. Accept / decline / act
The Programs area brought this information together and allowed people to move forward when action was required.

A CTA led to this area from relevant points in the experience and sustained the journey: notice → understand → access → act.

The architecture separated the two contexts

Administrative context

Program setup, grants, rules, and complex processes.

Beneficiary on mobile

Information worth reviewing, tracking, and acting on.

Designing for mobile is not deciding what fits on the screen. It is deciding what deserves to be there.

Portfolio, events, and programs in a single journey

  1. Administration-oriented experienceBeneficiary-oriented experience
  2. Large volume of functionalityPrioritized relevant tasks
  3. Navigation by areaPortfolio as the entry point
  4. Static reviewEvent tracking
  5. InformationInformation + action when needed
The product change lies in focus, hierarchy, and the distance between tracking and acting.

The portfolio became the entry point for tracking events and moving into programs whenever action was required.

Pris mobile flow from the portfolio to Programs, with proposals awaiting a response and acceptance confirmation.
The CTA connects the current position to programs awaiting a beneficiary decision.