Before adding capacity, find out where the work waits.
Consider an illustrative proposal. Writing it takes three hours. Getting permission to send it takes four days. The team is capable, the prospect is interested, and the company has a template. Yet the work sits because one person must confirm the price, resolve a scope question, and approve the promise.
Another writer might prepare more proposals. Another tool might produce them faster. Neither change necessarily shortens the wait for a decision.
Growth can stall for many reasons: weaker demand, rising costs, delivery limits, or an offer that no longer fits the market. An internal queue is one possibility worth investigating. A revenue plateau alone cannot tell a leader which problem the business has.
Centralization often begins sensibly. The owner knows the customers, protects the cash, and understands what the company can safely promise. A difficult scope, unusual commercial term, or sensitive client issue reaches that desk because the decision warrants experience.
Over time, more work follows the same path. A standard price needs confirmation because nobody has documented the boundary. A routine exception needs approval because the previous answer lives in a conversation. An employee escalates because asking feels safer than making a decision without clear authority.
The company may describe this as a staffing problem. People are busy, customers are waiting, and the owner is overwhelmed. But the visible workload includes more than tasks. It includes work waiting for information, permission, or a judgment that has no other reliable route.
A queue can form even when the person making decisions is fast. If requests arrive faster than that person can resolve them, pending work accumulates. Interruptions and incomplete submissions add to the burden. More leads or employees may increase those requests before the company has improved its ability to process them.
The practical question is which decisions truly require senior judgment, and which reach that level because the organization has never built another dependable path.
Research provides reasons to examine the operating system, although it cannot diagnose an individual company's bottleneck.
The U.S. Census Bureau's 2021 Management and Organizational Practices Survey collected more than 36,000 responses from manufacturing establishments. Larger establishments generally reported more structured management practices: practices that were more explicit, formal, frequent, or specific. This is an association within manufacturing, not evidence that formalization caused growth or that every business needs the same procedures. U.S. Census Bureau
A management field experiment in large Indian textile firms offers a narrower causal finding. Randomly selected treatment plants received intensive support in adopting management practices. The published study reported a 17% productivity increase in the first year through improved quality and efficiency and reduced inventory. Its setting and intervention differ substantially from those of an established American service business. It supports the value of operating practices in that setting, rather than promising a comparable return elsewhere. Quarterly Journal of Economics
The management implication here is an inference: asking someone to make a decision is insufficient if the relevant facts, limits, and consequences remain elsewhere. A manager may have a new responsibility and still need the owner to explain what an acceptable answer looks like.
For the hypothetical proposal, useful delegation might include an approved scope, a margin boundary, a standard set of terms, and a clear condition for escalation. That gives the team a basis for judgment. It also preserves senior attention for decisions outside those boundaries.
Start with one consequential process. Track when work arrives, when it is ready for a decision, when the decision occurs, and when the customer receives the result. Separate active work from waiting and rework. Include the return trips caused by missing information or ambiguous instructions.
In the opening example, three hours of preparation and four days awaiting approval are illustrative, not a benchmark. The comparison is useful because it directs attention to different remedies. Writing capacity addresses production time. Clearer decision rights or better inputs may address waiting. Some delays may be deliberate because a decision warrants careful review.
A simple timestamp record can reveal whether the longest wait is approval, missing customer information, scheduling, or coordination between teams. Ask the people doing the work what prevents the next step. Their answer often explains more than a total cycle-time number.
Do not measure speed alone. A shorter approval cycle that produces poor scopes, lower margins, or delivery failures has moved the problem. Track quality and commercial consequences beside elapsed time so the company can judge whether the process is actually improving.
Once the wait is understood, redesign the narrowest useful part of the process. Specify who can decide, what information they need, the boundaries within which they can act, and the conditions that require escalation. Make the answer accessible where the work occurs.
Then examine a small run of real cases. Did more work move without an unnecessary senior intervention? Were decisions sound? Did exceptions expose a missing rule, or did they genuinely require experience? Revise the boundary using those observations.
The founder may appropriately keep a decision involving unusual risk, strategic commitment, or a major customer. Reducing routine escalation can make that involvement more effective by giving it the time it deserves.
For FourStage, operating capacity includes the ability to move a sound decision through the company. Before recommending another hire or platform, we want to understand whether the work lacks hands, information, authority, or a dependable sequence.
A plateau may still originate in the market. Measuring where work waits gives leaders evidence about what the company can improve internally—and a better basis for deciding what to add next.
Reader question: Where does work wait longest in your business, and what information, decision, or authority would allow the next step?
Examples and process recommendations are illustrative FourStage analysis. Neither source establishes that approval queues explain a particular revenue plateau.
