Paragon

Paragon — B2B operations platform
Context:

Paragon is a manufacturing company that developed a B2B operations platform to help production operators manage tasks, workflows, and orders more efficiently.

Request:

Redesign current B2B solution because of low adoption.

Country:

Great Britain

My Role:
Product Designer (End-to-End Ownership) Led UX audit, research, and redesign. Conducted interviews and usability testings. Facilitated workshops with stakeholders. Delivered validated UX/UI solution and supported implementation.

Challenge

Despite full functionality, the Paragon B2B system had low adoption and high friction: operators struggled to complete tasks efficiently, workflows in the system did not match real processes, excessive navigation and manual searching slowed down operations.

1 /

UX Audit

Conducted a full audit of the existing system to identify:

  • usability issues
  • inconsistencies in interaction patterns
  • navigation and information architecture problems

Outcome: Defined key friction areas and initial hypotheses.

Insight: Critical issues were discovered at this stage, as the whole system wasn't designed for a touchscreen and operator's working environment.

UX audit findings
2 /

User Interviews

Conducted 8+ interviews with operators and stakeholders.

Goals:

  • understand user motivations and constraints
  • map real workflows across departments

Key insights:

  • operators relied on memory and workarounds
  • system did not reflect real task sequences
  • high cognitive load during task execution
User interviews
3 /

Workflow Discovery Workshop

Facilitated a workshop with stakeholders to:

  • align on actual workflows
  • visualize task dependencies
  • identify breakdown points

Created a shared understanding between business and users, reducing assumption gaps.

Workflow discovery workshop
4 /

Personas

Synthesised research into personas to:

  • represent key user groups
  • communicate needs to stakeholders
  • support decision-making

Shifted discussions from feature-based → user-centered thinking.

User personas
5 /

Usability Testing (Current System)

Conducted usability testing sessions to:

  • validate research findings
  • observe real task execution
  • measure efficiency and errors

Findings:

  • high task completion time
  • frequent navigation errors
Usability testing — current system
6 /

Business Impact Calculation

Quantified inefficiencies by translating UX problems into business metrics.

Estimated impact:

  • ~20–30% time loss per operator
  • significant hidden operational cost

This step was critical in aligning stakeholders and securing redesign support.

Business impact calculation
7 /

Redesign (HCD Approach)

For a new solution I took into consideration operator's working environment, department workflow and data necessary for task fulfilment.

Among features proposed for the business:

  • Changed button system — added metaphor of clickability by adding volume and space (skeuomorphism)
  • Color, clear contrast and use of Blue as primary action color for best accessibility rate
  • Font size was illegible for operators — highly increased where needed
  • Navigation made self-evident based on interview findings; improved content organisation
  • Eliminated extra information and visual distractions on each production stage
  • Improved filtering and search solutions
Redesign — before and after
Paragon redesign — HCD solution overview
8 /

Usability Testing (Redesign)

Tested redesigned solution with users.

Measured:

  • task completion time
  • error rate
  • user satisfaction

Also conducted a survey to capture overall perception.

  • improved clarity
  • faster task execution
  • positive user feedback
Usability testing — redesign validation
9 /

Iteration & Implementation

Identified improvements for the first iteration.

Delivered refinements based on testing.

Supported implementation and rollout.

Iteration and implementation
Timeline:

6 months (research → redesign → validation)

Team:

1 Product Designer (me, full ownership)

Impact:

User Impact

  • Reduced time to complete tasks (~20–40% faster)
  • Eliminated need for manual search in workflows
  • Increased clarity of task prioritisation
  • Improved onboarding experience
  • Operators transitioned to the new system after onboarding
  • Reduced reliance on external tools and manual processes

Business impact

  • Real-time visibility into task execution
  • Improved capacity planning and workload distribution
  • Reduced operational inefficiencies
  • Increased adoption of the system
  • Successful rollout into production

Due to the success of the redesign:

Paragon extended the collaboration to the other departments, expanded scope, scaled the design team, and signed a long-term contract.

Paragon (Part II)

One of the biggest wins of previous cooperation with Paragon was, their perception switch from "girl (designer) who does fancy images" into "researcher that brings sense to our digital product."

I recommended onsite research in London, because after the first phase I've realised that we are missing a lot of details that are not described in the process and happens in real life and could be only observed and then documented.

33 primary
interviews
60+ hours of interviews
& observations
7 usability
testings
10+ hours of
usability sessions
Paragon — onsite factory research

Ethnographic Research

It reveals user behaviour in real life context uncovering hidden pain points, workarounds, and workflow inefficiencies that are often missed in interviews.

Ethnographic research — factory observation
Ethnographic research — workstation observation

Workarounds

Collecting workarounds and real process environment insights.

Because when the user is really struggling with the process... He is trying to create his own solutions how to make it easier. This is our point to pay attention.

Workaround — invented easy coding for tasks

Invented easy coding for tasks (in red)

Workaround — collected own archive with visual task examples

Collected own archive with visual task's examples

Workaround — cheatsheet for task type and machine operation

Cheatsheet for task type and machine operation №

Workaround — message to handover shift

Message to handover shift to other operator

Pain point — machine often breaks down but no status in system

Machine often breaks down, but there is no such status in system

Pain point — no touchscreen, user needs to type by mouse

No touchscreen, so user needs to type in info by mouse

Pain point — touchscreen position inconvenient

Position of touchscreen doesn't allow convenient work

Pain point — forget to resume paused job, screen went black

Forget to resume paused job, because screen turned black

1 /

Processing User Interviews

The results of conducted user research were deeply learned and analysed. Translated into List of pain points later processed into Interview findings, clustering them and prioritising into key finding based on severity and frequency rate.

Processing user interviews — synthesis
2 /

User Journey Mapping

To cover the whole operational process and not miss any action that can be important for future solution usefulness.

  • To highlight pain points
  • Identify opportunities for improvements
User journey mapping
3 /

Ideation

Generated on brainstorming sessions — ideas were evolved into List of improvements and mind map of improved process itself.

Ideation — brainstorming session
4 /

Design

With an established design system already in place, focus shifted entirely to information architecture and workflow logic — ensuring the solution reflected real operator sequences, not assumed ones.

Design — IA and workflow logic
5 /

Usability Testings

7 sessions with real users in real context and analysis and documentation.

Usability testing — real context sessions
Timeline:

6 months (research → redesign → validation)

6 months (iterations and support)

Team:

2 Product Designers (work in parallel)

1 Visual Designer

Impact:

User Impact:

  • Workflows redesigned to reflect real operator behavior — eliminating the gap between system logic and working reality
  • 25–30% improvement in task completion time, validated through 7 usability testing sessions with real users in context
  • Hidden workarounds and undocumented steps surfaced through ethnographic research and removed from critical flows
  • Operators described the new system as relevant, practical, and supportive of their daily work

Business impact:

  • Reduced risk of costly rework by ~40% through early issue identification across 60+ hours of field research
  • Stakeholder perception shifted from "visual designer" to strategic UX partner — achieving full buy-in for research-led decisions
  • Real workflow documentation delivered as a permanent reference artifact for future product development
  • Increased confidence in product direction across operator teams, supporting higher adoption potential
The most valuable outcome in this project for me wasn't the redesign, but how Paragon changed its understanding of design itself. Shifting a client from "make it look nice" to "research drives product decisions that bring value for business" is harder than any UX challenge. And this shift turned a single project into a long-term partnership with visible results.
← previous next case →