How progress is measured
The Cloud Value Journey shows where you are and what comes next.
A five-stage path from a cloud you can trust to a cloud that changes what your organization can do. It shows where you are, what comes next, and how progress is measured.
-
Foundation
Can we trust the foundation?
-
Acceleration
Can we move fast without fear?
-
Innovation
Is technology improving what we deliver?
-
Optimization
Is cloud invisible and efficient?
-
Transformation
Is technology changing what's possible?
The five stages
Each stage answers one question.
Find the question your leadership is asking today. That is your stage.
Foundation
Can we trust the foundation?
Where you are
New to cloud, or struggling with basic operations.
What changes
A secure, compliant, cost-controlled environment with clear governance.
For example Moving a workload off aging hardware into an environment that passes its audit and has a budget someone owns.
What we measure Audit findings, open critical security events, and whether spend is visible and attributed.
Why this matters to your board The board can be told, with evidence, that patient data is protected and that cloud spending has an owner.
Acceleration
Can we move fast without fear?
Where you are
The foundation is solid but slow to change.
What changes
Automation, infrastructure as code, and compliance checks built into delivery.
For example Replacing hand-built servers with infrastructure as code, so a new environment takes minutes and arrives compliant.
What we measure How long a change takes to reach production, and how many changes need rework.
Why this matters to your board Initiatives the board has approved reach production sooner, and risk does not rise with the pace.
Innovation
Is technology improving what we deliver?
Where you are
Operations are efficient but not creating an advantage.
What changes
Analytics, AI, and new digital services built on the platform.
For example Standing up an analytics environment or an AI service on the platform, with the controls already in place.
What we measure New services delivered, and the clinical, member, or customer measure each one was built to move.
Why this matters to your board Technology spending shows up in the measures the board already reviews: care, member experience, or growth.
Optimization
Is cloud invisible and efficient?
Where you are
Cloud is driving some new work.
What changes
Cost, performance, and operations tuned so the cloud stops being a topic.
For example Tuning the cost and performance of what now runs at scale, and automating the operations around it.
What we measure Cost per unit of work, such as per member, per message, or per transaction, and time spent on routine operations.
Why this matters to your board Margin improves as volume grows, and the cloud comes off the list of things the board has to ask about.
Transformation
Is technology changing what's possible?
Where you are
Among the leaders in its field.
What changes
Technology shapes strategy and new business models.
For example Offering a data product or a new line of service that the organization could not have run before.
What we measure Revenue, reach, or outcomes from services that did not exist at the start.
Why this matters to your board Technology becomes a source of new revenue and reach, where it used to be a cost to govern.
The examples, measures, and board notes above are illustrations. The measures used in your value reviews are the ones your leadership already tracks, agreed with your Cloud Value Architect.
How to read the order.
Why Innovation comes before Optimization
Basic cost control belongs to Foundation, so it is in place from the start. Optimization is a later and different job: tuning what runs at scale until the cloud stops being a topic. That tuning pays off once there are new services worth tuning, which is why building them comes first.
What overlaps
The stages are not gates. Security, compliance, and cost discipline start in Foundation and never stop. An organization can be at Innovation for one system and Foundation for another, and a stage is never finished so much as it stops being the main question.
How progress is measured
By the question your leadership can now answer yes to, and by a small set of measures agreed at the start. Your Cloud Value Architect reports against them in each value review, and the self-assessment gives a first read in about two minutes.
Who owns it
One person owns your progress.
A Cloud Value Architect is the person accountable for your progress along the Cloud Value Journey.
They learn what your organization is trying to achieve, turn the technical work into a plan tied to those goals, and report results in regular value reviews. They are measured on your outcomes, not on SLA adherence.
What a value review covers
- The goals your leadership set, and where each one stands.
- What changed in the environment since the last review, and why it mattered.
- Problems and opportunities we found before you had to ask.
- The next step on the journey, and what it would take.
What a value review looks like.
Each change is recorded three ways: what was done, why it mattered, and who it affected. Each goal carries measures with a baseline, a current reading, a target, an owner, and a date.
Illustrative example, not a customer result
| What was done | Why it mattered | Who it affected |
|---|---|---|
| Backup schedules and retention moved from manual steps to automated lifecycle rules. | Lower risk of data loss, and evidence for the backup controls is produced without anyone collecting it. | Compliance officer, platform engineers |
| Environment builds moved to infrastructure as code with compliance checks in the pipeline. | A new environment arrives compliant, so releases stop waiting on a manual review. | Engineering leads, product owners |
| Three unused environments found and shut down. | Spend goes to the work in progress, and there is less to secure. | Finance, security |
| Measure | Baseline | Now | Target | Owner | Next review |
|---|---|---|---|---|---|
| Engineer hours a month spent collecting audit evidence | 60 | 22 | 10 or fewer | Compliance officer | Next quarterly review |
| Days from a release being ready to its compliance sign-off | 9 | 3 | 1 | Engineering lead | Next quarterly review |
Next step Agree the two measures that will show Innovation has started, and pick the first service to build.
Not in the cloud yet?
Then the journey starts with the reason for going.
Organizations that have not yet made the move begin at Foundation, with one advantage: the migration can be built for the outcome from the first day, so there is no old scorecard to unlearn.