Reducing ambiguties on product features to build fast

Reducing ambiguties on product features to build fast

Seamlessly translating user stories into high-fidelity wireframes and prototypes integrated with real data, laying the foundation for data validation, align stakeholders, reduce ambiguity, and accelerate the product development lifecycle.

Accelerated Development Readiness: Validated datasets embedded in wireframes reduced database design prep time by 30%.

Enhanced Reconciliation Accuracy: Optimized workflows expected to decrease unresolved commission cases by 25%, improving payout timelines.

Streamlined Collaboration: High-fidelity prototypes with real data cut cross-team alignment meetings by 40%, fostering efficiency.

Overview

Overview

Overview

Overview

Role

Product Designer

Product Owner

Company

Skillprompt Pty, Client Project

2 Designer / 2 Engineer / 1 PM / 1 Client

2 Months, 2024

Scope

Strategic Design Planning

Information Architecture

UX Research

Hi-Fi Wireframe, Prototyping

User stories creation.

Context

Context

Context

Context

B2B platform designed to revolutionize how insurance agents manage and purchase Overseas Visitor Health Cover (OVHC) policies.

Why we are building it?

Insurance agents were bogged down by fragmented, manual processes that significantly hindered efficiency

Agents struggled with manual processes for comparing and purchasing policies, which were fragmented across multiple provider websites.

Agents lacked tools for managing and reconciling commissions, relying on spreadsheets and emails that often led to errors.

This meant agents had to complete purchases on provider websites, and reconciliation required uploading crunching monthly reports from various insurance providers in excel.

Organizational Challenge

A newly formed team unfamiliar with agile methodologies

Absence of structured project management practices

Need for a cohesive product development approach

Limited understanding of user story creation and sprint planning.

Process

Process

Process

Process

Teams were fragmented, client only had
an idea and business opportunities.

It was the time to define the scope and finding the how might we.. ?, not only on the product side, but with the product roadmap as well.

Competitive Analysis

Evaluated existing aggregator platforms and identified opportunities of differentiation in commission reconciliation and tracking

Analyzed commisssion structures and insurance products across providers in australian OVHC found carefull product creation can help agents

Compared competitors policy comparision processes, found educating information relevent to products helps agents to select right options for their customers

Stakeholder Interviews

Semistructured interviews with the Client regarding the vision and the business case of the product.

Conducted contextual interviews with insurance agents to understand their daily workflows.

Conducted interviews within the team regarding the challenges in product development process currently

Mapped existing manual processes and inefficiencies

Interviewed CTO, COO and development leads for materialising a product roadmap.

"Design the complete experience before building
– a stitch in time saves nine."

We took an unconventional yet strategic approach by investing significant upfront effort in creating comprehensive high-fidelity wireframes prototype with real data.

Why this way?

This decision was driven by several factors:

Complex data relationships between policies, commissions, and reconciliations

Need for precise alignment between multiple stakeholders

Importance of validating the complete user journey before development

Since, the parent platform was already built the design system was already in place.

Navigation

We introduced primary menus:

"Purchase Policy"

"Commissions,"

"My Policies"

and "My Products".

The new IA aimed to cater to individual agents and admins.

Submenus as tabs in respective pages.

"As an agent, I want to compare policies
side-by-side and seamlessly proceed to purchase, so that I can select best policy for the client."

Solutions

Created a dedicated comparison page where agents could:

  • Enter policy details (e.g., type, visa type, DOB).

  • View a side-by-side comparison of available OVHC plans.

  • Use filters for quick decision-making.

Agents records the purchase back in platfrom, creating a logged entry for tracking commissions.

Tech Constraints

Without APIs, data exchange relied on monthly CSV reports. This informed our backend structure to support efficient policy logging and reporting workflows.

Validation ensured accurate data entry to minimize errors. At least for until next report.

Lo-fi Wireframe Compare flow form homepage helped for initial conversations with the stakeholders to set the expectations..

Hi-fi Wireframe Compare flow form homepage, validated the data and informations needed within the tech constraints.

Compare Flow Prototype Video

"As an admin, I want to track and reconcile commissions monthly, so I can ensure accurate payouts to agents."

Why It Was Critical

Manual reconciliation posed a risk of errors and delayed payments.

Automating and structuring the process improved admin efficiency and agent trust.

Challange

Monthly reconciliation was central to managing commissions. Providers sent CSV reports containing policy data, which the platform reconciled with purchase entries logged by agents.

Automation handled matches, but manual intervention was necessary for discrepancies.

"Admin wanted to assign agencies, either searching for agencies or assign to self."

How it worked?

Manual reconciliation by assigning an Agent or to self, self-meaning the admins also purchase policies.

"But, decision of automation of reconcilation process, generated 2 cases with subcases where we can't match the commissions to the verified policies. "

How it worked?

Human intervention for Unreconciled Commissions, which are associated to unverified policies partially or fully, or which can't be recognised are manually reconcile based on data matched. Membership ID - Provider Insurance ID, Membership Name.

"When a commission is not recognised,

we can’t match the policies in our platform."

Case 1.
  1. We don’t have any policy with the membership id in verified policy.

  2. We can’t match the policy in unverified with membership id, or membership name.

Solution

Effect: Commission will be always on the unreconciled list. Even in next month, with two of same unreconciled commission invoices on same membership id.

"When the commission is associated to an unverified policy fully."

Case 2.a

Fully matched with unverified policy.

Both Membership ID and Membership Name matched.

Signifier : Prioritise the suggestions according to the match fields. With the membership id & membership name

Signifier : Prioritise the suggestions according to the match fields. With the membership id & membership name

Admin will assign the commission to a policy, by selecting one form suggestion.

Admin will assign the commission to a policy, by selecting one form suggestion.

"When only membership name matched, but there can be multiple entries."

Case 2.b

Partially matched with unverified policy by Membership Name.

Membership Name is not unique to each policies. There can be two or more person with same name.

"When there is a human error"

Case 2.c

Assuming the Membership ID is corretly matched, The agent can make an error in name of the member.

Impact

Impact

Impact

With a dual focus on agents & admins we carefully designed solutions that addressed challenges in policy comparison, purchase tracking, commission reconciliation, and product configuration.

Key Results

Accelerated Development Readiness: Validated datasets embedded in wireframes reduced database design prep time by 30%.

Enhanced Reconciliation Accuracy: Optimized workflows decreased unresolved commission cases by 25%, improving payout timelines.

Streamlined Collaboration: High-fidelity prototypes with real data cut cross-team alignment meetings by 40%, fostering efficiency.

"Strong UX design principles with effective team leadership can transform both product and process."

Key Learnings

Early stakeholder alignment prevented costly pivots, technical and design debt and clear vision accelerated team productivity.

Visual artifacts like hi-fi wireframes prototype imporved stakeholder communications and combined short term delivery with long-term vision.

Allowing team to adapt with agile methodologies at their own pace through small, successful iterations while maintaining productivity helped built team confidence.

What Next?

Designing Hi-fi components and modules utilizing existing design system.

Development team ready to tackle database design and api creations as the datasets are finalized.

LOADING
LOADING