Help me create a fair, actionable management plan for this team situation. Team and operating context: [TEAM CONTEXT] Problem to address: [MANAGEMENT PROBLEM] Confirmed observations and evidence: [FACTS AND EXAMPLES] Roles, decision rights, and dependencies: [ROLES AND DEPENDENCIES] Constraints and desired outcome: [CONSTRAINTS AND OUTCOME] Produce a practical plan with these sections:
1. Problem statement: separate observed facts, impact, and assumptions to test. 2. Immediate actions for the next 10 business days, each in “owner — action — due date — evidence of completion” format. 3. A team operating rhythm covering priorities, status reporting, escalation, and decisions. 4. Expectations for managers and individual contributors, including how feedback will be given and documented. 5. A 30-day review agenda with measures that show whether the problem improved. Make accountability specific without turning normal delivery risk into personal blame. Recommend one accountable owner for each decision, while naming consulted or informed roles only when necessary. Where performance concerns exist, use concrete observed behavior, expected standard, support offered, and review date; do not diagnose motives or make employment, legal, or HR conclusions. Preserve confidentiality and do not include private details that the whole team should not receive. Do not invent missed dates, employee history, commitments, or authority. Before answering, check that no action has more than one accountable owner and that every expectation is observable. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TEAM CONTEXT] | Describe the team, its mission, size, work cadence, and relevant stakeholders. | A seven-person customer success team supporting 120 mid-market accounts; weekly pipeline review on Mondays. |
| [MANAGEMENT PROBLEM] | State the specific operational or people-management issue to solve. | Renewal risks are being surfaced too late for sales and leadership to help. |
| [FACTS AND EXAMPLES] | Provide confirmed examples, dates, metrics, and observed impacts. | Four of six August churns had no documented risk plan until the final 30 days; account notes are inconsistent. |
| [ROLES AND DEPENDENCIES] | List key roles, decision makers, and teams the work depends on. | CSMs own account plans; CS lead owns process; sales owns commercial negotiation; support provides incident data. |
| [CONSTRAINTS AND OUTCOME] | State limits such as staffing or policy and define the desired result. | No new headcount this quarter; by November, all red accounts need a documented plan at least 60 days before renewal. |
How to use
- Provide facts, examples, and impacts separately from your interpretation of why the problem exists.
- Use the first 10-day actions as the agenda for your next team meeting and assign named owners.
- Check that role expectations match actual decision authority before sharing the plan.
- Follow up with: “Turn the operating rhythm into a one-page team agreement with weekly meeting agendas.”
Variations
Role clarity
Use when two or more people believe they own the same work.
Create a role-clarity plan for [WORKSTREAM]. The involved roles are [ROLES], current handoffs are [CURRENT PROCESS], and recurring conflicts are [EXAMPLES]. Produce a decision-rights table with one accountable owner per decision, a handoff checklist, escalation path, and a 30-day adoption plan. Do not redefine reporting lines or promise authority not provided. Check that each decision has one owner and that no role is assigned work outside its stated remit.
Performance conversation
Use to prepare for a documented, supportive conversation about observable performance.
Prepare a manager conversation plan about [OBSERVED PERFORMANCE GAP] with [EMPLOYEE ROLE]. Use only these facts: [DOCUMENTED EXAMPLES]. The expected standard is [EXPECTED STANDARD], and available support is [SUPPORT]. Produce a private meeting agenda, neutral wording, questions to understand blockers, a written follow-up summary, and a review date of [DATE]. Do not infer intent, diagnose health issues, or recommend disciplinary action. Check that each concern is tied to an observable example.
Project recovery
Use when cross-functional delivery has slipped and needs a shared reset.
Create a work-management recovery plan for [PROJECT]. Current status: [FACTS]. Remaining scope: [REMAINING WORK]. Stakeholders and dependencies: [STAKEHOLDERS]. Deadline and constraints: [CONSTRAINTS]. Produce a recovery decision, a milestone plan with owners, risk triggers, a twice-weekly update format, and an escalation rule. Do not promise the original deadline is achievable without evidence. Check that every milestone has acceptance criteria and a decision owner.
Tips
- Use examples with dates and work artifacts, not personality labels such as “unreliable” or “not proactive.”
- Separate an accountable owner from contributors; shared accountability usually means nobody knows who makes the final call.
- Create escalation rules before a deadline is at risk, including the threshold, recipient, and decision needed.
- For sensitive performance issues, use AI to organize confirmed notes, then follow applicable HR policy and seek HR guidance where required.
FAQ
Can AI help write a performance improvement plan?
It can help organize observed behavior, expectations, support, and review dates. Employment actions should follow your organization’s HR and legal process.
How do I make team accountability fair?
Assign actions based on authority and access to the work, state the evidence of completion, and surface dependencies instead of blaming the person waiting on them.
What should a management cadence include?
It should define where priorities are set, how risks are reported, who decides trade-offs, and when the team reviews results.