A business does not become ready for its next stage of growth simply by producing a strategy. Growth readiness is visible in everyday operation: important decisions happen at the right level, work is handed over reliably, people can take leave without bringing essential activities to a halt, and leaders can identify problems early enough to respond.
For a smaller organisation, the temptation is to attempt a major transformation. A shorter, deliberately selective improvement programme is often a better starting point. Ninety days will not resolve every issue, but it is enough time to establish clearer ownership, test a few changes and decide what deserves further investment.
Begin with a candid baseline
The starting point is a small number of observable questions. Which services or customer commitments matter most? Who is accountable for them? Where are decisions delayed? Which tasks depend on one person? How dependable is the management information? What has been tested rather than merely assumed?
The answers need not produce a sophisticated maturity score. Indeed, a precise-looking number can give a misleading impression if it rests on guesswork. A simple four- or five-level scale can support discussion, provided the evidence and uncertainty are recorded alongside it.
The RJA Growth Readiness Toolkit is designed for this purpose. Its scores are prompts for prioritisation, not an externally validated benchmark or a guarantee of future performance. A low score should start a conversation about what matters, not an automatic purchase or reorganisation.
Days 1–30: understand and choose
The first month should produce clarity, not a large collection of documents. Select a few essential business outcomes and trace the work behind them. Identify critical dependencies, recurring exceptions and decisions that regularly need escalation.
Speak to the people who perform the work as well as those responsible for it. Senior managers may have a reasonable description of the intended process; colleagues often know where work actually waits or where information is missing.
At the end of the period, agree no more than three improvement priorities. Each should describe a specific outcome, why it matters, a responsible person and some evidence that would demonstrate improvement. Avoid tackling so many weaknesses that normal business activity is displaced.
Days 31–60: change the smallest useful things
The second month is about putting proportionate arrangements into practice. A founder may delegate three recurring decisions within clear limits. An operations lead may create a reliable handover checklist. Finance and sales may agree a common definition of an accepted order. A management team may introduce one weekly review of material exceptions.
The important point is that each change addresses an observed problem. A new management system, role or approval layer may be justified, but should be assessed against the simpler options first. The OECD’s 2026 D4SME survey describes skills and cost barriers reported by participating SMEs in relation to digital adoption. [2]
For an illustrative services company, a recurring delay in customer onboarding might be improved by assigning one owner to the entire handover, establishing minimum information requirements and checking completion before scheduling work. That is a modest intervention, but it creates a basis for measuring whether the delay has reduced.
Days 61–90: test and decide what remains
The third month should test whether the changes are used and effective. Review a sample of recent decisions, actual handovers and unresolved exceptions. Compare results with the baseline, whilst recognising that small volumes and changes in demand can complicate interpretation.
A useful result is not always a dramatic improvement in a metric. It may be that responsibilities are now explicit, an absence can be covered, or management has discovered a dependency that was previously hidden. Record those outcomes clearly and distinguish observed evidence from expectation.
Some actions will remain incomplete. That is not necessarily a failure of the exercise. The programme should produce a realistic next-stage roadmap, including larger investments or structural changes that require more time, budget or specialist input.
A practical set of review measures
I would be cautious about standardising the same KPIs for every business. A supplier-dependent retailer, a professional services company and a software product team face different constraints. However, a small set of questions can travel across sectors.
Are important customer commitments being met? How many decisions are unnecessarily escalated? Are material exceptions resolved within an agreed period? Can critical tasks be performed when a key colleague is absent? Is management information available when needed, and can its accuracy be explained?
Where a numerical measure is available, define its scope and owner. Where it is not, use an evidence record or a test. The business should understand the limitations of its own assessment rather than present uncertainty as a green status.
Decide how much change the organisation can absorb
Operational improvement competes with customer delivery, sales activity and recruitment. A well-intentioned programme can itself become a source of disruption if it demands too much time from a small leadership team.
I would prefer three completed and tested changes to a programme of twenty actions that continues indefinitely. Allocate realistic capacity, establish a short review cycle and stop initiatives whose costs exceed the value they are likely to produce. The next ninety days should be informed by what the first ninety actually achieved.
The distinction between growth and scale-readiness is ultimately one of management confidence. Demand can rise without the organisation needing to improvise every response. That confidence has to be earned through ordinary operational evidence.
Choose the right scale of ambition
A ninety-day programme should not pretend that every strategic problem can be resolved in a quarter. An unsuitable contractual model, inadequate leadership capacity or a major systems replacement may take longer. The programme can still create value by producing a clear definition of the problem, a responsible owner and a well-grounded decision about the next investment. The British Business Bank’s 2026 finance markets report provides wider context for smaller businesses considering investment and funding. [3]
For smaller organisations, available management attention is a real constraint. Asking every functional lead to run a dozen improvement projects alongside customer delivery can increase the very instability the exercise was intended to address. I would start with a limited number of changes, set aside realistic time and deliberately postpone initiatives whose benefits or dependencies remain uncertain. The ScaleUp Institute’s 2025 review identifies leadership and talent among the challenges reported by surveyed scaleup businesses. [1]
What to take into the next quarter
At the final review, the leadership team should distinguish three categories. The first is a working practice that has been adopted and checked, and now belongs in normal management routines. The second is an incomplete action with a clear reason, revised owner or deadline. The third is a larger issue requiring a separate business case, additional capability or more detailed diagnosis.
It is also worth asking what should stop. A new process may have rendered an old report unnecessary. Delegated authority may remove a routine approval meeting. Reducing avoidable work is part of improving an operating model, not an accidental bonus. There is little value in replacing informal confusion with a larger collection of formal obligations.
Sources and further reading
[1] ScaleUp Institute, Annual Review 2025 Read online
[2] OECD, Empowering SMEs in the age of AI: 2026 D4SME Survey Read online
[3] British Business Bank, Small Business Finance Markets Report 2026 Read online
Sources accessed 6 November 2026. All examples explicitly described as illustrative are hypothetical.
