COMPEL Certification Body of Knowledge — Module 4.5: Industry Standards Development and Methodology Advancement
Article 6 of 10
A methodology that remains static in the face of evolving technology, emerging industries, and changing organizational needs is a methodology in decline. The EATP Lead's role as methodology steward includes the responsibility to extend and specialize COMPEL — developing industry-specific adaptations, domain-specific modules, and emerging-technology supplements that keep the framework relevant, comprehensive, and practically useful.
The Extension Imperative
COMPEL was designed as a general-purpose AI transformation methodology applicable across industries and organizational contexts. This generality is a strength — it provides a common framework that enables cross-industry learning, consistent professional certification, and universal governance principles. But generality is also a limitation. A financial services firm implementing AI for algorithmic trading faces fundamentally different challenges than a healthcare organization implementing AI for clinical decision support, and both differ from a manufacturing enterprise implementing AI for predictive maintenance.
The COMPEL core must remain general — preserving the common vocabulary, lifecycle structure, and governance principles that unify the profession. But the methodology must be complemented by domain-specific extensions that provide the specialized guidance each industry and application domain requires.
Types of Extensions
The EATP Lead should understand the taxonomy of methodology extensions:
Industry Verticals
Industry-specific extensions that address the unique regulatory environments, data characteristics, stakeholder dynamics, and value chains of specific sectors:
- Financial Services: Regulatory compliance (Basel, MiFID, SOX), model risk management (SR 11-7), algorithmic trading governance, anti-money laundering AI, credit decisioning fairness
- Healthcare and Life Sciences: Clinical AI governance, FDA regulatory pathways, patient data privacy (HIPAA), clinical trial AI applications, diagnostic AI validation
- Manufacturing: Industrial IoT integration, predictive maintenance, quality control AI, supply chain optimization, digital twin governance
- Public Sector: Government AI ethics frameworks, citizen impact assessment, procurement regulations, inter-agency data sharing, democratic accountability
- Energy and Utilities: Grid optimization, predictive asset management, environmental compliance, safety-critical AI systems
- Retail and Consumer: Customer personalization governance, demand forecasting, pricing optimization, privacy-compliant marketing AI
Technology Domains
Extensions that address specific AI technology categories:
- Generative AI: Content governance, hallucination management, intellectual property implications, responsible deployment of large language models
- Computer Vision: Surveillance and privacy, bias in visual recognition, safety-critical visual AI, autonomous vehicle governance
- Natural Language Processing: Conversational AI governance, content moderation, translation quality, sentiment analysis ethics
- Reinforcement Learning: Autonomous decision governance, reward function design, safety constraints, human oversight mechanisms
- Edge AI: Distributed governance, offline operation, data sovereignty at the edge, model update governance
Organizational Types
Extensions for specific organizational contexts:
- Startup and Scale-up: Lightweight governance for fast-moving organizations, minimum viable AI governance, scaling governance with organizational growth
- Government and Public Administration: Democratic accountability, public interest assessment, inter-agency coordination, citizen engagement
- Non-Profit and Social Enterprise: Impact-focused AI governance, ethical AI for social good, resource-constrained implementation
- Multinational Corporation: Cross-border governance, multi-jurisdictional compliance, cultural adaptation, global-local balance
The Extension Design Process
The EATP Lead should follow a structured process for designing methodology extensions:
Step 1: Domain Analysis
Conduct a comprehensive analysis of the target domain:
- Regulatory Landscape: What regulations, standards, and guidelines apply specifically to AI in this domain?
- Stakeholder Map: Who are the stakeholders, and what are their specific concerns about AI?
- Data Characteristics: What types of data are used, and what are the specific governance requirements?
- Risk Profile: What domain-specific risks does AI introduce or amplify?
- Value Drivers: How does AI create value in this domain, and what metrics matter?
- Maturity Context: Where is this domain in its AI adoption journey?
Step 2: Gap Analysis
Map the COMPEL core framework against domain-specific requirements:
- Which COMPEL domains are fully applicable as-is?
- Which domains require modification or supplementation?
- Which domain-specific requirements are not addressed by any COMPEL domain?
- What domain-specific terminology should be mapped to COMPEL vocabulary?
Step 3: Extension Design
Design the extension to address identified gaps:
Supplementary Domains: Additional maturity assessment domains specific to the target sector. For example, a healthcare extension might add domains for Clinical Validation, Patient Safety, and Regulatory Pathway Management.
Modified Assessment Criteria: Industry-specific criteria and evidence requirements for existing COMPEL domains. For example, the Data Governance domain in a financial services extension would include specific criteria for model risk management compliance.
Specialized Lifecycle Activities: Industry-specific activities within each COMPEL lifecycle stage. For example, the Calibrate stage in a public sector extension would include citizen impact assessment activities.
Domain-Specific Templates and Tools: Industry-adapted versions of COMPEL assessment tools, roadmap templates, governance frameworks, and reporting formats.
Regulatory Mapping: Explicit mapping between COMPEL governance requirements and domain-specific regulatory requirements, showing how COMPEL compliance supports regulatory compliance.
Step 4: Validation
Validate the extension through:
- Expert Review: Review by domain experts and experienced COMPEL practitioners
- Pilot Implementation: Application in 2-3 organizations within the target domain
- Feedback Integration: Incorporation of pilot findings into the extension design
- Peer Review: External review by independent methodology experts
Step 5: Publication and Maintenance
Publish the extension through appropriate channels:
- COMPEL body of knowledge supplementary publications
- Professional organization publications
- Conference presentations and workshop deliveries
- Standards body contributions where applicable
Establish a maintenance process that ensures the extension remains current as domain conditions evolve.
Extension Governance
The proliferation of extensions creates a governance challenge. Without central coordination, extensions may diverge from COMPEL core principles, use inconsistent terminology, or provide conflicting guidance. The EATP Lead should advocate for and participate in extension governance:
Extension Standards
Define standards that all extensions must meet:
- Alignment with COMPEL core principles and Four Pillars
- Consistent terminology and vocabulary mapping
- Backward compatibility with COMPEL core assessments
- Minimum quality criteria for supporting evidence and validation
- Maintenance commitment from extension authors
Extension Registry
Maintain a registry of approved extensions that includes:
- Extension name, scope, and target domain
- Author(s) and maintaining organization(s)
- Version history and current version
- Validation status and evidence
- Compatibility with COMPEL core version
Community Contribution Process
Define a process through which the COMPEL community can propose, develop, review, and publish extensions. This process should balance quality control with accessibility — enabling practitioners to contribute while ensuring that published extensions meet professional standards.
The EATP Lead as Extension Author
The EATP Lead is the natural author of COMPEL extensions. The EATP Lead possesses the deep methodology knowledge required for core alignment, the practical experience required for domain relevance, and the research skills (developed through Module 4.5) required for rigorous development.
The EATP Lead should identify one or two domains where their expertise and experience are deepest and develop authoritative extensions for those domains. Over a career, an EATP Lead might develop extensions for several industries or technology domains, each contributing to the body of knowledge and establishing the EATP Lead as a recognized authority in that intersection.
Looking Ahead
The next article, Module 4.5, Article 7: Building and Leading Professional Communities of Practice, addresses how the EATP Lead creates and sustains the professional communities that support methodology advancement, knowledge dissemination, and professional development. Communities of practice are the social infrastructure of the profession — without them, methodology extensions remain documents rather than lived practice.
© FlowRidge.io — COMPEL AI Transformation Methodology. All rights reserved.