Description

A focused course, tailored for you

Digital PM's Programme-Owner Playbook for Services Productisation

How a senior digital project manager at a services firm authors a programme the firm sells when delivery shifts toward productisation.

When delivery shifts toward productisation, digital PMs who carry the title 'project manager' read as labour line. PMs who authored a programme the firm sells read as programme leadership.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

IT services firms shifting toward productised delivery reorganise PM functions in the same operating-model cycle. Senior digital PMs who continue managing per-project work are read by the deck as a labour-line item. PMs who authored a programme document the firm sells repeatedly are read as programme leadership.

The PMs who survive own a programme document under their byline, a weekly programme-state artefact the practice principal forwards, and a defensible scope statement that distinguishes PM from programme work.

The course covers the three artefacts and the 90-day path to programme-owner framing. Plus a hand-built implementation playbook against your real digital programme.

What you walk away with

A programme document under your byline.
A weekly programme-state artefact the practice principal forwards.
A defensible scope statement distinguishing PM from programme work.
A clean translation from per-project PM to programme owner.
A defensible answer when the productisation review asks which programme your work is associated with.
A 90-day plan from PM to programme-owner framing.

The 12 modules

Module 1. Reading the productisation shift for PM-level implications

Productisation shifts at IT services firms reorganise PM functions in the same operating-model cycle that introduces the new pricing model. The diagnostic for Senior Digital PM scope specifically. What 'productisation' means at PM level inside the firm.

Module 2. Per-project PM vs programme owner

Two structurally different framings of the same digital PM seat. Per-project work reads as labour line; programme ownership reads as the layer the firm sells alongside the offer. The three artefacts that mark the shift.

Module 3. Your programme document

Frame your current projects as one programme with measurable digital-experience outcomes. CSAT lift, conversion rate change, decision velocity. The document the practice principal adopts as the standard for digital programme ownership.

Module 4. Weekly programme-state artefact for the principal

Format, cadence, content of the weekly programme-state artefact the principal forwards. Three worked examples calibrated for services-firm digital programmes. The format that lands as essential reading.

Module 5. Defensible scope statement

The scope statement that distinguishes PM work from programme work defensibly. Outcome ownership, cross-team coordination, executive sponsorship. The language for the next principal conversation.

Module 6. Working with capture, BD, and the partner channel

Programme owners partner with capture, BD, and the partner channel during the productisation shift. The collaboration pattern that strengthens programme ownership rather than producing turf disputes. Worked examples of credit-sharing.

Module 7. Cross-programme leverage

Reusable PM practices that strengthen programme-owner positioning across multiple sold engagements. Discovery sequencing, prototype cadence, design-system integration. The patterns that compound across the practice.

Module 8. Customer-experience attribution

Programme attribution to customer experience outcomes. The specific story that connects PM work to CSAT lift, conversion rate, and revenue per visitor. The model finance accepts as evidence of programme value.

Module 9. Working with engineering and design practices

Programme overlap with engineering and design practices. The collaboration pattern that strengthens cross-practice positioning rather than producing scope disputes. Worked examples of three-way programme authorship.

Module 10. Scope statement: digital PM vs Senior Programme Manager

Two overlapping seats. The scope statement that puts you in the Senior Programme Manager or Practice Lead track defensibly.

Module 11. Promotion mechanics inside IT services PMO

Internal path inside IT services PMO functions. The promotion artefact. The two reviewers who matter.

Module 12. Your 90-day move to programme-owner framing

Day-by-day plan. Programme document v1 in week one. Weekly artefact format agreed by week two. Programme running by week three. Principal conversation in month two. Senior Programme Manager conversation in month three.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

Modules 1 and 2 cover the diagnostic for a digital PM at an IT services firm in productisation.

Modules 3 to 5 produce the three artefacts.

Modules 6 to 9 cover capture cadence, leverage, customer-experience attribution, and partnership.

Modules 10 to 12 cover scope, promotion, and 90-day execution.

What you get with this course

The 12-module course delivered as text plus downloadable templates.
Templates for the programme document, the weekly artefact, and the scope statement.
A hand-built implementation playbook generated for your specific scope (digital PM at a services firm in productisation).
Three worked examples of the weekly artefact.
Scripted talking points for the principal conversation.

What you will have in hand by Day 1, Week 1, Month 1

Day 1: Programme document scaffold drafted.

Week 1: Document v1 written; weekly artefact format agreed.

Month 1: Weekly artefact landing with principal; Senior Programme Manager conversation scheduled.

Before and after

Before

You run digital projects. Milestones land. The productisation shift is being discussed. There is no programme document with your byline.

After

Your programme document is in the firm's library. The weekly artefact lands with the principal. The Senior Programme Manager conversation is scheduled.

What happens if you do not address this

Productisation shifts compress per-project PM scope within one or two cycles.

Who it is for

For Senior Digital Project Managers, Programme Managers, and PMO Leads at IT services firms in productisation cycles.

Who this is NOT for. Junior PMs. PMs at firms not in productisation. PMs in pure infrastructure projects without programme scope.

How it arrives

Text-based course via LMS, plus downloadable templates and the hand-built implementation playbook.

Time investment. Roughly 10 hours of reading and 12 to 16 hours producing your real artefacts.

Why $199 is the right number

Internal PMO training is general. External PMI communities cover technique not the programme-owner move during productisation. A senior programme director mentor would cover maybe four of these 12 modules informally. $199 buys the focused playbook plus the implementation document for your real scope.

FAQ

Will the principal actually forward my weekly artefact?

Module 4 is built around the format principals forward.

What if my projects span multiple practices?

Module 3 covers that case.

Why pay for this instead of reading free PMI content?

Free content covers technique.

Is the Senior Programme Manager seat actually open?

Module 10 covers that diagnostic.

What is in the implementation playbook for me specifically?

A draft programme document against your real projects; a draft scope statement; a 90-day plan with conversations against your principal.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.