Embedded enterprise architecture leadership across multiple transformation programs for a major Queensland Government department.

The situation

A large Queensland Government department was running multiple concurrent transformation programs touching customer-facing services, internal business systems, data platforms, and security uplift. Each program had its own business sponsor, vendor partners, and technical teams. None had a shared architecture that connected them.

The department’s internal architecture function had capacity gaps. Programs were making technology decisions in isolation, security and compliance posture varied across initiatives, and legacy systems were accumulating technical debt as new capability was layered on top. Without coordinated architecture leadership, the department was at risk of delivering individually-correct projects that wouldn’t fit together.

Our approach

InnovateX embedded a Principal Solution Architect into the department’s architecture function as enterprise architecture leadership across the program portfolio.

Cross-program architecture oversight

The embedded role provided architecture leadership across six-plus concurrent programs, ensuring decisions made in one workstream didn’t undermine another. We worked across business, data, application, security, and infrastructure architecture domains, connecting business intent to technical execution.

Reusable architecture patterns

Where multiple programs faced similar architectural decisions, we designed reusable patterns that became the department’s reference architectures. Cloud landing zone patterns, identity and access patterns, data exchange patterns, and integration patterns. Programs adopting these patterns delivered faster and stayed aligned with the department’s broader architecture posture.

Functional and non-functional requirements

We established Functional Requirements (FRs) and Non-Functional Requirements (NFRs) tailored to the department’s security posture and compliance obligations, including ISM, Essential Eight, ASD Secure Cloud, and QGCDG. These requirements became the foundation that subsequent engineering work, including the parallel Azure cloud platform engineering case study, built against.

Governance and decision-making

We participated in architecture review boards, technical governance forums, and senior leadership briefings. Architecture decisions were captured in decision records, traced back to business outcomes and compliance obligations, and made visible to the broader department.

Capability uplift

The embedded model meant architecture knowledge transferred to internal architects and technical leads through working sessions, joint authorship of architecture artefacts, and mentorship. Internal architecture capability matured alongside the department’s transformation programs.

What we delivered

• Architecture oversight across 6+ programs running concurrently across the department.
• Reference architectures and patterns for cloud landing zones, identity, integration, data exchange, and security.
• Functional and Non-Functional Requirements documenting the department’s security and compliance posture, used as the foundation for downstream engineering work.
• Technology roadmaps aligning programs to a coherent multi-year direction.
• Architecture governance artefacts: decision records, review processes, governance forums.
• Internal architecture capability uplift through joint authorship, mentorship, and working sessions with internal staff.

Frameworks and standards used

Architecture frameworks: TOGAF-aligned domain decomposition (business, data, application, technology), ArchiMate for visual modelling, structured ADRs for decision records.

Government frameworks: ISM controls for information security, Essential Eight to Maturity Level 2, ASD Secure Cloud blueprint for cloud architecture, QGEA for Queensland Government enterprise architecture alignment, QGCDG for cloud deployment.

Industry frameworks: NIST Cybersecurity Framework, CIS Benchmarks, SMB1001 Gold for our own security posture.

Outcomes

• Coordinated direction across the program portfolio. Programs are no longer making isolated technology decisions. Architecture across cloud, security, integration, and data is aligned.
• Reusable patterns reduce delivery risk. New programs adopting the established patterns are reaching production faster with less rework.
• Compliance posture improved. Documented FRs/NFRs, aligned to ISM and Essential Eight, give the department a clear baseline for new initiatives and an audit trail for existing ones.
• Sustained engagement. The department has retained the architecture leadership role for over 12 months, reflecting the value of continuous architecture oversight rather than one-off project engagements.
• Internal architecture capability is maturing through embedded mentorship and joint delivery, reducing future dependency on external architects.