Case Study

Claim System Selection: Choosing a Platform for Growth

Claims Department, 8 Teams & Roles · 3 Months

Building an evaluation framework, grounded in real user needs, to select a claims system that could grow with the business.

100+
use cases built
7
focus groups run
8
teams involved
3
vendors evaluated
01 — The Problem

Outgrowing the system, and the checklist

Our existing claims system was approaching the end of its vendor contract, and the department had outgrown what the platform could support.

The real challenge wasn't picking a vendor off a feature list. It was making sure the decision reflected the actual, often role-specific needs of the people who'd use the system every day.

The easy path
Compare vendor feature sheets and renew or swap based on price and specs.
What was needed
A structured evaluation grounded in how each team actually works day to day.
02 — My Approach

Building the evaluation framework

I built the framework from the ground up: use cases to score every vendor demo against, focus groups to surface what teams actually needed, and hands on sandbox sessions to test it in practice.

100+ use casesacross 8 teams & roles
7 focus groupsover 4 weeks
100+ user storieswritten from focus group findings
4 guided sandbox sessionshands on testing per vendor
03 — The User Voice

Capturing feedback while it was fresh

After each vendor's demo and sandbox sessions, I sent a feedback survey immediately, before moving on to the next vendor. Keeping that sequence tight meant impressions stayed uncontaminated by comparison.

Analyzed in Excel, the results surfaced patterns leadership hadn't fully anticipated.

Finding 1
Different teams and roles had genuinely different needs. No single requirement covered everyone.
Finding 2
Ease of use consistently outweighed visual polish in what teams favored.
Finding 3
Openness to changing existing workflows mattered. Current process wasn't treated as fixed.
04 — In the Room

Coordinating the vendor onsites

I sat in on multi day onsite demos with each finalist vendor, coordinating focus sessions grouped by role during each visit.

Throughout, I served as the primary liaison between testers, vendor teams, and leadership, fielding questions in both directions and keeping the evaluation moving.

Testers
Leadership
↑ ↓
Liaison & Coordination
↑ ↓
Vendor Teams
05 — The Outcome

A decision shaped by the people who'd use it

The department selected a new claims system based on this evaluation. Structured use cases, direct user feedback, and hands on testing meant the decision reflected what people actually needed day to day.

The process surfaced considerations leadership hadn't originally scoped, and shaped the final decision at every stage.

Use cases + focus groups + surveys
A system chosen to grow with the business
1 / 6