A focused course, tailored for you
IT Services Project Manager's Programme-Authorship Playbook
How an IT services project manager anchors a programme when delivery restructures around AI augmentation.
When IT services firms restructure delivery around AI augmentation, project managers without published programme-authorship narratives read as billable coordination cost.
$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 running AI-augmentation restructure reach project manager functions in the same operating-model cycle. Senior PMs above are protected by their portfolio contribution; team leads below are protected by their direct delivery. The PM layer is the band the deck reviews most carefully.
The project managers who survive own a documented programme strategy with measurable delivery outcomes, a stakeholder map across the client account and capture team, and a quarterly programme-state artefact the practice principal forwards.
The course covers the three artefacts and the 90-day path to programme-authorship framing. Plus a hand-built implementation playbook against your real programme scope.
The 12 modules
Module 1. Reading AI-augmentation restructure for PM implications
AI-augmentation restructures at IT services firms reorganise PM functions in three predictable phases: enterprise platform review, vertical practice review, and PM-portfolio review. The diagnostic decodes which signals (delivery-margin compression, AI-augmentation revenue targets, billable-utilisation drift, capture-velocity benchmarks) indicate that the PM layer is in the redraw set. Which PMs survive on coordination coverage and which survive on documented programme-authorship.
Module 2. Generic PM vs programme-authorship owner
Two structurally different framings of the same PM seat read very differently to the deck. Generic PM shows up as coordination overhead with a meeting-coverage ratio. Programme-authorship reads as the leadership the practice structurally depends on through restructure: documented programme strategy, stakeholder map BD cites, and quarterly state artefact the practice principal forwards. The three artefacts that mark the shift.
Module 3. Your documented programme strategy
Construct the programme strategy as a practice principal-grade two-page document anchored to measurable delivery outcomes: schedule performance, cost performance, customer satisfaction (client CIO/CTO survey), expansion captured via modifications, AI-augmented delivery contribution, and renewal probability. Three structural templates (transformation-anchored, modernisation-anchored, sustainment-anchored) and the formula for choosing yours.
Module 4. Stakeholder map across the client account and capture team
Map your stakeholders across client (account-sponsor CIO, programme sponsor, end-user sponsors, contracting and procurement), capture team (account director, BD lead, solutioning lead), and adjacent partners. Format: stakeholder name, sponsorship-level, last meaningful interaction, current dependency status. The map BD cites by PM name and that the practice principal cites in restructure defence.
Module 5. Quarterly programme-state artefact for the practice principal
The quarterly artefact is a two-page state document covering programme momentum, client-account status, capture-team alignment, AI-augmented delivery outcomes, modification capture rate, and emerging risks. Cadence is end-of-quarter delivery to practice principal with copies to capture, BD, and pricing leads. Three worked examples from real IT services PM programme portfolios at different AI-augmentation stages.
Module 6. Working with capture, BD, and account leadership
PM work overlaps capture (large-deal pursuit, recompete), BD (account expansion via modifications), and account leadership (named-account executives). The collaboration pattern that strengthens defensibility positioning: programme artefacts shared with capture, joint pursuits credited, account-leadership co-sponsored quarterly reviews. Examples of capture narratives that elevated a PM to Senior PM.
Module 7. Margin-defence and AI-augmentation story
Margin is what finance reads first in cost-per-revenue restructure reviews. Format the margin story as a four-quarter trend with engagement-type breakdown, AI-augmentation contribution, talent-mix optimisation (onshore vs offshore vs near-shore), and forward pipeline. Three storytelling templates for different margin profiles and the talking points each gives the practice principal.
Module 8. Cross-programme leverage
Reusable PM practices that scale across programmes: client-onboarding protocols, quarterly business-review cadences, transformation-roadmap templates, AI-augmentation playbooks for delivery acceleration. The leverage pattern that signals PM-grade leadership rather than programme coverage. How to convert delivered PM work into published practice the practice principal cites in restructure defence.
Module 9. AI augmentation as accelerator
Use AI augmentation to strengthen programme rather than absorb it. The narrative documents how AI augmentation (delivery acceleration, automated status reporting, AI-assisted risk analysis, AI-driven client outputs) increased margin, accelerated delivery, and protected client outcomes. Three patterns and how to document each as programme-strengthening leadership the principal cites.
Module 10. Scope statement: PM vs Senior PM / Programme Director
Two overlapping seats with different scopes. PM scope covers programme delivery, capture support, IP authorship at programme level. Senior PM scope adds programme-line ownership, succession sponsorship, cross-programme leverage. Programme Director scope adds practice-area P&L, recompete pursuit ownership, and practice-cabinet responsibilities. The scope statement that puts you in the Senior PM and Programme Director track defensibly.
Module 11. Promotion mechanics inside IT services delivery
Internal path from PM to Senior PM to Programme Director. The promotion artefact (programme strategy, stakeholder relationship record, modification capture contribution, AI-augmentation outcomes) and the cycle calendar (Q1 review, Q2 nomination, Q3 cabinet review, Q4 announcement). What gets a PM shortlisted, what blocks a PM who is otherwise qualified, and how to time your move with the practice principal's succession plan.
Module 12. Your 90-day move to programme-authorship framing
Day-by-day plan with daily artefacts. Days 1-7: programme strategy scaffold drafted from your programme inventory. Days 8-21: stakeholder map v1 completed with client-account sponsorship statuses confirmed. Days 22-45: quarterly artefact v1 delivered to practice principal. Days 46-60: programme-line ownership conversation. Days 61-90: Senior PM conversation scheduled with practice-cabinet sponsor identified in module 11.
How this addresses your situation
Specific modules that map to what you said you are dealing with.
Modules 1 and 2 cover the diagnostic.
Modules 3 to 5 produce the three artefacts.
Modules 6 to 9 cover capture cadence, margin defence, leverage, and AI accelerator.
Modules 10 to 12 cover scope, promotion, and 90-day execution.
FAQ
Will the practice principal actually forward my quarterly artefact?
Module 5 is built around the format principals forward.
What if my programme is split across capture teams?
Module 3 covers that case.
Why pay for this instead of reading free PMI content?
Free content covers technique.
Is Senior PM actually open?
Module 11 covers that diagnostic.
What is in the implementation playbook for me specifically?
A draft programme strategy; a draft stakeholder map; a 90-day plan with conversations against your practice principal.
