MIKE KUECHENMEISTER · PRODUCT DESIGN

Making pay make sense for 8,000 advisors

A year of discovery that replaced one-off fixes with one funded vision, and set the roadmap for Northwestern Mutual’s compensation experience.

Role
Design Lead → Design Director, Field Rewards
Company
Northwestern Mutual
Timeline
About 12 months
Team
Product partner, development leadership, and the Field Engagement team (recruiting and scheduling advisors)
What I did
Framed the opportunity, led research and synthesis, defined principles and the system model, ran workshops with my design team, designed vision concepts, and co-led the pitch to business leadership

Northwestern Mutual’s 8,000+ financial advisors are paid entirely on commission, across 120+ programs and more than 10 disconnected systems. No one could see the whole picture of what they earned or why. I led a year of discovery: 24 interviews with advisors and their CFOs, 1,000+ insights, and a survey that let the field rank its own priorities. That produced design principles, a single system with views for advisors, leaders and the home office, and a shared experience vision. With product leadership, we pitched the highest-impact pieces to the business owners, and they adopted them into the roadmap. The first release, Minimum Earnings, saves an estimated 1,750 hours a year.

Compensation dashboard

When your paycheck is a puzzle

Northwestern Mutual sells only through its independent financial advisors, known internally as “the Field.” Their pay is 100% commission. It varies by product, by production, and over time, and it’s spread across bonuses, allowances, recognition programs, benefits and taxes.

For an advisor building a business, that pay is the business. But the information lived in more than 10 systems with little connection between them. Advisors couldn’t easily answer basic questions: What am I earning? What bonus am I close to? What happens if I hit my next goal?

Meanwhile, the teams serving them kept shipping one-off fixes, often tacked onto legacy systems, with no shared picture of where the experience was headed. Every fix added one more place to look.

One advisor’s pay, across 10+ systems

Listening at scale

I tied the work to the goals leadership already tracked (the size of the Field, advisor revenue, the diversity of the Field, and financial plans per household), then led the research. Our Field Engagement team was essential: they identified advisors and got them on the calendar.

  • A full system inventory mapped where every piece of an advisor’s pay actually lived.
  • 17 interviews with advisors (30 minutes each) and 7 with their CFOs (60 minutes each) covered commissions, allowances, recognition, bonuses and taxes.
  • More than 1,000 insights, which my team and I worked through together in synthesis workshops
Over 1,000 user insights organized by person and topic

Four decisions that shaped the vision

1. Let the Field rank its own problems

With 1,000+ insights, the risk was that stakeholders, or we as designers, would pick favorites. Instead, we grouped the insights into themes and asked advisors to rank them in a survey:

  • A complete view of contract value came first for 47.5%.
  • Understanding revenue, expenses and taxes came first for 31.1%.
  • Visibility into bonuses came first for 18.0%.

That ranking became the backbone of the roadmap, and it made our priorities easy to defend.

Survey results: theme prioritization

Our survey validated that the insights we gathered and synthesized accurately captured the field’s biggest needs. It also helped us understand which themes and opportunities were the most desirable.

01Providing the field a more complete view of the value of their contract, both current and projected into the future
02Helping the field understand their revenue, expenses, and potential tax obligation
03Maximizing the field’s contract through visibility into bonuses
0%25%50%75%100%
First choiceSecond choiceThird choiceLast choice
Advisor-ranked priorities

2. Set principles before screens

The same insights produced four principles that every later decision was measured against:

  • Create a unified experience.
  • Present actionable information.
  • Make rewards easy to understand.
  • Show long-term impact.

The themes said what to fix, and the principles said how.

3. Stop building one-off fixes

This was the decision that mattered most. Instead of patching another legacy system, I proposed a single Field Rewards platform:

  • Three views on one set of data: advisors, field leaders and the home office each see what they need.
  • Built into the platform advisors already use daily (NMXP), not added as another destination
  • The interface kept separate from the data, connected through APIs, so the experience could evolve without rebuilding the systems underneath

It also changed things for our development partners. Once they knew new work would land on one platform rather than being bolted onto old ones, they could plan and build with far more clarity.

Field Rewards experience solution overview

One integrated solution for field reps, their leaders, and the home office: a shared foundation, with a personalized view for each role.

Home office view
Field leader view
Field rep view
Field Rewards dashboard
Compensation
  • Wealth comp
  • Risk comp
  • Bonuses
  • Projections
  • Expenses
  • Loans
Rewards & Recognition
  • Production credits
  • Recognition tracking
  • Ribbon gallery
  • Award information
  • Sales reporting
Benefits
  • Health & wellness
  • Life & disability
  • Family planning
  • Retirement programs
  • Business protection
Management compensation
Leader awards
Manage benefits
Home office administration interface
Experience attributes
  • Role driven and personalized
  • Integrated into the broader field experience via NMXP
  • In-context educational components
  • Shared views for leaders, reps, and the home office
  • UI layer separated from data, built on APIs
  • Uses NMXP platform capabilities where possible
An integrated and personalized solution for all users

4. Show the future instead of describing it

Across about five workshops, my team and I worked through the themes and sketched solutions. From those, I designed vision concepts: short stories that follow one advisor through her day.

  • Checking a compensation summary across pay periods
  • Seeing her progress toward every bonus she qualifies for
  • Learning how a program works at the moment she needs it
  • Resolving minimum-earnings issues with the home office in real time

The concepts gave product, engineering and leadership the same picture to react to.

Choose a thumbnail to explore a day in the life of Britt Cruz, a Northwestern Mutual field rep.

Our vision through the eyes of a field rep

From vision to roadmap

With our product partner, we took the vision to the Field Rewards business owners, the program managers responsible for advisor pay and benefits. We asked them to prioritize the three pieces with the most impact:

  • Minimum Earnings
  • Earnings dashboards
  • A benefits overview and progress tracker

They adopted those asks into the product roadmap, which then shipped in stages:

  • Minimum Earnings (2023): turned a year-end paperwork process into a shared, daily view. It saves an estimated 1,750 hours a year.
  • Field Compensation Dashboard (2024): gave 8,000+ advisors insight into 120+ compensation programs.
  • Field Management Dashboard (2025): gave field leaders a view into their own and their team’s compensation.

I left Northwestern Mutual in October 2023. The 2024 and 2025 releases were built by the team after my departure, from this vision and these principles.

From vision to staged releases

What I took away

Evidence makes a vision defensible. Letting advisors rank their own priorities turned a design opinion into a business case.

One platform is a gift to engineering, not just to users. The biggest change was giving our development partners one clear place to build.

Bring the decision-makers in earlier. If I did it again, I’d invite the business owners into the ideation workshops, not just the final pitch. We’d likely have won even more of the roadmap, and it would have built the relationship sooner.