The EII Enterprise Development Lifecycle
The EII Enterprise Development Lifecycle is a governed, evidence-based method for understanding, developing, restoring, and sustaining an enterprise. It combines clinical thinking, human accountability, and AI-assisted analysis to connect enterprise conditions with coordinated action and measurable outcomes.
Think Clinically. Act Critically. Decide Intelligently.
AI-driven: every EDL engagement has an embedded assistant that advises and drafts evidence, findings, and interventions from the member's authorized context — while a named human approves every decision gate. AI never approves a decision or accepts risk.
EDL is a proposed EII methodology under development. It is not an accredited standard, scientifically validated framework, regulatory certification, or proven replacement for established frameworks. Software development is one activity within enterprise development; SDLC, secure SDLC, project delivery, and service management are positioned as supporting execution methods within relevant EDL interventions.
Three pathways through one method
Pathways change assessment priorities, evidence requirements, and intervention patterns. They do not assume growth is always the desired outcome — consolidation, transition, capability retirement, and orderly exit are supported where appropriate.
Genesis
Startup, capability formation, and accelerated growth.
Phoenix
Turnaround, disruption recovery, and realignment.
Continuing Wellness
Sustaining success, adaptation, and renewal.
Six repeatable phases
Each phase has required outputs and a human decision gate. Gates may be approved, conditionally approved, rejected, or returned. An urgent incident may proceed under existing emergency authority while EDL coordinates broader recovery and learning.
Establish Context
Define mission, business model, enterprise condition, scope, stakeholders, obligations, constraints, decision authority, baseline measures, and information permissions.
- Engagement charter
- Accountable sponsor
- Scoped enterprise profile
- Authorized evidence plan
- Success criteria
Sponsor approves scope; designated data owners authorize access.
Examine
Collect authorized evidence and stakeholder perspectives. Examine capabilities, processes, resources, dependencies, and conflicting information.
- Evidence register
- Enterprise capability and dependency map
- Documented gaps
- Stakeholder observations
Domain owners validate facts and limitations. Insufficient evidence triggers further examination or an explicitly bounded assessment.
Assess
Develop and compare explanations. Identify systemic causes, strengths, risks, readiness constraints, and cross-functional consequences.
- Reviewed findings
- Alternative explanations
- Uncertainty statements
- Priorities
- Baseline condition assessment
Accountable reviewers accept, challenge, or return findings for further examination.
Prescribe
Compare intervention options, including taking no action. Evaluate cost, benefit, dependencies, capacity, control requirements, and unintended consequences.
- Approved intervention plan
- Owners
- Resources
- Sequencing
- Decision rationale
- Outcome measures
- Rollback or contingency provisions
Authorized leaders approve commitments and risk treatment within delegated authority.
Execute
Coordinate approved interventions through appropriate delivery methods. Track dependencies, changes, exceptions, operational readiness, and control evidence.
- Delivery records
- Implementation evidence
- Readiness decisions
- Updated procedures
- Exception records
Designated authorities approve consequential changes and operational acceptance.
Reassess and Learn
Compare actual outcomes with baselines and targets. Review residual risk, conduct AARs, capture lessons, and update enterprise understanding.
- Validated outcome review
- Updated enterprise record
- Lessons
- Reassessment date or trigger
Accountable leaders choose to sustain, revise, re-examine, pause, or retire.
Twelve connected assessment domains
Assessment depth follows scope, materiality, access permissions, and risk. An enterprise need not upload all its information or complete every question.
Mission and strategy
Mission, business model, strategic intent, and enterprise condition framing.
Governance, legal, and ethics
Governance authority, legal obligations, ethics, and accountability.
Finance and resources
Financial position, capital, resource allocation, and viability.
People, leadership, and culture
Leadership, workforce, culture, and capability.
Operations and quality
Operational processes, quality, and delivery.
Customers, markets, and stakeholders
Customers, markets, stakeholders, and reputation.
Products and services
Products, services, value propositions, and lifecycle.
Technology and architecture
Technology estate, architecture, and platforms.
Data and AI
Data, AI systems, and information assets.
Cybersecurity and privacy
Security controls, privacy, and protection.
Partners and supply chain
Suppliers, partners, and supply chain dependencies.
Resilience, facilities, and continuity
Resilience, continuity, facilities, and recovery.
Foundational distinctions
EDL keeps seven distinctions separate rather than combining them into a single unexplained health score: enterprise condition, lifecycle phase, enterprise domain, capability maturity, readiness, risk, and evidence confidence. Different business units and capabilities within one enterprise may have different conditions and active lifecycle engagements.
Enterprise condition
The circumstances requiring attention.
Lifecycle phase
The work currently being performed.
Enterprise domain
The area being examined.
Decision gate
Human approval, rejection, or return.
Think Clinically. Act Critically. Decide Intelligently.
EDL connects enterprise conditions with coordinated action and measurable outcomes — governed, evidence-based, and accountable to authorized human owners.
Find the right membership