What must your business become able to do?

A growth strategy becomes more useful when it says what the business must become able to do. Entering a market, launching a service or pursuing acquisitions each requires a capability that can be used repeatedly by the people responsible for the result.

Describe the ability in business terms.

Start with a concrete sentence: “We need to be able to…” Finish it with an activity and a meaningful outcome.

For example, a business might need to assess acquisition opportunities consistently, give a customer a reliable quote during a conversation, or deliver a new service through an existing channel. These statements make the required ability easier to discuss and test.

Then ask why that ability matters to the growth ambition. Who benefits? What customer need does it address? What changes in the economics or the way the business competes? If that connection is weak, the capability may be interesting without being a priority.

Identify what is missing.

The gap may involve a product, data or technology. It may also involve a proposition, pricing, skills, decision rights, a customer journey or an operating process. A complete view matters because these parts influence one another.

A new decision tool needs information people can trust and a clear place in the decision process. A new service needs a customer promise that the operation can fulfil. An AI workflow needs access to representative work, review where judgement is required and someone responsible for the result.

Map what already exists, what can be adapted and what needs to be developed. An existing capability may need focused improvement. Buying or partnering may be appropriate for some elements. Make those choices against the business need, constraints and ongoing operating cost.

Make the investment case testable.

Describe the path from the capability to the outcome. Faster assessment might increase the number of worthwhile opportunities a team can examine. Better service might improve conversion or retention. Those effects depend on demand, quality and how the organisation uses the new ability.

Record the assumptions that carry most of the case:

  • customers or colleagues will use the capability;
  • it changes a consequential part of the work;
  • the quality is sufficient for its intended purpose;
  • the team can operate it at an acceptable cost;
  • the resulting capacity or improvement can be converted into business value.

Agree what evidence would support each assumption. Define the baseline, the success measures and the threshold for further investment before the build becomes difficult to change.

Build a useful version of the complete change.

Choose a focused scope that lets the business test the capability in real work. Include the necessary process, information, human judgement and ownership alongside the technology. Representative exceptions and handoffs are part of that test.

Involve the future owners early. Their participation helps establish whether the proposed design fits the work, what support is needed and which constraints have been missed. It also makes the transition into everyday use clearer.

Selected work shows examples of practical building and operating change. Assess the result in terms of what the business can now do, not simply whether a tool has been delivered.

Make ownership part of the capability.

Before expanding the work, establish who runs it, who can change it, how performance is reviewed and what ongoing effort is required. Check whether the original investment case still holds as real evidence arrives.

Expansion may be justified. The next step may also be to improve the design, change the scope or stop. Those choices are easier when the strategy has named the ability it needs and the outcome that makes it valuable.