COMPEL Certification Body of Knowledge — Module 3.6: Capstone — Enterprise Transformation Architecture
Article 2 of 10
The capstone project demands a specific organizational context — a real or realistically constructed enterprise for which the candidate will design a complete transformation architecture. This choice is not incidental. The organization selected shapes every dimension of the capstone: the strategic considerations, the assessment complexity, the roadmap design, the governance requirements, and the defensibility of the final architecture. Choosing well is the first act of professional judgment the capstone evaluates.
This article addresses the selection and scoping process: the criteria for choosing an appropriate organizational context, the scoping requirements that ensure sufficient complexity without unmanageable breadth, the ethical considerations that govern the use of real organizational data, and the alternative approaches available when confidentiality constraints prevent direct use of a client organization.
Selection Criteria
The capstone organization must be complex enough to require the full COMPEL framework — all Four Pillars of People, Process, Technology, and Governance; all 18 domains of the maturity model; the complete lifecycle of Calibrate, Organize, Model, Produce, Evaluate, and Learn — while remaining bounded enough that a single consultant can design a credible transformation architecture within the capstone timeline.
Organizational Scale
The capstone organization should be of sufficient scale that enterprise-level strategic considerations genuinely apply. A small startup does not require the multi-year, multi-business-unit transformation architecture that the capstone tests. A fifty-person technology company, however innovative, does not present the organizational complexity, governance requirements, or portfolio management challenges that define the EATE's domain.
The ideal capstone organization employs at least several hundred people, operates across multiple functions or business units, and faces the kind of structural complexity — reporting relationships, governance layers, budgeting processes, technology environments, regulatory obligations — that makes enterprise transformation genuinely challenging. Organizations with one thousand to fifty thousand employees typically provide the right level of complexity. Larger organizations can work but may require the candidate to scope the capstone to a major division or regional operation.
Industry Context
The industry context matters because it shapes the strategic, regulatory, and competitive dimensions of the transformation architecture. Industries with active regulatory landscapes — financial services, healthcare, government, energy — provide rich material for the governance and regulatory strategy components of the capstone, drawing on Module 3.4, Article 1: Governance as Strategic Advantage. Industries undergoing rapid technological disruption provide compelling strategic contexts. Industries with complex supply chains or multi-sided platforms provide opportunities to demonstrate ecosystem thinking, as developed in Module 3.1, Article 8: Ecosystem and Partnership Strategy.
There is no prescribed industry. Candidates should select industries they understand well enough to produce credible strategic analysis. Fabricating industry knowledge undermines the capstone's credibility. If the candidate's professional background is in financial services, a financial services organization is a natural choice. If the candidate has deep experience in manufacturing, a manufacturing enterprise provides authentic material. The capstone tests transformation architecture competency, not industry expertise, but it does require sufficient industry understanding to produce contextually sound recommendations.
AI Maturity Starting Point
The capstone organization should be at an early to intermediate stage of AI maturity — typically Level 1 (Foundational) to Level 3 (Defined) across most domains on the COMPEL maturity scale. An organization that is already at Level 4 (Advanced) or Level 5 (Transformational) across most domains does not present sufficient transformation scope for a compelling capstone. Conversely, an organization at the very earliest stages of AI awareness may lack the infrastructure and readiness data needed to design a credible architecture.
The most productive capstone contexts involve organizations that have made initial AI investments — perhaps launching pilot projects, establishing a data analytics function, or beginning to explore AI governance — but have not yet designed or executed an enterprise-wide transformation program. This provides the candidate with enough existing organizational reality to ground the assessment while leaving substantial architectural work to be done.
Data Accessibility
The candidate must have access to sufficient organizational data to produce a credible assessment and architecture. This does not require access to every internal document, but it does require enough information to characterize the organization's strategic position, organizational structure, technology environment, talent landscape, governance posture, and current AI capabilities across the 18 domains.
For candidates using their current or former employer, this data is typically accessible through direct experience. For candidates using a client organization (with appropriate permissions), engagement documentation provides a foundation. For candidates constructing a composite or fictional organization, the data must be fabricated with enough specificity and internal consistency to support rigorous analysis. The evaluation panel will probe the organizational context during the oral defense, and vague or internally contradictory descriptions undermine credibility.
Scoping the Capstone
Even within an appropriately sized organization, the capstone must be scoped carefully. The transformation architecture should be comprehensive enough to demonstrate mastery of the full COMPEL framework while focused enough to permit depth and rigor.
Geographic Scope
For multinational organizations, the candidate should define the geographic scope of the transformation architecture. A global transformation program spanning dozens of countries introduces complexity that may exceed what can be addressed with rigor in the capstone format. Scoping to a major region, a headquarters operation, or a defined set of markets is acceptable, provided the candidate addresses how the architecture would scale geographically as part of the strategic roadmap.
Business Unit Scope
For diversified organizations, the candidate may scope the capstone to a subset of business units. The scoping rationale should be strategic — selecting business units that represent the organization's primary value creation engines or that present the most compelling transformation opportunity. The candidate should address cross-business-unit considerations — shared services, enterprise governance, portfolio interdependencies — even if the detailed architecture focuses on a defined subset.
Temporal Scope
The capstone transformation architecture should cover a three-to-five-year horizon as the primary planning frame, consistent with the multi-year program design principles established in Module 3.1, Article 3: Multi-Year Transformation Program Design. The first twelve to eighteen months should be detailed with specific initiatives, milestones, and resource requirements. Years two through five should be designed at a higher level of abstraction, reflecting the inherent uncertainty of longer planning horizons while demonstrating strategic vision.
Functional Scope
The capstone must address all Four Pillars and all 18 domains. The candidate cannot scope out People, or Governance, or any individual domain. However, the depth of treatment may appropriately vary by domain. Domains that are central to the organization's transformation challenge warrant detailed analysis and architectural design. Domains that are less critical in the specific context can be addressed more concisely, provided the candidate demonstrates awareness of their relevance and articulates why lighter treatment is appropriate.
Using a Real Organization
Many candidates choose their current employer, a former employer, or a client organization as the capstone context. This has significant advantages: the candidate brings authentic knowledge of the organizational context, the assessment can draw on real data, and the resulting architecture may have practical applicability. However, using a real organization introduces ethical and confidentiality considerations that must be managed carefully.
Confidentiality Obligations
The candidate must ensure that the capstone project does not violate any confidentiality obligations — employment agreements, non-disclosure agreements, client contracts, or regulatory requirements. The capstone document will be reviewed by the evaluation panel, and potentially referenced in certification records. No proprietary information that the candidate is obligated to protect should appear in the capstone.
Practical approaches to managing confidentiality include:
Anonymization. The candidate uses the real organizational context but anonymizes the organization's name, specific product names, financial figures, and other identifying details. The evaluation panel understands that anonymization is standard practice and does not penalize it.
Aggregation and abstraction. Instead of reporting specific data points, the candidate presents aggregated or abstracted representations — maturity ranges rather than precise scores, directional strategic characterizations rather than specific financial targets, structural descriptions rather than detailed organizational charts.
Permission. In some cases, the candidate may obtain explicit permission from the organization to use organizational information in the capstone. This is the cleanest approach where feasible, but candidates should secure written authorization and understand its scope.
Ethical Considerations
Beyond contractual obligations, the candidate should consider whether the capstone could create reputational risk for the organization. An assessment that identifies significant governance gaps or leadership deficiencies, even if anonymized, could be identifiable to readers with industry knowledge. The candidate should exercise professional judgment, presenting honest analysis while avoiding unnecessary exposure of organizational vulnerabilities.
The ethical foundations of COMPEL consulting practice, established across the governance modules and reinforced in Module 3.5, Article 7: Methodology Innovation and Evolution, apply with particular force in the capstone context. The capstone should demonstrate ethical consulting practice, not merely analyze it abstractly.
The Composite Organization Approach
When confidentiality constraints prevent the use of a specific real organization, the candidate may construct a composite organization — a fictional entity that combines realistic elements drawn from the candidate's professional experience, industry knowledge, and published case studies.
The composite approach has distinct advantages. It eliminates confidentiality concerns entirely. It allows the candidate to design an organizational context that provides rich material across all dimensions of the COMPEL framework. It can incorporate elements from multiple organizations the candidate has worked with, creating a more comprehensive transformation challenge than any single organization might present.
The risks of the composite approach are fabrication and inconsistency. A composite organization must be internally consistent — its strategy, structure, culture, technology environment, industry context, and competitive position must cohere as a believable entity. The evaluation panel will probe the organizational context, and a composite that does not hold together under questioning will undermine the capstone's credibility.
Candidates using the composite approach should:
Ground the composite in reality. Base the organization on real industry dynamics, realistic organizational structures, and plausible strategic challenges. Reference published industry trends and known organizational patterns rather than inventing from whole cloth.
Document the organizational context thoroughly. Provide sufficient detail about the composite organization's history, strategy, structure, culture, technology environment, and competitive position that the evaluation panel can assess the capstone architecture against a well-defined context.
Maintain internal consistency. Ensure that every element of the composite — from the board's strategic priorities to the technology team's capability profile — fits together logically. An organization that simultaneously has a highly innovative culture and rigid change-resistant governance is not impossible, but such tensions must be acknowledged and addressed in the transformation architecture.
The Organizational Profile Document
Regardless of whether the candidate uses a real or composite organization, the capstone begins with an Organizational Profile Document that establishes the context for the transformation architecture. This document should address:
Organizational overview. Industry, size, structure, geographic footprint, primary products or services, and competitive positioning.
Strategic context. The organization's strategy, key strategic challenges, competitive dynamics, and the role that AI is expected to play in the organization's future.
Current AI landscape. The organization's current AI initiatives, capabilities, investments, and organizational posture toward AI. This provides the foundation for the assessment layer.
Stakeholder landscape. Key stakeholders, sponsors, and decision-makers relevant to AI transformation. The political and organizational dynamics that will shape transformation feasibility.
Regulatory and compliance context. Applicable regulations, industry standards, and compliance obligations that affect AI deployment and governance. This connects to the regulatory strategy work of Module 3.4.
Constraints and boundaries. Budget ranges, timeline expectations, known organizational constraints, and any factors that will bound the transformation architecture.
The Organizational Profile Document is not the capstone itself. It is the foundation upon which the capstone architecture is built. A well-crafted profile demonstrates the candidate's ability to characterize an organizational context with the precision and insight needed to design a credible transformation program — a skill fundamental to consulting practice at any level, but essential at the EATE level where the organizational contexts are the most complex.
Approval and Iteration
Before proceeding to the full capstone architecture, the candidate should have the organizational selection and scope reviewed — either by a faculty advisor, a mentor within the EATE program, or through a structured peer review process. This review serves two purposes: confirming that the selected organization and scope provide adequate material for a capstone-quality project, and identifying potential issues — insufficient complexity, confidentiality risks, scoping problems — before the candidate invests substantial effort in the architecture design.
This early review mirrors actual consulting practice. Before committing to a major engagement, the EATE consults with colleagues, validates assumptions, and confirms that the engagement scope is appropriate. The capstone process models this professional discipline.
The organizational selection and scoping phase sets the trajectory for the entire capstone project. A well-chosen organization with clearly defined scope enables the candidate to demonstrate the full range of EATE competencies. A poorly chosen context — too simple, too complex, too constrained by confidentiality, or too poorly understood — can undermine even the most methodologically sophisticated architecture. This first decision deserves the same care and judgment that the EATE would bring to scoping a real enterprise engagement.
Module 3.6, Article 2 of 10. Next: Module 3.6, Article 3: The Enterprise Transformation Architecture Framework.