Skills

Build a Strategy Implementation Roadmap

10 weeks · 0 milestones

Translate a strategic direction into a concrete 12-month implementation plan for a real organisation — specifying milestones, accountable owners, budget assumptions, resource requirements, and a risk register with mitigation plans. The plan must be tied to a real named organisation and a specific strategic context, not a generic template. Proof requires review by a practitioner who can confirm the roadmap is grounded in the organisation's real constraints and that the budget and resource assumptions are defensible.

Part of: Business & Management · Proves for: UG

Milestone map

3 milestones

Define the Strategic Initiative and Stakeholder Landscape

1–2 weeks

Select a real strategic initiative that requires a structured implementation roadmap — a technology implementation, an organisational change programme, a market entry, or a product launch. Define the initiative scope, objectives, and success metrics. Map the stakeholder landscape: who benefits, who is at risk, who has decision authority.

Proof required

Submit: (a) an initiative brief (minimum 500 words) describing the initiative, objectives, and measurable success criteria, (b) a stakeholder map categorising stakeholders by influence and impact (using a power-interest matrix or equivalent), and (c) a change readiness assessment identifying the top two or three organisational obstacles to successful implementation.

What gets checked

Initiative is real — not a hypothetical exercise
Success criteria are measurable — 'improve customer satisfaction' is not measurable; 'achieve NPS of 45+ within 6 months of launch' is
Change readiness assessment identifies specific organisational obstacles, not generic change management challenges

Common mistakes

Success criteria are aspirational rather than measurable
Stakeholder map includes only the obvious stakeholders — the most important analysis is identifying hidden stakeholders (those who will be affected but have not been consulted)

Powstik Guide

An initiative brief and a stakeholder map.

Steps

State the initiative and its goal.
Set measurable success criteria.
List every stakeholder group.
Rate each by influence and interest.

Template

Initiative:
Success criteria:
| Stakeholder | Influence | Interest | Approach |
|-------------|-----------|----------|----------|

What gets sent back

Brief under 500 words.
Success criteria not measurable.
Stakeholders not rated.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Challenge the success criteria: 'Your success metric is 'system is live by Q3' — but is on-time delivery sufficient for success? What user adoption or business outcome metrics will tell you whether the initiative succeeded?'

You'll sign in first, then come straight back here.

Build the Phased Implementation Roadmap with Dependencies and Risks

3–4 weeks

Build a phased implementation roadmap with milestones, dependencies between phases, resource requirements for each phase, and a risk register. The roadmap must include a critical path analysis identifying the sequence of activities that determines the minimum implementation timeline.

Proof required

Submit: (a) a phased roadmap spanning the full implementation with at least three phases, showing milestones, activities, and durations (Gantt or equivalent format), (b) a dependency map showing the five most critical cross-phase dependencies, (c) a resource plan by phase (headcount and cost by function), and (d) a risk register covering the top five risks with probability, impact, and mitigation strategy.

What gets checked

Roadmap phases are defined by genuine phase gates, not arbitrary time boxes
Critical path is identified — not just a list of activities
Risk register assesses probability AND impact — not just lists risks

Common mistakes

Roadmap phases with no defined phase gate criteria — phases should end when specific deliverables or decisions are complete
Risk register missing the interconnection between risks — a single trigger risk that creates cascading secondary risks is much more dangerous than five independent low-probability risks

Powstik Guide

A phased roadmap with a critical path and risk register.

Steps

Split the work into at least three phases.
Define each phase gate as a decision or deliverable.
Map the five dependencies that cross phases.
Find the critical path: the chain that sets the end date.
Cost each phase by function.
Score the top five risks by probability and impact.

Template

| Phase | Gate (deliverable or decision) | Key activities | Duration | Depends on | Cost |
|-------|--------------------------------|----------------|----------|------------|------|

Critical path:

| Risk | Probability (1–5) | Impact (1–5) | Score | Mitigation | Triggers other risks? |
|------|-------------------|--------------|-------|------------|-----------------------|

What gets sent back

Phases defined only by dates.
No critical path, just an activity list.
Risks without probability and impact.

Resources

Foundationstart here

Depthgo deeper

Masteryfor the dedicated

What a verifier looks for

Challenge the critical path: 'You've identified X as the critical path — but your dependency map shows that Y also blocks Phase 3. If Y slips, does the critical path change? Walk me through how you handle that scenario.'

You'll sign in first, then come straight back here.

Present the Roadmap to a Change or Programme Management Professional

1 week

Present the implementation roadmap to a programme manager, management consultant, or senior project manager who will challenge at least two of your phase gate criteria or risk mitigation strategies.

Proof required

Submit: (a) Q&A log from the review session (minimum 300 words with at least two challenges and responses), and (b) attendance record with reviewer name and credentials.

What gets checked

Reviewer has programme or change management expertise
Q&A log shows challenges to roadmap logic, not just clarifying questions
Responses address the structural challenges analytically

Common mistakes

Review session with a project coordinator rather than a senior programme manager
Challenges met with 'we'll address that during implementation' rather than analytical engagement

Powstik Guide

Your roadmap, challenged by a programme manager.

Steps

Mark the gate and the risk you are least sure about.
Book a programme manager, consultant or senior project manager.
Ask them how many parallel tracks your organisation can run.
Log two challenges and your answers.
Adjust the timeline if the answer changes it.

Template

Review session log
Date:            Duration:
Reviewer name:
Reviewer role and years of experience:

Challenge 1 (a phase gate or mitigation):
  What they asked:
  My answer:
  Did it hold? What would I change?

Challenge 2:
  What they asked:
  My answer:
  Did it hold? What would I change?

Change I made after the session:
Reviewer's overall view (their words):

What gets sent back

A junior coordinator instead of a senior programme manager.
Answers like 'we'll handle that later'.
Fewer than two challenges logged.

Resources

Foundationstart here

Depthgo deeper

Masteryfor the dedicated

What a verifier looks for

Your most valuable challenge: 'Your Phase 2 has eight parallel workstreams — in your experience, what's the realistic maximum number of parallel tracks an organisation of this size can successfully manage, and how does that affect your timeline estimate?'
Provide written confirmation (minimum 150 words) of your programme management credentials and the challenges raised.

You'll sign in first, then come straight back here.

Part of

Prove Your Business Strategy Chops →

Related outcomes

Milestone map

3 milestones

Define the Strategic Initiative and Stakeholder Landscape

1–2 weeks

Proof required

What gets checked

Initiative is real — not a hypothetical exercise
Success criteria are measurable — 'improve customer satisfaction' is not measurable; 'achieve NPS of 45+ within 6 months of launch' is
Change readiness assessment identifies specific organisational obstacles, not generic change management challenges

Common mistakes

Success criteria are aspirational rather than measurable
Stakeholder map includes only the obvious stakeholders — the most important analysis is identifying hidden stakeholders (those who will be affected but have not been consulted)

Powstik Guide

An initiative brief and a stakeholder map.

Steps

State the initiative and its goal.
Set measurable success criteria.
List every stakeholder group.
Rate each by influence and interest.

Template

Initiative:
Success criteria:
| Stakeholder | Influence | Interest | Approach |
|-------------|-----------|----------|----------|

What gets sent back

Brief under 500 words.
Success criteria not measurable.
Stakeholders not rated.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Challenge the success criteria: 'Your success metric is 'system is live by Q3' — but is on-time delivery sufficient for success? What user adoption or business outcome metrics will tell you whether the initiative succeeded?'

You'll sign in first, then come straight back here.

Build the Phased Implementation Roadmap with Dependencies and Risks

3–4 weeks

Proof required

What gets checked

Roadmap phases are defined by genuine phase gates, not arbitrary time boxes
Critical path is identified — not just a list of activities
Risk register assesses probability AND impact — not just lists risks

Common mistakes

Roadmap phases with no defined phase gate criteria — phases should end when specific deliverables or decisions are complete
Risk register missing the interconnection between risks — a single trigger risk that creates cascading secondary risks is much more dangerous than five independent low-probability risks

Powstik Guide

A phased roadmap with a critical path and risk register.

Steps

Split the work into at least three phases.
Define each phase gate as a decision or deliverable.
Map the five dependencies that cross phases.
Find the critical path: the chain that sets the end date.
Cost each phase by function.
Score the top five risks by probability and impact.

Template

| Phase | Gate (deliverable or decision) | Key activities | Duration | Depends on | Cost |
|-------|--------------------------------|----------------|----------|------------|------|

Critical path:

| Risk | Probability (1–5) | Impact (1–5) | Score | Mitigation | Triggers other risks? |
|------|-------------------|--------------|-------|------------|-----------------------|

What gets sent back

Phases defined only by dates.
No critical path, just an activity list.
Risks without probability and impact.

Resources

Foundationstart here

Depthgo deeper

Masteryfor the dedicated

What a verifier looks for

Challenge the critical path: 'You've identified X as the critical path — but your dependency map shows that Y also blocks Phase 3. If Y slips, does the critical path change? Walk me through how you handle that scenario.'

You'll sign in first, then come straight back here.

Present the Roadmap to a Change or Programme Management Professional

1 week

Present the implementation roadmap to a programme manager, management consultant, or senior project manager who will challenge at least two of your phase gate criteria or risk mitigation strategies.

Proof required

Submit: (a) Q&A log from the review session (minimum 300 words with at least two challenges and responses), and (b) attendance record with reviewer name and credentials.

What gets checked

Reviewer has programme or change management expertise
Q&A log shows challenges to roadmap logic, not just clarifying questions
Responses address the structural challenges analytically

Common mistakes

Review session with a project coordinator rather than a senior programme manager
Challenges met with 'we'll address that during implementation' rather than analytical engagement

Powstik Guide

Your roadmap, challenged by a programme manager.

Steps

Mark the gate and the risk you are least sure about.
Book a programme manager, consultant or senior project manager.
Ask them how many parallel tracks your organisation can run.
Log two challenges and your answers.
Adjust the timeline if the answer changes it.

Template

Review session log
Date:            Duration:
Reviewer name:
Reviewer role and years of experience:

Challenge 1 (a phase gate or mitigation):
  What they asked:
  My answer:
  Did it hold? What would I change?

Challenge 2:
  What they asked:
  My answer:
  Did it hold? What would I change?

Change I made after the session:
Reviewer's overall view (their words):

What gets sent back

A junior coordinator instead of a senior programme manager.
Answers like 'we'll handle that later'.
Fewer than two challenges logged.

Resources

Foundationstart here

Depthgo deeper

Masteryfor the dedicated

What a verifier looks for

Your most valuable challenge: 'Your Phase 2 has eight parallel workstreams — in your experience, what's the realistic maximum number of parallel tracks an organisation of this size can successfully manage, and how does that affect your timeline estimate?'
Provide written confirmation (minimum 150 words) of your programme management credentials and the challenges raised.

You'll sign in first, then come straight back here.