Mastering the TOGAF® Standard: A Career Path in Architecture Frameworks - Certbolt

The TOGAF® (The Open Group Architecture Framework) Standard is a comprehensive framework for enterprise architecture that provides an approach for designing, planning, implementing, and governing an enterprise information architecture. Developed by The Open Group in 1995, TOGAF® has become one of the most widely adopted enterprise architecture frameworks globally, utilized by organizations to improve business efficiency and align IT strategies with business goals.

Historical Context and Evolution

TOGAF® originated from the Technical Architecture Framework for Information Management (TAFIM), developed by the U.S. Department of Defense in the 1990s. Recognizing the need for a standardized approach to enterprise architecture, The Open Group adapted and evolved TAFIM into TOGAF®, making it applicable across various industries and organizations. Over the years, TOGAF® has undergone several updates, with the latest being the 10th Edition, released in April 2022.

Core Objectives of the TOGAF® Standard

The primary objectives of the TOGAF® Standard include:

Standardization: Providing a common language and methodology for enterprise architecture.
Efficiency: Streamlining the development and implementation of enterprise architectures.
Alignment: Ensuring that IT strategies are in harmony with business objectives.
Flexibility: Allowing customization to meet specific organizational needs.

Key Components of the TOGAF® Standard

The TOGAF® Standard comprises several key components that collectively support the development and management of enterprise architecture:

1. Architecture Development Method (ADM)

At the heart of the TOGAF® Standard lies the Architecture Development Method (ADM). The ADM offers a systematic approach to developing and managing enterprise architecture, ensuring that all aspects of the architecture are considered and integrated. It is designed to be iterative and adaptable, allowing for continuous refinement and evolution of the architecture as business needs change.

2. Enterprise Continuum

The Enterprise Continuum is a model for structuring a virtual repository of all the architecture assets. It provides a method for classifying architecture and solution artifacts, showing how generic solutions can be specialized to meet specific needs.

3. TOGAF® Resource Base

This is a set of guidelines, templates, and tools to support the ADM. It includes a wealth of resources that can be used to tailor the ADM to specific organizational contexts.

4. Architecture Content Framework

The Architecture Content Framework provides a detailed model of architectural work products, including deliverables, artifacts, and building blocks. It ensures consistency and completeness in the outputs of the ADM.

Benefits of Implementing the TOGAF® Standard

Organizations that adopt the TOGAF® Standard can expect several benefits:

Improved Alignment: Ensures that IT strategies are in sync with business objectives.
Enhanced Efficiency: Streamlines processes, reducing redundancy and improving resource utilization.
Risk Mitigation: Provides a structured approach to identifying and addressing potential risks.
Cost Savings: Optimizes resource allocation, leading to cost reductions.
Standardization: Promotes consistency across projects and departments.

The TOGAF® Standard serves as a comprehensive framework for enterprise architecture, offering a structured approach to aligning IT strategies with business objectives. Its components, including the ADM, Enterprise Continuum, Resource Base, and Content Framework, provide organizations with the tools and methodologies needed to develop, implement, and manage effective enterprise architectures. By adopting the TOGAF® Standard, organizations can achieve improved efficiency, alignment, and agility in their operations.

Architecture Development Method (ADM) in the TOGAF® Standard

The Architecture Development Method (ADM) is the core of the TOGAF® Standard. It provides a step-by-step approach for developing enterprise architecture, ensuring consistency, completeness, and alignment with business goals. ADM is iterative, allowing organizations to evolve their architectures incrementally while adapting to changes in business strategy, technology, and organizational needs.

ADM is designed to be flexible and adaptable to different organizational contexts. Its cyclical process helps architecture teams revisit and refine their work at regular intervals, fostering continuous improvement and learning. This part will delve into the structure, phases, and practical applications of the ADM, explaining how it facilitates the systematic development and management of enterprise architecture.

ADM Structure and Phases

ADM consists of ten core phases that guide the development of enterprise architecture from start to finish. Each phase addresses specific aspects of the architecture lifecycle, from defining the vision to maintaining and managing the deployed architecture.

Preliminary Phase

This initial phase sets the groundwork for architecture development. It focuses on:

Establishing the architecture capability within the organization
Defining architecture principles
Setting up governance frameworks
Identifying key stakeholders and sponsors

The goal is to ensure that the organization is prepared to undertake enterprise architecture initiatives and that there is a clear understanding of roles, responsibilities, and expectations.

Phase A: Architecture Vision

In this phase, the architecture team creates a high-level view of the proposed solution, including:

Business context and drivers
Key stakeholders and their concerns
Preliminary architecture models
Business goals and objectives
Approval for architecture development

Phase A helps establish a shared understanding of the project scope and objectives across all stakeholders. It sets the direction for subsequent phases.

Phase B: Business Architecture

This phase focuses on developing a business architecture that defines:

Business processes
Organizational structures
Business goals and objectives
Information flows and capabilities.

It ensures that the business needs are well-understood and form the basis for the overall enterprise architecture. Business Architecture serves as a foundation for aligning IT systems with business strategies.

Phase C: Information Systems Architectures

Phase C is divided into two sub-phases:

Data Architecture: Defines how organizational data is stored, processed, and maintained. It includes data models, standards, and governance structures.
Application Architecture: Specifies the software applications that support business processes, including interactions, dependencies, and integration requirements.

This phase helps develop a detailed blueprint of the organization’s information systems and their alignment with business goals.

Phase D: Technology Architecture

Here, the architecture team defines the technology infrastructure required to support the information systems and business processes. It includes:

Hardware and software platforms
Network and communication systems
Technical standards and guidelines
Infrastructure security and performance requirements

The goal is to ensure that the technical environment supports both current and future business needs.

Phase E: Opportunities and Solutions

This phase focuses on identifying implementation projects and defining transition architectures. Activities include:

Defining the implementation roadmap
Assessing opportunities for reuse or consolidation
Establishing project priorities and dependencies
Identifying solution building blocks (SBBs)

It translates the architectural models into tangible initiatives and projects for implementation.

Phase F: Migration Planning

In this phase, the architecture team develops a detailed implementation and migration plan. It includes:

Transition plans and timelines
Risk assessment and mitigation strategies
Resource requirements and budgeting
Integration with project management processes

Migration planning ensures a smooth transition from the current architecture to the target architecture while minimizing business disruption.

Phase G: Implementation Governance

This phase ensures that the implementation of the architecture is properly managed and aligned with the design. It includes:

Monitoring project execution
Managing architecture compliance
Resolving implementation issues
Updating governance records

Implementation governance helps maintain architectural integrity and ensures that deviations from the architecture are addressed promptly.

Phase H: Architecture Change Management

Once the architecture is implemented, organizations need to manage change proactively. This phase focuses on:

Monitoring for technology or business changes
Evaluating the impact of proposed changes
Managing the architecture lifecycle
Initiating new ADM cycles if necessary

Architecture Change Management ensures the long-term sustainability and relevance of the architecture.

Requirements Management

Although not a phase in itself, requirements management is a central, ongoing activity that supports all ADM phases. It involves:

Capturing and managing requirements
Validating and prioritizing requirements
Ensuring traceability of requirements to architecture elements

This activity ensures that the architecture continues to meet stakeholder needs throughout the development and implementation process.

Iteration and Adaptability in ADM

ADM is not a rigid process; it is designed to be iterative and customizable. Iteration allows architecture teams to:

Revisit earlier phases based on feedback
Adjust the architecture in response to new requirements or constraints.
Improve accuracy and alignment with business goals over time.

Organizations may tailor ADM based on their specific context, such as size, maturity, industry, and objectives. For example, a small company might simplify certain phases, while a large enterprise may adopt more rigorous governance practices.

ADM cycles may be executed at different levels of the organization (strategic, segment, capability), each with its scope and objectives. This layered approach enables better alignment between enterprise-wide goals and individual business unit needs.

Practical Applications of ADM

Organizations use ADM to develop enterprise architectures for various purposes, such as:

Modernizing legacy IT systems
Integrating mergers or acquisitions
Implementing digital transformation strategies
Enhancing enterprise security and compliance
Optimizing IT investments and operations

In practice, ADM helps bridge the gap between IT and business units. Involving stakeholders in all phases promotes transparency, accountability, and collaboration. The iterative approach ensures that the architecture evolves with the organization, rather than becoming obsolete or irrelevant.

ADM Tools and Techniques

TOGAF® also provides guidance on tools and techniques to support ADM, including:

Architectural views and viewpoints for communicating architecture to stakeholders
Capability-based planning to align architecture with business capabilities
Risk management frameworks to assess and mitigate project risks
Architecture modeling tools and repositories to maintain consistency and traceability

Organizations may also integrate ADM with other frameworks, such as ITIL, COBIT, or Agile methodologies, to create a comprehensive enterprise management approach.

The ADM is the cornerstone of the TOGAF® Standard, providing a proven, adaptable process for developing and managing enterprise architecture. Its structured phases guide organizations through defining, designing, implementing, and maintaining architectures that align with business goals and adapt to change.

By applying ADM effectively, organizations can ensure better governance, improved efficiency, and higher return on investment. The method’s flexibility, stakeholder engagement, and integration with broader business and IT strategies make it an essential tool for enterprise architects worldwide.

Core Components and Key Concepts of the TOGAF® Standard

In this, we explore the foundational components and key concepts that structure and support the implementation of the TOGAF® Standard. These components go beyond the ADM and provide essential context, tools, and mechanisms that ensure the architecture development process is efficient, scalable, and aligned with organizational goals. Understanding these core elements helps enterprise architects and IT leaders manage complexity, improve collaboration, and support long-term enterprise transformation.

Content Framework and Meta-Model

The TOGAF® Content Framework provides a structured way to organize and represent the outputs and artifacts developed throughout the ADM process. It defines how architecture content should be captured, described, and related, enabling consistency and reusability across different architecture projects.

The core part of the content framework is the Content Meta-Model. This model defines the key architectural entities, their relationships, and their attributes. It provides a detailed structure for organizing architecture artifacts, including:

Actors and roles
Processes and functions
Applications and services
Data entities and components
Technology components

By using a consistent meta-model, organizations can reduce ambiguity, improve traceability, and create a unified architectural repository. The meta-model also supports the creation of architecture views tailored to the needs of different stakeholders.

Architecture Repository

The Architecture Repository acts as a central location where all architectural work products are stored and managed. It supports the governance, versioning, and reuse of architectural assets. The repository is typically organized into the following sections:

Architecture Metamodel: Describes the types of architectural elements and how they relate.
Architecture Landscape: Provides snapshots of the enterprise’s architecture at different points in time.
Standards Information Base: Contains reference standards and best practices.
Reference Library: Includes templates, patterns, and other reusable artifacts.
Governance Log: Records decisions, issues, and compliance checks.
Architecture Capability: Describes the processes, tools, and roles involved in managing architecture.

A well-maintained architecture repository ensures continuity, transparency, and quality across the enterprise architecture practice. It also serves as a valuable reference for future projects and strategic planning.

Enterprise Continuum and Architecture Continuum

The Enterprise Continuum is a conceptual framework that helps classify and organize architectural artifacts. It provides a way to understand the evolution and diversity of architectures across organizations and projects.

The Enterprise Continuum includes two major components:

Architecture Continuum – This shows how generic architectural patterns evolve into organization-specific architectures. It ranges from foundational architectures (e.g., TOGAF® Foundation Architecture) to tailored architectures that reflect unique organizational needs.
Solutions Continuum – This focuses on the actual implementation of architectures. It includes everything from generic solution models and products to specific applications and services used in a particular environment.

These continuums help architecture teams:

Understand the context of their current and target architectures
Reuse proven models and solutions.
Avoid reinventing the wheel.
Bridge the gap between abstract frameworks and real-world applications.

Building Blocks and Artifacts

The TOGAF® Standard emphasizes the use of building blocks in developing enterprise architecture. A building block is a reusable component that can be composed to form larger, more complex systems. There are two main types:

Architecture Building Blocks (ABBs): These represent logical components that describe capabilities and standards at a conceptual level (e.g., a business service or data model).
Solution Building Blocks (SBBs): These are physical components that implement architecture building blocks (e.g., a database server or specific software product).

Using building blocks promotes modularity, reduces duplication, and accelerates architecture development. Artifacts, on the other hand, are specific representations or documents that describe architectural content, such as catalogs, matrices, and diagrams.

Some key artifact types include:

Business Capability Maps
Application Interaction Matrices
Technology Infrastructure Diagrams
Data Flow Diagrams
Security Architecture Views

These artifacts help communicate architectural decisions to stakeholders and serve as documentation for governance and implementation teams.

TOGAF® Reference Models

TOGAF® includes reference models that provide standard architectural patterns and templates to guide the development of architectures. These models offer a common starting point and reduce the complexity of developing architecture from scratch.

TOGAF® Foundation Architecture

This provides a generic, reusable framework for developing architectures. It includes core services and functions commonly found in most enterprise architectures, such as:

Authentication
Directory services
System management
Messaging and communication
Data interchange

These components are not specific to any industry or technology, making them widely applicable.

Technical Reference Model (TRM)

The TRM is part of the Foundation Architecture and offers a high-level view of the key technology components and their interactions. It provides a common vocabulary for discussing infrastructure components and includes:

Application platform interface
Business applications
Operating systems and platforms
Network services
Infrastructure interfaces

TRM ensures that all technology components can interact effectively within the architectural framework, reducing integration issues.

Capability-Based Planning

Capability-Based Planning is a strategic planning technique used in the TOGAF® Standard. It focuses on identifying and developing the specific business capabilities an organization needs to meet its goals. This approach is useful for aligning IT and business strategies because it translates abstract business visions into actionable plans.

Key characteristics of capability-based planning:

Focuses on outcomes and the ability to deliver services
Identifies gaps between current and desired capabilities
Supports prioritization of initiatives based on business value
Helps align investment with strategic objectives

Organizations use capability maps and heatmaps to visualize which areas need development and how to prioritize efforts and investments accordingly.

Architecture Governance

Governance ensures that architectural processes are managed effectively and that the resulting architectures meet quality standards and align with business objectives. TOGAF® provides a comprehensive governance framework that covers:

Architecture compliance: Ensuring projects adhere to architectural standards and guidelines.
Architecture contracts: Agreements between architecture and implementation teams to deliver agreed outcomes.
Governance bodies: Committees or boards responsible for oversight and decision-making.
Governance processes: Formal procedures for managing change, reviews, and approvals.

Architecture governance increases accountability, improves decision-making, and reduces the risk of misaligned or failed initiatives.

Security Architecture

Security is a critical aspect of any enterprise architecture. TOGAF® includes guidelines for integrating security throughout the architecture lifecycle. This includes:

Identifying security requirements during early phases
Incorporating risk assessments into planning
Using security architecture views to show access controls, data protection, and compliance
Ensuring alignment with regulatory standards

By embedding security in the architecture, organizations can better protect their assets and maintain trust with stakeholders.

Interoperability and Integration

Modern enterprises rely on complex systems and diverse technologies. The TOGAF® Standard supports interoperability by promoting:

Standard interfaces and protocols
Shared data models and taxonomies
Modular building blocks
Clear architectural definitions and contracts

These practices help ensure that systems can work together, even when developed by different teams or vendors.

The TOGAF® Standard is more than just a methodology; it is a comprehensive framework that includes models, tools, governance practices, and reusable content structures. The concepts discussed in this section — including the content framework, architecture repository, enterprise continuum, building blocks, reference models, and governance mechanisms — equip organizations with a robust toolkit to handle complex enterprise transformations.

By mastering these core components, enterprise architects can improve alignment, reduce costs, and increase the strategic value of IT investments. These practices also help ensure that architecture is not a one-time activity but an ongoing discipline that supports continuous innovation and adaptability.

Applying the TOGAF® Standard in Real-World Scenarios

After exploring the foundational concepts, framework components, and strategic benefits of the TOGAF® Standard, it is crucial to understand how this standard is applied in real-world enterprise environments. This part focuses on practical implementation, industry use cases, challenges, and how organizations tailor the standard to meet specific business needs. The goal is to demonstrate the flexibility of the TOGAF® Standard and its effectiveness across various domains and industries.

Preparing for Implementation

Implementing the TOGAF® Standard is not a one-size-fits-all process. Organizations must begin by evaluating their current enterprise architecture maturity and setting realistic goals. The following steps typically guide organizations preparing for TOGAF® adoption:

Assessment of Readiness: Evaluate current business processes, IT systems, stakeholder alignment, and governance structures.
Defining Architecture Vision: Set clear goals and expected benefits of adopting TOGAF®. This includes outlining how architecture will support strategic business initiatives.
Establishing Architecture Board: Form a team responsible for architecture oversight, decision-making, and compliance.
Tool and Repository Selection: Choose tools that support architecture modeling, documentation, and collaboration.

Once the foundation is established, organizations can begin adopting the Architecture Development Method (ADM) in alignment with their internal processes.

Industry Use Cases of TOGAF® Implementation

1. Government and Public Sector

Government institutions use TOGAF® to streamline services, manage public resources, and improve IT governance. For example:

A federal agency uses TOGAF® to modernize legacy systems, enhance data sharing across departments, and improve security frameworks.
Municipal governments employ TOGAF® to align digital infrastructure projects with citizen services.

The TOGAF® Standard supports transparency, regulatory compliance, and interoperability among diverse agencies.

2. Healthcare Industry

In healthcare, TOGAF® helps integrate complex systems involving patient records, billing, diagnostics, and telemedicine. For example:

Hospitals implement TOGAF® to unify patient information across various departments, improving care delivery and operational efficiency.
Insurance providers use TOGAF® to develop architectures that support claims management, fraud detection, and data protection.

With patient data privacy regulations such as HIPAA, TOGAF® assists in embedding security into system design and architecture governance.

3. Financial Services

Banks and insurance companies adopt TOGAF® to improve agility, reduce risk, and innovate services. For example:

A retail bank uses TOGAF® to transition to cloud computing while maintaining compliance with financial regulations.
An investment firm integrates TOGAF® to streamline mergers and acquisitions, managing IT alignment between merged entities.

Financial institutions leverage the standard to respond quickly to market changes while ensuring system reliability and regulatory compliance.

4. Telecommunications

Telecom companies use TOGAF® to manage vast IT networks and deliver new digital services. Examples include:

A telecom provider uses TOGAF® to introduce 5G infrastructure with integrated service delivery platforms.
Architecture teams utilize the TOGAF® Standard to ensure interoperability between customer management, billing systems, and network operation centers.

TOGAF® enables these organizations to manage complex IT landscapes and roll out scalable services efficiently.

Tailoring the TOGAF® Standard

While TOGAF® provides a robust framework, it must be adapted to fit the unique needs of an organization. Tailoring can be done in the following ways:

Selective Application: Focus on specific phases of ADM that align with project needs.
Custom Templates: Develop organization-specific templates for architecture artifacts and deliverables.
Simplified Views: Use simplified architecture views for non-technical stakeholders.
Integration with Agile and DevOps: Combine TOGAF® with Agile methodologies and DevOps practices for iterative development.

For example, a company with a fast-paced product development environment might adapt ADM for shorter sprints and continuous integration.

Common Challenges in TOGAF® Implementation

Despite its benefits, organizations may face challenges while implementing the TOGAF® Standard:

1. Resistance to Change

Employees and departments may resist changes to processes and roles. Address this through:

Executive sponsorship
Change management initiatives
Regular communication and training

2. Complexity

TOGAF® is a comprehensive framework that can be overwhelming for newcomers. Simplify by:

Starting small with pilot projects
Using tailored versions of ADM
Training and certification programs

3. Lack of Skilled Resources

Enterprise architecture requires professionals trained in both business and IT domains. Solutions include:

Hiring certified TOGAF® professionals
Investing in internal training
Using external consultants for the initial phases

4. Poor Integration with Existing Processes

If TOGAF® is seen as separate from current practices, adoption may suffer. Improve this by:

Embedding TOGAF® within existing governance structures
Aligning it with other frameworks such as ITIL, COBIT, or PRINCE2
Demonstrating early wins to build momentum

Measuring the Success of TOGAF® Implementation

To assess the effectiveness of TOGAF® adoption, organizations should define and track key performance indicators (KPIs) such as:

Reduction in system redundancies
Time taken for project delivery
Alignment between IT and business goals
User satisfaction with architectural changes
Cost savings due to optimized resource usage

Periodic reviews and feedback loops help refine the architecture practice and sustain long-term benefits.

Certification and Career Opportunities

As the demand for enterprise architects grows, so does the value of professional TOGAF® certification. Individuals with TOGAF® credentials are often considered for roles such as:

Enterprise Architect
Solution Architect
IT Strategy Consultant
Chief Technology Officer (CTO)

These roles are essential in aligning IT capabilities with strategic goals, especially in large enterprises where complexity is high.

The certification is structured in two levels:

Foundation (Level 1): Covers the basic terminology, concepts, and structure of the TOGAF® Standard.
Certified (Level 2): Focuses on practical application and advanced knowledge of the ADM and TOGAF® components.

Professionals can pursue these certifications individually or through structured training programs.

Evolving Role of Enterprise Architecture

The role of enterprise architecture is changing with digital transformation. Today, architects are expected to:

Enable innovation by identifying emerging technologies
Support cloud transformation and platform modernization.
Ensure business continuity through scalable IT systems.
Lead cross-functional collaboration across IT, HR, operations, and marketing.

Enterprise architecture is now seen as a strategic discipline that bridges business vision and technological execution.

Real-World Tools Supporting TOGAF® Implementation

Several tools are available to help organizations implement TOGAF® efficiently. These tools offer features such as modeling, repository management, compliance checks, and stakeholder collaboration.

Popular enterprise architecture tools include:

ArchiMate-based modeling tools
Architecture modeling suites like BiZZdesign, Avolution ABACUS, and Orbus iServer
Integration with project management and IT service management platforms

These tools enhance the usability of TOGAF® and support large-scale enterprise architecture practices.

TOGAF® in Enterprise Strategy

The TOGAF® Standard continues to evolve to meet modern business demands. Future developments are likely to include:

Better alignment with Agile and DevOps
Enhanced support for cloud-native architectures
Focus on digital business models and transformation
More flexible guidance for small to medium-sized enterprises

As digital technologies continue to redefine business, TOGAF® will remain a key player in enabling structured, efficient, and scalable enterprise transformation.

The TOGAF® Standard provides a structured yet flexible approach for developing and managing enterprise architectures. Its real-world application across industries showcases its value in guiding organizations through complex technological and strategic transformations. By tailoring the framework to specific needs, managing adoption challenges, and leveraging skilled professionals and tools, enterprises can maximize their return on investment.

Whether you are a business leader seeking strategic clarity, a project manager improving service delivery, or an IT architect designing scalable solutions, the TOGAF® Standard offers a universal language and methodology to support success. In the next phase of your architectural journey, consider how TOGAF® principles can be embedded into your daily practices to build resilient, responsive, and results-oriented organizations.

Final Thoughts

The TOGAF® Standard has proven to be a cornerstone framework in the world of enterprise architecture, offering a structured methodology for aligning business goals with IT infrastructure. Its enduring relevance, from its origins in government frameworks to widespread adoption by Fortune 500 companies, showcases its adaptability and practical utility in real-world environments. Through its core framework—the Architecture Development Method (ADM)—and its defined architectural domains, TOGAF® provides a clear roadmap for organizations navigating the complexities of digital transformation, modernization, and strategic planning.

In today’s business climate, where rapid technological change is the norm, organizations are under continuous pressure to remain agile while maintaining governance, efficiency, and alignment across teams. The TOGAF® Standard meets these needs by offering a flexible structure that can be tailored to fit any industry or scale. Whether integrating legacy systems, migrating to cloud platforms, or improving communication between IT and business units, TOGAF® enables smoother execution and long-term success.

One of its greatest strengths lies in its holistic approach. Breaking enterprise architecture into business, application, data, and technology domains helps leaders understand the interdependencies within their operations. This comprehensive view is essential for making informed decisions, mitigating risks, and identifying growth opportunities. Furthermore, the standard’s emphasis on documentation, governance, and continuous improvement fosters transparency and accountability throughout the organization.

For individuals, obtaining certification in the TOGAF® Standard can significantly enhance career prospects. As businesses increasingly rely on architecture frameworks to drive change and ensure strategic alignment, certified professionals are in high demand. The TOGAF® certification validates not only technical knowledge but also strategic thinking—qualities essential for leadership roles in modern enterprises.

While adopting the TOGAF® Standard is not without challenges, such as organizational resistance, resource constraints, and the steep learning curve, it offers immense long-term value when applied thoughtfully. By focusing on business outcomes, building cross-functional collaboration, and investing in proper tools and training, organizations can overcome these barriers and embed architecture into their strategic fabric.

In summary, the TOGAF® Standard is more than just a set of guidelines, it’s a strategic enabler. It equips organizations with the principles, processes, and tools necessary to thrive in a complex digital world. As enterprises continue to evolve, those guided by a strong architectural foundation will be best positioned to adapt, innovate, and lead.