The hidden cost of "probably got done"

There's a phrase that runs through every multi-site operation in the world. It comes up in regional manager meetings. It shows up in HQ check-ins. It's what gets said when leadership asks the question they all want answered.

The phrase is "probably got done."

It's used about morning routines. About safety checks. About visual merchandising. About patient rounds. About the campaign that was supposed to launch this week. About the conversation HQ had with the team last month.

And it's the most expensive phrase in your operation. Here's why.

The math of "probably"

Most operations leaders never calculate the real cost of execution gaps. The numbers are uncomfortable.

For a multi-site retail operation, the math typically runs like this:

Your network executes its operating standards at approximately 78% completion rate (industry average)
Each missed routine has a downstream cost - customer impact, revenue loss, safety risk, brand consistency
For a 1 billion SEK retailer, this translates to 20-40 million SEK in annual operational leakage

The number is roughly the same in restaurants, hospitality, and healthcare - measured differently, but the same shape:

Hospitality: missed room checks → bad reviews → bookings lost
Restaurants: skipped morning prep → slow service → customers don't return
Healthcare: forgotten patient rounds → safety incidents → liability exposure
Transport: missed pre-trip checks → delays → passenger satisfaction drops

The cost of "probably got done" is the cost of every standard you set that doesn't reliably happen - multiplied by every location you operate.

It's not a marketing line. It's the largest unbudgeted expense in most multi-site operations.

Why traditional solutions don't fix it

Most operations leaders have tried to solve this. The standard approaches don't work, and here's why:

Paper checklists

Sit in a binder. Nobody checks. Even when they're filled in, the data sits at the location - invisible to HQ until next audit.

Audits

Happen monthly or quarterly. By the time the gap shows up in an audit report, the damage is already done. Audits measure what was, not what is.

Mobile apps

Adoption is the problem. Frontline staff aren't sitting at a desk - they're on their feet, hands full. An app that requires logging in, navigating menus, and tapping through screens gets ignored when it's needed most.

Manager check-ins

Take time from the work managers should actually be doing. They become symbolic "yes, we did it", rather than verifiable.

Dashboards

Show that something happened or didn't. Don't tell you what to do about it. You're left with the same problem: now you know about a gap, but it's still up to someone to act.

The pattern: these solutions measure, audit, or report. They don't close the loop.

What does work - three principles

Operations that have solved this share three things in common. Not technology. Principles.

1. Real-time confirmation, not weekly reporting

The gap between "the routine was done" and "we know the routine was done" is where leakage happens. The operations that fix this build confirmation into the routine itself — each step confirmed as it happens, not signed off later.

This isn't surveillance. It's the same principle a kitchen uses for food safety: confirm the temperature when you take it, not from memory at end of shift.

2. Exception-based management, not exhaustive reporting

If you're reading reports about everything that went right, you're wasting time. The operations that work focus management attention on the exceptions - the location that didn't complete, the step that got skipped, the shift where execution slipped.

Everything else doesn't need attention. The team handled it.

3. Make doing it easier than skipping it

If the system that confirms execution is more painful than ignoring it, people will ignore it. The operations that work - especially the ones with frontline teams who didn't grow up with software - make the confirmation part as light as a single tap.

The principle: the easier you make compliance, the more compliance you get.

Three steps you can take this week

You don't need a year-long transformation project. You need to start.

Step 1 - Identify the single routine that costs you most when it's missed.

Not your top-ten list. Your number one. The morning prep. The safety check. The cash count. The patient round. The one that, when it doesn't happen, creates the most downstream damage.

Step 2 - Measure your real baseline. Honestly.

Not what your standard says. What's actually happening. If you don't know, ask three regional managers what they think completion rates are. Their answers will probably differ by 20%. That gap is your starting point.

Step 3 - Build a confirmation loop for that one routine.

Start at one location. Get it working. Then scale. Not 50 locations on day one - one location, with confirmation, for 30 days.

The pattern will tell you everything about why "probably got done" runs your business.

What changes when you fix this

Operations that close the execution gap consistently see similar results:

Routine completion rates rise from 75-80% to 92-97% in 90 days
Customer satisfaction rises by 0.5-1.0 NPS points (the impact of consistent execution is direct)
Manager time spent on compliance audits drops 40-60%
Network-wide consistency - your worst location starts performing more like your best

The math runs in the opposite direction now. The same operation that was leaking 20-40 million SEK to "probably got done" recovers most of it within 12 months.

How Yump helps

Yump runs every routine - scheduled, assigned, confirmed.

One standard, every location, every shift. Real-time confirmation, not weekly reports. Exception alerts to the right person, not dashboards for HQ.

Want to see what "actually got done" looks like at every location?

Möchten Sie sehen, wie Yump in Ihrem Team funktioniert?

20 Minuten. Ihr Anwendungsfall statt Standardpräsentation.

Demo vereinbaren