COMPEL Certification Body of Knowledge — Module 4.6: The EATP Lead Capstone — Portfolio Defense and Leadership Synthesis
Article 4 of 10
Framework interoperability is a defining competency of the EATP Lead — the ability to integrate COMPEL with other enterprise frameworks to create unified transformation approaches that leverage each framework's strengths. The capstone portfolio must demonstrate this competency with rigor and specificity, showing not merely that multiple frameworks were present in the engagement but that they were deliberately integrated into a coherent operating model.
What the Panel Evaluates
The examination panel assesses framework interoperability across several dimensions:
Integration Depth: Did the candidate superficially reference other frameworks, or did they design specific integration mechanisms — shared processes, aligned governance, unified terminology, integrated tooling — that created genuine interoperability?
Framework Knowledge: Does the candidate demonstrate genuine understanding of the partner frameworks, or merely surface-level familiarity? The panel will probe the candidate's knowledge of specific framework elements and how they interact with COMPEL.
Design Rationale: Can the candidate articulate why specific integration decisions were made? What trade-offs were considered? What alternatives were evaluated and rejected?
Practical Impact: Did framework interoperability produce measurable benefits — reduced duplication, faster delivery, better governance, improved stakeholder buy-in — or was it a theoretical exercise?
Required Framework Integration Evidence
The portfolio must demonstrate integration with at least two frameworks beyond COMPEL. The candidate should select frameworks that were genuinely relevant to the engagement rather than artificially introducing frameworks for the sake of the capstone requirement.
For each integrated framework, the portfolio must include:
Integration Architecture Document
A structured document that maps the integration between COMPEL and the partner framework:
Conceptual Mapping: How do the frameworks' core concepts align? Where are they complementary? Where do they overlap or conflict?
For example, a COMPEL-SAFe integration architecture might map:
| COMPEL Element | SAFe Element | Integration Approach |
|---|---|---|
| Calibrate stage | PI Planning inputs | Assessment results feed PI objectives |
| Organize stage | ART design | Transformation architecture informs ART structure |
| COMPEL governance | Lean governance | Unified governance council |
| 18-domain maturity | SAFe Business Agility | Cross-referenced maturity dimensions |
| Evaluate stage | Inspect & Adapt | Integrated measurement and retrospective |
Process Integration: Which processes are shared, which are framework-specific, and how do handoffs work? Process integration should be documented at a level of detail that would allow another practitioner to replicate the approach.
Governance Integration: How are governance structures aligned? Are there unified governance bodies, or parallel structures with defined coordination mechanisms?
Tooling Integration: How do the tools and artifacts used by each framework interact? Are there shared repositories, integrated dashboards, or common data models?
Terminology Reconciliation: Where do the frameworks use different terms for similar concepts? A terminology glossary that maps equivalent terms prevents confusion and miscommunication.
Integration Decision Log
A documented record of key integration decisions, including:
- The decision point (what needed to be decided)
- The options considered
- The criteria used to evaluate options
- The decision made and its rationale
- The outcome (if known at the time of portfolio preparation)
The decision log demonstrates the candidate's analytical process and provides the panel with specific decisions to probe during the defense.
Integration Outcomes
Documented evidence that framework interoperability produced value:
- Quantitative outcomes where measurable (time saved, costs reduced, quality improved)
- Qualitative outcomes where quantification is not possible (stakeholder satisfaction, governance coherence, reduced confusion)
- Honest assessment of integration challenges and how they were addressed
Common Framework Integration Patterns
The candidate should demonstrate familiarity with established integration patterns and explain how they applied or adapted them:
COMPEL + SAFe
Integration Pattern: COMPEL provides the strategic architecture and maturity assessment framework; SAFe provides the agile delivery mechanism. COMPEL's Calibrate and Organize stages inform SAFe's portfolio and program levels. COMPEL's Evaluate and Learn stages integrate with SAFe's Inspect and Adapt ceremonies.
Key Integration Points:
- COMPEL maturity assessments inform SAFe portfolio backlogs
- COMPEL governance structures align with SAFe Lean Portfolio Management
- COMPEL's four pillars map to SAFe's core competencies
- COMPEL evaluation metrics integrate with SAFe OKRs and KPIs
COMPEL + TOGAF
Integration Pattern: COMPEL provides the AI transformation methodology; TOGAF provides the enterprise architecture methodology. COMPEL's technology and governance architecture dimensions align with TOGAF's Architecture Development Method (ADM).
Key Integration Points:
- COMPEL's Organize stage maps to TOGAF's Architecture Vision and Business Architecture phases
- COMPEL's technology domains align with TOGAF's Technology Architecture phase
- COMPEL's governance architecture integrates with TOGAF's Architecture Governance
- COMPEL maturity targets inform TOGAF's target architecture
COMPEL + ITIL 4
Integration Pattern: COMPEL provides the transformation methodology; ITIL 4 provides the service management framework for operationalizing AI capabilities through its Service Value System (SVS). COMPEL's Produce stage transitions into ITIL 4 service value chain activities. COMPEL's governance integrates with ITIL 4's guiding principles and governance practices.
Key Integration Points:
- COMPEL's Produce stage maps to ITIL 4's Obtain/Build and Deliver and Support value chain activities
- AI model operations align with ITIL 4 practices such as Service Level Management, Monitoring and Event Management, and Incident Management
- COMPEL's Learn stage aligns with ITIL 4's Continual Improvement practice and the Improve value chain activity
- AI governance integrates with ITIL 4's guiding principles (Focus on Value, Start Where You Are, Collaborate and Promote Visibility) and its 34 management practices
COMPEL + COBIT
Integration Pattern: COMPEL provides AI-specific transformation methodology; COBIT provides the enterprise IT governance framework. COMPEL governance dimensions align with COBIT governance objectives.
Key Integration Points:
- COMPEL's governance pillars map to COBIT governance and management objectives
- COMPEL's maturity model aligns with COBIT's capability model
- COMPEL's risk management integrates with COBIT's risk optimization goal
- COMPEL's stakeholder management aligns with COBIT's stakeholder needs cascade
COMPEL + ISO 42001
Integration Pattern: COMPEL provides the implementation methodology; ISO 42001 provides the management system standard. COMPEL's governance and organizational dimensions map to ISO 42001 clauses.
Key Integration Points:
- COMPEL's governance domains map to ISO 42001 clauses 4-10
- COMPEL's maturity assessment informs ISO 42001 gap analysis
- COMPEL's lifecycle supports ISO 42001 Plan-Do-Check-Act cycle
- COMPEL's four pillars align with ISO 42001's resource and operational requirements
Avoiding Common Pitfalls
Superficial Integration
The most common pitfall is claiming framework integration when what actually happened was parallel use of frameworks without genuine integration. The panel will distinguish between:
- "We used SAFe for delivery and COMPEL for AI governance" (parallel use, not integration)
- "We designed unified governance councils, aligned planning cadences, and created shared metrics dashboards that integrated COMPEL maturity data with SAFe velocity metrics" (genuine integration)
Framework Overload
Demonstrating integration with too many frameworks can result in shallow treatment of each. It is better to demonstrate deep, rigorous integration with two frameworks than superficial reference to five.
Ignoring Tensions
Frameworks sometimes conflict — in terminology, in assumptions, in recommended practices. The strongest portfolios acknowledge these tensions and explain how they were resolved. Pretending that all frameworks harmonize perfectly is not credible.
Missing the Organizational Dimension
Framework interoperability is not merely a methodological exercise — it is an organizational challenge. Different teams within the organization may be aligned with different frameworks and may resist integration. The portfolio should address how organizational resistance to framework integration was managed.
Looking Ahead
The next article, Module 4.6, Article 5: The Governance Harmonization Artifact, addresses the portfolio component that demonstrates the candidate's ability to design and implement cross-organizational governance architectures — harmonizing AI governance across organizational boundaries, regulatory jurisdictions, and institutional cultures.
© FlowRidge.io — COMPEL AI Transformation Methodology. All rights reserved.