From Local Wins to System Health: Avoiding Sub-Optimization
- RESTRAT Labs
- 5 hours ago
- 14 min read
Optimizing individual parts of a business often harms the overall system. Organizations frequently focus on isolated metrics like team productivity or cost savings, which can lead to bottlenecks, delays, and poor customer outcomes. For example, a sales team might close deals faster than the delivery team can handle, or cost-cutting might compromise quality, as seen in General Motors' ignition switch crisis.
The key to avoiding these pitfalls is shifting focus from local wins to system-wide performance. This means:
Measuring end-to-end lead time and flow efficiency instead of departmental utilization.
Assigning clear accountability for the entire process to avoid work getting stuck between teams.
Aligning incentives across departments to ensure everyone works toward shared goals.
Reducing work-in-progress (WIP) to prevent bottlenecks and improve throughput.
Why Systems Thinking Is So Important
What Sub-Optimization Looks Like
Common Sub-Optimization Traps
Sub-optimization often follows familiar patterns, with the "Stay Busy" mentality being one of the most frequent pitfalls. Managers, worried about underutilized resources, push departments to operate at maximum capacity. This approach causes non-bottleneck teams to churn out work at full speed, justifying their resource usage. However, this overloads the actual bottleneck, reducing the entire system's throughput. For example, a design team might produce 50 mockups in a month, but if engineering can only implement 10, the extra 40 just pile up. Meanwhile, the bottleneck team gets bogged down with emails and estimates instead of moving the system forward [2].
Another trap is siloed metric misalignment, where departments optimize for their own KPIs at the expense of the broader system. Take purchasing, for instance. The team might focus on securing the lowest material costs, which sounds great - until defective materials lead to rework and delays for Quality and Operations. While the purchasing dashboard shows reduced costs, the production floor grapples with inefficiencies that slow everything down [7].
"If 94% of problems are system problems, then 94% of the time, blaming workers is wrong" [7].
In smaller businesses, sales teams often fall into this trap by overloading the delivery team. Imagine a remodeling contractor landing five new projects in a week. It’s a win for sales, but if the crew can only complete two projects per month, the backlog grows, slowing everything down. Coordination becomes chaotic, customers wait longer, and overall satisfaction drops. Sales hit their numbers, but the system as a whole suffers.
Local Optimization Focus | Systemic Optimization Focus | Result of Local Focus |
Departmental Utilization | End-to-End Lead Time | Work queues grow, and bottlenecks worsen [3] |
Individual Team Velocity | Cross-team Flow | Tasks are completed but not delivered ("false wins") [3] |
Cost-cutting / No Slack | Resilience and Buffers | Systems become fragile and prone to failure [8] |
Siloed Decision Making | Shared System Outcomes | Teams clash, and internal conflicts rise [2] |
Spotting these patterns early can help prevent bottlenecks, delays, and the constant cycle of putting out fires.
How to Spot Sub-Optimization
Recognizing sub-optimization as it happens is essential for shifting focus from local wins to improving overall system performance. One key indicator is growing work queues between teams. If teams consistently complete their tasks on time, but product releases are delayed, that’s a red flag. Items marked "ready for deployment" sitting idle for days or weeks while teams move on to new tasks is another clear sign [3].
Constant firefighting and political blame games are also symptoms of sub-optimization. If teams spend more time in coordination meetings than on productive work - or if finger-pointing becomes the norm - it’s a sign that the system is prioritizing local efficiency over global outcomes [2]. A small business example might involve contractors working out of sync, like an electrician arriving before drywall is finished. These missteps create delays and rework that don’t show up on any single vendor’s performance metrics.
"A company where everyone is busy 100% of the time is terribly inefficient." - Tiago Forte, Founder, Forte Labs [2]
Finally, beware of misleading success metrics. A team may hit all their targets, showing "green" on dashboards, while the overall customer lead time doubles. For instance, finishing a task early means little if the next team waits two weeks to pick it up. The system’s inefficiencies will always surface, even if individual metrics look great [3].
Why Sub-Optimization Happens
Metrics That Hide Bottlenecks
Sometimes, the metrics we rely on can be deceiving. Departments often track their own success using metrics like velocity, utilization, or task completion rates. These numbers might look great on paper, but they can mask deeper problems. For instance, a design team might proudly report completing 40 story points in a sprint, but if those deliverables never make it to customers, the actual value produced is zero [3]. Bright green dashboards can hide delays that leave customers waiting.
This issue ties back to what W. Edwards Deming called the local optima trap - the flawed assumption that improving one part of a system automatically improves the whole [2]. According to the Theory of Constraints, speeding up a non-bottleneck area often creates the illusion of progress. In reality, this just shifts more work toward the true bottleneck, forcing it to spend time managing extra tasks instead of producing value [2].
"For optimizing the whole, we must sub-optimize the parts."W. Edwards Deming [4]
A glaring example of this is the General Motors ignition switch scandal. The company prioritized cost-cutting metrics over safety, ignoring a defect that could have been fixed for less than $1 per car. This short-sighted focus on localized cost savings led to a catastrophic failure, resulting in over 100 deaths [1]. While the metrics showed cost savings, the overall system suffered devastating consequences.
These flawed metrics often create the perfect storm for siloed decision-making and misaligned priorities.
Siloed Decisions and Misaligned Incentives
Sub-optimization thrives when teams don’t share a common goal. Without a clear system-wide purpose, individual departments naturally focus on their own objectives, often working against one another [7]. For example, sales might aim for variety, manufacturing might prioritize standardization, and finance might push for minimal inventory. The result? A fragmented system that struggles to perform efficiently.
The pressure to “stay busy” only makes things worse. Managers, worried about underutilized resources, push teams to operate at full capacity. This leads to what Tiago Forte calls "expensive busyness" - a situation where teams take on unnecessary projects just to appear productive. This overloads the system with work-in-progress, ultimately clogging the bottleneck [2][3].
"A company where everyone is busy 100% of the time is terribly inefficient."Tiago Forte, Founder, Forte Labs [2]
Incentive structures can also deepen the problem. Take purchasing, for example. If the team is rewarded solely for securing the lowest material costs, they might prioritize cheap materials that compromise quality. While purchasing metrics might look strong, downstream teams are left dealing with rework and delays - hurting the system as a whole. Misaligned incentives like these lock organizations into a cycle of inefficiency.
Missing Accountability for End-to-End Flow
Another major factor behind sub-optimization is the lack of accountability for the entire process. One of the biggest challenges is that no one owns the whole system. Without clear ownership of end-to-end flow, work often gets stuck between teams [7]. For example, features marked "development complete" might sit for weeks waiting for testing. These delays don’t show up in any individual team’s metrics, creating blind spots.
Deming famously estimated that 94% of problems in an organization are system-related, not the fault of individual workers [7]. When no one is accountable for the bigger picture, systemic issues are often blamed on employees. Teams end up shouldering the blame for delays caused by poor handoffs, conflicting priorities, or unseen bottlenecks.
"If 94% of problems are system problems, then 94% of the time, blaming workers is wrong."Allan Paterson [7]
This lack of system-wide accountability can also lead to what Peter Senge describes as "accidental adversaries." Teams unintentionally undermine each other because their incentives don’t align [5]. For instance, if marketing is rewarded for placing orders rather than delivering them on time, they might overload the assembly line. This causes delays, frustrates customers, and increases penalties. Without someone ensuring overall alignment, these localized efforts fail to translate into meaningful results for the customer, repeating the same pitfalls over and over again.
How to Design for System Health
To avoid the traps of narrow focus and disconnected responsibilities, organizations need systems that evaluate overall performance, assign clear accountability, and align goals with end-to-end success.
Measure Flow and Total Value, Not Departmental Efficiency
It’s time to rethink what you measure. Metrics like velocity, utilization, or task completion may seem helpful, but they often give a false sense of progress. Instead, focus on metrics that track the entire process: end-to-end lead time, cycle time, flow efficiency, and throughput. These reveal how long it takes for work to move from start to finish, rather than just showing how busy individual teams are.
For example, the Penny Game simulation demonstrated that reducing batch sizes improved delivery speed by 470% for the first unit and 222% for the final unit - even though individual steps took 21–44% longer. This highlights how prioritizing local efficiency can harm overall performance[10].
Organizations should also adopt quality-adjusted metrics. Measuring activity alone - like "coverage" or "utilization" - isn’t enough. Take India’s Janani Suraksha Yojana program, which offered cash incentives to increase facility-based births. While utilization rose, the program didn’t significantly lower maternal or newborn mortality because it focused on activity rather than system-wide quality[11]. The lesson? Measure outcomes, not just effort.
Once measurement improves, the next step is clarifying ownership of the entire process.
Assign Clear Ownership of System Flow
When someone owns the entire value stream, they can address bottlenecks and ensure smooth flow across all stages.
This requires assigning roles specifically responsible for system flow. In large organizations, this might mean appointing a Release Train Engineer (RTE) or creating a cross-functional transformation team with expertise in system thinking[3][4]. For smaller businesses, the owner or a trusted operations lead often takes on this responsibility, overseeing the process from start to finish.
These roles need the authority to manage non-bottleneck areas. According to Eli Goldratt’s Theory of Constraints, teams working in non-bottleneck areas must adjust their pace to match the system’s main constraint. This prevents unnecessary buildup of work-in-progress[9]. While this approach can be tough for managers to accept, it’s essential for maintaining overall system health.
With roles defined, aligning incentives across the organization ensures everyone works toward shared goals.
Align Incentives to System Outcomes
Misaligned incentives can lead to fragmented efforts. For example, rewarding purchasing teams solely on cost savings can result in lower-quality materials. Similarly, incentivizing sales teams only on deal closures - without considering delivery capacity - can overwhelm the system. And if teams are rewarded for speed without factoring in rework, quality takes a hit.
"For optimizing the whole, we must sub-optimize the parts."W. Edwards Deming[4]
To prevent these issues, reward teams based on system-wide results. Recognize efforts to reduce lead times, improve first-pass quality, and boost customer satisfaction - not just individual or departmental achievements. Budgets should also support the organization as a whole, rather than forcing departments to compete for resources[12].
Tesla offers a great example of this approach. By vertically integrating its production - manufacturing its own batteries, motors, and ERP software - and co-locating engineering with manufacturing, Tesla reduced variation and captured internal learning. This setup allowed the company to make weekly design changes while maintaining a cost advantage over traditional manufacturers that outsource components[7]. Instead of focusing on isolated fixes, Tesla optimized its entire system for better results.
System Thinking for SMBs
The challenges of misaligned priorities and inefficiencies hit small businesses harder and faster than larger enterprises. For a 10-person contractor or a 25-person service business, optimizing the wrong areas can cause noticeable damage in just days, not months.
Coordinating Sales and Delivery
One common issue arises when sales and delivery teams work at cross-purposes. If sales incentives focus solely on "orders placed" rather than "orders delivered on time", chaos can erupt. Sales may close deals faster than the delivery team can handle, leading to delayed starts, rushed jobs, and mounting rework. This disconnect often stems from management’s push for rapid growth, which clashes with operations' need for stability to make the most of existing resources[5].
To address this, businesses should hold joint planning sessions where sales and delivery teams align on what’s realistically achievable. Visual tools that map out the entire value stream can also help identify bottlenecks and delays in handoffs[3][6]. Without this alignment, teams risk exacerbating the problem when they aim for maximum utilization - a pitfall explored below.
Why Maximizing Utilization Backfires
Small business owners often worry about underutilized staff or crews. This fear leads to a "stay busy" rule, where every team is expected to operate at 100% capacity. While this might sound efficient, it often backfires. Non-bottleneck teams may start projects just to stay busy, creating an overload that overwhelms the true bottleneck - whether it’s a specialized worker, a permitting process, or a quality control step.
When bottlenecks are bogged down with tasks like answering emails, providing estimates, or processing extra requests, their productive capacity diminishes, dragging down the entire system’s throughput[2]. Even if dashboards show high utilization, customer lead times can double, and delivery falters. The key is to accept that some teams need to operate below full capacity to maintain overall flow. Instead of tracking individual activity, businesses should focus on metrics like end-to-end lead time and cycle time to measure real progress[3][6].
Sequencing Vendors and Subcontractors
Vendor coordination is another critical piece of the puzzle for small businesses. Relying on the cheapest or fastest vendor can lead to system-wide delays. For instance, a low-cost electrician who arrives late might derail the schedules of the plumber, HVAC installer, and final inspection, turning a small win into a larger operational headache.
Most problems stem from system-wide issues rather than individual vendor failures. Subcontractors who don’t understand the overall goal - like on-time delivery and minimized total costs - can unintentionally disrupt the flow[7]. The solution lies in building long-term partnerships with vendors who understand how their role affects subsequent stages. Mapping the value stream helps pinpoint where delays occur between vendors. Instead of focusing on keeping every subcontractor busy, businesses should aim to optimize overall flow[2][3]. Improvements made to non-bottleneck vendors often just shift the problem elsewhere, piling up work at the true constraint[2].
How to Catch Sub-Optimization Early
Warning Signs to Monitor
Spotting sub-optimization early can save businesses from significant headaches later. One of the clearest red flags is the "green dashboard" trap. This happens when local metrics - like team velocity or departmental utilization - look great, but overall lead times either stagnate or worsen. For example, if every team reports success but customer deliveries keep slowing, you’re witnessing sub-optimization in action[3].
Another tricky indicator is the utilization paradox. It’s easy to assume that running every team at 100% capacity means peak efficiency. But in reality, this often signals a brewing problem. Overloading non-bottleneck areas creates unnecessary work that clogs up the system's actual constraints. Imagine a small business where every worker is busy, but projects still drag. The bottleneck - maybe a specialized installer or a slow permit approval process - gets overwhelmed with coordination requests, causing delays[2].
Then there’s integration chaos, which happens when local optimizations fail to mesh with the broader system. For small and medium-sized businesses (SMBs), this might look like subcontractors finishing their tasks on time, only for sequencing issues to result in rework, delays, or failed inspections. These misalignments are a hallmark of sub-optimization, where local wins come at the expense of overall system flow[3][6].
Identifying these warning signs is critical, but it’s only the first step. The real challenge lies in addressing them before they spiral out of control.
Using Feedback Loops to Surface Problems
Once you’ve spotted potential issues, feedback loops become your best tool for intervention. These loops help uncover hidden problems early, allowing for quicker fixes. One of the most effective methods is tracking flow metrics instead of activity metrics. For instance, instead of focusing on how busy teams are, track how long work takes to move through the system. Metrics like lead time (the total time from request to delivery) and cycle time (the active time spent working) can reveal whether local improvements are helping or hurting overall flow[3].
Another powerful tool is value stream mapping. This approach lets you visualize every step in your process, from the initial request to final delivery. By doing this, you can pinpoint exactly where work gets stuck. For example, a remodeling contractor might find that delays don’t occur during installation but during the handoff from sales to scheduling - or while waiting for vendor quotes that could be batched more efficiently[3][6].
Limiting WIP (work in progress) is another way to expose bottlenecks. When teams are restricted from starting new tasks until current ones move forward, they’re forced to address handoff issues and sequencing problems. This approach naturally highlights which "local improvements" are causing friction elsewhere[3].
Finally, don’t overlook incentive alignment. Misaligned goals - like rewarding sales for orders placed while penalizing delivery for delays - can sabotage system performance. Regularly reviewing how teams are measured and rewarded can reveal these structural conflicts before they cause serious damage. As experts like Deming and Goldratt have stressed, understanding the entire system is key to avoiding local optimizations that harm overall performance.
"For optimizing the whole, we must sub-optimize the parts."W. Edwards Deming[4]
Ultimately, feedback loops aren’t just about collecting data - they’re about ensuring every team understands how their actions impact the health of the entire system. This shared understanding is critical for keeping sub-optimization in check.
Conclusion
What Enterprises and SMBs Should Remember
Improving performance in one area doesn't always lead to better overall outcomes. In fact, focusing too much on local metrics can backfire, creating bottlenecks, increasing coordination challenges, and slowing down overall delivery. Deming's famous observation - that optimizing individual parts can hurt the whole - still holds true today [4]. Sometimes, teams might need to work at less than full capacity to keep the entire system running smoothly. This requires shifting priorities from local metrics like task completion rates or utilization to broader goals, such as reducing end-to-end lead times and delivering greater value to customers.
The numbers tell a compelling story. Roughly 94% of organizational issues stem from systemic problems - things like processes, tools, and resource allocation - not individual shortcomings [7]. Focusing solely on individual performance misses the bigger picture. It's management's responsibility to refine the system itself by aligning incentives, breaking down inter-team barriers, and helping everyone see how their efforts contribute to the organization's overall success.
This approach is just as vital for SMB studios. When smaller organizations chase quick wins at the local level, they often end up slowing down operations as a whole. By reorienting efforts toward system-wide outcomes, businesses of all sizes can achieve sustainable, long-term improvements.
Why System Optimization Wins Long-Term
When organizations take a system-wide approach, the benefits ripple across the entire operation. Companies that focus on overall system health consistently outperform those that chase isolated gains. A great example is Tesla, which thrived during the 2020s supply chain crises thanks to its well-planned vertical integration [7]. On the flip side, ignoring system-level thinking can be disastrous. The General Motors ignition switch scandal is a stark reminder of what happens when cost-cutting in one area undermines safety and system integrity. The fallout included over 100 deaths, massive legal fees, and lasting damage to the company’s reputation [1].
As systems become more interconnected, the winners will be those who prioritize smooth workflows over busywork, transparency over silos, and shared goals over narrow departmental targets. Whether you're running a large enterprise or a small studio, success hinges on designing systems with intentionality. A well-thought-out system fosters collaboration, reduces inefficiencies, and ensures the entire organization moves in sync - because when the system works, so does everything else.
FAQs
How can I tell if we’re sub-optimizing?
When observing your system, keep an eye out for situations where localized improvements fail to boost overall performance. For instance, a team might work faster, yet customer delivery times still stretch out. Or, efficiency gains could coincide with growing work queues. Another red flag is when departments prioritize their own metrics - like utilization rates - over the system's overall flow.
Other symptoms include rework, delays further down the line, or accumulating tasks that add no real value. To identify these issues, shift your focus to system-wide metrics such as throughput and flow, which provide a clearer picture of how well the entire process is functioning.
What system-level metrics should we track first?
To ensure your system runs smoothly and avoids inefficiencies, it’s important to track metrics that measure overall performance, not just individual parts. Some key metrics to focus on include:
Throughput: This measures the value delivered over a period of time.
Flow efficiency: Tracks how effectively work moves through the system.
Cycle times: Measures how long it takes to complete a process from start to finish.
For small and medium-sized businesses (SMBs), this might mean monitoring the total time it takes from when a customer first inquires to when the project is completed. These metrics help identify bottlenecks, align different parts of the business, and ensure that improvements benefit the entire operation - not just isolated areas.
Who should own end-to-end flow in our org?
To truly optimize a system for delivering value, the owner or leadership team needs to take charge of the entire process from start to finish. By focusing on the end-to-end flow, they ensure the system isn't just working efficiently in isolated areas but is aligned toward achieving shared goals. This approach avoids fragmented efforts that can undermine overall performance and keeps everyone working toward common outcomes.
