A focused course, tailored for you
Federal IT Services PM Manager's Portfolio-Authorship Playbook
How a PM manager at a federal IT services firm anchors a portfolio when delivery rebalances around AI-augmented federal delivery.
When federal IT services firms rebalance portfolios around AI-augmented delivery, PM managers without published portfolio-authorship narratives read as coordination overhead.
$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
Federal IT services firms running portfolio rebalancing reach PM Manager functions in the same operating-model cycle. Senior managers above are protected by their division ownership; coordinators below are protected by their direct delivery. The PM Manager layer is the band the deck reviews most carefully.
The PM managers who survive own a documented portfolio strategy with measurable delivery and recompete outcomes, a stakeholder map across agency client and capture team, and a quarterly portfolio-state artefact the senior manager forwards.
The course covers the three artefacts and the 90-day path to portfolio-authorship framing. Plus a hand-built implementation playbook against your real PM Manager scope.
The 12 modules
Module 1. Reading federal rebalancing for PM Manager implications
Federal portfolio rebalancing reorganises PM Manager functions in three phases: enterprise contract-vehicle review, agency-vertical review, and Manager-portfolio review. The diagnostic decodes which signals (recompete-win-rate drift, labour-category-cost ratios, AI-augmentation revenue contribution, contract-vehicle-mix shifts) indicate that the PM Manager layer is in the redraw set. Which Managers survive on coordination coverage and which survive on portfolio-authorship.
Module 2. Generic Manager vs portfolio-authorship leader
Two structurally different framings of the same federal IT services PM Manager seat read very differently to the rebalancing review. Generic Manager shows up as coordination overhead with a meeting-coverage ratio. Portfolio-authorship reads as the leadership the division depends on across recompete cycles: documented portfolio strategy, stakeholder map across agency and capture, and quarterly state artefact the senior manager forwards.
Module 3. Your documented portfolio strategy
Construct the portfolio strategy as a senior-manager-grade two-page document anchored to measurable delivery and recompete outcomes: programme portfolio revenue and margin trends, recompete win-rate, customer-satisfaction scoring, AI-augmented delivery contribution, agency-mission outcome contributions, and expansion pipeline via contract modifications. Three structural templates (transformation-anchored, sustainment-anchored, mission-critical-anchored).
Module 4. Stakeholder map across agency client and capture team
Map your stakeholders across agency client (department CIO, agency CFO, mission leaders, contracting officers across portfolio), capture team (capture lead, BD director, solutioning lead, pricing lead), and adjacent partners (technology partners, subcontractor leadership). Format: stakeholder name, sponsorship-level, last meaningful interaction, current dependency status. The map the senior manager cites by PM Manager name.
Module 5. Quarterly portfolio-state artefact for the senior manager
The quarterly artefact is a two-page state document covering portfolio momentum, agency-client status, capture-team alignment across recompete cycles, AI-augmented delivery outcomes, federal-compliance positioning (ATO, FedRAMP, FISMA, RMF), and emerging risks. Cadence is end-of-quarter delivery to senior manager with copies to division executive committee. Three worked examples from real federal IT services PM Manager portfolios.
Module 6. Working with capture, BD, and contracting officers across portfolio
Manager work overlaps capture (multiple recompete-pursuit teams), BD (multi-account expansion via modifications), and contracting officers (contract-modification negotiation, performance reviews across multiple agencies). The collaboration pattern that strengthens defensibility positioning: portfolio artefacts shared with capture, joint pursuit-team participation, contracting-officer relationships across portfolio. Examples that elevated a PM Manager to Senior Manager.
Module 7. Federal-specific overlays: ATO, FedRAMP, FISMA, RMF, FAR
Federal IT services compliance is heavy: ATO sign-offs, FedRAMP for cloud, FISMA for system security, RMF for risk-based authorisation, CMMC for defence supply chain, FAR for acquisition. The compliance overlays that strengthen the portfolio narrative as regulator-aware federal IT leadership.
Module 8. Cross-portfolio leverage
Reusable Manager practices that scale across programmes: portfolio review templates, ATO-acceleration playbooks, AI-augmented delivery patterns, customer-satisfaction maintenance protocols, capture-coordination cadences. The leverage pattern that signals portfolio-authorship Manager leadership rather than programme coverage. How to convert delivered Manager work into published practice the senior manager cites in rebalancing defence.
Module 9. Recompete portfolio preparation
Recompete reads the portfolio-state artefacts: past performance scoring across programmes, customer-satisfaction surveys, contract-modification capture rate, key-personnel continuity, and price-to-win analysis. The recompete-preparation cadence (24 months out: portfolio artefacts; 18 months out: capture coordination; 12 months out: solutioning; 6 months out: proposal) and how Manager authorship across the cycle protects Manager seats.
Module 10. Scope statement: Manager vs Senior Manager / Director
Two overlapping seats with different scopes. Manager scope covers portfolio delivery, capture support, IP authorship at portfolio level. Senior Manager scope adds division-line ownership, succession sponsorship, cross-portfolio leverage, division-cabinet participation. Director scope adds division-wide P&L and federal-vertical-cabinet responsibilities. The scope statement that puts you in the Senior Manager and Director track defensibly.
Module 11. Promotion mechanics inside federal IT services PM Manager
Internal path from Manager to Senior Manager to Director. The promotion artefact (portfolio strategy, agency-client relationship record, recompete-win contribution, federal-compliance leadership) and the cycle calendar (annual performance review, capture-tied promotion review, federal-vertical cabinet announcement). What gets a Manager shortlisted, what blocks a Manager who is otherwise qualified.
Module 12. Your 90-day move to portfolio-authorship framing
Day-by-day plan with daily artefacts. Days 1-7: portfolio strategy scaffold drafted from your programme inventory. Days 8-21: stakeholder map v1 completed with agency-client sponsorship statuses confirmed. Days 22-45: quarterly artefact v1 delivered to senior manager. Days 46-60: division-line ownership conversation. Days 61-90: Senior Manager conversation scheduled with division-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, federal compliance, leverage, and recompete preparation.
Modules 10 to 12 cover scope, promotion, and 90-day execution.
FAQ
Will the senior manager actually forward my quarterly artefact?
Module 5 is built around the format senior managers forward.
What if my portfolio spans multiple agencies?
Module 3 covers that case.
Why pay for this instead of reading free leadership content?
Free content covers framing.
Is Senior Manager actually open?
Module 11 covers that diagnostic.
What is in the implementation playbook for me specifically?
A draft portfolio strategy; a draft stakeholder map; a 90-day plan with conversations against your senior manager.
