How Do You Run Today’s Business While Building Tomorrow’s Growth Engine?

How Do You Run Today’s Business While Building Tomorrow’s Growth Engine? My answer is direct: Current revenue pays for tomorrow, but the operating system usually protects only current revenue. I separate keep-the-lights-on work, committed growth work and option-building work before asking for another initiative.

How to fund a growth engine without weakening delivery

A growth engine earns credibility when the business can pass up a short-term opportunity without abandoning its long-term thesis, and can stop a long-term bet without protecting sunk cost. That is the standard I would take to a board review.

Put one growth decision in front of the CEO and executive team with its current facts, constraint and owner. Ask what must be true for the preferred option to work, then examine the second-order demand it creates for managers, customers, data, culture and the board. A good plan becomes an operating choice in that conversation.

The dual-horizon map becomes useful when it is tied to a capacity decision. The first task is to mark the hours, budget and senior attention already consumed by reliability work, then reserve a small, explicit share for the next growth engine. The number matters less than the trade-off. If the reserve cannot survive one difficult month, it was never a real commitment.

A board conversation should separate the performance of the current engine from the evidence behind the next one. Current revenue may be healthy while the assumptions behind future growth are weakening. I want those signals visible in the same pack, with a named decision for each one. That stops a good quarter from becoming an excuse to postpone reinvention.

The practical test is a calendar that reveals priorities without requiring a speech. The delivery review asks whether promises were kept. The reinvention review asks which assumption changed and what the organisation will do differently. When the same meeting tries to answer both questions, urgent variance usually wins because it has the louder evidence.

Founders often carry the hidden cost of this conflict by becoming the escalation point for every trade-off. The handover is a decision-rights exercise: which horizon belongs to which leader, what must be consulted, and what can be decided locally? I record those rules in the operating rhythm so the growth engine is not dependent on one person’s memory.

A credible reinvention portfolio contains small tests, not a theatre of certainty. Each test has a customer or operational hypothesis, a learning deadline and a stop condition. The team earns more capacity by reducing uncertainty. It does not earn it by producing a longer status report.

The result I look for is strategic resilience. The organisation can protect a long-term choice while meeting a short-term obligation, and it can stop a weak bet without treating the decision as failure. That combination is the capability that lets growth compound.

Protect the cash-producing engine before asking for more growth. Give the decision an owner and collect evidence from the next operating cycle. If nobody can point to a changed choice, handoff or conversation, the recommendation is still too abstract.

For How Do You Run Today’s Business While Building Tomorrow’s Growth Engine, I would use the Leadership Capability Architecture framework to make the decision rights and routines visible, then check the practical intelligence layer in CapabilityAI. The relevant service context is this implementation pathway. Those links let a reader move from this specific question into a working diagnostic.

The handoff that protects both engines

In The Leadership Shift, I describe a large transformation spread across global enterprise organisations where a big-bang delivery model, employee disengagement and lost corporate knowledge held back new capability. The funding process could not support a test-and-learn cycle. The practical change was an incremental plan with tangible benefits early enough to rebuild confidence. That experience still shapes how I separate today’s engine from tomorrow’s growth work.

The two horizons should not compete for the same proof. Current delivery is judged by the promise kept this week. Growth work is judged by what the team learned, what assumption changed and whether the next test deserves attention. Keeping those tests separate makes it possible to protect service quality without pretending that every new idea has earned a permanent place in the plan.

The two horizons also need different meeting questions. For today’s work, ask where service, cash or delivery is at risk this week. For tomorrow’s work, ask which assumption the team is testing and what permission it needs. Mixing those questions creates either a firefight or a science project. I put them on the same page, but I do not give them the same approval path. The distinction lets leaders protect reliability while still making room for evidence that could change the shape of the business.

The review should end with a choice about attention. Protect the work that keeps the present dependable, fund the test that could change the future and make the trade-off visible to the people carrying it.

A growth engine needs a place in the calendar before it needs another idea. A useful test is to mark the hours already consumed by customer commitments, operational fixes and internal approvals. The remaining capacity is the real budget for tomorrow’s work. If nobody can name it, the business is not funding growth. It is hoping that growth will fit into the gaps.

The monthly review should make one trade-off visible. Which current promise will be protected, and which proposed move will wait? That choice belongs with the person who carries the consequence. A board can challenge the choice, but it should not create a second queue of priorities after the meeting.

Small experiments work when their limits are clear. Give each one a customer or process assumption, a date for evidence and a condition that ends the test. The team does not need to predict the future. It needs to learn enough to decide whether the next pound and hour should follow.

The CEO’s attention is most useful where the horizons collide. A reliability issue may consume the same specialist needed for a growth test. Set the decision right once, record it and let the owner act. Reopening the same argument every week is a hidden tax on both horizons.

At the end of a quarter, I would look for three signs: the present engine is dependable, the future bet has produced evidence and the organisation can say what it stopped doing. That is a more honest growth plan than a long list of initiatives.

The growth review should not become a second strategy meeting. Bring one decision, one piece of evidence and one request for capacity. If the request cannot be answered, record the constraint instead of adding another action. That record helps the team see whether the problem is money, attention or an assumption that has not survived contact with customers.

Protecting the present also means naming what can wait. A reliable service gives the business permission to test, but only if the test has a boundary. Keep the current promise visible, fund the smallest next move and review both on their own terms.

A useful board question is whether the future work has earned another month of attention. Ask what the team expected to learn, what it actually learned and which assumption changed. If nothing changed, do not disguise the result with a new label. Close the test, keep the evidence and return the capacity to the current engine. If something did change, name the next decision and the person who will make it. This keeps growth work connected to the business rather than turning it into a permanent side project with its own language, meetings and measures. The discipline is modest, but it protects both horizons from the same failure: activity becoming a substitute for choice.

That is the operating bargain: current delivery stays dependable while a small, named test earns the right to more attention. The work is visible, the trade-off is recorded and the next decision has an owner.

The operating plan should show the two horizons side by side. Current work gets a service measure and a named owner. The growth test gets an assumption, a learning date and a limit on spend. Review them in the same month, but do not score them with the same measure. Reliability earns trust by keeping a promise. Growth earns another test by changing what the team knows. Mixing the measures makes both conversations less useful. A board member should be able to see where capacity went, what evidence arrived and which choice follows from it.

Further reading: Can You Articulate Your Strategy in 35 Words?

Further reading: Are You Leading a Coaching Business or a Human Development Business?