06 / 19 · 65+ interviews, six personas, one portal

Supplier Experience

Novartis was rebuilding the platforms it uses to work with suppliers. Over six months, my team of four ran more than 65 interviews, built six validated personas and turned them into a self-service Supplier Portal concept.

Role
Lead UX Strategist
Client
Novartis
Industry
Healthcare & life sciences
Work
UX strategy, User research, Persona development
Team
Four UX practitioners, working inside the Supplier Experience subchapter with the change-management team

When a supplier cannot see where an invoice stands, they send an enquiry, and someone at Novartis has to answer it. The company set out to modernise these workflows with new platforms: supplier requests, self-service registration, Master Data Governance for suppliers (MDG-S) and a Supplier Portal.

Enterprise platforms at Novartis had long been built process first. Requestors, back-office teams, procurement, risk management, business owners and suppliers were rarely asked what they needed. It showed in duplicate records between Ariba and SIM, unclear process status and a steady stream of enquiries that cost both sides time.

What would it take for six very different user groups, spread across countries and systems, to shape a programme that had always been driven by process?

My team of four joined the Supplier Experience subchapter and treated research as part of delivery. A segmentation workshop narrowed the field to the personas that mattered most. Country contacts helped us recruit, and more than 65 anonymous interviews produced six validated archetypes. We shared them in large forums, refined them with stakeholders and used them to design a self-service onboarding flow and a Supplier Portal on OneDS components.

My role

Lead UX Strategist. Led a team of four UX practitioners embedded in the Supplier Experience subchapter. Defined the end-to-end UX strategy, ran the persona segmentation workshop, set up the interview programme and turned the findings into the direction for supplier onboarding and the Supplier Portal.

What made it hard

  • Six groups, one programme

    Requestors, P2P back office, procurement, third-party risk management, suppliers and business owners each had different goals and pain points.

  • A process-first culture

    Platforms had historically been designed around what the technology could do. Getting research into every stage meant changing how the programme made decisions.

  • Global and fragmented

    Users sat in many countries and worked across Ariba, SIM and ServiceNow, with country-specific rules and language needs.

  • Honest feedback in a corporate setting

    People needed a safe, anonymous space to describe what was not working without worrying about the consequences.

Questions we asked

  1. Which customer groups have the most influence on the supplier experience, and which are we not hearing from?
  2. What do suppliers need to see to stop sending enquiries?
  3. Where does work fall between systems such as Ariba and SIM?
  4. How do we keep personas alive once the research team moves on?
01

Mapping the customer groups

A 90-minute online workshop in Miro opened the work. We diverged first, listing every possible persona for each customer group, then converged through dot voting on the ones with the biggest impact on the programme. Six primary groups came out of it: requestors, P2P back office, procurement teams, third-party risk management, suppliers and business owners.

Mapping the customer groups

The segmentation workshop ran remotely on one Miro board, from context to customer groups, votes and next steps.

02

Listening across countries

Country contacts helped us find 10 to 20 participants per persona group, and each received a pre-read before their session. Semi-structured, anonymous interviews covered roles, goals, pain points and aspirations. We clustered the findings in Miro into empathy maps and pain maps. They surfaced duplicate supplier records, unclear process status and a workload peak from November to February.

Listening across countries
Listening across countries

Interview notes were clustered into empathy maps and a source-to-contract pain map.

03

Six validated archetypes

More than 65 interviews produced six archetypes across two work streams, each with a persona sheet, an empathy map and a pain map. We shared early versions with project teams, collected feedback in large forums and iterated before finalising them, so the teams who would use the personas had helped shape them.

Six validated archetypes

Each archetype came as a set: persona sheet, pain map and empathy map.

04

From insight to a self-service portal

The personas pointed to one goal: fewer enquiries through more transparency. The Supplier Portal concept combines guided onboarding, invoice and payment status, a knowledge base and a support centre with a chatbot. It serves large accounts that work with Novartis at a strategic level and small suppliers with little engagement. The UI uses tested OneDS components, and we validated it with users at each stage.

From insight to a self-service portal
From insight to a self-service portal

The experience map linked both supplier archetypes to onboarding, invoice status, a knowledge base and support.

In motion

Outcomes

  • 65+user interviews
  • 6validated archetypes
  • 6customer groups mapped
  • 4UX practitioners in the team
  • Reduced onboarding time through self-service registration and onboarding tools
  • Higher efficiency with fewer manual interventions
  • Better stakeholder collaboration built on validated research insights

What I took away

  • Recruit through local contacts. Country contacts and a promise of anonymity got us answers we would never have heard in a steering meeting.
  • Let users build the personas. Releasing early drafts in open forums did more for adoption than a polished final deck.
  • Plan for the handover. Next time I would set up a living persona catalogue from day one, so the work keeps paying off after the engagement ends.
Lead UX Strategist
Preetham Lawrence
Have a hard problem worth solving?

Let's solve it together.

preetham.lawrence@icloud.com
+41 76 740 46 30Phone
LinkedIn↗ Writing on Medium↗

Design leader based in Zürich, Switzerland. Open to leadership roles and selected collaborations.

© 2026 Preetham LawrenceIndex