Digital Strategy and Enterprise Scale · Module 1
Strategy and target state architecture
A target state keeps strategy concrete.
Previously
Start with Digitalisation Advanced
Look at digital roadmaps, operating models, governance, regulation and how to align data, architecture and people at sector or enterprise scale.
This module
Strategy and target state architecture
A target state keeps strategy concrete.
Next
Data sharing, models, and standards
At scale, digitalisation depends on shared meaning.
Progress
Mark this module complete when you can explain it without rereading every paragraph.
Why this matters
Strategy is a sequence of hard choices, not a list of everything you want.
What you will be able to do
- 1 Explain strategy and target state architecture in your own words and apply it to a realistic scenario.
- 2 A target state is a shared picture of how the system should work, not a vendor shopping list.
- 3 Check the assumption "Target is testable" and explain what changes if it is false.
- 4 Check the assumption "Ownership is clear" and explain what changes if it is false.
Before you begin
- Comfort with earlier modules in this track
- Ability to explain trade-offs and risks without jargon
Common ways people get this wrong
- Vendor-first target state. If the target state is vendor-first, it will not survive constraint changes.
- No migration plan. Without a migration plan, the target state remains aspirational.
Main idea at a glance
From vision to delivery
Four layers that connect strategic intent to operational reality. Click each to see what belongs inside.
Stage 1
Strategic vision
The strategic vision defines what success looks like in business terms. Not technology milestones, not project completions, but real outcomes. Revenue growth, customer satisfaction, cost reduction, risk mitigation, service reliability. Each vision element should be specific enough to measure and honest enough to fail.
I have seen too many strategies that describe a future state nobody can measure. If the vision cannot be expressed as a number that moves, it is not a strategy. It is a mood board.
Strategy without governance is a wish list. Governance without delivery is bureaucracy. All four layers must work together.
A target state keeps strategy concrete. A reference architecture keeps teams aligned as they deliver in parallel.
The hardest part is focus. You cannot improve every capability at once, so you choose the few that unlock the rest.
Target state view
Move from today to a focused future design.
Stage 1
Fragmented data
Data models are different across teams. The same entity has different names, different structures, and different update cadences in each system. Reports disagree because they pull from different versions of the truth.
This is the most common problem I see. Not because organisations are careless, but because they grew fast and each team solved their own data problem independently. That was rational at the time. It just does not scale.
The transition is not a big bang. Prioritisation decides the sequence. Get that wrong and you build the right thing in the wrong order.
Worked example. The target state that became a poster, not a plan
Worked example. The target state that became a poster, not a plan
A team produces a beautiful target state diagram. Everyone nods. Delivery then starts as twenty unrelated projects because nothing was prioritised and nothing had owners.
A target state earns its keep when it does three things. It forces choices, it sequences the work, and it makes accountability explicit. My opinion is that if the target state cannot answer “what do we do next quarter”, it is a picture, not architecture.
Common mistakes in target state work
Target-state anti-patterns
Avoid these traps when designing strategic architecture.
-
Listing everything instead of prioritising
Choose what unlocks outcomes first under real constraints.
-
Mixing capability, project, and tool
Keep these layers distinct so decisions stay coherent.
-
No operational model
Define how services are run, monitored, and supported.
-
No migration story
Document how you move safely from today to target state.
Verification. A target state quality bar
Target-state quality bar
Use this quality gate before approval.
-
Top three outcomes with evidence metrics
Define explicit proof for each strategic outcome.
-
Named capability owners
Assign owners beyond delivery roles to sustain operations.
-
Phased roadmap with dependencies
Include a risk register and sequencing logic.
-
Explicit stop-doing list
Free capacity by ending low-value work intentionally.
Reflection prompt
If you could only fix one capability that would reduce chaos for everyone, what would it be. Choose one from identity, data quality, integration, monitoring, or decision rights. Why that one.
Mental model
Target state
A target state is a shared picture of how the system should work, not a vendor shopping list.
-
1
Current state
-
2
Gaps
-
3
Target state
-
4
Steps
Assumptions to keep in mind
- Target is testable. If the target is not testable, teams interpret it differently.
- Ownership is clear. A target state without owners becomes a document, not a plan.
Failure modes to notice
- Vendor-first target state. If the target state is vendor-first, it will not survive constraint changes.
- No migration plan. Without a migration plan, the target state remains aspirational.
Key terms
- target state
- The future view of how services, data, and operating models should work together.
- reference architecture
- A shared blueprint that shows the major components and how they connect.
Check yourself
Quick check. Strategy and target state
0 of 6 opened
Why is a target state useful
It keeps strategy concrete and aligns teams on a shared future view.
What does a reference architecture provide
A shared blueprint for how major components connect and what should stay stable.
Scenario. Everyone loves the target state diagram, but delivery starts as twenty unrelated projects. What was missing
Sequencing and decision rights. The target state needed priorities, owners, and a next quarter plan, not only a picture.
What should guide capability choices
Which changes unlock the most outcomes and reduce risk, given real constraints.
Why is ownership part of the target state
Unclear ownership makes delivery and governance fragile over time.
What keeps a target state credible
Clear priorities, phased delivery, measurable outcomes, and an honest migration plan.
Artefact and reflection
Artefact
A concise design or governance brief that can be reviewed by a team
Reflection
Where in your work would explain strategy and target state architecture in your own words and apply it to a realistic scenario. change a decision, and what evidence would make you trust that change?
Optional practice
Score key capabilities today versus the target and spot the largest gaps.