Transformation Approaches

No single approach works for every organization or use case. Use this page to understand the mix; you will apply it during Implementation.

Approach Comparison

Approach	What It Is	Best For	Main Strength	Main Risk
Framework-driven	Use defined standards and operating rules from day one	Regulated and process-mature environments	Predictable and scalable	Can feel slow in discovery phases
Hierarchical (top-down)	Leadership-led prioritization and mandate	Enterprise-wide alignment programs	Strong direction and accountability	Can miss frontline reality
Pragmatic (bottom-up)	Use-case-first experimentation and iteration	Fast-moving teams and emerging needs	Fast learning and rapid value proof	Fragmentation if not coordinated
Governance and trust	Risk-tiered controls across lifecycle	High-impact or sensitive deployments	Trust, safety, and auditability	Excess control can slow innovation

When To Use Each

• Use Framework-driven when requirements and controls are clear.
• Use Hierarchical when coordination across many teams is the bottleneck.
• Use Pragmatic when uncertainty is high and learning speed is critical.
• Use Governance and trust for all approaches, with deeper controls for higher risk tiers.

Recommended Blend

1. Start pragmatic to discover high-value opportunities.
2. Apply hierarchical alignment to prioritize and fund.
3. Standardize with framework-driven delivery for scale.
4. Keep governance controls active through all stages.

Tailoring Guidance

Context	Delivery Bias
High uncertainty, low compliance burden	Adaptive and pragmatic
Moderate uncertainty, multi-team dependencies	Hybrid with hierarchical coordination
Low uncertainty, high compliance burden	Predictive and framework-driven

Reference alignment: PMBOK tailoring, ITIL service strategy, NIST AI RMF, ISO/IEC 42001.

Next Step

You have finished the Playbook reading pass. Continue to the Implementation Guide for the step-by-step delivery path.