My Design Process: Applying Behavioural Models for Intuitive Solutions
I adopted a Design Thinking approach, fostering an iterative process crucial for navigating multiple stakeholder inputs and inherent complexities.
Research & Shared Understanding:
My design process began with qualitative research. workshops with key stakeholders (Product Owner, BA, Propositions Lead, Solution Architect, Tech Designer) were instrumental in creating initial user flows for the various customer journeys.
This collaborative mapping not only validated existing processes but also established a shared understanding of where the new insurance offering would conceptually reside within the overall customer experience.
Following this, I conducted interviews with three frontline customer agents. These interviews provided critical insights into their daily pain points, existing workflows, and how the new insurance product would impact their efficiency and cognitive strain.

Ideation & Cognitive Load Reduction (Key Decision & Rationale)
The most significant challenge during ideation was directly addressing the cognitive load on agents. Many solutions were proposed, but the complexity of integrating a new product across multiple customer journeys, diverse device types, and varied customer packages made a straightforward solution elusive.
To overcome this, I leveraged insights from behavioural models, specifically applying the B.I.A.S framework (Block-Interpret-Act-Store). This framework suggests that users tend to “Block” information overload, especially if it seems irrelevant to their immediate task. Therefore, the design needed to frame context effectively to help users “Interpret” the screen more efficiently.
My key decision was to implement a progressive disclosure approach.
Instead of bombarding the agent with all insurance-related information upfront, I designed a solution where a dedicated “insurance eligibility” button would activate and become visible only when required within the specific customer journey.
This means agents not actively looking to add insurance would not be distracted by irrelevant information, thereby “blocking” unnecessary cognitive input.
When the relevant agent clicked this button, only then would the eligible devices for that specific customer, along with relevant insurance options, become visible.

This strategic use of progressive disclosure, informed by the BIAS framework, significantly reduced cognitive load by presenting information only when contextually relevant.
The third step involved meticulously analyzing all the various customer journeys to strategically embed this progressive disclosure mechanism wherever appropriate.

Collaboration
Throughout the design process, close collaboration was maintained with the development team and business stakeholders.
Workshops were held to explain design rationale and gather technical feasibility input, ensuring the proposed solutions were not only user-centred but also technically viable.