Strategy looks three to five years ahead, yet investment decisions land in the next 12 months. Capability mapping and early architectural input show leaders which projects must come first, what each will really involve and how much delivery capacity to hold in reserve.
Key Insights:
- Sequence the future-state roadmap around dependencies.
- Retain 20% of delivery capacity in reserve.
- Give every investment a clear business driver.
A future-state enterprise architecture shows what an organisation needs in place to deliver its strategy. However, strategic ambitions can easily run ahead of what the business is capable of delivering. For leaders, the challenge is working out how to get from where the organisation is today to where it needs to be.
Leaders need to make some practical decisions about where to invest and in what order. Existing systems and architectural dependencies will influence those decisions, while changing business priorities mean the roadmap needs enough flexibility to adapt over time.
Getting the roadmap right is important because decisions made today will shape what the organisation can achieve in the years ahead. So how can leaders develop a realistic roadmap that connects immediate investment priorities with their longer-term strategic ambitions?
Turning a three-to-five-year strategy into a 12-month plan
Business strategies typically look three to five years ahead, but organisations need to make investment decisions much sooner. What happens over the next 12 months needs to deliver value now, while putting the business in a position to achieve its longer-term ambitions.
Of course, priorities can change along the way. Emerging technologies such as AI often create new opportunities, while changing market conditions or regulatory requirements can affect what the business needs to invest in.
Business capability mapping helps organisations work out what they already have in place and what they will need to develop to deliver their strategy. From there, they can build a roadmap that identifies which projects need to happen first and how the work should be sequenced over time.
The roadmap also needs to evolve as business requirements change. Otherwise, organisations risk following a plan that no longer reflects their priorities or the capabilities they need to build.
How project dependencies shape the change roadmap
A three-to-five-year roadmap may look achievable on paper, but whether it works in practice depends on how projects are sequenced and the dependencies between them. Starting a project before the necessary systems or capabilities are in place can create delays and additional costs, with consequences for other initiatives across the delivery portfolio.
Even a relatively straightforward project can turn out to be more complicated than expected. For example, it might need data from multiple systems, each with its own architecture and constraints. Getting that data out and bringing it together then has the potential to become a significant piece of work before the project can deliver its intended outcome.
The architectural requirements vary considerably from one project to another. A process improvement might only need minor changes to existing systems, whereas meeting a new regulatory requirement could involve substantial security architecture work. Acquisitions can introduce another level of complexity level of complexity through the need to integrate different systems. Understanding these requirements early gives organisations a better idea of what each project will involve and how much it’s likely to cost.
Leaders also need to be realistic about how much work their organisation can take on and build in contingency for unexpected demands.
A practical rule of thumb is to commit around 80% of available delivery capacity, keeping the remaining 20% in reserve. That way, when new regulatory requirements or strategic opportunities emerge, there’s room to respond without derailing projects already underway.
Using capability mapping to prioritise investment
Business capability mapping helps leaders work out where to invest. A simple green, amber or red assessment of existing capabilities can highlight the biggest gaps and where resources are needed most. A red rating, for example, might mean a supporting system is missing entirely or that several existing systems don’t work well together. Either way, the organisation could be looking at a more complex delivery challenge than anticipated.
From there, leaders can start building their change portfolio, working out which projects need to happen first and which depend on other work being completed. Every proposed investment should also have a clear business driver, whether it supports the strategy, addresses a regulatory requirement or improves operational resilience. Leaders are then able to weigh competing priorities and decide which investments will make the greatest contribution to the broader roadmap.
Bringing enterprise architecture expertise into investment planning early can help organisations identify dependencies and make better decisions about what to fund and when. An experienced, independent perspective can also help challenge assumptions about delivery complexity and ensure the roadmap remains realistic.
Before committing to the roadmap, leaders need to be confident that their investment priorities make sense and that the organisation can realistically deliver the work. A closer examination of capability gaps and the dependencies between projects can help uncover potential problems while there is still time to adjust the roadmap.
Keeping the roadmap aligned with the future state
Leaders can make better investment decisions when they understand how their future-state architecture supports the organisation’s strategy. A clear picture of capability gaps and project dependencies helps them set priorities and develop a roadmap that reflects what the business can realistically deliver.
As business priorities change, leaders also need to keep reviewing the roadmap and adjusting their investment decisions to stay on course towards their longer-term goals.
Quay Consulting is a professional services business specialising in supporting organisations to turn future-state architecture into a practical investment and delivery roadmap. Meet our team or reach out to have a discussion today.



