Implementation guide
Seven phases, three rings
The implementation cycle asks seven questions in order. One full turn of the cycle should take no more than six months, so that momentum and support are not lost. Larger initiatives are split into several iterations.
The seven phases
01What are the drivers?Recognize the need to act. Outline business case, stakeholder map and a wake-up call for management.Phase 102Where are we now?Assess the current state. Selected objectives, current performance levels and a risk profile.Phase 203Where do we want to be?Define the target state and analyze the gaps. Target levels, improvement opportunities and a detailed business case.Phase 304What needs to be done?Design and build improvements. Project definitions, change response plans and success metrics.Phase 405How do we get there?Implement improvements. Implemented improvements and realized quick wins.Phase 506Did we get there?Operate and measure. Updated scorecards and measures of how well the change took hold.Phase 607How do we keep the momentum going?Monitor and evaluate. Recommendations, lessons learned and a satisfaction survey.Phase 7
Three rings
Program management
The outer ring. It starts, plans, runs and reviews the program.
Change enablement
The middle ring. It prepares people and keeps them committed to the move from the current state to the future state.
Continual improvement life cycle
The inner ring. It assesses, designs, builds, operates and measures the improvements themselves.
Trigger events
- Mergers and acquisitions
- A shift in the market
- A new operating or sourcing model
- New regulation
- A significant technology change
- New leadership
- External audits
- A new enterprise strategy
- A large digital transformation initiative, including AI at scale (new in COBIT 7)
- Pressure to demonstrate digital trust, ESG and responsible use of technology (new in COBIT 7)
Triggers connect to the design factors: when a design factor changes, governance is reviewed.
Pain points added in COBIT 7
30 in total, up from 20
- Technical debt
- Serious security incidents such as ransomware and phishing
- I&T initiatives with no link to strategy
- Recurring incidents with no root cause found
- Inaccurate I&T inventories
- Slow recovery from incidents
- Poor cloud management
- Underinvestment in modernization and security
- Mishandling of personal data
- Low digital literacy