The prompt
Score 10 of 10, Excellent
Use it when Someone on your team has been promoted, and you want to tell everyone what they did to earn it and what changes, once they have seen the wording.
- {{audience}}
- {{person_name}}
- {{new_role}}
- {{effective_date}}
- {{channel}}
- {{achievements}}
- {{what_changes}}
- {{coverage}}
- {{person_agreed}}
Full prompt and why it works
Prompt
Write an announcement telling {{audience}} that {{person_name}} has been promoted to {{new_role}}, starting {{effective_date}}, to send by {{channel}}. The team needs to know what changes for them, such as who to go to for what, and {{person_name}} deserves credit for the specific work that earned the promotion, so that it reads as recognition rather than an org chart update. What they did to earn it, with examples: """ {{achievements}} """ What changes in their role, and who now goes to them (or elsewhere) for what: {{what_changes}} Who covers their old responsibilities, if anyone: {{coverage}} What {{person_name}} has agreed may be shared, and whether they want to tell anyone themselves first: {{person_agreed}} Produce three parts, each under its own heading: 1. The announcement, under 200 words: the news and the date in the first sentence; two or three specific things they did, from the examples; what changes for the team and who to go to now; congratulations; and an invitation to congratulate them that fits the channel. 2. A short version for a team chat, under 60 words. 3. A one-line message to {{person_name}} asking them to read the draft before it goes out. It should sound warm and specific, like a manager who saw the work up close. For example: "Over the last year [name] took our month-end close from eight days to five and trained two new analysts along the way." That example shows the form only; use the real examples. Do not mention pay, grade or level numbers, and do not compare {{person_name}} with anyone else or mention others who were considered. Do not use praise the examples do not support, such as "always goes above and beyond". Leave out anything {{person_name}} has not agreed to share. If their agreement is not confirmed, or the effective date or the change in responsibilities is not final, do not present it as final: put [CONFIRM BEFORE SENDING: what] at the top of the draft.
Variables
- {{audience}}
- Who receives it, for example "the whole department".
- {{person_name}}
- The name of the person promoted, as the team knows them.
- {{new_role}}
- Their new role or title.
- {{effective_date}}
- When it takes effect, for example "June 1".
- {{channel}}
- How it goes out, for example "email and the team channel".
- {{achievements}}
- What they did to earn it, with specific examples and results.
- {{what_changes}}
- What changes in their role and who goes to them for what now.
- {{coverage}}
- Who takes over their old responsibilities, or "not decided yet".
- {{person_agreed}}
- Whether they have approved the announcement and what they are happy to share, or "not asked yet".
Why it works
- What to avoid. No pay, no levels, no comparisons and no mention of others who were considered, which protects colleagues who also wanted the role.
- An example. A sample line shows credit given for one specific result, the opposite of generic praise.
- If unsure. If the person has not approved it, or the date or new responsibilities are not final, the draft carries a CONFIRM line at the top.