Strategic Prompting Toolkit
PMs who already sense the difference between a vague AI answer and a strategic one, but haven't had a repeatable way to name what makes the difference — until now. You want the AI to sharpen how you think through the project, before it drafts a single word.
Stop Getting Generic Answers From AI
A framework for nine real PM use cases. One prompt library you write yourself, built from your actual project.
Free. No email required.
Bad Prompts Equal Bad Outputs
Sort these six prompts before you read another word. Some are vague. Some are strategic. Guess which is which.
A. "Help me with stakeholder communication."
B. "Act as a senior stakeholder engagement consultant with 15 years in software projects. I need to email a stakeholder who's worried about our timeline. Review the notes below and draft a confident, empathetic 150-word message that reinforces our value and ends with a clear next step."
C. "What should I do about my risky project?"
D. "Act as a proactive risk analyst. Review my project plan below and flag five risks across technical, resource, and stakeholder categories. Return a prioritized list with likelihood and impact ratings, plus one mitigation per risk."
B and D are strategic. A and C are vague. If you sorted that correctly, you probably sensed the difference without a framework. What you likely can't do yet is name the rule.
Every strategic prompt answers four questions the vague ones skip:
WHO should the AI emulate,
WHY are you actually asking,
WHAT exactly should it do,
HOW should it respond.
Skip any one and you're back to prompt A — a generic question that gets a generic answer, because the AI had to guess who you are and what you need.
Structure your intent, and AI amplifies it. That's the whole toolkit.
What's Inside
A 16-page guide built to be used, page by page, on your real project. Every use case runs the same way: a worked example shown first, then the same four questions turned back on your real project, each with a self-check so you know when your answer is specific enough to use.
Three tiers, less scaffolding each time. By the last one, you won't need the training wheels:
Curious: full scaffolding, worked examples shown first
- Status Update: turn rough notes into a status email a sponsor reads closely
- Risk Assessment: surface the risks you didn't know to look for
- Value Reframing: connect your deliverables to why anyone should care
Collaborating: reduced scaffolding, including a match exercise and two AI role-play checks
4. Stakeholder Analysis: stop getting blindsided by predictable pushback
5. Methodology Design: build an approach when Agile and Waterfall both feel wrong
6. Task Time Audit: find what you could stop doing
7. Decision-Making Framework: get decisions to stop routing through you
8. Micro-Learning Plan: keep growing without carving out time for a course
9. AI Ethics Checklist: know what's safe to paste into the chat
Orchestrating: minimal scaffolding, no exact question, just a synthesis challenge
Chain two of your own prompts into a single workflow.
What you'll have at the end is a Strategic Prompt Library: nine prompts you wrote yourself, plus one chained workflow, built from whatever's live on your desk this week.
Strategic Thinking, Made Visible
You can find prompting tips anywhere — a YouTube video, a LinkedIn carousel, a list someone scraped together over a weekend. What's harder to find is a way to think about the ask before you make it.
This toolkit makes that thinking visible, one use case at a time. Every example is filled in for reference, but every prompt you use is the one you write, because the WHO and the WHY have to come from your project. Naming what you need before you ask for it is the habit a generic list can't hand you.
Who It's For
PMs who already sense the difference between a vague AI answer and a strategic one, but haven't had a repeatable way to name what makes the difference — until now. You want the AI to sharpen how you think through the project, before it drafts a single word.
Not for you if you're looking for GenAI LLM tricks to paste in as-is and move on. This toolkit hands you a structure: every use case asks you to name your own WHO, WHY, WHAT, and HOW before you get an answer. Slow down for that first pass, or the fill-in-the-blank prompts here won't do the work for you.
A Taste of It: Status Update
"I have ten minutes and a page of rough notes."
Here's your problem: you know what happened this week, but turning scattered notes into something a sponsor will read closely takes longer than the update deserves.
EXAMPLE (already filled in, for reference):
WHO: Act as an executive communication expert.
WHY: I need to send a concise project update to my sponsor, and I only have rough notes.
WHAT: Transform my bullet points below into a professional status email.
HOW: Three to four paragraphs covering progress, issues, and next steps, in a confident, leadership tone.
Then it's your turn: name your own WHO, WHY, WHAT, and HOW, checked against your actual notes and your actual sponsor. One banned list applies to every WHY you write in the guide — no "help me," "some," "things," "stuff," or "a bit." Catch yourself reaching for one of those, and that's the toolkit working: stop, and get specific instead.
That's one use case. The toolkit has eight more, plus the chained workflow.
Get the Toolkit
Free. No email required.
No opt-in, no gate — just the guide. Download it, keep it open next to whichever AI tool you already use, and start with whichever use case is live on your desk this week.
Not Ready to Stop There?
Keep the insights coming. Every week, one idea for project managers who lead with AI, built to apply directly to your actual work.
Want to go further, faster? I work with project managers 1:1 to build this kind of thinking into how you run your actual projects, using AI as the thinking partner throughout. A free 30-minute call is the next step: you leave with a clearer picture of what working together would address, no pressure to decide on the call.