Why Your Clients Don't Need to Understand Complexity — They Need to See Through It

Published in June
23 June 2026
Reviewed
Rao Adavikolanu
Chief Marketing Officer
Published in June

23 June 2026

Summarize blog with

Showing clients 200 implementation tasks doesn't build confidence. It creates anxiety. HealthEZ's April Slinger explains what to show instead — and what happens when you get it right.

HealthEZ handles close to a million possible plan combinations per client implementation. Deadlines range from 90 days to one business hour. (They did not succeed that time.) 

The HR leaders going through this process aren't healthcare experts — but they're making decisions that touch their entire employee population and their own careers. 

Get it wrong, and employees can't see a doctor. That's not an inconvenience. That's a career-ending crisis for the person who approved it.

April Slinger, who leads implementation at HealthEZ — a third-party administrator of self-insured health plans for employer groups — brought this environment to Propel 26 not to explain how complex it is, but to explain how they made it simple for the people going through it.

Read on for the key takeaways from the session.

Why complexity isn't the problem — scale is

In 1869, the transcontinental railroad was completed. Suddenly, people could move fast across vast distances. 

That progress exposed a problem that had always existed but had never mattered: there were 144 local times in North America. Each one was based on the position of the sun. Pocket watches were accurate and completely unreliable the moment you left your town.

The solution wasn't to teach every traveler to calculate solar position. It was an abstraction — the time zone. Time zones don't eliminate the complexity. They contain it in a shared framework that makes it invisible to the people using it.

Slinger's point: this is the mirror of what every PS team is facing today. "As soon as scale and variability increase, clarity has to change. 

What used to work no longer does." You can't teach your clients astrophysics. You have to contain the complexity, simplify their experience, and focus on the outcomes you want them to achieve. 

The underlying 200 steps still exist. The client never needs to see them.

The Domino's Pizza Tracker principle: transparency without expertise

When Slinger looked outside healthcare for a model of how to solve the complexity-clarity problem, she landed on Domino's.

The Pizza Tracker works because it dissolves a human problem — people are bad at waiting and genuinely hate not knowing where things stand. 

It doesn't require any understanding of dough preparation, oven temperatures, or delivery routing. It gives you a simple, intuitive view of progress that you can monitor as obsessively as you want.

"Modern customers are expecting transparency without needing any expertise."

The real insight isn't about pizza. It's about what information to surface. "People don't struggle because they have too little information. 

They struggle because they have too much." Herbert Simon: "A wealth of information creates a poverty of attention." Einstein's version: "Make everything as simple as possible, but not simpler" — simplicity only has value when it preserves accuracy.

HealthEZ wasn't trying to hide the complexity of their implementations. They were translating it into the clearest possible experience for clients who were overwhelmed, operating under high personal stakes, and not there to become healthcare experts.

How HealthEZ collapsed 200 implementation tasks into 3 outcomes

The first step was brutal honesty about the existing task list. It was just that — a list. No prioritization, no connection between steps, nothing that communicated value. 

So Slinger's team asked a simple question for every task: Why does this step exist? Some had no good answer. Those got cut. The ones with good answers collapsed into the outcome they served.

The result: three outcomes. Access to care. A plan that works. Everyone is getting paid.

"Once we said that out loud, it was so obvious to everyone. It was something that no one had ever said out loud before."

From there, HealthEZ stopped showing clients task lists entirely. Outcomes only. Milestones only. Only things clients can influence. Where deeper information exists, clients know where to find it — but it's not pushed at them by default.

They also named the experience. "Easy Implementation" — branded, commercialized, included in sales conversations, referenced at kickoff, built into marketing materials. Brokers started expecting it when they returned from a sale. 

It became a market differentiator, not an internal tool. Slinger's standard for her team: consistent narrative, not a uniform script. Every implementation manager tells the same story in their own words.

4 key takeaways from HealthEZ's outcome-driven implementation model

  • Collapse tasks into outcomes, not the other way around. Start with the question: What must be true for the customer to feel successful? Walk backward from that to the task list. Cut anything that doesn't answer it. Collapse the rest into the fewest meaningful outcomes you can name out loud without a slide deck.

  • Stop showing clients task lists. They create anxiety, not clarity. Show outcomes, milestones, and only what the client can influence. Surface a simple to-do / doing/done progression with a clear path to move forward. Keep the 200 steps inside your team — invisible to the client by default.

  • Commercialize the portal — it's a product. Give it a name. Brief your sales team on it. Put it in marketing materials. Open it live at kickoff. When clients know what to expect before implementation starts, adoption is faster and resistance nearly disappears. When it has a name, it becomes something people want to be part of — not a system they're asked to use.

  • Measure what used to be invisible. HealthEZ tracked access to care as their primary implementation metric — not NPS, not utilization. Within two years of redesigning the experience, access to care went from 43% to 90%. Broker escalations to the CEO during the busy season dropped to zero. Average delivery speed improved by two days across the board. "Simplifying complexity isn't just good design. It's good business."

Conclusion

April Slinger closed with a number: 43%-90% access to care in two years. That's the metric that matters most at HealthEZ — not because it looks good in a QBR, but because it means employees can actually see a doctor.

The path to that number wasn't more technology or more process. It was a decision to stop treating implementation as a list of tasks and start designing it as a journey toward outcomes clients could understand and track.

The time zone analogy is the right frame: complexity doesn't disappear. You contain it in a shared framework so the people going through it don't have to understand how it works — only where they are and what they need to do next.

When you do that well, your clients don't just complete implementation. They tell everyone else it was the best process they've ever been through.

Check out the rest of our Propel 26 recaps here for more insights from the industry's best.

Authored by

Kailash Ganesh

Reviewed by

Rao Adavikolanu

Kailash Ganesh is a professional services researcher at Rocketlane with more than seven years of experience in content, research, and market analysis. He studies how enterprise PS teams are adopting agentic AI to transform delivery operations, has evaluated every major PSA platform in the category, and writes from the perspective of a practitioner who watches enterprise PS teams make these exact decisions daily.

FAQs

“Speeds up CSV importing and saves me from having to get customers to use a template file or create mapped data exports. Quick to integrate and flexible outside the happy path. We found defining workbooks and templates confusing; at a prior job it was configured through code, which I preferred.”

Source: G2 review

Sebastian
Intercom

AI that executes your delivery work (Add to any plan)

Most popular

Standard

Ideal for expanding organizations needing more in-depth capabilities and integration for scaling.

$49

per team member/
month billed annually

*minimum of 5 team members

  • Full partner ecosystem support
  • Dynamic templates for any project
  • Milestone CSAT for customer pulse
  • Docs, forms, projects in one place
  • Docs, forms, projects in one place
  • Approval-governed time tracking
  • 200 Automations/user/month
  • Native HubSpot, Jira, Slack Integration

Most popular

Premium

Great for teams desiring tailored workflows with comprehensive reporting capabilities.

$69

per team member/month billed annually

*minimum of 5 team members

  • Real-time project profitability
  • AI resourcing and capacity planning
  • All revenue recognition models
  • Centralized rate cards and budgets
  • Portfolio reporting for leaders
  • Bill faster & improve cash flow
  • Native Salesforce integration

Most popular

Enterprise

Tailored for large enterprises requiring a fully customizable, comprehensive delivery engine.

Custom Pricing

*minimum of 5 team members

  • SAML SSO and role-based access
  • Unlimited, hands-off automations
  • Soft-allocate pipeline deals early
  • Skills matrix for smarter staffing
  • Staff global teams ahead of demand
  • Multi-currency global delivery
  • Snowflake data + custom reports

Full reviews for all 11 tools below

<TL;DR>

Best all-in-one Certinia alternative for B2B SaaS and technology PS teams with 25 to 150 consultants. Delivery, resource management, project financials, client portal, and agentic AI in one PSA, with no Salesforce dependency. From $49/user/mo (full PSA from $69) · 4.7/5 on G2 · 4 to 12 week go-live

<TL;DR>

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.

Trusted by top companies

One platform does what the entire table above tries
to split across tools.

One platform does what the entire table above tries
to split across tools.

One platform does what the entire table above tries
to split across tools.

Myth

Enterprise implementations fail because customers don’t follow the process or provide clean data on time. Most delays are purely “customer-side” issues.

Fact

Implementations fail because complex environments need real-time technical problem-solving. FDEs unblock workflows, integrations, and unknown constraints that traditional onboarding teams can’t resolve on their own.

Get a better all-in-one PSA

Get a better all-in-one PSA

Did you Know?

Companies that embed engineers directly with customers see significantly higher enterprise retention compared to traditional post-sales models — because embedded engineers uncover “unknowns” that never surface in ticket queues.

Sebastian mathew

VP Sales, Intercom

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.