Selected story 02 · Systems / Product ownership

The design was approved.
Delivery exposed a deeper systems question.

The design was approved.

Delivery exposed a deeper systems question.

Late in delivery, an edge case exposed something deeper than a screen-level issue: the interaction depended on system behaviour that needed clearer definition and validation.

HMI

Cross-functional alignment

Validation

MY ROLE

HMI Product Owner

UX / Product design

FOCUS

Risk judgement

System validation

Delivery leadership

SCOPE

Interaction behaviour

Cross-functional alignment

Validation approach

CONTEXT

Complex HMI

Changing system states

Multiple configurations

Confidentiality note: This case study is based on professional work completed under confidentiality. Visuals and interaction examples have been independently reconstructed to demonstrate the design thinking and principles involved, and do not reproduce production UI or confidential specifications.

THE STORY IN 20 SECONDS

I protected delivery without ignoring the risk — then built the evidence to resolve it properly.

A late edge case raised an important question: was the issue introduced by the new direction, or did it reveal a deeper behavioural gap? With limited evidence, I avoided making a premature design change and opened a parallel investigation. That work clarified the underlying behaviour, strengthened the HMI direction and introduced a more robust approach to dynamic validation.

Evidence established

Previous and revised behaviour compared dynamically.

Direction agreed

A clearer HMI direction was aligned around the behavioural evidence.

Process strengthened

The learning was turned into reusable guidance and a stronger validation approach.

01 · The decision before the diagnosis

We had an issue. We didn’t yet have enough evidence to call it a defect.

The easiest reactions sat at opposite extremes: change immediately, or dismiss the issue and continue. Neither was responsible.

OPTION A

Change the design immediately

High disruption, without a confirmed root cause or evidence that a rushed HMI change would improve the behaviour.



High certainty was required. We didn't have it.

THE DECISION

Hold the direction. Investigate in parallel.

Avoid a premature change while actively reducing uncertainty — validate the behaviour, identify the root cause, then decide with evidence.


Avoid a premature change while actively reducing uncertainty — validate the behaviour, identify the root cause, then decide with evidence.

Progress protected. Risk still owned.

02 · Separate the problems

The uplift wasn’t the root cause.

That distinction mattered. Without it, we could have changed the wrong thing and weakened a direction that was already performing well.

01 · Check the new uplift

Confirm whether the issue was introduced by the current work or merely exposed by it.

02 · Compare the current HMI

Inspect the approved interaction and its assumptions against actual system behaviour.

03 · Look backwards

Trace how the behaviour had been defined over time and identify where assumptions remained implicit.

04 · Look beyond one screen

Check configuration differences, edge cases and the validation coverage around them.

03 · ONE QUESTION. DIFFERENT ANSWERS

A design debate wasn’t going to solve a system question.

Different disciplines interpreted the expected behaviour differently. I brought the discussion back to the interaction, its previous definitions and the actual system evidence.

EXPERIENCE PERSPECTIVE

Keep the current design.

The interaction remained defensible from the usability perspective already reviewed.

SYSTEM PERSPECTIVE

Change is required.

The interface needed to represent underlying behaviour more consistently across configurations.

DELIVERY PERSPECTIVE

The HMI team needs to decide.

The teams were working from different assumptions about the expected behaviour.

04 · Build the missing evidence

The investigation moved from opinion to behaviour.

We reviewed system capability, HMI assumptions, prior definitions and dynamic behaviour, including edge cases that static review had not fully exposed.

CAPABILITY COMPARISON

The underlying system could behave differently across configurations.

WHAT WAS MISSING

Static review had not captured the full dynamic behaviour.

DYNAMIC VALIDATION

We compared the behaviour dynamically, not just the screens.

05 · The root cause

The screen wasn’t the root problem. The behaviour depended on an unresolved rule.

What looked like a visual defect was the visible symptom of several assumptions interacting at once.

06 · Fix now without designing ourselves into another corner

One problem needed three horizons.

HORIZON 01 · IMMEDIATE

Resolve the customer-facing behaviour

Address the highest-priority mismatch with a proportionate change that could be delivered safely.

HORIZON 02 · STRENGTHEN

Resolve remaining interaction inconsistencies

Address the remaining issues that required broader design and system coordination.

HORIZON 03 · SYSTEMIC

Strengthen the underlying behavioural definition

Address the underlying definition so future implementations do not rely on local workarounds.

07 · Change the process, not only the screen

The learning became part of the validation approach.

The learning was captured as reusable guidance, with dynamic behaviour and edge cases brought earlier into validation.

Capability first

Confirm what the underlying system and variants can actually support before locking the HMI behaviour.

Dynamic validation

Review changing states and edge cases, not only static screens and ideal paths.

Document the rule

Capture behavioural guidance as reusable knowledge so future designers do not have to rediscover the reasoning.

08 · From evidence to agreement

Once the evidence was clear, the debate changed.

The revised direction gained broader alignment. The conversation moved from whether the issue existed to how it could be resolved responsibly.

09 · Mobilise

Once aligned, the work still needed structure.

Once the direction was aligned, my role shifted from investigation to orchestration: align ownership, separate parallel workstreams, resolve dependencies and keep the remaining delivery focused.

NOW

Squad alignment


Bring every contributor onto the same problem definition, decision and priority.

NEXT

Parallelise work


Split ownership into parallel workstreams and remove unnecessary waiting between teams.

DEPENDENCY

Asset integration


Coordinate dependent work so the revised direction could land coherently.

FINAL INTEGRATION

Protect the finish


Keep the final work focused on the agreed intent rather than reopening resolved decisions.

10 · OUTCOMES

A stronger decision. A stronger way to reach it.

The revised direction was delivered, dynamic behaviour was validated, and the learning was turned into reusable guidance for future work. The outcome was not only a stronger HMI response, but a more robust way to identify and validate behavioural risk.

Reconstructed interaction study · Designed in Figma · Animated in After Effects

WHAT THIS PROVES

Design approval alone doesn’t validate the full behaviour.

The lasting value was not just resolving one interaction. It was improving how behavioural risk is identified, tested and carried into future design decisions.

Protect delivery without hiding risk

Not every late concern requires an immediate design change. The job is to reduce uncertainty quickly enough to make the right call.

Turn disagreement into evidence

When credible perspectives disagree, inspect the system, behaviour and constraints rather than resolving the question by opinion alone.

Fix the system around the design

The result was not only a revised HMI direction, but a stronger validation approach for future work.

HMI Product Owner / UX designer

Delivered 2026

Duration 1 month