← All work
Case study · Internal tool · Financial services

Life Event Tool

When a client dies, divorces or becomes incapacitated, the paperwork depends on a dozen variables. I built a tool that walked every branch and home-office associate through the decision and told them exactly which documents they needed.

Role
Came up with it, designed it and built it
Where
Raymond James, as a Business Technology Specialist (2014–2016)
Users
Every branch and home-office associate
Type
Internal decision-support tool
01

The problem

Financial services firms have processes for the hardest moments in a client's life: a death, a divorce, someone becoming unable to manage their own affairs. Each one needs paperwork before anything can move, and the paperwork is different every time. It depends on a dozen variables about the client, the account and the event.

The people handling these requests sit in branches and in the home office. They aren't specialists in every edge case, and they shouldn't have to be. They needed one place to answer a simple question: for this situation, exactly what do we need?

02

My role

I came up with the tool and built it. Most of the work wasn't code. Getting the logic right took weeks of sitting with compliance and operations, walking through real scenarios and mapping out every edge case until the rules were complete and everyone agreed on them.

Then I turned that rulebook into an application: a guided set of questions that any associate could answer, ending in a clear list of the documents that case needed.

03

How it worked

This is an illustration of how the tool worked. The actual questions, rules and screens are internal to Raymond James and aren't shown here.

04

Hard problems

The logic lived in people's heads

The rules weren't written down in one place. They were spread across compliance, operations and years of experience. The real work was getting those people in a room, walking scenario after scenario, and turning what they knew into one complete set of rules that everyone signed off on.

Complete, but simple to use

A dozen variables can combine into a huge number of cases. Showing all of that to an associate would defeat the point. The tool walked each associate through the decision tree, so they only saw the questions that applied to the case in front of them.

Built for everyone, not just experts

It went to every branch and home-office associate, so it had to work for someone handling their first case of this kind, not just for the specialists who already knew the rules by heart.

05

Results

The Life Event Tool went into use across every branch and the home office, giving associates one place to answer "what do we need for this case?" It's still one of the projects I'm proudest of.

It also shaped how I work. The code was the easy part. The value came from understanding the problem deeply enough to get every edge case right, and that's the approach Goar Labs takes to every build, especially in regulated work.

Have a process only a few people really understand?

I turn complicated rules into tools anyone on your team can use correctly.

Let's talk →
← Previous case studyEast Lake Classic Next case study →Bandogram