Digital transformation · Amgen · Current

Connecting programs through a unified CDP.

Multiple programs were being consolidated and migrated onto a new customer data platform, creating a dense network of dependencies, stakeholders, and readiness decisions.

MultiProgram scope

OneCDP direction

E2EReadiness view

The mandate / 01

A transformation is a network.

A timeline can show when each workstream hopes to move. It cannot, by itself, show what must move together.

The transformation connected program commitments, data and platform dependencies, stakeholder decisions, migration sequencing, and readiness criteria. Each program could appear healthy in isolation while the combined transition still carried hidden risk.

My role was to connect those views: make dependencies explicit, give decisions an owner and consequence, and keep the analytics program aligned to the wider platform transition.

Confidentiality boundary

Platform architecture, internal program names, and transition plans are generalized. The cross-program operating logic and leadership decisions are accurate.

The readiness system / 02

See what must move together.

The operating view separated activity from readiness. It linked the work to the decision and transition condition that each dependent program actually needed.

01 / MapPrograms

Identify owners, commitments, milestones, and critical interfaces.

02 / ConnectDependencies

Show what is upstream, downstream, shared, or decision-bound.

03 / DecideMigration path

Sequence movement around consequence, evidence, and constraints.

04 / ProveReadiness

Make transition criteria, risk, and sign-off visible end to end.

Transformation artifact indexGeneralized view

Dependency map

Programs, interfaces, owners, timing, and the consequence of a missed handoff.

Readiness scorecard

Evidence-based conditions for movement, not optimistic percent-complete reporting.

Decision register

Clear choice, owner, deadline, impact, and the work waiting behind it.

Transition narrative

A leadership view of what is moving, what changed, and where intervention matters.

Key decisions / 03

Manage the seams, not just the streams.

The transformation risk lived between programs—where ownership, assumptions, and timing could quietly diverge.

Plan as a network

Represent dependencies and decisions as first-class work, not notes beside an otherwise linear plan.

Separate progress from readiness

Make a workstream prove its transition conditions instead of equating activity with confidence.

Escalate consequence

Frame issues around what becomes impossible, costly, or risky if a decision does not land.

Hold one narrative

Give teams and leaders a coherent view of the transformation even when their local details differ.

Value created / 04

Movement became coordinated.

The work gained a clearer view of what must move together, where decisions were blocked, and what each program needed before transition.

That shared readiness view let teams discuss the same transformation rather than several disconnected local plans. It also kept the analytics program connected to the decisions shaping the wider platform.

MultiConnected program view

Dependencies and transition conditions represented across workstreams.

OneTransformation narrative

A common leadership view of movement, decisions, and risk.

E2EReadiness logic

Evidence carried from local delivery through coordinated transition.

Reflection / 05

What this work reinforced.

Transformation leadership is often the work of making the space between programs visible.

The most consequential dependency is often a decision, not a deliverable.
Readiness must be evidence-based or it becomes a synonym for optimism.
A shared narrative lets leaders intervene at the system level instead of chasing local status.