Develop a Delegation Framework
ChatGPT Prompt
Build a delegation framework for a {role} managing {team_size} people. Start with the audit: list current work against a matrix of impact versus who-else-could-do-this, and identify what should be delegated, automated, or dropped entirely. Define delegation levels from 'do exactly this' to 'decide and act, tell me afterwards' and the criteria for choosing a level based on the person's demonstrated capability with THIS type of task, not their seniority. Give the handover conversation structure — context, outcome, constraints, check-in points, and what 'good' looks like — plus the follow-up cadence that supports without micromanaging. Add the four things that should never be delegated and the recovery process when delegated work goes wrong.
💡 Pro Tip: Replace placeholders in [BRACKETS] with your specific information for best results.
How to Use This Prompt
- 1Click the copy button above to copy the prompt to your clipboard
- 2Open ChatGPT, Claude, or your preferred AI assistant
- 3Paste the prompt and replace any [PLACEHOLDER TEXT] with your specific details
- 4Review the AI's response and iterate if needed for better results
Related Tags
Related Prompts
Write Conflict Resolution Guidelines
Write workplace conflict resolution guidelines for managers at a {company_size} company. Distinguish clearly between three categories that require different handling: task conflict (often productive), interpersonal conflict, and conduct violations (which are not conflicts and must escalate immediately). For the first two, give a staged process — direct conversation, facilitated conversation, formal mediation, escalation — with the criteria for moving between stages. Include a manager script for the facilitated conversation, rules for documentation, guidance on remaining neutral while still being accountable for outcomes, and the specific situations where HR or legal must be involved from the first moment rather than after attempts to resolve it locally.
Design a Daily Planning Routine
Design a daily planning routine for a {role} working {work_hours}. Cover both ends: a 10-minute evening shutdown that closes open loops and sets tomorrow's priorities while today's context is still fresh, and a 5-minute morning start that confirms rather than re-decides. Specify how the day's one or two non-negotiable outcomes are chosen and how they get calendar time before the day fills. Include the mid-day checkpoint, the rule for handling work that arrives after the plan is set, and what to do when the day is derailed by 10am — since a plan that only survives good days is not a system. Give the exact questions asked at each step and keep the whole routine under 20 minutes.
Write a Focus and Deep Work Schedule
Design a deep work schedule for a {role} who needs {deep_hours} of focused work per day but currently gets {actual_hours}. Diagnose the gap first — meeting fragmentation, notification interruption, unclear priorities, or task-switching — since each has a different fix. Then build the schedule: block placement matched to personal energy rather than convention, block length with a realistic ramp for someone not used to sustained focus, and the protection strategy including how to decline meetings without political cost. Cover the pre-block ritual that shortens the warm-up, the environment and device setup, what to do when a block is interrupted anyway, and how to capture intrusive thoughts without leaving the work. Add a weekly review of actual versus planned focus hours.
Develop a Project Management Workflow
Design a project management workflow for a {team_size} team running {project_type} projects in {tool}. Define the stages from intake to closure with explicit entry and exit criteria for each, so 'in progress' means the same thing to everyone. Cover: how work enters (and who can say no), how it is sized and prioritised, work-in-progress limits, the definition of done, handoffs between roles, and how blockers are surfaced within a day rather than at the next status meeting. Specify the meeting cadence and what each meeting decides — cancelling any that only report status a board already shows. Add the fields every item must carry, the automation worth building first, and the three metrics that reveal whether the workflow is working.
Create an Email Management System
Design an email management system for someone receiving roughly {email_volume} messages a day in {email_client}. Define: the processing schedule (two or three fixed windows rather than continuous monitoring, with the reasoning), the triage decision tree — delete, delegate, respond now if under two minutes, defer to a task system with a date, or file — and a folder structure that is deliberately shallow, since elaborate hierarchies cost more to maintain than search does. Add the filters and rules worth setting up first, template responses for the five most repetitive replies, a rule for unsubscribing rather than deleting repeatedly, notification settings, and a weekly review. State what the system does when it inevitably falls behind.
Design a Meeting Agenda Template
Create meeting agenda templates for four types: decision, brainstorm, status or standup, and one-to-one. Each must state at the top the single question the meeting exists to answer, the decision-maker, the required pre-reading, and who genuinely needs to attend versus who can read the notes. Give a timed structure, the facilitator's opening and closing lines, and how outcomes are captured as owner-plus-date rather than a vague 'we should'. Add the test for whether the meeting should exist at all, a rule for ending early when the question is answered, and guidance on async alternatives for each type. Include the follow-up note format, sent within a stated number of hours.