• Internal programme
  • Strategy & roadmap
  • Backlog prioritisation
  • Portfolio management
  • Change management

Internal Digital Transformation Programme: How I ran it

I led the diagnosis, executive alignment and roadmap for a company-wide digital transformation at an HR and staffing company in Iberia. About 60 initiatives, 6 workstreams and a 14-week planning cycle, sequenced with a weighted scoring model I designed with my team.

How I ran it

Cadence, roles, risks and the decisions behind the delivery.

Governance

  • Roadmap signed off by the executive team
  • A project sheet for every initiative
  • A repeatable method from requirements to closure: for each initiative I defined the scope, objectives, expected results and resources needed, then planned the stages, managed execution with clients, vendors, developers and marketing, monitored progress and closed with a final review

Who did what (RACI)

RACI matrix: for each activity, who does the work (R), approves (A), is consulted (C) or informed (I)
ActivityLeadExecHeadsDevVendorsData
Interviews and initiative inventoryLead: A/RExec: IHeads: CDev: not involvedVendors: not involvedData: not involved
SWOT workshop and digital visionLead: A/RExec: CHeads: CDev: not involvedVendors: not involvedData: not involved
Initiative project sheetsLead: A/RExec: not involvedHeads: CDev: not involvedVendors: not involvedData: not involved
Roadmap prioritisation (scoring model)Lead: A/RExec: CHeads: CDev: not involvedVendors: not involvedData: not involved
Executive sign-offLead: RExec: AHeads: not involvedDev: not involvedVendors: not involvedData: not involved
Document management systemLead: AExec: not involvedHeads: CDev: CVendors: RData: not involved
Application developmentLead: AExec: not involvedHeads: CDev: RVendors: CData: not involved
Reporting dashboardsLead: AExec: IHeads: not involvedDev: not involvedVendors: not involvedData: R
B Corp assessmentLead: A/RExec: CHeads: CDev: not involvedVendors: not involvedData: not involved

R does the workA approvesA/R approves and doesC consultedI informed

Main risks and how I handled them

Competing priorities across 10 business areas

Scope

Scoring model designed with the team, task-force input on priority and difficulty, executive sign-off.

Roadmap larger than delivery capacity (about 60 initiatives)

Resources

Sequencing across a multi-year roadmap, with the score shaping the order.

Data quality behind the KPIs and dashboards

Technical

Data cleansing built into the reporting initiative.

Decisions

Use the GROWTH method: Discover → Picture → Plan

Context
The programme needed a repeatable way to go from needs to a roadmap.
Decision
Plan in a 14-week cycle with interviews, a SWOT workshop and a prioritised roadmap.
Outcome
A signed-off roadmap of about 60 initiatives.

Group the initiatives into six workstreams

Context
About 60 initiatives are hard to follow without structure.
Decision
Technology architecture, process automation, data-driven, efficiency & cost, innovation, brand image.
Outcome
A roadmap executives could read at a glance.

Prioritise with a weighted scoring model

Context
Every area asked for its own initiatives.
Decision
I designed a weighted scoring model with my team; priority and difficulty were set by the task force at the workshop; I prioritised the roadmap with my manager.
Outcome
A prioritised order for delivery.

Turn a shared spreadsheet into a client-portal tracker

Context
A simple idea: track process status with clients in a shared spreadsheet.
Decision
Rethink what the client needs and build a tracking app inside the client portal with automatic notifications.
Outcome
“Digitise what exists” became “rethink what the client needs”.

Working on something like this?

Download my CV or message me on LinkedIn.