Architecture Practice Design and Reform for a National Construction Corporation

Overview

The client — the Technology Services division of a national construction and real estate corporation — delivered ICT solutions across major infrastructure and development projects both domestically and internationally. The division operated two primary delivery models: full-lifecycle engagements spanning strategy through to operations, and design-and-construct engagements focused on solution delivery within established parameters.

Despite a talented team and a strong portfolio of project experience, the division had no formal architecture practices bridging the gap between strategic vision and detailed design. This resulted in inconsistent solution approaches, limited reuse of proven designs across projects, and a dependency on individual knowledge rather than organisational capability. Leadership recognised that formalising the architecture function was essential to maturing the division's service offering and scaling its delivery capacity.

The Challenge

An evaluation of the division's architecture capability revealed significant gaps between the quality of work being delivered on individual projects and the organisation's ability to systematically capture, govern, and reuse that knowledge:

• No formal architecture processes existed between the initial opportunity assessment and detailed design phases — strategic intent was translated to implementation through informal channels, primarily email
• Architecture artefacts were stored across file systems with no discoverability, version control, or classification — making reuse across projects difficult and knowledge transfer slow
• There was no common language for discussing and categorising the division's technology solution domains, meaning each project team described similar capabilities differently
• No compliance or assurance mechanisms existed to verify that project designs aligned with agreed standards or architectural direction
• Architecture decisions and change requests were managed informally, with no governance structure to assess trade-offs, grant dispensations, or track deviations
• The division's deep project experience was concentrated in individuals rather than codified in reusable standards, patterns, and reference architectures

Our Approach

This engagement is a direct example of Knowble's Architecture Excellence service — designing and embedding architecture practices that elevate organisational capability from individual expertise to institutional maturity.

Knowble took a structured approach to designing the architecture practice:

• Current state assessment — evaluated existing architecture maturity by mapping the division's current artefacts, processes, and delivery touchpoints against TOGAF Architecture Development Method (ADM) reference processes
• Gap analysis — identified where formal architecture outputs were missing, where informal practices existed that could be formalised, and where the division's existing delivery methodology (a five-phase model spanning Strategy through Transition) needed architecture integration points
• Framework design — designed three core architecture processes (Capability Planning, Development, and Governance and Assurance) mapped directly onto the existing project delivery phases, ensuring architecture became an overlay on established ways of working rather than a separate workflow
• Artefact development — produced a comprehensive suite of interrelated deliverables that operationalised the framework, each designed to reinforce the others

The framework was grounded in TOGAF and ISO/IEC/IEEE 42010:2011, adapted to the practical realities of the division's project-driven operating model.

What We Delivered

Knowble delivered six integrated artefacts that together formed a complete, operational architecture practice:

• Architecture Process Integration — the foundational strategy document defining how architecture processes integrate with the division's delivery methodology, including thirteen actionable recommendations across architecture planning and delivery. This mapped each recommended architecture output to existing artefacts, identifying where gaps needed to be filled and where current practices could be elevated
• Technical Reference Model — a comprehensive taxonomy of all ICT solution domains under the division's management, establishing a common organisational language across specialist domains (safety and security, workplace, lifestyle, utilities, transportation) and foundation platforms (experience services, information and integration, network and communications). The TRM provided the classification backbone for the architecture repository and governance processes
• Architecture Principles — twenty-two enduring principles across four domains (Business, Information, Solution, and Security), each structured with a clear statement, rationale, and implications. These ranged from strategic alignment and risk management through to data governance, solution reuse, and zero-trust security — developed using five quality criteria to ensure they were understandable, robust, complete, consistent, and stable
• Governance and Assurance Framework — a governance board structure with defined composition, decision-making protocols, and two operational processes: Compliance Assessment (ensuring project designs meet standards) and Change Assessment (managing evolution of the architecture repository). The framework was deliberately positioned as an enabling function rather than an authoritative gate, with measurement indicators to track adoption and effectiveness
• Design Assessment Template — the practical compliance instrument connecting governance to project delivery, including a self-assessment checklist aligned with the TRM solution domains and a structured outcome process (Endorsed, Dispensation with conditions, or Recommendations for revision)
• Architecture Repository Requirements — a functional specification for a digital platform to store, classify, discover, and govern all architecture resources, with requirements for document management, compliance assessment workflows, and change request tracking

Outcomes

The engagement transformed the division's architecture capability from informal, individual-dependent practices to a structured, governed, and scalable discipline:

• From individual expertise to institutional capability — proven solutions, patterns, and standards were codified into a structured repository with a common taxonomy, reducing dependency on individual knowledge and accelerating onboarding for new team members
• Consistent service delivery — the architecture framework provided a repeatable approach to solution design across all project engagements, supporting the division's ambition to present a more mature and consistent service offering to both internal and external clients
• Embedded governance — compliance assessment and change management processes were integrated into existing delivery tollgates, ensuring architecture quality without introducing bureaucratic overhead. Dispensation mechanisms acknowledged that pragmatic trade-offs are a reality of project delivery while ensuring they are visible and time-bound
• Reuse and efficiency — the Technical Reference Model and architecture repository created the conditions for systematic reuse of approved solutions across projects, reducing tender response times and design effort for recurring capability domains
• Measurable adoption — the governance framework included built-in metrics (repository activity, compliance rates, dispensation volumes, assessment turnaround) providing the division's leadership with ongoing visibility into the health and adoption of the architecture practice