The invisible cost of employee app friction.

A large, multi-national bank had invested heavily in a lead prioritization feature inside Salesforce. The goal was straightforward: help advisors follow up on the highest-quality leads faster than competitors.

The feature worked as designed. But no one could answer a basic question: was it actually being used?

They couldn't see which team members relied on it, how often it influenced decisions, or whether it made any difference in speed to follow-up. Which meant they couldn't prove the investment was working.

When they finally looked at real team member behavior, the gaps were hard to ignore.

Some business relationship managers ignored the feature entirely. Others used it inconsistently. And the highest-performing team members had quietly built their own ways of working around it.

The issue wasn't the feature itself. It was the gap between how it was designed and how they actually managed new and existing client relationships.

Once they could see that, the fixes were straightforward: redesign around real behavior, remove friction in key steps, and align the experience to how top performers actually delivered financial expertise and client-centric solutions.

A telco team relied on an internal point of sale (POS) system and support applications to help their retail sales associates.

Performance was off. Associates would run into various issues with the app while helping customers and report them to IT. But the system didn't reflect it.

Dashboards showed surface-level metrics, but nothing pointed to a clear issue. So every investigation started the same way — piecing together tickets, chasing anecdotal feedback, and reacting after the fact.

By the time problems were identified, they had already impacted the in-store experience.

When the team finally could see in real-time how their associates were using the app, the pattern became obvious.

They could see where associates were getting stuck, which steps were taking too long, and where crashes were happening in real time instead of hours or days later. In one case, they uncovered a spike in blank pages and crashes that had been quietly degrading the experience across locations.

What had looked like isolated issues turned out to be systemic.

With that visibility, the team stopped guessing and started prioritizing.

A hotel group rolled out a new Property Management System across its locations.

From a rollout perspective, everything was complete. The system was live, and no major issues were being reported.

But adoption didn't match expectations.

When the team looked at how front desk staff actually navigated the system, the problem wasn't failure. It was friction.

Some staff members were still using an outdated support URL instead of the new platform. Others followed workflows with extra steps that no longer added value. Nothing dramatic. Nothing that triggered alarms.

But these moments happened during guest check-in — in front of the guest — and they happened thousands of times a day.

Small inefficiencies, repeated at scale, became measurable delays.

Once the team could see those behaviors, the fixes were simple.

They redirected staff members to the correct system, streamlined workflows, and removed steps that added time without improving outcomes.