Businesses do not make a technology plan more ambitious by adding work their people cannot deliver. They create more competing demands, less focus and less room to respond when circumstances change.

That matters when planning for 2027. New technology, changing customer needs and regional or global events can alter priorities long before an annual plan has run its course. A business that has committed all its capacity at the start of the year has left itself little ability to respond.

A deliverable plan connects business priorities to the people, funding and foundations available. It also makes clear what will wait, what could change and how leaders will decide. Those choices deserve as much scrutiny as the initiatives being approved.

Leave room for the business to change

Planning creates direction, helps teams prepare and establishes expectations. Its value does not depend on predicting the whole year correctly. It depends on giving the business a workable starting point and a way to make sensible decisions as conditions change.

That requires some flexibility in the commitments themselves. If every team is fully allocated, a new customer requirement or an unexpected operational problem can only be absorbed by delaying something else, reducing its scope or asking people to carry more work. The plan should acknowledge those choices before they become urgent.

Separate firm commitments from work that is conditional on funding, capacity or earlier results. Be specific about the decisions that would trigger a review, such as a material change in demand, a missed dependency or evidence that an investment is no longer worthwhile. Leaders can then change the plan deliberately, while keeping the business outcome in view.

Leaders need to get into the detail

A summary showing available headcount tells leaders very little about whether the right people have time to do the work. Delivery depends on particular skills, operational knowledge and decisions. Those demands need to be understood across the whole portfolio.

Leaders should speak to their teams and expect their own leadership teams to work through the layers beneath them. Ask how estimates were built, whose contribution is required and what those people are already committed to. A reassuring answer at executive level needs to stand up when tested with the people expected to deliver it.

Consider three initiatives that each need the same finance expert to define requirements, validate data and approve changes. Each project might have a funded delivery team, yet all three still depend on one person’s time around their existing responsibilities. Reviewing the projects separately can hide the constraint that makes the combined plan unrealistic.

Include the work required from the wider business: testing, training, process decisions, adoption and support after launch. Give people room to challenge assumptions without being treated as obstructive. Their explanation of what cannot fit may be the most useful planning evidence the leadership team receives.

Make funding decisions against the outcome

When funding is tight, leaders need to be clear about what each investment is expected to achieve. A growing business may still be cautious about committing cash, while a business working hard to maintain performance may need to reprioritise more sharply. Neither can afford a portfolio that consumes resources without moving the business forward.

The assessment needs to go beyond the initial project cost. Internal effort, implementation, training, support and ongoing operation all draw on the business. If these demands are omitted, an apparently affordable initiative can displace other valuable work or require further spending before its benefits are realised.

For each priority, identify the business result, how progress will be assessed and what has to be funded before that result is possible. Where the return is uncertain, consider a smaller, useful stage that produces evidence for the next decision. Budget approval should reflect that delivery path, rather than assume the rest will somehow be absorbed.

Build the foundations while putting AI to work

The business strategy should set the direction: which customers to serve, where to grow, how to improve performance and what the organisation needs to protect. AI is a tool and an enabler within that strategy. Calling a business AI-first does not resolve those choices or establish the capability to execute them.

Processes and data matter because AI will operate within the business that actually exists. Unclear responsibilities, inconsistent information and poorly understood workflows affect what can be automated and how confidently its output can be used. Culture and talent matter too: people need the skills, time and confidence to change how they work and challenge the results.

That does not mean every process must be redesigned and every dataset perfected before AI can be useful. Foundation work and practical AI adoption can progress in parallel, provided the dependencies are understood. The plan needs to distinguish what can be tried now from what cannot be relied on at scale until earlier work is complete.

For example, a business could test AI-assisted drafting using a defined set of approved customer-service information while separately improving the quality and ownership of its customer records. That would test one bounded use case; it would not establish that AI was ready to make decisions across every customer account. The scope, data and level of human review should reflect that distinction.

AI may also help teams analyse information, identify inconsistencies and support the work of improving their foundations. Its contribution should be tested in the actual workflow, including the effort needed to check and use its output. Any capacity released can then inform the plan, rather than being assumed in advance to make an overloaded roadmap fit.

If the capacity does not exist, commit to less

Once the detail is visible, leaders may find that the proposed work simply exceeds the capacity available. The response has to change the commitments. Spreading the same people more thinly across more initiatives does not solve the underlying problem.

Reprioritisation means deciding what will stop, wait or become smaller. Those decisions should be made across the business, because each sponsor can make a persuasive case for their own project. The leadership team’s responsibility is to judge the combined demands and protect the work that matters most.

Sequencing can help where work genuinely depends on an earlier result. Additional capability can help where a specific skill or delivery gap can be funded and filled. Neither removes the need to assess the time required from internal experts, decision-makers and the teams that will use the result.

Before signing off the roadmap, bring the outcome, capacity, funding and dependency assessments together. Can the people doing the work explain how it fits alongside their existing commitments? If a significant new priority arrives, is it clear who will decide what gives way?

A plan that passes those tests gives people a credible commitment to work towards and leaders a basis for adapting it. Delivering fewer priorities with proper focus can create more progress than keeping everything nominally active. The ambition should be measured in what the business can achieve, rather than how much work it has agreed to start.

Relentica’s Strategy, Advisory & Delivery work helps leadership teams connect business priorities to practical roadmaps and delivery. If a particular capacity, funding or dependency issue is holding up your 2027 plan, talk to Relentica about a roadmap review.