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

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

Example for: a support lead moving a 6-person team from shared email to a helpdesk tool by end of April.

1. Subject line (team)
Kickoff: Moving support to Helpdesk by 30 April

2. Team message

We're moving all customer support from the shared inbox to Helpdesk, with full cutover by 30 April.

Why: Last quarter, 140 tickets got answered twice or not at all because the inbox has no ownership. Helpdesk assigns every ticket to one person and tracks response times.

Scope:

  • In: email tickets, saved replies, tagging, routing rules
  • Out: phone support and live chat (reviewed in Q3)

Roles:

  • Priya: tool setup and routing rules
  • Marcus: converting our 60 saved replies
  • Dana: training plan and two practice sessions
  • Leo: weekly progress report to ops leadership
  • Me (Sam): decisions, blockers, final go-live call

First deadline: Friday 14 March, 5 pm. Priya shares a test workspace and Marcus uploads the first 20 saved replies.

Questions: Post in #helpdesk-move so everyone sees the answer. For anything private, message me directly. We'll also hold a 15-minute Q&A on Tuesday at 10 am.

3. Subject line (stakeholders)
Support is moving to Helpdesk: what changes for you

4. Stakeholder message

The support team is moving from the shared inbox to Helpdesk, with full cutover by 30 April. Customers will get faster, tracked replies, and you will be able to see ticket status without asking us.

What you'll get: read-only Helpdesk access and a short how-to guide by 18 April.

What we need from you: nothing until then. Sales, please keep forwarding customer issues to the usual support address. It will route automatically.

Questions go to Sam Okafor in #helpdesk-move.

5. Gaps

  • Practice session dates are not set yet. Dana should confirm them before 14 March.
  • No rollback plan if go-live slips. Worth deciding before April.
  • It's unclear who approves the routing rules: Priya or Sam?
Written by AI from this prompt. Your results will vary.

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 in Productivity