Portfolio

1. Mapping the Risk Placement Workflow

Working with underwriting experts, we mapped the full lifecycle of risk placement: Submission --> Risk Evaluation --> Reinsurance placment --> Policy structuring --> Issuance

This helped us identify key decision points and where automation could reduce manual effort.

2. Designing Decision Support for Underwriters

Underwriters needed to quickly evaluation: risk appetite, placement capacity, regulatory constraints, cross-border policy structures

We designed decision-support workflows that surfaced critical information in context, allowing udnerwriters to confidently structure complex policies.

3. Enabling Multinational Policy Placement

The next phase of the platform enabled underwriters to: book risk across multiple countries, structure multinational insurance programs, understand jurisdiction-specific constraints, and identify opportunities for cross-selling additional coverage.

This dramatically expanded the ability for teams to serve global clients.

Outcomes

The experimented prototypes and final platform delivered measurable business impact: 

$800M annual premium retained through the automated reinsurance placement facility.

Additional benefits included:

• Faster underwriting cycles

• Reduced reliance on manual coordination with reinsurance partners

• Improved visibility into multinational risk structures

• New opportunities for cross-selling global insurance programs

Why this Project Matters

This work demonstrates how thoughtful platform design can transform complex enterprise workflows.  

By translating intricate underwriting and regulatory requirements into intuitive systems, we enabled teams to make faster, more informed decisions while unlocking significant business value.

Multi-Surface Financial Platform

Designed a unified payment and invoice management experience across web and mobile, enabling:

• Invoice tracking and filtering

• Digital payment workflows

• Due-date prioritization

• Program eligibility visibility

Result:

Drove 80%+ adoption across the Midwest customer base.

System-Level Design Standards

The platform required alignment across multiple squads working in parallel.

• Defined scalable interaction patterns

• Established system-level UX standards

• Reduced inconsistency across surfaces

• Enabled faster feature delivery through reusable design patterns

Translating Operational Complexity

Agriculture is operationally complex:

• Financing programs

• Seasonal buying cycles

• Consultant-driven trust relationships

• Legacy backend systems

Rather than digitizing blindly, the design focused on:

• Preserving consultant trust

• Reducing cognitive load

• Making financial clarity immediately visible

• Supporting both reactive and proactive engagement

Design Principles

1. Trust first, efficiency second

2. Make financial clarity effortless

3. Align digital experience with existing relationship behaviors

4. Build patterns that scale across teams

Business Impact

• 80%+ adoption across Midwest region

• Increased digital payment utilization

• Reduced reliance on manual consultant workflows

• Established scalable UX standards across squads

• Enabled iterative shipping within legacy system constraints

Discovery & Problem Framing

To ground the work in real operational needs, I led exploratory research including:

• Contextual observations of live incident calls

• User interviews with incident managers and support engineers

• Synthesis into personas, journey maps, and baseline metrics

Using these insights, I facilitated three cross-functional design thinking workshops focused on:

• Identifying the highest-friction moments in incident response

• Aligning on priority workflows 

• Defining success criteria tied to resolution speed and clarity

This phase ensured alignment across product, engineering, and operations before moving into solutions.

Workflow-First UX

Rather than designing isolated screens, I focused on end-to-end workflows, ensuring users could:

• Quickly understand incident severity and status

• See ownership and responsibilities at a glance

• Move seamlessly between coordination, investigation, and resolution tasks

Rapid Prototyping & Validation

I translated workshop outcomes into:

• Storyboards and low-fidelity wireframes (Axure, Balsamiq)

• Clickable prototypes for usability testing

• High-fidelity specifications to support engineering build

Usability testing validated assumptions and informed iteration before development, reducing downstream rework.

Systems Thinking & Implementation Support

To streamline development and ensure consistency:

• I created a CSS theme aligned with the broader UI patterns

• Defined reusable components and interaction patterns

• Partnered closely with engineers during build and QA to validate implementation fidelity

This approach helped bridge design intent and technical reality.

Outcomes & Impact

• Improved clarity and usability for incident managers during high-pressure scenarios

• Reduced friction in coordination and handoffs across roles

• Established repeatable UX patterns for incident workflows

• Enabled pilot releases with measurable feedback before scaling

While specific metrics were sensitive, stakeholder feedback confirmed faster alignment, clearer ownership, and improved confidence during incident response.

Key Learnings

• In high-stakes systems, reducing cognitive load is more impactful than adding features

• UX must support decision-making under pressure, not just task completion

• Early cross-functional alignment using data-informed roadmaps significantly helps converge after diverging in design thinking workshops

• Staying involved through implementation ensures the experience delivers as designed

Tools Used

Google Drive  |  Mural  |  Design Thinking  |  Balsamiq  |  Axure  |  Webstorm  |  Survey Analytics  |  Statistical Analysis

Discovery & Framing

I led early discovery to understand:

• How different teams interpreted and applied appetite

• Where friction occurred in lookup vs management workflows

• How appetite decisions fit into broader end-to-end processes

This work informed the definition of:

• Core personas (e.g., contributors, reviewers, decision-makers)

• Primary and secondary workflows

• MVP scope for pilot testing

Systems-First Thinking

Rather than designing one-off screens, I approached Appetite as a system:

• Structured information hierarchies to support fast scanning

• Designed reusable patterns that could scale as appetite definitions expanded

• Ensured consistency across mobile, tablet, and desktop breakpoints

Multi-Persona Experience

The platform supported both:

• Consumers of appetite (quick lookup, clarity)

• Managers of appetite (editing, governance, ownership)

Design decisions were grounded in how users mentally categorized and applied appetite in real workflows.

Pilots / Test-and-Learn Iteration

To reduce risk:

• Designed an MVP mobile experience for early release

• Led usability testing across three pilot groups

• Synthesized feedback into prioritized improvements for future sprints

This iterative approach allowed the team to validate assumptions before broader rollout.

Collaboration & Delivery

• Partnered closely with product to define MVP scope and roadmap priorities

• Worked with engineering to ensure designs were feasible and scalable

• Used Figma to maintain consistency across breakpoints and iterations

• Supported agile delivery through Jira and Confluence documentation

Outcomes & Impact

• Established a centralized, trusted appetite reference for teams

• Improved consistency and confidence in decision-making

• Reduced friction in submission workflows

• Created a scalable foundation for future appetite management features

While metrics were not publicly shared, adoption across pilot groups validated the system’s clarity and usefulness.

Key Learnings

• Systems design is critical when products must scale across roles and devices

• API usage analytics indicate UX adoption better than UI analytics if API is leveraged

• Breakpoint consistency is essential for enterprise adoption

• Early validation prevents costly rework later

Tools Used:

Microsoft OneDrive, Teams  |  Miro  |  Balsamiq  |  Figma  |  Survey Analytics  |  Jira  |  Confluence Wiki