Write a Project Kickoff Message for Your Team and Stakeholders
You get a short team kickoff message covering why, scope, roles, first deadline and questions, plus a shorter stakeholder version and a list of gaps.
Prompt
You are an experienced project manager who writes kickoff announcements people actually read.
Your job: write a short kickoff message announcing a new project to my team, plus a separate version for stakeholders outside the team.
Before writing, ask me these questions in one numbered message, then wait for my answers:
1. What is the project, and why are we doing it now?
2. What is in scope, and what is explicitly out of scope?
3. Who is involved, and what does each person own?
4. What is the first deadline, and where should people send questions?
Rules:
- The team message stays under 200 words and covers why, scope, roles, first deadline and questions, in that order.
- Open with one sentence saying what the project is and when it ends. No warm-up lines.
- Every role line names a person and one concrete thing they own.
- The first deadline includes a date, a time and exactly what is due.
- The stakeholder version stays under 120 words, drops internal task detail, and says what they will get, when, and whether anything is needed from them.
Output format:
1. Subject line (team)
2. Team message
3. Subject line (stakeholders)
4. Stakeholder message
5. Gaps: a short list of anything vague or missing that could confuse readers
If an answer is missing, mark it TBD and flag it in Gaps instead of guessing.Example output
Tips and common edits
Why this works
- Fixing the order (why, scope, roles, deadline, questions) makes the message easy to skim and stops key details from getting buried.
- Requiring a name plus one owned task per role removes vague ownership, a common reason kickoffs stall.
- The Gaps list catches missing dates and decisions before the team reads the message and starts asking.
Use this in ChatGPT, Claude or Gemini on the day you kick off a project. Have the project goal, scope limits, owner names, first deadline and your preferred question channel ready.
Common edits
- Ask for a Slack-length team version under 100 words with bullet points only.
- Add a fifth question about tone, for example formal for leadership or casual for a small team.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build a RACI Chart from Your Project Task List with Ownership Gaps Flagged
Turns a pasted task list into a RACI table with one Accountable per task, flags unowned or over-consulted tasks, and lists questions to confirm with your team.
Draft a Hard Team Announcement for a Reorg, Delay or Policy Change
Get a clear team announcement that states the news first, shows what changes and stays the same for each group, and answers likely questions honestly.
Write a Project Status Report with RAG Calls, Risks and Leadership Asks
Turns your raw project notes into an executive-ready status report with justified red/amber/green ratings, done vs. planned work, a risk table and specific decisions needed.
Plan a Sprint Retrospective with Timed Steps, Questions and a Dot-Vote
Get a retro format matched to your team's mood and problems, with a timed agenda, warm-up, open questions, and a dot-vote that ends in at most three owned actions.
Build a Reusable Report or Memo Template Anyone on Your Team Can Fill In
Get a blank document template with headed sections, one-line guidance under each, a fully filled example, and a short pre-send checklist.
Build a Timed Meeting Agenda with Owners, Decision Labels and Pre-Reads
Get a timed agenda where every item has a Decide, Discuss or Inform label, an owner and minutes that fit the slot, plus pre-reads and a list of items to handle async.