Case Study · WS Audiology · Signia · 2023

Connexx B2B tool facelift

Designer · Signia desktop fitting software · UI refresh and usability validation

A facelift of Signia’s Connexx fitting software for hearing-care professionals. I ran usability testing with twelve HCPs across two markets and fixed navigation, terminology, and status feedback without touching the underlying tool. 12 of 12 testers completed five of six tasks unaided, and the terminology research drove the redesign.

Usability Testing UI Design Enterprise UX Medical Devices
Connexx 10.0 Data Insights screen: cards for wearing time, program usage and manual changes, a colour-coded acoustical-environment donut, and a Signia Assistant changes table, in the refreshed flat UI
Data Insights · the default landing screen, shown as tested · renamed Data Logging afterwards, the name every HCP already used

Connexx is the desktop software hearing care professionals use every day to fit Signia hearing aids. Version 10.0 needed a modern look without disturbing the muscle memory of the people who live in it. I helped run a moderated usability test of the refreshed interface with twelve professionals across the UK and Germany, then turned what I saw into the changes that shipped.

Connexx 10.0 is fitting software: HCPs use it to run hearing tests, tune sound, and manage patient data in the shop. The brief asked for a facelift: a new flat illustration style, refreshed Signia iconography, an updated colour palette. One hard rule shaped all of it. I could not touch the UX workflows, the codebase ruled that out, so I solved every problem in the visual layer.

12
Sessions of user testing
2
Markets · DE / UK

Software people live inside

Connexx is specialised fitting software. An audiologist or dispenser opens it in the shop to run hearing assessments, customise sound for a patient, manage their history, and get the hearing aids performing. Many HCPs use it daily, so interface familiarity is high, and any change risks breaking the muscle memory built over years.

That is what made the brief sharp. The look had to move forward; the flows could not. Connexx is a legacy Windows application, and its codebase did not allow functional change, so the facelift carried all the weight: a new flat illustration style, refreshed Signia iconography, and a new colour palette, layered onto screens whose information architecture stayed exactly where users expected it.

A facelift is harder than a redesign. A legacy codebase froze the flows, so I had to solve every problem in the visual layer. That layer is also the one most likely to disturb the muscle memory people build over years.

I owned the redesign and ran the research

I was the designer on the facelift. I owned the visual redesign across the high-frequency fitting screens and the Figma component library behind it, co-authored the moderated test script, and built the clickable prototype in both languages. I ran the UK sessions myself and sat in on the German sessions at EUHA as note-taker, then turned the feedback into the changes that shipped.

What I owned

  • The visual redesign of the high-frequency fitting screens
  • A reusable Connexx component library in Figma
  • The clickable prototype, German and English
  • The UK usability sessions, end to end
  • Analysis and the recommendations that fed the release

Who I worked with

  • Iconic UX team: test script, design reviews
  • Twelve HCP participants: UK remote and German in person
  • Product stakeholders: the facelift brief and its limits

Two HCPs, opposite habits

Before designing, I built two personas from the panel’s profiles and pre-interviews to anchor the decisions. The facelift had to serve both at once: keep the expert’s flow intact while making the occasional user’s re-entry faster.

Daily user
Klaus · Master Acoustician
Who
~30 years’ experience, Germany. Runs Connexx via NOAH every day and knows every shortcut.
Habit
Lands on Data Logging by default and treats it as home. Skeptical of anything that touches muscle memory.
Needs
The facelift to feel familiar, not new. “When you know where everything is, you find everything easily.”
Occasional user
Sarah · Hearing Aid Dispenser
Who
~9 years’ experience, UK. Uses Connexx a couple of times a week.
Habit
Relies on labels and visual cues, not muscle memory. Gets lost in nested menus and reads section titles literally.
Needs
Scanning and re-finding to be faster. “Looks a bit messy, only text.”

What I kept, and why

Not every inherited choice was debt. Some conventions did real work, and the discipline of a facelift is knowing which ones to leave alone. The one that mattered most was the ear colour coding, shared across Connexx, the companion apps, and Signia marketing.

Before and after

Same Basic Tuning screen, same controls in the same places. The facelift redrew the chrome, the icons, and the palette and opened up the white space, while the workflow underneath stayed exactly where users expected it.

The previous Signia Connexx Basic Tuning screen: a darker top bar, a denser toolbar, and the older sidebar layout
Before Signia Connexx · the layout HCPs had used for years
The facelifted Connexx 10.0 Basic Tuning screen: flatter chrome, refreshed iconography, a lighter palette, and more white space
After Connexx 10.0 · flatter chrome, refreshed icons, more white space

Red right, blue left · a Signia convention HCPs and patients already share · kept untouched

KeptRed and blue ear coding

Red means right, blue means left. Continuity across the product family outweighed any visual-debt argument; changing it would break recognition everywhere, in the software, the apps, and the marketing.

NewFlat illustration and iconography

Briefed by the 2023 Signia brand refresh. Replaced the older skeuomorphic style with something lighter and closer to the marketing site, on a screen HCPs stare at all day.

NewWhite-heavy layout

Chosen for the modernistic touch in the brief, closer to current SaaS conventions. I accepted the trade-off up front: calmer, but a contrast risk, and testing punished it. Several HCPs said it “blurs into one.”

KeptLanding on Data Logging

Pre-interviews confirmed most HCPs already default-land there and find it useful. I kept the default; only the name changed.

ConstraintNo workflow changes

A technical limitation, not a design choice. Every screen kept its existing information architecture, and the visual layer did all the lifting.

Palette · what the screen carries

Signia red#ED0400 · brand red is the right-ear red, one red not two
Left-ear blue#0072CE · kept coding
Ink#1A1A1A · text and chrome
Surface#FFFFFF · the modernistic white

Accessibility

Connexx is a legacy Windows desktop application; the codebase limits control over type scale and contrast tokens, so a full WCAG pass was out of scope for a facelift. The strongest win the visual layer allowed was enlarging the base font, driven straight by the “font is small, people leaned in” feedback. I flagged the low-contrast secondary nav as debt and logged the red/blue dependency as a colour-blind risk for the roadmap. Not an accessible product yet, but the facelift moved the baseline and named the debt for the next release to absorb.

The redesign, screen by screen

I owned the visual redesign across the screens HCPs touch most. Each kept its workflow and changed only its surface. The captions name the decision, not the pixels.

Connexx 10.0 Client List dialog: a searchable client table with tabs for clients and sessions, and actions to add, edit, delete, or load a client
Client list · where every fitting starts · open an existing client, or add a new one
Hearing Aid Detection dialog: the hearing aids in range listed with right and left checkboxes, the selected pair shown as red right and blue left cards, and a Next Step section
Hearing aid detection · the new Connect & Detect flow · devices in range, red right and blue left
Facelifted Configuration screen: the device controls cluster, with rocker-switch press actions set from labelled dropdowns
Configuration · the controls cluster reordered and relabelled · the screen Task 4 stumbled on
Facelifted Program Handling screen: the two gain graphs above a list of program pills, with one tap to add a predefined program
Program Handling · predefined programs, one tap to add · “simply presented, not nested”

German prototype build · the workflow underneath is identical to the English version

A component library for Connexx

The facelift could not stay a loose set of screens. The same parts repeated everywhere: the red and blue device cards, the gain graphs, sliders, program pills, dialogs, the secondary-nav flyout. So I standardised them into a reusable Connexx component library in Figma. It held the redesign consistent screen to screen, made handoff to engineering legible, and gave whoever came next a system to build on instead of a pile of mockups. I shipped the new screens; the library is how the team keeps them coherent after I left.

Six tasks, two languages

The moderated test ran on a clickable Figma prototype, in German and English, with twelve HCPs whose experience ranged from two to forty years. I ran the five UK sessions remotely myself; the seven German sessions at EUHA I attended in person as note-taker. Six scripted tasks, each with a defined start state, a goal, and a success criterion, plus a follow-up question like “do you think the hearing aids are now connected?” I scored every task as completed unaided, completed with a hint, or failed. Twelve participants covered both markets and the daily-versus-occasional split, past the point where new issues kept surfacing.

Open an existing client
Data Insights
First impressions of the new UI
Connect & Detect
New flow
Switch to a new hearing-aid pair
Program Handling
Programs
Add a predefined Loud Environment program
Configuration
Hearing aidNeeded hints
Set a rocker-switch press as a trigger
Basic Tuning
Sliders
Raise Speech by two levels
Telecare
Secondary nav
Activate the client for remote follow-ups

Six scripted tasks · German in person at EUHA, English remote in the UK · Task 4 is where it broke down

What worked, what to fix

Twelve of twelve completed five of the six tasks without help. Task 4, setting a rocker-switch trigger in Configuration, needed hints for four of them, and that pointed straight at navigation and labelling. The praise and the pain split cleanly.

What worked

  • Structure read as tidier and more equalised than before
  • Landing on Data Logging matched what HCPs wanted to see first
  • The Connect & Detect dialog was self-explanatory; the Connect button was spotted immediately
  • Red and blue coding let people identify left and right at a glance
  • Distinct, clearer icons in the secondary navigation
  • Program Handling read as simple, not nested: “beautiful, with the hook on the left”

What to improve

Visual clarity
High
Signal
Body font felt small, people leaned in. Red section titles read as “red-ear” content. “Very bright, it all blurs into one.”
Why
White-heavy and low-contrast at once, the brief-level risk made live.
Fix
Larger body font, desaturated titles, real contrast between cards and background.
Navigation & terminology
High
Signal
Personalisation, Configuration and Program Handling blurred together for occasional users. Everyone said “Data Logging,” nobody said “Data Insights.”
Why
The labels named the system, not the user’s mental model.
Fix
Reordered and relabelled the cluster, added tooltips, renamed Data Insights to Data Logging.
Connection status
Medium
Signal
Hard to tell from Data Insights whether the aids were connected; the “Simulation” label was easy to miss. People were unsure which side was selected.
Why
Connection state and side selection are the things you must never guess in a fitting.
Fix
Explicit connected / disconnected state pill, and a stronger side-selection indicator.
Connect & Detect
Medium
Signal
No Disconnect on the post-connect screen, and “New fitting” came pre-selected in Next Step, one slip from a full re-selection.
Why
A new flow felt incomplete and risked an accidental, destructive choice.
Fix
Added Disconnect, removed the pre-selection, collapsed secondary detail into an expandable section.

What shipped

These findings shipped as UI changes in the Connexx 10.0 release: one fix per pain point, numbered to match the four findings above.

  • 01 · Readable hierarchy: larger body font, desaturated section titles, and real contrast between cards, dividers, and background to break the wall of white.
  • 02 · Language that matched users: “Data Insights” renamed to “Data Logging,” the Personalisation / Configuration / Program Handling cluster reordered, and tooltips added to the secondary-nav icons.
  • 03 · Clear connection status: a connected / disconnected state pill replacing the easy-to-miss “Simulation” badge, and a stronger left/right side indicator.
  • 04 · A safer Connect & Detect flow: a Disconnect button on the post-connect screen, no pre-selected “New fitting,” and secondary detail collapsed into an expandable section.

12 of 12 testers completed five of the six tasks unaided. Only Task 4, setting a rocker-switch trigger in Configuration, needed hints, and it pointed straight at navigation and labelling. Testers backed that up in their own words: occasional users could not tell Personalisation, Configuration and Program Handling apart, and everyone called the landing screen “Data Logging,” nobody said “Data Insights.”

A dedicated contrast pass, colour-blind-safe alternatives to the red/blue dependency, and terminology research run upstream, before the next visual test rather than inside it.

On impact

Shortly after launch the B2B side of Connexx moved to another team in a re-org, so post-launch measurement lived with them. What I can show is the design that shipped and the research that shaped it, not a long-term metric I did not own.