Your First AI Prompts as a PM

The difference between a mediocre AI result and a great one almost always comes down to how you write your prompt. This lesson teaches you a simple framework for writing effective prompts that produce useful PM output every time.

What You'll Learn

• The CRAFT framework for writing PM-specific prompts
• How to provide context that gets better results
• Common prompt mistakes PMs make and how to fix them
• Five ready-to-use prompt templates for everyday PM tasks

The CRAFT Framework for PM Prompts

Great prompts share five characteristics. Use the CRAFT framework to structure yours:

• C -- Context: Give background about your project, team, or situation
• R -- Role: Tell the AI what role to play (e.g., "Act as a senior project manager")
• A -- Action: Clearly state what you want the AI to do
• F -- Format: Specify the output format (bullet points, table, email, etc.)
• T -- Tone: Define the communication style (formal, concise, executive-friendly)

Example: Bad Prompt vs. CRAFT Prompt

Bad prompt:

"Write a project update."

This gives AI almost nothing to work with. You'll get a generic, unhelpful response.

CRAFT prompt:

"Context: I'm managing a mobile app redesign project. We're in sprint 4 of 8. The design phase is complete, and the development team has finished 60% of the frontend. We're one week behind on the API integration due to a third-party dependency delay.

Role: Act as an experienced project manager writing for a non-technical audience.

Action: Write a weekly status update covering progress, risks, and next steps.

Format: Use bullet points grouped under Progress, Risks, and Next Steps. Keep it under 200 words.

Tone: Professional but approachable. This goes to the VP of Product."

The second prompt gives you a polished, ready-to-send update in seconds.

Five Essential PM Prompt Templates

Here are five prompts you can copy and customize immediately:

1. Weekly Status Report

I'm managing [project name]. Here's what happened this week:
- Completed: [list items]
- In progress: [list items]
- Blocked: [list items]
- Key metrics: [any numbers]

Write a concise weekly status report for [audience].
Format: Brief summary paragraph, then bullet points
under Progress, Risks, and Next Steps.
Keep it under 250 words.

2. Meeting Agenda Generator

I need an agenda for a [meeting type] meeting.
Attendees: [list roles/names]
Duration: [time]
Key topics we need to cover: [list topics]
Decisions needed: [list decisions]

Create a structured agenda with time allocations
for each item. Include a 5-minute buffer.

3. Risk Identification

My project involves [brief description].
Team size: [number]
Timeline: [duration]
Technology/tools: [list]
Dependencies: [list external dependencies]

Identify the top 10 risks for this project.
For each risk, provide: description, likelihood
(high/medium/low), impact (high/medium/low),
and one mitigation strategy.
Format as a table.

4. Task Breakdown

I need to break down this user story into tasks:
"[user story text]"

Context: We're using [methodology]. The team includes
[roles]. Sprint length is [duration].

Break this into specific development tasks with
estimated hours. Include acceptance criteria for
the user story.

5. Stakeholder Email

I need to send an email to [stakeholder role] about
[topic]. Key points to communicate:
- [point 1]
- [point 2]
- [point 3]

The stakeholder is [context about their priorities
or concerns]. Tone should be [professional/casual/urgent].
Keep it under [word count] words.

Common Prompt Mistakes PMs Make

Mistake 1: Being Too Vague

Problem: "Help me with my project plan."

Fix: Include project type, team size, timeline, methodology, and what specifically you need help with.

Mistake 2: Not Specifying the Audience

Problem: Writing a technical update that goes to executives, or an executive summary that goes to developers.

Fix: Always tell AI who will read the output. "This is for my engineering team" produces very different content than "This is for the CEO."

Mistake 3: Accepting the First Output

Problem: Taking whatever AI generates and using it directly.

Fix: Iterate. Say "Make it more concise," "Add a section about risks," or "Rewrite the first paragraph to lead with the deadline change." AI conversations are iterative -- treat them like a back-and-forth with a team member.

Mistake 4: Not Providing Real Data

Problem: "Write a status report for a software project."

Fix: Feed in your actual bullet points, metrics, and context. The more real information you provide, the more useful the output.

Practice Exercise

Try this right now with your AI tool of choice:

1. Pick a real project you're working on
2. Use the Weekly Status Report template above
3. Fill in your actual data
4. Generate the report
5. Iterate at least once (ask for a change)
6. Compare the result to what you'd normally write manually

Most PMs find this exercise saves them 15-20 minutes on their very first try.

Key Takeaways

• Use the CRAFT framework: Context, Role, Action, Format, Tone
• Always specify your audience -- it dramatically changes the output
• Iterate on AI responses rather than accepting the first draft
• Start with the five template prompts and customize them for your projects
• The more real context you provide, the better the output
• AI is a conversation partner -- refine results through back-and-forth