AI for Project and Program Leaders: Scenarios and Prompts

#

Part 2 of the Human Skills, AI-Expanded series

Program directors and PMO leads live in the gap between strategy on slides and delivery in the wild. You inherit conflicting priorities, stale RAID logs, and steering committees that want clarity in twenty minutes. AI does not replace your accountability to sponsors—but it can shrink the hours you spend reading, structuring, and drafting so you spend more time on tradeoffs, people, and commitments.

If you have not read the series frame yet, start with Leaders, Human Skills, and AI: What Stays Yours. This post applies that frame to delivery leadership.

Who this is for

#

• Program or portfolio director
• PMO lead or head of project delivery
• Senior project manager on strategic initiatives
• Transformation or change program lead

You are not learning how to build a Gantt chart from scratch. You are learning where AI saves a day without letting it sign your name on a recovery plan or a go-live date.

A week in this role

#

A typical week might include:

• Portfolio or pipeline review with leadership
• Preparing or attending a steering committee
• Escalating a red project (schedule, budget, or benefits)
• Mediating stakeholder conflict on scope or resources
• Refreshing risks and dependencies before a stage gate
• Chasing benefits evidence that never quite matches the business case

AI helps most on synthesis and first-draft structure. It helps least on politics, blame, and promises.

Scenario 1: Portfolio must align to strategy

#

Situation

#

Leadership published annual OKRs. You own twelve active projects with different sponsors. Half the room will ask why a pet project still has funding.

Human skill you are exercising

#

Strategy–project alignment—making work visible against outcomes, not just status colors.

What AI or an agent can do

#

• Map each project to primary and secondary OKRs
• Flag orphan work (no clear strategic home)
• Propose reprioritization options with tradeoffs stated plainly

What you must not delegate

#

Which projects survive, which sponsors you disappoint, and how you message those calls.

Example prompt

#

Role: portfolio analyst for a program leader.  

Inputs: [paste OKRs] [paste project list with owner, budget, status, benefits one-liner].  

Task: 
(1) Map each project to primary/secondary OKR or mark "unclear".   
(2) List orphan projects.   
(3) Suggest three reprioritization options with tradeoffs.

Output as a table. Mark assumptions. No invented metrics.

Outcome

#

You enter the portfolio conversation with a defensible map, not a defensive list of activities. Human time goes to negotiation, not spreadsheet archaeology.

Scenario 2: Red project needs a recovery path

#

Situation

#

A flagship initiative is red on schedule and amber on budget. Sponsors want a recovery plan in five days. You have ten weekly status reports, email threads, and contradictory explanations from workstream leads.

Human skill you are exercising

#

Crisis leadership and earned value / performance judgment at leader level—you interpret variance, you do not just recite it.

What AI or an agent can do

#

• Extract recurring root-cause themes from status narratives
• List contradictions between reports (scope stable vs change requests rising)
• Draft three recovery options: re-baseline, descope, or restructure governance—with pros/cons

What you must not delegate

#

The recovery commitment, the conversation with the sponsor who approved the original date, and accountability for prior reporting.

Example prompt

#

Role: program recovery analyst.  

Inputs: [paste last 6 weekly status summaries]  

[current baseline: planned end date, budget, scope summary].

Tasks:  
(1) Top 5 root-cause themes with evidence quotes.   
(2) Contradictions between reports.  
(3) Three recovery options (re-baseline, descope, governance reset) with risks and sponsor talking points.  

Do not invent dates or dollars. Flag missing data. Separate facts from inference.

Outcome

#

Your recovery workshop starts with shared facts, not opinions. You still own the ugly sponsor meeting.

Scenario 3: Steering committee in 48 hours

#

Situation

#

You have twenty minutes on the agenda. The committee expects decisions on funding, risk acceptance, and a dependency that another division keeps missing.

Human skill you are exercising

#

Executive communication—clarity, decisions requested, no burying the lead.

What AI or an agent can do

#

• Turn status + RAID + prior actions into an 8-slide outline
• Surface top three decisions and top three risks with suggested responses
• Draft likely questions from finance, operations, or technology peers

What you must not delegate

#

Tone, what you admit went wrong, and any approval you are not empowered to give.

Example prompt

#

Audience: executive steering committee. Time: 20 minutes.  

Inputs: [status summary] [RAID log] [last steering actions].  

Draft: 8-slide outline (title + 3 bullets each), top 3 decisions needed, top 3 risks with recommended response. Flag data gaps.

Outcome

#

You sound prepared, not scripted. Slides support the conversation; they do not replace your judgment in the room.

Scenario 4: The risk register is stale

#

Situation

#

The RAID log has not changed in six weeks, but everyone knows integration testing is fragile and a key vendor is slipping. You need a refresh before a stage gate without a three-day workshop.

Human skill you are exercising

#

Risk identification and response—seeing new threats and matching responses to appetite, not checkbox compliance.

What AI or an agent can do

#

• Scan recent change logs, meeting notes, or chat exports (redacted) for risk signals
• Suggest new risks with probability/impact ranges and draft responses
• Highlight risks that are duplicates or pure issues (no uncertainty left)

What you must not delegate

#

Risk appetite, acceptance of residual risk, and escalation to the right executive owner.

Example prompt

#

Role: risk analyst supporting a program director.  

Inputs: [current RAID log] [change log or meeting notes from last 30 days].  

Output:  
(1) Proposed new risks (title, cause, impact range, suggested owner).  
(2) Risks to close or downgrade with rationale.   (3) Top 3 risks needing executive decision.  

Use qualitative H/M/L if numeric data is missing. Do not fabricate incidents.

Outcome

#

The register reflects reality again. The gate review discusses real exposure, not last quarter’s ghosts.

Skills touched in this article

#

Related capabilities you will still build without AI—WBS quality, agile cadence, contract literacy—but AI gives you more cycles to practice them instead of drowning in documents.

Try this week

#

1. Export a one-page project list and your team’s OKRs; run the portfolio alignment prompt.
2. Pick your reddest workstream; run the recovery prompt on real status text (redact names if needed).
3. Before the next steering meeting, generate an outline and delete half—keep only what supports a decision.
4. Refresh RAID with the risk prompt; close at least two obsolete items manually.
5. Write one sentence: what you owned that AI could not.

Risks and guardrails

#

• False precision: AI may invent percentages or dates—verify against baselines and finance.
• Blame language: Drafts may sound accusatory; edit before forwarding to teams.
• Confidentiality: Status reports often contain M&A, personnel, or customer detail—use enterprise-approved tools and redaction.
• Schedule fantasy: Recovery options can be optimistic; stress-test with leads who own the work.
• RAID theater: Auto-generated risks nobody owns are worse than an empty log.

Related reading

#

• Leaders, Human Skills, and AI: What Stays Yours — series hub (Part 1)
• LLM Skills and Human Skills — what models can and cannot do reliably

Also in this series: HR leaders; general managers; technology executives; agentic AI; playbook.

Try one prompt this week on a real project. Write down what was useful and what was wrong—both are worth sharing with your team.