Skip to main content

AI Prompt Library

This page collects practical AI prompts for project managers, service improvement teams and busy professionals. They are designed for workplace administration, planning, communication and personal productivity. Remove personal, patient-specific or confidential information before using any AI tool.

1. Project Brief Prompt

Description: Turn a loose AI request into a clear work brief. This is the prompt pattern from today's post: Role, Goal, Context, Source, Constraints, Output and Review.

Example use cases

Project scoping, service improvement planning, stakeholder updates, governance papers and decision support.

Prompt

Role: Act as [role or lens, such as project manager, service improvement lead or risk reviewer].

Goal: I need [the decision, document or action you need to support].
Context: [briefly explain the workplace situation, audience and why this matters].
Source: Use only the information below:
[paste notes, draft text, meeting summary, process issue or source material]
Constraints: Do not invent data, dates, approvals or policy requirements. Do not include personal, patient-specific or clinical advice. Flag privacy, governance, change-management or evidence gaps.
Output: Produce [format, such as one-page brief, options paper, table, checklist or email].
Review: End with questions to confirm and items that need human judgement before use.

2. Meeting Notes to Action Register

Description: Convert messy meeting notes into clear actions, owners and follow-up points.

Example use cases

Project meetings, working groups, improvement huddles and vendor check-ins.

Prompt

Turn the notes below into an action register.

Use columns for Action, Owner, Due date, Dependency, Risk or issue, and Clarification needed.
Only use information in the notes. If an owner or due date is missing, write "To confirm".
Keep wording suitable for a professional workplace audience.

Notes:
[paste meeting notes]

3. Stakeholder Update

Description: Create a concise status update that separates progress, risks and decisions.

Example use cases

Weekly project updates, sponsor emails, steering committee summaries and internal newsletters.

Prompt

Draft a stakeholder update for [audience].

Use this structure:
1. Headline status
2. Progress this period
3. Risks or blockers
4. Decisions needed
5. Next steps

Use a calm, factual tone. Do not overstate certainty. If information is missing, list it under "To confirm".

Source material:
[paste update notes]

4. Risk Register Starter

Description: Identify likely delivery, operational, privacy and change risks from project notes.

Example use cases

Project initiation, health service workflow changes, technology rollouts and process redesign.

Prompt

Review the project notes below and create a draft risk register.

Use columns for Risk, Cause, Impact, Likelihood, Consequence, Current controls, Proposed treatment, Owner and Review date.
Flag any privacy, governance, workforce, adoption, data quality or operational continuity risks.
Do not invent facts. Mark assumptions clearly.

Project notes:
[paste notes]

5. Process Improvement Problem Statement

Description: Shape a vague operational issue into a clear problem statement and improvement aim.

Example use cases

Lean Six Sigma projects, service delays, handover issues, rework, queue management and administrative bottlenecks.

Prompt

Help me turn this issue into a clear process improvement problem statement.

Include:
1. What is happening
2. Who is affected
3. Evidence available
4. Operational impact
5. What is out of scope
6. Draft improvement aim
7. Measures that could show improvement

Do not include clinical advice or personal information. Highlight missing data.

Issue notes:
[paste notes]

6. Five Whys Root Cause Draft

Description: Explore possible causes without jumping too quickly to a solution.

Example use cases

Recurring delays, repeated defects, missed handoffs, unclear ownership and process failures.

Prompt

Use the Five Whys technique to explore likely causes of this process issue.

For each "why", give the reasoning, assumptions and evidence needed to confirm it.
Separate facts from hypotheses.
End with likely root cause themes and suggested data to collect next.

Issue:
[describe issue]

7. Project Charter Starter

Description: Create a first draft charter from early discovery notes.

Example use cases

New projects, improvement initiatives, system changes and cross-functional work packages.

Prompt

Create a draft project charter from the notes below.

Include Purpose, Background, Objectives, Scope, Out of scope, Deliverables, Stakeholders, Milestones, Risks, Dependencies, Measures of success and Open questions.
Keep it concise and practical.
Do not invent approvals, budget or dates.

Notes:
[paste discovery notes]

8. Change Impact Scan

Description: Think through who will be affected by a proposed change and what support they may need.

Example use cases

Workflow redesign, software adoption, reporting changes, role changes and new governance processes.

Prompt

Assess the likely change impacts of the proposed change below.

Use columns for Stakeholder group, What changes for them, Likely concerns, Support needed, Communication message, Training need and Adoption risk.
Include operational, privacy, governance and workload considerations.

Proposed change:
[describe change]

9. Benefits and Measures Plan

Description: Translate a project idea into measurable benefits and practical indicators.

Example use cases

Business cases, improvement projects, post-implementation reviews and benefits tracking.

Prompt

Create a simple benefits and measures plan for this initiative.

Include Benefit, Why it matters, Leading indicator, Lagging indicator, Data source, Baseline needed, Review frequency and Owner.
Flag measures that may be hard to collect or easy to misinterpret.

Initiative:
[describe initiative]

10. Options Brief

Description: Compare options in a balanced way before a decision meeting.

Example use cases

Choosing a workflow, selecting a tool, prioritising improvements or deciding between delivery approaches.

Prompt

Prepare an options brief for this decision.

Decision needed:
[describe decision]

Options:
[list options]

For each option, summarise Pros, Cons, Risks, Effort, Dependencies, Reversibility and Who needs to be consulted.
End with a balanced recommendation and assumptions to validate.

11. Policy or Procedure Summary

Description: Summarise a long internal document into practical actions and questions.

Example use cases

Procedure reviews, implementation planning, audit preparation and team briefings.

Prompt

Summarise the document excerpt below for a workplace implementation audience.

Include:
1. Main obligations or requirements
2. Practical actions for teams
3. Risks if misunderstood
4. Questions to confirm with the policy owner

Use only the text provided. Do not give legal, clinical or compliance advice.

Excerpt:
[paste excerpt]

12. Workshop Agenda Builder

Description: Design a focused workshop that leads to decisions or usable outputs.

Example use cases

Process mapping, risk workshops, requirements sessions, retrospectives and planning days.

Prompt

Create a workshop agenda for [topic].

Audience: [participants]
Time available: [duration]
Desired output: [decision, map, action plan, risks, requirements]

Include agenda sections, timing, facilitator notes, materials needed, pre-work and follow-up actions.
Keep the design practical and avoid activities that do not support the output.

13. Lessons Learned Review

Description: Convert project experience into useful lessons and future controls.

Example use cases

Post-project reviews, sprint retrospectives, implementation closeout and continuous improvement planning.

Prompt

Turn the notes below into a lessons learned summary.

Group insights under What worked, What did not work, Root causes, Recommendations, Controls to keep and Follow-up actions.
Avoid blame. Focus on system, process, communication and decision factors.

Notes:
[paste notes]

14. Personal Weekly Planning Prompt

Description: Prioritise a busy week by outcomes, constraints and energy, not just tasks.

Example use cases

Personal planning, study, side projects, work priorities and household administration.

Prompt

Help me plan my week.

My commitments:
[paste list]

My top outcomes:
[paste outcomes]

Constraints:
[time, energy, deadlines, family or study commitments]

Create a weekly plan with Must do, Should do, Could do and Not this week. Suggest a realistic first action for each must-do item.

15. Message Tone Refiner

Description: Improve a draft email or message so it is clear, respectful and action-oriented.

Example use cases

Stakeholder follow-ups, difficult conversations, meeting requests, personal messages and escalation notes.

Prompt

Improve the message below.

Audience: [who will receive it]
Purpose: [what the message needs to achieve]
Tone: clear, respectful, concise and practical

Keep the meaning accurate. Do not add facts. Make the ask and next step obvious.
Provide two versions: concise and slightly warmer.

Draft:
[paste message]

Comments

Popular posts from this blog

3 Questions to Ask Yourself Before Diving Into Becoming an Entrepreneur

This post originally appeared in Inc . The pursuit of an entrepreneurial venture feels a lot like jumping off a high cliff into deep water. It's scary at first and there's no going back once you leap, but after you muster up the courage, it is one of life's most exhilarating experiences. Before you hastily rush into a triple backflip dive, it is best to do some homework and prepare. Is the water deep enough to attempt a safe dive? Has anyone jumped from this point before (and survived)? After I jump, is there a way for me to get back to land safely? Is getting hurt worth the risk? Entrepreneurship is no different. Success is about more than just quitting your job and leaping head over heels into your venture. You first have to do your homework. It's hard to define the right time to begin a new endeavor, and the reality is no time is ever going to be perfect. But before you take the plunge, here are three questions to consider. 1) Are you personally a...

7 Ways to Build a Focused Team

This post originally appeared in Inc. Buzzing about which new startups will prosper and which will flop is a favorite pastime in Silicon Valley. But a new company's prospects aren't based on just what the company creates, says Stanford professor  Lindred Greer . They're also based on the people creating it and, more important, how they treat one another.  "Startup success is as much about managing the people as it is about creating the product," says Greer, an organizational behavior professor at Stanford Graduate School of Business. Based on her research on entrepreneurship and team dynamics, Greer will teach a new course at Stanford GSB this spring focusing on the unique team-dynamic challenges faced by early-stage startups. In a recent interview, she offered tips for managing startup teams. Be Aware of Culture in Early Stage Startups The culture of early stage startups forms the backbone of the culture the company will have in later years. Therefor...

Stop Playing the Victim with Your Time

This post originally appeared in HBR "It’s just not fair. There’s always too much to do. Everyone just keeps piling more work on me. I feel so helpless." Sound familiar? If so, you’re not alone. Many people feel like they have a crushing number of requests coming at them from every side that make them a victim to their circumstances. They see forces outside themselves as the reason that they don’t have time to exercise, can’t leave work at a reasonable time, or just generally struggle to get everything done. Although there are occasionally situations that are outside of your control — that recent bout with the flu, for example — most aren’t. And even though it can feel gratifying in the short term to blame others for your situation, this attitude toward your  time investment will leave you truly powerless in the long run. When you play the victim with your time, everything around you suffers. You’re constantly on edge in your interactions with others because you f...