The prompt
Score 10 of 10, Excellent
Use it when Someone on your team needs to know in writing what good looks like in their role, before problems or a review.
- {{role_title}}
- {{person_context}}
- {{role_description}}
- {{my_notes}}
- {{team_norms}}
Full prompt and why it works
Prompt
Write a one-page expectations document for the {{role_title}} role on my team, as it applies to {{person_context}}. I will go through it with them in a one-on-one and we will both keep a copy, so it has to be clear, fair and specific enough that we would agree on whether each expectation is being met. What the role is for and what it covers: """ {{role_description}} """ What good work looks like to me in this role, in my own words: """ {{my_notes}} """ Team norms that apply to everyone (hours, response times, meetings, tools): {{team_norms}} Use these headings: 1. Purpose of the role: two sentences. 2. Main responsibilities: four to seven, each a short line. 3. What meeting expectations looks like: for each responsibility, one observable standard, such as a deadline, a quality check, a volume or a behavior. For example: "Month-end reconciliations are complete by the third working day, with exceptions listed for the controller." 4. How we work together: decisions they make alone, decisions to check with me, and how and when we review progress. 5. Support they can expect from me. Keep it to about 350 to 450 words, addressed to "you", in plain, neutral language. Do not include comments on personality or general attitude ("be more proactive") or anything about personal life; turn vague expectations into something a person could see or measure. Do not add standards that are not in my notes or the role description, and do not hint at disciplinary consequences, because this is an expectations document, not a warning. If my notes are vague about a responsibility, write the closest observable standard you can and mark it "[CONFIRM]" so I can adjust it before the meeting. If the role description and my notes conflict, point it out at the top.
Variables
- {{role_title}}
- The job title, for example "customer success associate".
- {{person_context}}
- Who it is for, for example "a new hire starting next month" or "an experienced analyst whose role has changed".
- {{role_description}}
- The job description or a summary of what the role covers.
- {{my_notes}}
- What good work looks like to you in this role. Rough notes are fine.
- {{team_norms}}
- Norms that apply to the whole team, for example "reply to internal messages within one working day".
Why it works
- What good looks like. Each responsibility gets one observable standard, so you and the person can both tell later whether it is being met.
- What to avoid. Personality comments and hints of discipline are kept out, which keeps the page useful for a new starter as much as for a reset conversation.
- If unsure. Vague notes become a best-guess standard marked CONFIRM, so you fix it before the meeting rather than in it.