Efficiency in B2B & Industrial Systems
Reduce Operating Errors & Accelerate Workflows
Confusing interfaces cost companies real money. With a data-driven research approach, I make usability measurable and optimize your systems in a targeted way.
Established Benchmarks (SUS & VisAWI)
Focus: Collection of established usability and aesthetics metrics from identified users via targeted surveys.
Goal of this phase: Measurement of perceived interaction quality (SUS) and visual trust building (VisAWI) as an objective comparison basis.
Card Sorting
Focus: Structuring menu logic, parameters, and navigation structures with real users.
Goal of this phase: Aligning the information architecture with the mental models of users to eliminate confusion and misclicks.
Usability Testing
Focus: Moderated test sessions with click prototypes or in the live system.
Goal of this phase: Qualitative validation of new workflows and proof of usability improvement before final software implementation.
Why efficiency in B2B systems starts with information architecture
Confusing interfaces are rarely a cosmetic problem. They are a structural problem. When users have to work with complex data for eight hours a day, a clear information architecture determines how many errors occur and how long onboarding takes.
Information architecture as a lever
I structure menus, parameters, and navigation paths to match the mental models of the users. Card sorting and user flows are the tools here, not the goal.
Relief across entire shifts
Every unnecessary cognitive burden adds up over the working day. I reduce that burden where it originates: in navigation, terminology, and the system's response to errors.
The 3-Level Package Structure for B2B System Efficiency
From the first usability audit to comprehensive validation of complex interfaces – choose the right level for your industrial system.
Usability Audit & SUS Benchmark
Quick inventory of usability in preparation for relaunches or system adjustments.
Umfang:
- SUS benchmarking (baseline measurement of usability score 0–100)
- Expert review of critical workflows and screens
- Processing of measurement results in the Git repository
Zielgruppe:
Companies that need an objective baseline for their software and want to identify first optimization potentials.
Information Architecture & Flows
User-centered restructuring of menus, parameters, and navigation paths.
Umfang:
- Everything from package 1 (SUS benchmarking & audit)
- Card sorting with at least 20 representative B2B users / operators
- Development & validation of optimized user flows
- Handover of structured navigation concepts in the Git repository
Zielgruppe:
Teams whose B2B software, configurators, or HMI panels are overloaded and want to eliminate confusion in operation.
Full Usability Validation
Maximum security through testing interactive prototypes with real users.
Umfang:
- Everything from package 1 & 2 (benchmark, card sorting & user flows)
- Moderated usability testing with click prototypes (remote or on site)
- Error analysis and proof of usability improvement
- Comprehensive handover of validated interaction patterns and epics in the Git repository
Zielgruppe:
Companies that need to fundamentally rebuild critical industrial software or roll it out error-free.
FAQ: Efficiency in B2B & Industrial Systems
Pragmatic answers on methodology, effort, and results – so you can assess whether a data-driven approach fits your system.
What exactly is a SUS benchmark and what does it deliver?
The System Usability Scale (SUS) is a standardized survey methodology that quantifies subjective perception into a measurable score. It shows how good the usability of your system currently is, where problems exist, and whether any action is needed at all.
From how many participants is card sorting meaningful?
Since card sorting is evaluated statistically, I recommend at least 20 representative users. Only from this order of magnitude can reliable patterns in mental model formation be recognized and meaningful structure decisions be made.
On which systems can usability tests be conducted?
Usability tests can take place with click prototypes or directly in the live system. The choice depends on the project goals: prototypes are suitable for validating concepts early, live systems for proving concrete problems in existing operations.
Who needs to participate on the customer side?
On the customer side, the Product Owner or a comparable functionally responsible person should be available. Central, however, is the recruitment of real users who regularly use the system – without them, no valid statement can be made.
How much time do internal employees need to plan?
The internal effort is limited. For briefing at the start of the project and debriefing after the tests, you should plan around 4 hours.
How are results documented and handed over?
All results are stored version-securely in a Git repository and additionally prepared as PDF documentation. The development team thus receives a clear, traceable basis for implementation.
Our software was developed for years without user involvement – where do we start?
In this case, I recommend not redesigning the entire system at once. Together we identify a small but business-critical area where operating errors are particularly expensive or users are most frustrated. There we conduct a targeted usability test.
This minimal test delivers quickly tangible insights, shows where the biggest lever lies, and builds trust for further, step-by-step optimizations – without major upheaval or long lead time.
When are improvements measurable?
First measurable improvements only show after implementing the recommended measures. The SUS benchmark provides the baseline at the beginning, against which success can later be verified.