thinkhard.SI

Prompt repository Managers & leads

Write a team charter that says what your team owns and what it does not

Other teams are unsure what your team does, and you need a charter covering its purpose, what it owns, how to request work and who decides what.

Registry no.
MGT-054
Collection
Managers & leads
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
8

Managers & leadsAny chat

The prompt

Score 10 of 10, Excellent

Use it when Other teams are unsure what your team does, and you need a charter covering its purpose, what it owns, how to request work and who decides what.

  • {{team_name}}
  • {{my_manager}}
  • {{purpose}}
  • {{ownership}}
  • {{not_ours}}
  • {{customers_and_dependencies}}
  • {{intake}}
  • {{measures}}
Full prompt and why it works
Prompt
Draft a team charter for {{team_name}}, for my team and the teams we work with to read, so that anyone can tell in two minutes what we own, what we do not, how to bring us work and who decides what. It is a draft for the team to discuss with me and for {{my_manager}} to approve. Day-to-day norms such as meeting habits and reply times belong in our working agreement, so leave them out.

Why the team exists, in my words: {{purpose}}

What we own today (products, services, processes, systems, decisions):
"""
{{ownership}}
"""

Work people bring to us that we think belongs elsewhere, and where it should go:
"""
{{not_ours}}
"""

Who we serve, and the teams we depend on or who depend on us: {{customers_and_dependencies}}
How work reaches us now, and how we want it to: {{intake}}
How we measure whether we are doing our job: {{measures}}

Use these headings:
1. Purpose: two sentences at most.
2. What we own: a bulleted list, each item specific enough that a newcomer could route a request, for example "The billing service and its alerts" rather than "Billing".
3. What we do not own: each item with where it goes instead.
4. Who we serve and how to work with us: how to request work, what to include, how we prioritize and what response to expect.
5. Decision rights: a table with the columns Decision, We decide, We are consulted, Someone else decides (name the role).
6. How we measure success: the measures above, each with its source.
7. Review: when we will revisit the charter.

Keep it under 600 words, in plain words a new hire in another team could follow. Do not claim ownership of anything not in my lists, and do not promise response times I have not given. If it is unclear whether something is ours, put it under a final heading, "To agree", as a question for the team or for {{my_manager}}.

Variables

{{team_name}}
Your team, for example "the data platform team".
{{my_manager}}
Who approves the charter, for example "the head of engineering".
{{purpose}}
Why the team exists, in a sentence or two of your own words.
{{ownership}}
What the team owns today: products, services, processes, systems and decisions.
{{not_ours}}
Requests that reach you but belong elsewhere, and where each should go.
{{customers_and_dependencies}}
Who you serve, who you depend on and who depends on you, for example "sales and support; we depend on IT for accounts".
{{intake}}
How work reaches you now and how you want it to, for example "direct messages now; a request form from next month".
{{measures}}
How you know the team is doing its job, with where each number comes from.

Why it works

  • Length. The charter covers ownership, intake and decision rights and leaves meeting habits to the working agreement, so the two documents do not overlap.
  • An example. "The billing service and its alerts" against "Billing" shows how specific an ownership line must be for a newcomer to route a request.
  • If unsure. Anything whose owner is unclear goes under "To agree" as a question, rather than being claimed or given away by the AI.

How to use it

  1. Press Fill in blanks and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.
  4. When the answer comes back, check it before you use it. The Fact Check List lists every figure, quote and source in the answer worth checking, riskiest first.
Use it from code

Get this prompt as JSON from the free REST API, with your own text in the blanks, or let an AI assistant fetch it through the MCP server. No key.

curl -s https://thinkhard.si/api/v1/prompts/team-charter

With the MCP server added to Claude, ChatGPT, Cursor or VS Code, call get_prompt with {"prompt": "team-charter"}, or just ask for it by name.