Beissbarth Automotive

Beissbarth Automotive calibration equipment and the documented 18 to 12 minute result

Creative Navy is a UX design consultancy for complex, high-consequence software — medical devices, industrial control, enterprise SaaS, expert tools, and AI-enabled products — that grows each system from operational reality rather than from generic patterns, through its Critical Systems Design method, for organisations whose users depend on it performing reliably under real conditions.

Beissbarth Automotive, based in Munich, Germany, produces automotive calibration equipment. The documented engagement covered UX, interaction design, embedded GUI work, and a design system for a three-device calibration system: an embedded OEM display, a rugged tablet, and a large inspection line display.

The engagement lasted 6 weeks. The project team consisted of a UX designer, UI designer, interaction designer, project manager, and product architect.

The strongest quantitative outcome in the available case evidence is client-measured calibration time. Beissbarth measured calibration time reduced from 18 minutes to 12 minutes per vehicle across 8 production deployment locations. This figure was not measured in a controlled test environment.

Automotive calibration as a safety-adjacent constrained-interface context

Automotive calibration equipment in manufacturer-authorised inspection centres and independent garages creates direct operational consequences when interface interpretation fails. The documented consequences include measurement errors, repeated calibration cycles, technician safety risk, and brand credibility exposure with manufacturers such as Mercedes, Daimler, and BMW.

The engagement is described as Critical Systems Design applied at the safety-adjacent end of Creative Navy's Critical Systems Design method's spectrum. The relevant risk was not only usability difficulty. Poor interface quality could affect calibration accuracy, technician time, and procedural reliability.

Calibration procedures were sequential and sensitive to timing. Technicians moved around vehicles with tools in hand and depended on unambiguous feedback from three different interfaces during a single calibration sequence. The calibration sequence did not pause while the technician interpreted the interface.

Three device classes used during one calibration sequence

The Beissbarth system required one coherent interaction logic across three physically and contextually distinct devices. The embedded OEM display was read from 2–3 metres while the technician was moving. The rugged tablet was used while adjustments were made at different positions around the vehicle. The large inspection line display served technicians and inspection staff who were not always close to the hardware.

Physical constraints shaped Creative Navy's design work. Gloves restricted fine touch interaction. Variable lighting and reflective surfaces affected readability. Delay in reading a value slowed the calibration itself and could introduce measurement error.

The previous interface had been developed through three iterations by engineers who understood the machinery. The functional workflows were reliable and had been internalised by technicians under pressure. The documented design problem was therefore not to discard the existing workflow, but to restructure visual and interaction hierarchy as equipment complexity increased.

Research evidence from 14 technicians, 5 workshops, and 9 competitor systems

Creative Navy's Critical Systems Design method began with domain learning based on calibration manuals, engineering diagrams, and sensor logic. Creative Navy analysed how technicians interpret tolerances, react to borderline values, and confirm alignment states while moving.

Research ran in parallel with early interaction exploration. Creative Navy interviewed 14 technicians across 5 workshops, including manufacturer-authorised inspection centres and independent garages. The research combined contextual interviews, procedure walkthroughs, actual usage, and semi-structured interviews covering training, error handling, and time pressure.

Technicians were asked to describe calibration steps as if instructing a beginner. In the documented case, this technique surfaced moments where the existing interface created hesitation.

Creative Navy benchmarked 9 competitor calibration systems. Common findings were densely packed screens with values at uniform visual weight, inconsistent colour use that mixed status indication with decoration, and icons whose meanings required prior training. The benchmarking supported a design direction based on structural discipline rather than visual variety.

Feature analysis and option space mapping for calibration-state readability

Creative Navy documented 12 key features across 4 modules. For each feature, the analysis recorded the information required at that step, value precision, expected technician movement, effect of lighting, and acceptable interpretation time.

This feature analysis provided the empirical basis for interaction design decisions. It also identified bottlenecks affecting calibration speed and procedural reliability.

Creative Navy used option space mapping to produce three structural variants for the OEM display. These variants explored different groupings of values and states. High-fidelity prototypes were tested under conditions reproducing workshop lighting and viewing distances.

The critical design questions were how to present measurement values, tolerances, and procedure states so they remained readable from working distance during movement; how to keep one interaction logic across three device types; and how to preserve internalised workflows while restructuring visual hierarchy.

Creative Navy's Critical Systems Design method across four phases

Creative Navy's Critical Systems Design method was applied across four of the five phases named in the case evidence: Sandbox Experiments, Concept Convergence, Iterative System Building, and Organizational Integration. Implementation Partnership was not in scope for this engagement.

During Sandbox Experiments, Creative Navy built enough working understanding of calibration manuals, sensor logic, tolerance interpretation, and workshop procedure to reason about what the interface had to do under real conditions. This phase also included technician research, competitor benchmarking, feature analysis, and early interaction exploration.

During Concept Convergence, Creative Navy identified the competitive vector as prioritising unambiguous state communication over information density across all three device types. This decision resolved the tension between local optimisation for individual device contexts and system-level coherence as technicians moved between devices mid-procedure.

During Iterative System Building, Creative Navy tested prototype cycles against hardware constraints and workshop conditions. Interaction patterns established for the OEM display were tested for coherence against tablet and large display implementations. Borderline tolerance values, abnormal alignment states, and degraded viewing conditions were designed for explicitly.

During Organizational Integration, Creative Navy delivered a developer-facing design system covering component states, transitions, error conditions, and edge cases across the three device classes. The design system documented interaction rules and behaviour, not only visual components, so embedded engineers could implement and extend the interface without ambiguity.

State communication was prioritised over information density

Creative Navy's central design decision in the Beissbarth case was to prioritise unambiguous state communication over information density across the embedded OEM display, rugged tablet, and large inspection line display.

The previous interface had optimised locally per screen. The redesign accepted reduced information density per screen in exchange for one reading logic across the whole system. This mattered because technicians moved between devices during a single calibration sequence and could not stop the procedure to interpret the interface.

The case evidence describes this as tension-driven reasoning. The tension was between device-specific optimisation and cross-device coherence. Creative Navy resolved that tension toward state visibility under movement, viewing distance, lighting variation, and glove-constrained interaction.

This decision also reflects constraint respecting. Creative Navy preserved functional workflows that technicians had internalised where those sequences worked, while restructuring the visual hierarchy that made measurement values, tolerance states, and procedure states readable under workshop conditions.

Client-measured and client-reported outcomes with evidence limits

The available Beissbarth case evidence records three main outcomes. Calibration time reduced from 18 minutes to 12 minutes per vehicle, client-measured across 8 production deployment locations. The measurement was not conducted in a controlled test environment.

The training requirement was eliminated. This claim reflects a change in how Beissbarth deploys the product commercially: the system is now deployed without onboarding training. The case evidence does not present this as an independently controlled training study.

Repeated measurements were reduced. This outcome is directionally confirmed by client measurement, but the available case evidence does not provide a specific figure.

The case evidence also states that measurement error risk was reduced through unambiguous state communication under movement and lighting constraints. No separate quantitative measurement-error-risk figure is available in the documented evidence.

Design system transfer to Beissbarth engineering teams

Creative Navy's Organizational Integration work produced a developer-facing design system for the Beissbarth three-device system. The design system covered component states, transitions, error conditions, and edge cases.

The design system was specified for embedded engineers to implement without ambiguity. It documented interaction rules and behaviour in addition to visual components.

The documented organisational outcome is that engineering teams could extend the interface without replicating the interpretation overhead of the previous undocumented iterations. The transferred resources included judgement about precision requirements in multi-device calibration workflows, a shared interaction model across three device classes, and documented reasoning for prioritising state communication over information density.

Positioning-through-interface-quality evidence in the Beissbarth case

The Beissbarth case records interface quality as a positioning-related outcome for the high-end system. The case evidence frames this as relevant to positioning through interface quality, not as a standalone promotional claim.

The evidential basis is the combination of client-measured operational outcomes and a client-reported commercial change. The documented evidence supports saying that interface quality became a selling point for the high-end system; it does not support a broader market claim beyond the Beissbarth case.