Most business owners spend years trying to create growth. Then growth arrives, and it rarely waits politely while the business gets ready.
It may arrive as more enquiries, a larger contract, a new location or a steady increase in customer demand. At first, the change feels encouraging. The team is busy, sales are moving and the opportunity the business has been working toward appears to be taking shape.
Then other signs begin to appear. Customers follow up more often. Managers spend more time coordinating everyday work. Routine decisions reach the owner. Employees put in more effort, but completed work does not increase at the same pace. Revenue may still be growing, yet the business feels harder to run.
That tension sits at the centre of growth readiness. Growth describes the increase in demand or activity. Readiness describes the business’s ability to absorb that increase without losing control, quality or profitability.
The first answer might be “the team,” “cash flow” or “my own time.” Those answers are useful starting points, although each needs to be explored. Which work would slow down? Where would information be missing? Which decisions would begin to queue? Would the business be able to keep the same promise to customers?
Larry Greiner’s work on organizational growth helps explain why this question matters. Practices that help a company succeed at one stage can become sources of pressure at the next. Direct owner involvement may give a young business speed and consistency. As volume rises, the same concentration of decisions can slow routine work and limit the people who are expected to manage it.
The business has not necessarily become less capable. The amount and frequency of work have changed, while the way the company coordinates that work may still reflect an earlier stage.
The Growth Readiness Framework
Growth readiness becomes easier to assess when the work follows a clear sequence. Acumen’s framework uses four actions: Scan, Locate, Diagnose and Prioritize.
The order matters. A broad scan prevents leadership from defining the issue too narrowly. Following the work replaces general impressions with specific observations. Diagnosis separates the visible symptom from its cause. Prioritization turns the analysis into a manageable decision.
Skipping one of these steps creates familiar problems. A business may buy software before it understands the workflow, hire into a process that still creates rework or launch several improvement projects without deciding which constraint deserves attention first.
Let us take each stage in turn.
Step 1Scan the Business
The scan begins with a broad question: What would need to be ready for the business to handle more work well?
When one employee is overwhelmed or a delivery is late, attention naturally moves toward the place where the pressure is visible. The cause may sit somewhere else. An overloaded coordinator may be correcting information collected during sales. A late project may have spent several days waiting for approval. A cash shortage may come from the payment timing of a profitable new contract.
Starting with a wider view helps leadership see those connections. The scan covers five readiness areas: people, processes, operational capacity, systems and financial resources.
These areas are separated for the purpose of review. In practice, they affect one another constantly. The value of the scan comes from noticing those relationships before the business commits to an explanation.
People
Small businesses often grow because people are flexible. The owner fills gaps, experienced employees handle unusual situations and job boundaries remain informal. That flexibility can serve the business well for a long time.
Pressure appears when responsibility grows faster than clarity. A manager may be expected to deliver a result while still needing the owner to approve pricing, staffing changes, customer exceptions and scheduling decisions. The manager carries accountability, but the authority needed to keep the work moving remains elsewhere.
The scan should examine what each role owns, which decisions employees can make and where escalation is genuinely required. It should also consider whether people have the information and capability to use that authority well. Moving a decision without providing context or support simply moves the risk.
A useful question is: Which routine issues still reach senior people because their judgment is essential, and which reach them because nobody has made the decision boundary clear?
Processes
Processes usually develop through experience rather than formal design. One person keeps a spreadsheet. Someone else remembers to send a reminder. An experienced employee knows what must be checked before work begins. At a manageable volume, conversation and memory bridge the gaps.
Growth increases the number of times those gaps must be bridged. More customer requests create more handoffs. Missing information travels further before someone notices it. Employees spend more time checking, correcting and following up. A workaround that took ten minutes once a week may now appear several times a day.
During the scan, leadership should ask whether important recurring work has a clear beginning, owner and expected result. What information needs to move with the work? What does a complete handoff look like? How does the next person know they can begin?
The goal at this stage is to identify exposure, not to start writing procedures for everything. Documentation becomes useful after the business understands the work it wants people to repeat.
Operational Capacity
Capacity includes more than employee headcount. It includes equipment, space, specialized knowledge, management attention and the speed at which decisions move through the business. Two teams with the same number of people can produce very different results because their work is organized differently.
Andrew Grove’s distinction between activity and output is helpful here. A team can remain busy throughout the day while completed customer work changes very little. Time may be absorbed by searching for information, correcting earlier work or waiting for decisions. The workload is real, but some of it does not create additional output.
The scan should therefore look at incoming demand and completed work together. Is backlog growing? Does overtime appear regularly? Is one skill, machine or approval point limiting the pace of the entire process? Does the business have enough management attention to coordinate the additional work?
These questions do not assume that hiring is unnecessary. They help the company understand what kind of capacity it needs and whether a new employee would be able to use their time productively.
Systems
Systems include software, spreadsheets, shared files and the routines through which information becomes available. As a business grows, personal memory and disconnected records give managers a weaker view of what is happening.
Employees may maintain different versions of the same customer information. Project status may live in inboxes or private notes. Managers may need to ask several people before they can understand the workload. These conditions slow decisions and make it harder to see where work is collecting.
The scan should ask what information people need at the point of action. Can they see what has arrived, who owns the next step and what is waiting? Can a manager understand the state of delivery without interrupting several employees for updates?
This creates a clearer basis for later technology decisions. The company can define what the system needs to support before it evaluates new platforms or integrations.
Financial Resources
Growth often requires spending before the financial return arrives. Payroll, inventory, training, equipment and subcontractor costs may need to be funded before the customer pays. Several projects starting together can widen that timing gap quickly.
Revenue and available cash need to be considered separately. BDC’s working capital guidance notes that growing sales can increase the cash tied up in receivables and inventory. A profitable contract can therefore place short-term pressure on the business while it is being delivered.
The scan should examine when the company will incur costs, when it can invoice and how long customers normally take to pay. Deposits, milestone billing, supplier terms and financing may all affect whether the company can support the growth it intends to accept.
What the Scan Should Produce
The scan should leave leadership with a short set of plausible areas to examine, not a long list of conclusions. At this point, the business may see that owner approvals, incomplete intake and cash timing deserve attention. It should resist declaring any one of them the root cause until it follows the work.
The scan gives the company a map. The next stage shows where pressure is actually appearing on that map.
Step 2Locate Where Pressure Appears
Locate moves the review from a broad organizational view into the work itself. Choose a recent customer request and trace what happened from beginning to end.
Use a real example. It could be a proposal, an order, a patient booking, a service call or a project change. Speak with the people who handled it. Reconstruct the emails, decisions, handoffs, systems and delays involved.
The official process may say that sales sends confirmed work to operations. The actual process may include missing information, a separate spreadsheet, an approval and an experienced employee quietly correcting the file before anyone else sees it. Both versions matter, but only the second explains how the work currently moves.
John Shook’s work on A3 problem solving emphasizes understanding current conditions where the work takes place. That principle is especially useful here. General statements such as “communication is poor” become more informative when leadership can point to the exact exchange that broke down and describe its effect on the customer or the next employee.
Four Signals That Help You Follow the Work
Wait, return, repeat and depend are simple observation prompts within the Locate stage. They do not provide the diagnosis by themselves. They help the business notice where pressure is visible and identify what deserves a closer look.
Wait
A proposal may require forty minutes of review and still sit for three days. A purchase order may be ready except for one specification. A customer request may remain in a shared inbox because several people can see it and no one clearly owns the next step.
Measure the time spent working separately from the time spent waiting. The difference often reveals that employees complete their individual tasks quickly while the customer experiences the combined queues between them.
Return
Work returns when a handoff does not give the next person what they need. Sales may pass a project to delivery without a confirmed requirement. An intake form may omit information required for scheduling. The problem becomes visible in the receiving role, even though it began earlier.
Look at what a complete handoff should contain and where the business can verify it. Detecting a missing requirement before additional work begins usually costs less than repairing the result near the end.
Repeat
Repeated work often looks too small to investigate. An employee copies customer details into several systems. A supervisor answers the same policy question every week. A proposal is recreated because the previous version cannot be found.
Volume changes the significance. Ten minutes repeated thirty times a month consumes five hours. When the repetition interrupts several employees, its effect extends beyond the minutes recorded.
Depend
Dependence appears when the process contains an invisible step shaped like a particular person. Employees may save questions for the owner. Customers may insist on speaking with one experienced team member. A manager may carry responsibility for delivery while waiting for somebody else to approve routine changes.
The dependency may involve judgment, system access, a supplier relationship or knowledge that has never been shared. Notice what slows down when that person is away or focused on another priority. The delays often reveal how the process actually works.
Locate the Capacity Constraint
The four signals help identify where work loses momentum. The next question is what the pattern is doing to capacity.
Imagine a ten-step process. Nine steps can handle twenty requests a day, while one approval point can handle eight. As demand rises, work collects around that point. The surrounding employees become busier, but the business still completes work at the pace of the limiting step.
This is why a busy team may still contain recoverable capacity. People can be fully occupied by chasing information, fixing handoffs and managing queues. Removing those conditions may create room immediately. If the evidence still shows that demand exceeds sustainable output, the business has a much stronger case for adding staff or equipment.
Pay Particular Attention to Owner and Key-Person Dependency
Owner dependency often develops for good reasons. The owner understands the history, knows the customers and can resolve an exception quickly. In the earlier stages of a business, direct access to that judgment may improve speed and quality.
As the company grows, small questions arrive more frequently. The owner’s attention becomes fragmented, employees learn to wait and managers have fewer opportunities to exercise judgment. Routine delivery also becomes vulnerable whenever the owner is unavailable.
Paul Rogers and Marcia Blenko’s work on decision roles is useful when examining this pattern. It distinguishes the people who provide input or make a recommendation from the person who holds the decision and the people responsible for carrying it out. The distinction can reveal approvals that exist through habit rather than necessity.
At the Locate stage, the task is still observational. Record which decisions reach the owner, what information accompanies them and what happens while the team waits. The next stage will determine why that pattern continues and what response fits it.
Consider a professional services firm that believes it needs another coordinator. Enquiries are rising, proposals are slower and the current coordinator is working overtime.
Tracing recent enquiries shows that some requests wait for the owner to confirm pricing. Files return from delivery because the scope is incomplete. Customer details are copied across email, a spreadsheet and the project system. Non-standard terms reach one senior employee who knows the history.
These observations show where time is being consumed. They do not yet prove that hiring is unnecessary or that one specific process change will solve the problem. That conclusion requires diagnosis.
Diagnose the Cause
Diagnosis begins after the business has a broad view of readiness and a concrete picture of how work moves. The aim is to explain what condition keeps producing the observed pressure.
Suppose the team is working overtime and projects are late. Demand may genuinely exceed sustainable capacity. Incomplete intake may be creating rework. Routine approvals may be sitting with the owner. Managers may be changing priorities faster than employees can finish. A specialized skill may be missing.
Each explanation can produce the same visible symptom. Each leads to a different decision.
| What the business is experiencing | What may be contributing | What to examine before acting |
|---|---|---|
| “The team is overloaded.” | Sustained demand, rework, waiting, unclear ownership, interruptions or excessive approvals | Separate time spent completing customer work from time spent searching, correcting and waiting. |
| “We need better software.” | Fragmented information, duplicate entry, unclear workflow or limited visibility | Define the work, information and decision that the system needs to support. |
| “We need SOPs.” | Inconsistent execution, difficult training, recurring errors or an unstable process | Confirm that the intended workflow is understood and workable before documenting it. |
| “The owner needs to delegate.” | Unclear authority, missing information, limited capability or genuine high-risk decisions | Identify which decisions are routine, what boundaries apply and what support the team needs. |
| “We need more sales.” | A real demand gap, weak conversion, poor retention, underpricing or delivery constraints | Confirm whether the business can deliver additional demand reliably and profitably. |
Move From a Broad Complaint to a Specific Condition
Statements such as “communication needs to improve” or “the process is inefficient” identify a concern, but they do not give the business enough direction to act.
A stronger statement identifies where the issue occurs, what happens and why it matters. For example: “Project information is not confirmed before scheduling, so operations must contact sales and the customer after the start date has been promised.”
That description gives leadership something it can verify. It can examine recent projects, identify which information was missing and see whether the additional contact affected delivery time or customer expectations.
Separate the Observation, the Explanation and the Proposed Solution
These three elements often become mixed together in everyday conversation. “The team is overloaded” is an observation. “We do not have enough people” is one possible explanation. “We should hire another coordinator” is a proposed solution.
The explanation may prove correct, but the observation alone does not establish it. The same overloaded team may be spending part of each day correcting incomplete work, waiting for decisions or responding to priorities that change before earlier work is completed.
Keeping the three elements separate improves the discussion. Employees can agree on what they are experiencing without having to agree immediately on the cause. Leadership can compare several plausible explanations before the organization becomes attached to one response.
Test the Explanation Before Funding the Solution
Diagnosis should slow the decision down only long enough to avoid an expensive commitment to the wrong response.
If the company hired another employee, would completed output rise? The answer may be yes when demand exceeds the team’s sustainable capacity. If every project still waits for the same owner approval, the new employee may join the queue.
If the company introduced new software, would it support a clearer flow of work? A platform can reduce duplicate entry and improve visibility. It cannot decide what information a handoff requires or who has authority to approve an exception unless the business first defines those requirements.
The same logic applies to marketing. More demand can support growth when the business has room to deliver it. When operations are already strained, a successful campaign sends more work toward the existing constraint.
For each suspected cause, ask: If this condition changed, what result should improve? The answer might involve turnaround time, backlog, rework, overtime, customer follow-ups or routine interruptions reaching the owner.
Then look for evidence that could disprove the explanation. If incomplete intake appears to cause delays, examine projects with complete intake. If they experience the same delays, another factor may be more important. This discipline keeps the diagnosis open long enough to learn from the work rather than defend the first theory.
The evidence should match the decision. A reversible process change may need several recent examples and a short test. A major hiring, restructuring or technology commitment deserves a broader view of demand, workload and cost. Diagnosis should be proportionate. The aim is sufficient confidence for the decision in front of the business.
Recognize When Several Causes Interact
Operational problems do not always have one isolated cause. Incomplete information may create extra approvals because managers do not trust what they receive. Those approvals may then increase owner dependency and make the team appear short-staffed.
The diagnosis should explain the chain clearly enough to identify a practical intervention. It does not need to produce a perfect model of the entire business. Leadership needs enough confidence to choose a useful next step and know what result to monitor.
The firm’s first observation was that proposals were slow and the coordinator was working overtime. Following the work revealed pricing waits, incomplete scope information and duplicate entry.
Diagnosis now asks which conditions account for the delay. A review of recent files may show that standard proposals also wait because nobody has authority to approve them within an agreed range. It may show that incomplete scope causes delivery teams to return files after scheduling. Duplicate entry may consume time, although it may account for less delay than the approval queue.
The resulting explanation can include more than one cause: routine pricing decisions remain with the owner, and the intake handoff does not consistently provide delivery with a usable scope. The firm should still measure incoming demand and sustainable output before concluding that it has no staffing need.
Prioritize the Next Improvement
A serious readiness review usually identifies several valid improvements. Roles may need clarification. One handoff may need redesign. Managers may need better information. Cash timing may require attention. The company may also have a genuine staffing need.
Attempting all of these at once adds another layer of work to a team that already feels pressure. Prioritization narrows the decision using three considerations: impact, urgency and feasibility.
Impact
Impact keeps the discussion connected to a meaningful business result. An issue that quietly affects every customer may deserve attention before a dramatic exception that appears twice a year.
Consider the scope of the effect. Does the issue delay one role or the whole customer journey? Does it create a few minutes of inconvenience or repeated rework across several employees? Does it affect service quality, margin, customer trust or the owner’s ability to focus on the business?
Urgency
Urgency concerns the consequence of waiting. A weak handoff may become urgent because a large contract will double the number of times it occurs. A cash timing issue may need attention before the company accepts work that requires substantial upfront spending. A key-person dependency may carry continuity risk when nobody else can perform a critical task.
The loudest request of the day does not automatically define urgency. The business consequence does.
Feasibility
Feasibility asks whether the organization can carry the change through. A large system implementation may have considerable potential and still be unrealistic while the team lacks process ownership, clean information or implementation capacity.
A smaller change may remove enough pressure to make the larger investment possible. Clarifying a recurring decision can reduce waiting quickly. Improving intake can give a later software project cleaner requirements. Revising deposits or invoicing can create room to fund training or hiring.
Make the Trade-Off Explicit
Prioritization means choosing what to address now and what will remain open. Michael Porter’s work on strategy emphasizes the role of trade-offs and fit. The same discipline is useful here. A business cannot treat every improvement as the first priority, and one decision may change the conditions for the next.
Leadership should be able to explain why the chosen issue matters, why it is suitable to address now and what evidence would cause another issue to move ahead of it.
The preferred option should also have a credible alternative. If management chooses to improve intake before hiring, it should still state what demand or output evidence would trigger the hiring decision. This prevents a focused process improvement from becoming an excuse to avoid a real capacity investment.
Compare a Small Number of Realistic Options
Prioritization works better when leadership compares two or three credible responses. A list containing every possible improvement creates noise. A discussion built around one favourite solution creates false certainty.
For each option, consider what pressure it addresses, what must already be true for it to work and what new effort it creates. Hiring adds capacity after recruitment, onboarding and effective allocation. Software may improve visibility after the business defines the information and workflow it needs. A process change may recover time quickly, while leaving a genuine resource limit untouched.
This comparison makes the trade-off concrete. The team can see what each option changes and what it leaves unresolved.
Sequence Improvements That Depend on One Another
Some improvements create the conditions for others. Clarifying ownership can make training more effective. Improving intake can give a software implementation cleaner requirements. Adjusting deposits or billing can create the financial room needed for hiring.
Sequence does not always mean delaying the larger decision. A business may need to recruit while it improves a handoff because demand already exceeds capacity. In that case, leadership should make both parts explicit: what capacity the new role will add and what operational change will help the person use that capacity well.
Define What Improvement Will Look Like
Choose one or two measures that reflect the result the business expects. If the change concerns a handoff, track how often work arrives complete and how many files return. If it concerns decision authority, track turnaround time and the number of routine escalations. If it concerns capacity, compare incoming work, completed output, backlog and overtime.
Set a review date and name an owner for the improvement. Observe what changed before launching another initiative. The result will either support the diagnosis or show that the business needs to revisit it.
The professional services firm could compare three responses: hire another coordinator, improve intake and routine pricing authority, or replace the current project system.
Incomplete intake and pricing waits affect many files, so their impact is broad. The business can test clearer intake requirements and an approved pricing range quickly, which makes the change feasible. A complete system replacement would require more time and clearer requirements. Hiring remains a credible option if incoming demand and backlog stay above the team’s sustainable output after the avoidable delays are reduced.
The firm can therefore begin with the bounded process and decision changes, measure proposal turnaround and returned files, and continue monitoring workload. That choice does not assume that process improvement will remove the staffing need. It creates better evidence for the hiring decision and gives a future employee a more workable operating environment.
Applying the Framework Over 30 Days
A business does not need a company-wide transformation to begin. One month of focused work can create a much clearer starting point.
- Scan the five readiness areas. Ask the owner, managers and employees where a 25% increase in demand would create difficulty. Compare their answers and record the areas that deserve closer examination.
- Locate pressure in recent work. Trace two or three customer requests through the actual process. Record the handoffs, decisions, systems, work time and waiting time. Use wait, return, repeat and depend as observation prompts.
- Diagnose the likely cause. Develop a specific explanation and test it with the people doing the work, recent examples and available data. Identify what result should change if the explanation is correct.
- Prioritize one improvement. Compare the candidate issues using impact, urgency and feasibility. Assign an owner, choose a measure and set a review date.
The first improvement might be a clearer handoff, a decision boundary, a staffing change, better customer intake, a collection adjustment or a technology investment. The response should follow the evidence gathered through the framework.
Before You Add More Pressure
No business needs to fix every weakness before it grows. Leadership needs enough clarity to answer four questions:
- Scan: Where could additional demand expose the business?
- Locate: Where is pressure appearing in the actual flow of work?
- Diagnose: What condition keeps producing that pressure?
- Prioritize: Which improvement matters most and can realistically be implemented now?
Growth readiness gives owners and management teams a way to prepare before the next opportunity adds more pressure. It connects a broad view of the business with what employees and customers experience every day. It also helps leadership invest in the right improvement, in the right order, for a reason the organization can explain.
Return to the opening question: If demand increased by 25% next month, where would the business feel it first? A useful answer should identify more than the department that would become busy. It should show where the work would struggle, what is likely to cause the pressure and what the business should strengthen first.
When the Symptoms Are Clear but the Cause Is Not
If growth is making the business harder to manage, several improvements are competing for attention, or leadership is debating whether to hire, automate, document or restructure, a focused diagnostic may provide the clearest starting point.
Acumen’s Business Scaling & Operations Diagnostic examines what is limiting the business before implementation decisions are made. For broader growth decisions, see our Growth Management consulting service.
Sources
Greiner, Larry E. Evolution and Revolution as Organizations Grow. Harvard Business Review. How management practices and organizational needs change as a business grows.
Grove, Andrew S. High Output Management. Activity, output, limiting steps and the design of productive work.
Shook, John. Managing to Learn: Using the A3 Management Process. Observing current conditions, framing problems and testing explanations.
Rogers, Paul, and Marcia W. Blenko. Who Has the D? How Clear Decision Roles Enhance Organizational Performance. Harvard Business Review. Decision roles, accountability and execution.
Porter, Michael E. What Is Strategy? Harvard Business Review. Strategic choices, trade-offs and fit across business activities.
Business Development Bank of Canada. How Working Capital Helps You to Keep Growing. Working-capital requirements associated with inventory, receivables and growth.