This is from the “Accounting Makes Cents” podcast episode #118 released on Monday, 27 July 2026.
Today, we’re looking at a classic management accounting dilemma: What happens when the metrics designed to drive efficiency end up creating unexpected operational issues?
Now, if you’ve been working through your CIMA preparation—specifically around P1 and P2—you’ve likely come across the term ‘goal congruence’. It refers to the ideal scenario where every division, subsidiary, and manager is working toward the exact same strategic objectives as the parent group.
But aligning these goals in practice can be highly complex.
Jump to show notes.
To see how these concepts play out in the real world, we’re looking at a major franchise dispute happening right now, which we’ll analyse through a parent-subsidiary lens. I’d actually also like to use this case study for the next couple of episodes to create a mini-series of sorts. There’s just so much to be discussed here in this case.
Anyway, here’s the case: A large pizza franchisee operator has filed a $100 million lawsuit against Pizza Hut’s corporate parent company over the mandated implementation of an AI delivery platform. The operator claims the technology disrupted their delivery pipeline and impacted their revenue.
Now, a quick caveat here: I am obviously not a lawyer, and we are not here to discuss the legal technicalities or predict the outcome of the court case. Instead, we are going to look at this strictly from a management accounting perspective. First, we’ll outline the operational details and corporate structures reported in the case. Then, we’ll layer on the CIMA performance management topics so you can see exactly how to apply these theories to your exams. Let’s get into it.
The Real-World Drama: The Pizza Hut Case
Let’s look at the operational setup described in the lawsuit.
Before the new technology was introduced, the franchisee managed its own local contract with DoorDash. Under that system, local branch managers retained operational control over the dispatch process. They used a manual tablet in the kitchen to request a driver only when an order was prepared, hot, and ready for delivery. Additionally, managers had the authority to manually block specific drivers from picking up from their stores if they had a history of poor service.
Then, two top-down corporate changes occurred.
First, Pizza Hut Corporate signed a national partnership agreement with DoorDash. Second, Pizza Hut mandated that all operators transition to a centralised AI dispatch platform. The strategic goal on paper was to automate the dispatch process, reduce human error, and optimize delivery routing.
However, according to the lawsuit, the integration created an unintended consequence. The new system gave independent DoorDash drivers visibility into the kitchen’s internal live data. Drivers could see the real-time production status of orders, what was coming down the line next, and the exact tip amount attached to each delivery.
The lawsuit claims that because these drivers operate as independent contractors looking to maximise their pay-per-hour, they used this data transparency to adjust their behaviour:
- Cherry-Picking: It is alleged that drivers frequently declined low-tip or cash-on-delivery orders, causing that food to sit on the warming racks longer.
- Order Batching: Because drivers could see live kitchen data, they could see when a high-tip order would be ready in the near future. The lawsuit claims drivers would wait in the parking lot, delaying the delivery of an already-completed order so they could bundle multiple high-tip deliveries into a single trip.
Furthermore, because of the national corporate agreement, local branch managers no longer had the system authority to block or penalise these external drivers.
According to the metrics cited in the filing, before the AI rollout, 90% of deliveries arrived in under 30 minutes. Following the implementation, the time food spent waiting on the rack increased from under 5 minutes to over 20 minutes, more than half of all deliveries took 45 minutes or longer, and sales in major markets declined by nearly 10%.
The CIMA Accounting Breakdown
So, how do we take these operational facts and use them to understand our CIMA syllabus? This situation provides a clear example of two core concepts from P1 and P2: Sub-optimisation and Goal Congruence.
The Perils of Sub-optimisation
In management accounting, sub-optimisation occurs when one specific part of an organisation optimises its own performance metrics at the expense of the larger group’s primary objectives.
In this scenario, the independent drivers optimised their personal metrics—their return per mile and pay per hour. However, because they are external contractors rather than company employees, their incentives did not align with protecting the brand’s long-term customer retention. When a performance management system allows one segment to optimise in isolation, it can disrupt the broader operational flow.
The Realities of Goal Congruence
This brings us back to goal congruence.
When designing KPI targets or implementing automated systems, management must ensure that the incentives of external partners align with the strategy of the business. By providing external contractors with sensitive tip data without a mechanism for local accountability, a conflict of interest was introduced. The goals of the independent delivery network and the strategic goals of the kitchen were no longer congruent.
The Solution: How Do We Fix the System?
Now, if you are sitting a CIMA case study exam, you can’t just stop at identifying what went wrong. To score high marks, you have to act as the strategic consultant and propose a fix. So, if we were stepped into this organisation as accountants, how do we redesign this performance measurement system to restore goal congruence?
There are three concrete control mechanisms we could implement:
A. Developing Joint or Shared KPIs Right now, the performance management system is completely fragmented. The kitchen is measured on food preparation speed, while the external drivers are measured strictly on their individual trip routing and efficiency. Because their metrics are isolated, their behaviors conflict.
To fix this, we need to introduce Joint KPIs. Instead of evaluating the driver purely on their personal transit metrics, their financial incentive should be tied to a shared outcome—such as a ‘Freshness Window’ or a specific Customer Satisfaction score for that exact delivery. When the external contractor and the internal kitchen share the exact same metric, their operational goals are forced back into alignment.
B. Data Masking and Balanced Information Symmetry The operational disruption in this case was triggered by information asymmetry—specifically, giving sensitive, non-essential operational data to external parties. The algorithm gave independent contractors full visibility into the live kitchen queue and the exact tip amounts before they accepted the job.
From a management control perspective, the fix here is data restriction. The system should only provide independent contractors with the information strictly necessary to execute their immediate task: the pickup location, the drop-off location, and the estimated readiness time. By masking sensitive financial variables like tips until after the service is secured or completed, you eliminate the data transparency that allowed the system to be gamified in the first place.
C. Restoring Local Variance Flags (The Principle of Exception Reporting) When corporate signed the national contract, they stripped local branch managers of their system authority to block underperforming drivers. This completely broke the local feedback loop.
To correct this, management accountants would recommend implementing a system of Exception Reporting and local variance flags. If the centralised algorithm dispatches a driver whose operational metrics fall outside acceptable tolerances—such as excessive wait times in the parking lot or repeated customer complaints—the system must automatically flag this variance and restore temporary manual override power to the local manager. You cannot manage a decentralised network effectively if you completely eliminate local supervisory control.
Key Takeaways
So here’s our takeaway from this case and the topics we’ve covered:
Align Metrics with Core Strategy: If a business’s competitive advantage relies on speed and product quality, KPI targets must protect those factors rather than focusing solely on routing or driver efficiency.
Account for Human Behavior: Systems and automation look flawless on a dashboard, but they must be designed around how individuals will interact with and potentially leverage that data.
Show notes simplified
In this episode, MJ the tutor looks at a real-world $100 million corporate disaster to answer a big exam question: what happens when the metrics you design to drive efficiency actually break your business? Students will learn the perils of sub-optimisation, and why KPIs that look perfect on a spreadsheet can totally fail in real life.
MJ THE TUTOR 