10. Strategic and organisational alignment
Strategic and organisational alignment ensures that digital projects are not only well-executed but also meaningfully contribute to organisational goals and broader whole-of-government priorities. It involves connecting project objectives with strategic intent, aligning delivery with business processes, and fostering shared ownership across leadership and operational teams. In complex environments, strong alignment helps maintain focus, secure stakeholder buy-in and ensure that digital investments deliver sustained public value.
The SRO plays a critical role in championing alignment between project goals, policy intent, and organisational strategy. This includes engaging senior stakeholders, integrating the project into broader reform agendas, and ensuring that delivery decisions reflect long-term priorities. SROs need to champion integrated planning through governance forums, secure agreements on shared infrastructure, and connect technical designers early to prevent duplication and delays. When alignment is weak or unclear, projects risk becoming siloed, losing relevance, or face resistance from key stakeholders. Strategic alignment also supports prioritisation, helping to manage competing demands and resource constraints.
For delivery teams, organisational alignment translates into clear direction, consistent support, and smoother integration with business operations. Challenges often arise when delivery is disconnected from strategic planning, or when teams lack visibility of how their work contributes to broader outcomes. Misalignment can lead to duplicated effort, unclear ownership, or difficulty embedding solutions into existing processes. Delivery teams benefit from regular engagement with business leaders, shared understanding of strategic goals, and mechanisms to adapt delivery in response to changing organisational priorities. Strong alignment fosters collaboration, accelerates adoption, and enhances the overall impact of digital initiatives.
Key lessons
Cross-agency coordination
Cross-agency reform initiatives required strong alignment, coordination and sequencing from the outset. Agreements across relevant bodies, with senior executive endorsement and early collaboration between technical leads, supported alignment of priorities and delivery activities across major initiatives.
Related actionable insights:
1 - Collaborate across agencies | 3 - Align technology strategy | 5 - Use independent expertise | 6 - Maximise reuse opportunities | 7 - Align agility across levels
Policy impacts
Maintaining regular cross-area engagement helped manage policy impacts on delivery. Policy changes could significantly affect delivery. Regular engagement between corporate, policy and delivery areas helped make changes visible and manage impacts early.
Related actionable insights:
2 - Coordinate agency reforms | 3 - Align technology strategy | 7 - Align agility across levels
Enterprise reuse
Flexible, scalable solutions that met both project and enterprise needs created broader efficiencies and ben fits, including lower support and maintenance costs. Solutions that could scale and adapt across agencies also supported long-term sustainability and reuse.
Real life learning
The project was delivering an enterprise-wide uplift of ICT and data capabilities, enabling improved ways of working and service delivery. Strong and effective governance, particularly through the project board and the product owner, was critical in navigating the balance between division-specific requirements and a flexible solution that can meet agency-wide needs. The product owner played a key role in navigating trade-offs between standardisation and customisation. They supported a more consistent agency-wide solution and reduced the cost and complexity of maintaining multiple division-specific solutions. This reinforced the importance of strong product ownership and governance in achieving enterprise-wide value, while balancing division-specific needs.
“Develop flexible and scalable solutions. It’s around understanding ‘Is it a public infrastructure that we need to be looking at? Is it going to end up being a system of government significance?'"
Related actionable insights:
2 - Coordinate agency reforms | 4 - Focus on core capabilities | 6 - Maximise reuse opportunities | 7 - Align agility across levels
Actionable insights
- Prioritise cross-agency collaboration to foster innovation and avoid duplication.
Put practical cross-agency coordination mechanisms in place early, such as shared governance forums or inter-agency working arrangements, to identify opportunities for reuse, shared capability and lessons learned. Coordinate internal agency reforms through governance and reporting.
Use governance forums to create line of sight across initiatives, identify overlaps, align sequencing and identify where shared technology or change effort would improve efficiency.“I think you need to be able to find a way through your governance forums and reporting to try … draw together your reform so there’s at least a line of sight of where things interact and where the opportunities might be to do unified change management and common capabilities from a tech perspective.”
Align your technology roadmap with organisational and government strategy.
This supports consistent advice to government and more realistic expectations about what can be delivered and when. Align your roadmap with broader government priorities and use this to guide conversations with stakeholder groups.“Having a clear technology roadmap supports things like consistent advice to government on what can be achieved and when.”
- Focus on core capability needs.
Step back and identify common capabilities that could support multiple digital programs across government. Use this to guide investment and design decisions. - Leverage independent expertise and architectural reviews.
External perspectives can reveal patterns, risks and opportunities that internal teams may miss. Establish architectural reviews or communities of practice to share lessons and strengthen decision-making. Broaden how you think about re-use.
Re-use is not limited to systems. It can include licensing, components, patterns and knowledge. Look for practical opportunities to re-use what already exists and document examples to build momentum over time.“Our understanding of re-use has to evolve to be re-use of many different things. There’s always benefit even if it’s just ‘(software) licencing’ -trying to think about the elasticity of re-use to get small hops over time rather than aiming for nirvana.”
- Align agility across project, program and enterprise levels.
Make sure governance, decision-making and organisational processes are responsive enough for projects to adapt and deliver value without being held back by slower-moving structures.