Blair McMillan

01 / Case study

Farm Succession Planning Tool

Turning a fragmented, document-heavy process into a single digital workflow.

Client
A large financial services organization
Role
Lead UX Researcher · Product Designer

A specialized planning service helped farm and agribusiness families work through succession, estate planning, business continuity and financial independence. The expertise behind the service was strong. The experience surrounding it wasn’t. I led the UX research and designed a new platform from the ground up — rethinking how Financial Professionals initiate, build, submit and manage complex succession cases.

02 / The problem

Nobody designed this. It accumulated.

The process had grown into a patchwork of fillable PDFs, email, cloud storage, shared drives, Word documents and specialist internal systems. Financial Professionals gathered information from clients, organized documents, assembled PDFs and submitted everything to an internal consulting team — who then had to enter much of it again, by hand, into another system.

  1. Advisor & client
  2. Fillable PDFs
  3. Email
  4. Cloud storage
  5. Shared drives
  6. Internal systems

Manual re-entry

Every hop a single case made before anyone could work on it.

40%

of a specialist’s active case time was being spent manually re-entering submitted information.

But the inefficiency wasn’t the whole problem. Advisors struggled to understand what information was required, what had already been submitted, what was still outstanding, and where a case stood once it entered the process.

That mattered because these were not quick transactions. A case could involve several family members, businesses, ownership structures and advisors, and stay open for months or years.

What the process misunderstood

It treated them like documents.They were really long-running relationships.

03 / The system

The official process told half the story.

I approached this as a service and workflow problem rather than a form redesign. Through interviews, workflow analysis and conversations with Financial Professionals and internal specialists, I mapped how information actually moved through the organization — as opposed to how it was supposed to.

Advisors had built their own systems around the official one: Word documents, cloud folders, email threads, handwritten notes, third-party tools. Every one of those workarounds marked a place the process was failing, and together they pointed at the principle the replacement had to follow.

A successful replacement couldn’t simply digitize the existing PDF. It had to support the way people actually worked.

How information moved between farm families, Financial Professionals and internal specialists — and where it stalled, doubled back or had to be typed twice.

04 / What I designed

A workspace, not a submission packet.

I designed a centralized digital workspace for building and managing cases. Rather than completing documents and assembling a packet, advisors build a case progressively through structured sections covering the client, family, businesses, ownership and financial situation. Documents upload directly instead of being combined into carefully prepared PDFs.

Structure alone wasn’t enough. Specialists needed the story behind the data — family relationships, unusual circumstances, competing goals, the context that makes each farm different. So the experience deliberately accommodates both structured information and open narrative. A farm isn’t a collection of fields in a database.

How people, businesses, assets and ownership are organized underneath the interface.

Designing for complexity

No assumptions about what a farm looks like.

Ownership could be fractional. A family might run several businesses. Land, equipment and operating entities might each be owned differently. Instead of forcing those situations into a linear form, I designed the underlying experience around the relationships between people, businesses, assets and ownership.

Accommodate complicated cases without making every case feel complicated.

05 / The shift

Submitting became the beginning, not the end.

The platform changed what happens after an advisor submits. Cases stay visible over time, so a Financial Professional can see status, what’s outstanding and what happens next. Automated follow-ups keep momentum, and structured information can move into downstream systems instead of being typed in again.

Old

  1. Complete form
  2. Assemble PDFs
  3. Submit
  4. Wait

New

  1. Build case
  2. Submit
  3. Track
  4. Collaborate
  5. Follow up
A case as a place you return to, rather than a packet you post and wait on.

06 / What it changes

Experience work, argued as operations.

Better-structured incoming cases mean fewer incomplete submissions and far less duplicated work. That is the same argument in three different currencies, depending on who is listening.

  1. The organization

    Greater case capacity, less administrative work, and better visibility into how the program was performing.

  2. Financial Professionals

    Less time preparing documentation, and a clearer way to manage complicated cases that stay open for a long time.

  3. Farm families

    Less friction around a planning process that is already complicated, and often deeply personal.

Beyond the initial product

The research also turned up where this could go: AI-assisted document intake, interpreting handwritten notes, smarter reuse of information already on file, automated fact-finder completion. Rather than forcing those into the first version, the platform was designed on a foundation that can carry increasingly intelligent workflows over time.

Looking back

This wasn’t about putting an old form online.It was about understanding the system surrounding that form, and redesigning the experience around the people who actually had to use it.