Story 01 · Product strategy

The flagship was changing.
The experience wasn’t.

An established experience was being considered for the next flagship with minimal change. I challenged whether that direction still matched the product ambition, proposed an alternative, and helped turn it into a scalable product change.

Product strategy

HMI

Product ownership

MY ROLE

HMI Product Owner

UX / Product design

FOCUS

Risk judgement

Hands-on interaction design

Design implmentation

SCOPE

Interaction behaviour

Cross-functional alignment

Delivery

CONTEXT

Complex HMI

Design systems

Senior stakeholder alignment

The story in 20 seconds

An inherited interaction became a product rethink.

Challenged the inherited direction

The proposed direction reused an established interaction that had been designed around a different set of experience priorities.

Proposed a new experience

I pushed for a new direction rather than treating the flagship as a visual variation of the existing experience.

Took it through delivery

The direction progressed through experience, system, architecture, product and delivery reviews, adapting as constraints emerged.

The visible uplift wasn’t where the work started. It began by questioning the direction underneath it.

The starting point

The project started from an inherited direction.

An established experience already existed. Reusing it would minimise implementation change and reduce delivery risk. From a delivery perspective, the logic was sound.

Existing experience → Minimal change → Flagship context

Consistency

Patterns were understood.

Effort

Less technical impact.

Timing

Easier to accommodate.

Risk

Less uncertainty.

The context had changed. The interaction logic hadn’t.

The existing solution had been shaped around a different set of experience priorities. In the new context, some of those assumptions no longer held.

If the product ambition was changing, why were we treating the experience as fixed?

The intervention

I challenged the assumption behind the experience.

Rather than treating the flagship as another implementation of the existing experience, I proposed that we rethink the experience itself.

01

Inherited direction

An established experience will be considered for the next flagship.

02

Question the assumption

I challenged whether this direction still matched the flagship definition.

03

New opportunity

I proposed a new alternative approach and define the key interactions.

04

Reframe

This led to a clearer direction and scalable experience.

The strategic tension

A better flagship could create a worse system.

The flagship introduced a different display size, creating an opportunity to rethink the experience. But optimising it independently risked breaking consistency across the wider product family.

Option A — Preserve consistency

Reuse the existing interaction layout and design language across different vehicle programmes.

Consistent, but constrained

Conceptual illustrations used to demonstrate design trade-offs.

Not representative of actual vehicle interfaces or display configurations.

Option B — Optimise for the flagship

Create a dedicated layout that takes advantage of the different flagship display.

Optimised, but fragmented.

Conceptual illustrations used to demonstrate design trade-offs.

Not representative of actual vehicle interfaces or display configurations.

Neither answer was good enough.

Neither answer was good enough.

How can the flagship lead without becoming an exception?

My direction

Design the experience first. Then work backwards to the system.

I used the flagship experience as a reference point, identifying which interactions could remain shared, which needed refinement, and where new rules were required to support different product configurations.

Keep

Preserve proven interactions and familiar patterns.

Shared interaction patterns, familiar controls and behaviours that did not need to change.

Improve

Refine existing interactions to improve clarity and usability.

Existing interactions refined for greater clarity and adaptability.

Redefine

Rethink interaction rules that limit the intended experience.

New interaction rules where established patterns could no longer support the intended experience.

Flagship ambition

→

Shared interaction principles

→

Scalable experience

Illustrations are conceptual abstractions created to communicate design principles. They do not represent production interfaces.

Evidence, not preference

A new direction had to perform better — not just look newer.

01 / COMPARATIVE USABILITY TESTING

Testing the proposed direction

A/B comparisons using Maze, with presentation order varied to help reduce order bias.

Task success

Existing direction

Proposed direction

Effectiveness

Completion time

Existing direction

Proposed direction

Efficiency

02 / HUMAN FACTORS

Human Factors review

Assessed clarity, discoverability and task flow, using the findings to refine the proposed interactions.

03 / PRODUCT COHERENCE

Cross-product validation

Evaluated whether improvements could be accommodated within the shared interaction system without introducing unnecessary fragmentation.

From proposal to commitment

The proposal had four questions to survive.

Is it better?

Design comparison · Usability · Human factors

Can it work?

System capability · Architecture · Performance

Can we deliver it?

Effort · Timing · Components · Dependencies

Is it worth the risk?

Product impact · Quality · Delivery risk

Challenge raised → New proposal → Cross-functional review → Senior review → Direction agreed

Challenge raised → New proposal → Cross-functional review → Senior review → Direction agreed

Approval wasn’t the finish line

Protect the intent. Flex the implementation.

Implementation introduced shared-system constraints, cross-feature dependencies and delivery pressure.

Component strategy

Balancing reuse with local flexibility.

Feature dependencies

One change affected other features.

Timing pressure

The available delivery window narrowed.

My role changed with the project

I started by challenging the direction. I ended up helping a squad deliver it.

Direction

Proposal · Principles · Experience

Alignment

Design · Product · System · Architecture

Delivery

Priorities · Ownership · Specification · Risk

From challenge to delivery

The direction made it through.

01 / Inherited direction

02 / Direction challenged

03 / Alternatives explored

04 / New experience proposed

05 / Direction validated

06 / Cross-functional alignment

07 / Delivery adaptation

08 / Specification released · 2026

What began as questioning an inherited direction became my first product direction taken from initial challenge through to delivery.

Validated

Comparative testing supported improvements in usability.

Aligned

A shared interaction direction was agreed across stakeholders.

Delivered

Design specifications released to the supplier.

Image © Jaguar Land Rover Limited. Used for illustrative purposes only. The imagery does not represent the design work described in this case study.

Image © Jaguar Land Rover Limited. Used for illustrative purposes only. The imagery does not represent the design work described in this case study.

Story 02 · Systems / Product ownership

P

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

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

Delivery exposed a deeper challenge: the design depended on behaviours and assumptions that had not been fully resolved across the wider system.

Delivery exposed a deeper challenge: the design depended on behaviours and assumptions that had not been fully resolved across the wider system.

Read the decision

HMI Product Owner / UX designer

Released to supplier · 2026

Duration 1 year, 3 months