How I Built a KPI Review Cycle That Actually Changed Franchisee Behaviour

37 franchisees. That's how many I was responsible for when I realised that our KPI tracking was generating beautiful reports that changed absolutely nothing.

Every month, we'd pull the data. Revenue trends, food costs, labour percentages, customer satisfaction scores, speed of service averages. The dashboards looked professional. The reports were thorough. And the same underperforming stores kept underperforming, month after month.

The problem wasn't the data. The problem was that we had no system for turning data into decisions.

That's when I built the Operations Review Cycle — a framework that connects KPI measurement to coaching conversations to action commitments on a fixed cadence. It's the system I'm most proud of building, because it didn't just measure performance. It changed behaviour.

Let me explain why most KPI frameworks fail first, because understanding the failure mode is critical to understanding the solution.

Failure mode one: measuring too much. When everything is a KPI, nothing is a KPI. I've seen franchise systems track 40+ metrics and present them all in a monthly report. The franchisee opens the report, feels overwhelmed, can't figure out what to focus on, and closes it. Nothing changes.

Failure mode two: no cadence. Data gets reviewed "when there's time." In practice, that means it gets reviewed during a crisis — when a store is already in trouble — and ignored when things seem okay. By the time the data triggers a conversation, the damage is done.

Failure mode three: data without conversation. The report gets sent via email. Nobody discusses it. The franchisee might glance at the numbers, nod, and go back to running the store. There's no moment where someone says, "Your food cost was 34% last month when the target is 30%. What happened and what's your plan to fix it?" Without that conversation, the data is just noise.

Failure mode four: no consequence. Even when conversations happen, they don't connect to anything tangible. A franchisee can have the same coaching conversation about the same problem for six months straight with no escalation and no impact on their standing in the network.

The Operations Review Cycle addresses all four failure modes. Here's the structure.

Metric selection: I stripped the KPI framework down to eight metrics. Not eight categories — eight individual numbers. Revenue growth, food cost percentage, labour cost percentage, speed of service average, customer satisfaction score, training compliance rate, food safety audit score, and overall operations assessment. These eight metrics cover the full picture of store performance without overwhelming the conversation.

Fixed cadence: reviews happen monthly. Not "roughly monthly" — on specific dates that are locked in the calendar at the start of the year. The franchisee knows exactly when their review is happening. There's no ambiguity and no excuse for not being prepared.

Structured conversation: every review follows the same format. First, I present the data — five minutes, no discussion. Just the numbers. Then the franchisee responds to the data — what they see, what surprised them, what they already know about. Then we identify the one or two metrics with the biggest gap between actual and target. Finally, we agree on specific actions with deadlines.

The conversation structure is critical. Most coaching conversations in franchise systems are either too soft (vague encouragement, no specifics) or too hard (interrogation, franchisee gets defensive). The structured format prevents both extremes. The data speaks first — not the coach and not the franchisee. That removes emotion from the initial assessment.

Action commitments with follow-up: every review ends with written commitments. "I will reduce food cost from 34% to 31% by implementing portion control checks at the start of every shift, and I will have this in place by March 1." The commitment is specific, measurable, and time-bound. At the next monthly review, the first thing we check is whether last month's commitments were met.

Tiered consequences: the cycle feeds into a tier system. Franchisees who consistently meet or exceed targets are in Tier 1 — they get the most autonomy and first access to new store opportunities. Franchisees who are meeting most targets but have areas to improve are in Tier 2 — they get standard support and coaching. Franchisees who are consistently below target are in Tier 3 — they get intensive support, more frequent reviews, and are not eligible for expansion until they improve.

This tiering is what gives the cycle teeth. Before this system, a franchisee could underperform for a year with no real consequence. Now, sustained underperformance directly affects their ability to grow. That changed behaviour faster than any coaching conversation alone.

The specific behaviours that shifted after implementation.

Franchisees started preparing for reviews. When you know your numbers are going to be discussed on a specific date, you start paying attention to them before the conversation. Several franchisees told me they began reviewing their own data weekly because they didn't want to be surprised in the review.

Food cost management improved network-wide by 2.3 percentage points in the first six months. That sounds small until you do the maths — across dozens of stores, 2.3 points of food cost savings is hundreds of thousands of dollars annually.

The "perpetual underperformers" either improved or exited. The tier system made it clear that the franchise network had standards. Franchisees who weren't willing to meet those standards self-selected out. That sounds harsh, but it's better for everyone — including the franchisee, who can redirect their energy somewhere they'll be more successful.

Expansion decisions became data-driven. Before the cycle, expansion approvals were influenced by relationships, enthusiasm, and lobbying. After implementation, the data determined eligibility. That removed politics from the process and gave every franchisee a clear, transparent path to growth.

The principle underneath all of this is simple: measurement without a decision point is just data collection. The Operations Review Cycle works because every cycle ends with a decision — an action commitment, a tier assignment, an expansion eligibility determination. That decision is what turns data into behaviour change.

If you run a multi-site business and your KPI framework isn't changing anything, the problem isn't your metrics. It's your rhythm.

Want to discuss how to build a review cycle for your business? daine@dainereid.com.