|
Today's Executive Briefing When the same workaround appears againYou see the pattern when the same approval returns because the assigned role lacks a required decision right, when a handoff arrives before the figures needed to complete it, or when a recurring exception requires coordination the documented process never assigned. You reconstruct the context, secure the approval, or connect the people involved. The activity continues. The same need returns. That recurrence is evidence. More comparison is required before you choose a change. A capacity shortage and an operating-design mismatch can create the same visible queue. A capacity shortage exists when the resources at the constrained step cannot meet current demand at the required speed and quality, even though the ordinary route supplies the necessary authority, information, and process support. Volume and variability both matter. More time, qualified skill, system throughput, or another relevant resource at that step should increase throughput or reduce waiting without changing the route. An operating-design mismatch exists when the route lacks a decision right, information input, or recurring dependency the activity requires. An implementation failure occurs when the route supplies that element on paper, but practice does not. Either finding supports a design or mixed classification only when the gap contributes to the workaround's recurrence. If it does, adding capacity alone leaves the workaround in place. Another person, more time, or a faster system still meets the same missing approval, late input, or unassigned handoff. Structured management practices varied substantially across plants owned by the same firm: roughly 40 percent of the observed variation occurred within firms in a sample of about 32,000 U.S. manufacturing plants. (National Bureau of Economic Research, “What Drives Differences in Management?,” 2017) The sample covers manufacturing plants, and the analysis is observational. It cannot diagnose your business or establish that company growth caused a specific mismatch. It demonstrates that meaningful differences in management practices can exist within the same firm. A company-wide process description therefore cannot establish that the operating route works the same way across teams or locations. Examine how the relevant approvals, information, and handoffs function in practice. Recurrence alone does not settle the diagnosis. Treat volume as the primary capacity finding when the ordinary route supplies the authority, information, and process support required for the work and the remaining constraint is insufficient capacity at the constrained step. If a material route defect also contributes to the recurring workaround, record a mixed finding. If that connection remains unclear, keep the diagnosis unresolved. Use the recurrence as your starting point. Record what changed in the demand, what the ordinary route was expected to supply, what you did outside that route, and what consequence followed. Then test one bounded change. Use that evidence to choose additional capacity, a different route, both, or another observation cycle. Recurring Workaround RecordTime: 10–15 minutes Choose one workaround that appeared at least twice during the past 30 days. Complete one record.
Diagnostic readSelect one:
Run the test through one operating cycle as an initial learning step. Record whether you still need the workaround at the same point, need it elsewhere, or no longer need it during that cycle. Do not treat one cycle as proof of a durable fix. Scope limit: Use one record as evidence about one recurring pattern. Do not apply its result to the entire operating model. Immediate action: Use the evidence from this cycle to decide whether the next move is additional capacity, a change to the operating route, both, or another observation cycle. © 2026 Lauren Carter. This instrument is proprietary. For individual diagnostic use only. Reproduction, adaptation, or redistribution in any form requires prior written permission from Lauren Carter. Lauren If you're forwarding this—you already know who needs it. Trust that. |
A twice-weekly diagnostic on the structural conditions underneath how organizations actually perform. Each issue names a mechanism most strategy conversations skip, then gives you a tool to test it in your own operation. Built for executives, founders, and operators who already suspect the problem is architectural.