Executive Personal Productivity Operating System

Public field comparison

Executive Personal Productivity Operating System

Executive Personal Productivity Operating System

Design a practical weekly operating system for executive priorities, decisions, delegation, energy management, communication, and follow-through.

Design an evidence-grounded weekly operating system for executive priorities, calendar capacity, decisions, delegation, meetings, communication, energy constraints, and follow-through.

Use this to build a practical executive productivity system around priorities, decisions, delegation, energy, and follow-through.

Use this prompt to turn an executive’s real calendar, priorities, decision backlog, and operating constraints into a practical weekly cadence and controlled rollout plan.

Executive Weekly Planning
Leadership Operating Rhythm
Decision Backlog Management
Delegation System Design
Calendar Redesign
Strategic Priority Planning
Energy Management Review
Founder Productivity System
Meeting Cadence Review
Executive Follow-Through

Executive weekly cadence design
Calendar capacity and focus-time redesign
Decision backlog and ownership triage
Delegation accountability system design
Recurring meeting and communication review
Executive operating-system rollout planning

Role and responsibilities
Current weekly calendar
Strategic priorities
Recurring meetings
Decision backlog
Delegation options
Energy constraints
Communication channels
Review cadence
Non-negotiables
Current friction points
Team support available
Planning horizon
Success criteria

Role and responsibilities
Current weekly calendar
Strategic priorities
Recurring meetings
Non-negotiables
Planning horizon
Success criteria
Decision backlog
Delegation options
Energy constraints
Communication channels
Review cadence
Current friction points
Team support available

Paste your role, responsibilities, weekly calendar, strategic priorities, recurring meetings, decision backlog, delegation options, energy constraints, communication channels, review cadence, non-negotiables, and current friction points. Convert the output into calendar blocks, checklists, delegation rules, and a weekly review ritual.

Open ChatGPT, replace every bracketed variable with current information, and provide sanitized supporting evidence such as a weekly calendar export, recurring-meeting list, decision backlog, priority plan, communication expectations, delegation roster, and known constraints. State “None” where appropriate, then run the prompt. Review and authorize all proposed calendar, meeting, communication, and delegation changes before anyone implements them.

A startup CEO wants to reduce reactive work and create a weekly cadence for strategic decisions, investor updates, hiring, product review, delegation, and follow-through.

A startup CEO supplies a sanitized calendar, strategic priorities, investor and hiring obligations, recurring meetings, unresolved decisions, delegation options, and energy constraints. ChatGPT produces a proposed weekly cadence, decision and delegation registers, meeting-change trials, verification criteria, and a human-controlled rollout plan without claiming that any changes were executed.

Advanced

Advanced

ChatGPT

ChatGPT

planning

planning

executive-productivity
weekly-planning
delegation
decision-management
priority-system
operating-rhythm
founder-productivity
calendar-redesign
leadership-workflow
meeting-cadence
focus
execution
follow-through

executive-productivity
weekly-planning
operating-rhythm
calendar-redesign
decision-management
delegation
meeting-cadence
capacity-planning
follow-through
leadership-workflow

Executive Productivity Operating System Prompt

Executive Productivity Operating System Prompt

Build an executive weekly productivity system for priorities, decisions, delegation, energy, communication, and follow-through.

Design an evidence-grounded executive cadence for priorities, decisions, delegation, meetings, communication, capacity, and follow-through.

Prompt-body line comparison

Removed Added Unchanged context

−You are an executive productivity advisor specializing in leadership operating rhythms, weekly planning systems, decision quality, delegation, energy management, meeting cadence design, communication discipline, and executive follow-through.
+Create a practical weekly executive operating system from the supplied materials. The result must protect strategic work while preserving essential operational coverage, decision quality, delegation accountability, and realistic recovery capacity.
 
−Your task is to create a practical personal operating system that helps an executive protect strategic work, clarify decisions, reduce reactive work, delegate effectively, and maintain a realistic weekly cadence.
+INPUTS
 
−Context:
−Use the context below. If any important detail is missing, list it under “Missing Inputs” and make a conservative assumption before continuing.
+Minimum tailoring inputs:
+- Role and responsibilities: [Role and responsibilities]
+- Current weekly calendar: [Current weekly calendar]
+- Strategic priorities: [Strategic priorities]
+- Recurring meetings: [Recurring meetings]
+- Non-negotiables: [Non-negotiables]
+- Planning horizon: [Planning horizon]
+- Success criteria: [Success criteria]
 
−* Role and responsibilities: [Role and responsibilities]
−* Current weekly calendar: [Current weekly calendar]
−* Strategic priorities: [Strategic priorities]
−* Recurring meetings: [Recurring meetings]
−* Decision backlog: [Decision backlog]
−* Delegation options: [Delegation options]
−* Energy constraints: [Energy constraints]
−* Communication channels: [Communication channels]
−* Review cadence: [Review cadence]
−* Non-negotiables: [Non-negotiables]
−* Current friction points: [Current friction points]
−* Team support available: [Team support available]
−* Planning horizon: [Planning horizon]
−* Success criteria: [Success criteria]
+Useful operational inputs:
+- Decision backlog: [Decision backlog]
+- Delegation options: [Delegation options]
+- Energy constraints: [Energy constraints]
+- Communication channels: [Communication channels]
+- Review cadence: [Review cadence]
+- Current friction points: [Current friction points]
+- Team support available: [Team support available]
 
−Important constraints:
+Treat an explicit “None” as supplied information, not a missing input.
 
−* Do not create an unrealistic productivity system that requires excessive administrative overhead.
−* Do not invent responsibilities, team members, meetings, constraints, or priorities not provided.
−* Separate confirmed context from assumptions.
−* Keep the system practical for the executive’s real calendar and energy limits.
−* Protect strategic work without ignoring urgent operational responsibilities.
−* Avoid generic productivity advice.
−* Do not recommend removing important meetings without explaining the tradeoff.
−* Do not treat energy, stress, or workload constraints as medical advice.
−* Include human review gates for legal, financial, HR, security, public-facing, investor, hiring, compliance, or other high-impact decisions.
−* Make the system simple enough to run weekly.
−* Focus on decisions, priorities, delegation, communication, and follow-through.
+CHATGPT OPERATING BOUNDARIES
 
−Task:
−Create a weekly executive personal productivity operating system.
+Use ChatGPT to analyze only the text, files, and facts supplied in this conversation; reconcile schedule information; identify capacity conflicts; compare operating choices; and draft proposed calendar blocks, registers, rules, checklists, and review rituals.
 
−Output format:
+Do not imply access to a live calendar, inbox, task manager, messaging platform, HR system, company records, or current organizational conditions unless their contents are supplied here. Do not claim to have rescheduled or cancelled meetings, sent messages, assigned work, obtained approval, measured results, or implemented the system. All changes are proposals until an authorized person executes them and supplies evidence.
 
−### 1. Executive Context Summary
+Do not expose unnecessary personal, employee, candidate, investor, customer, security, legal, or health information. Recommend redaction where detailed records are not needed. Treat workload and energy information as planning constraints, not as a medical diagnosis. Legal, financial, HR, hiring, security, compliance, investor, public-facing, and other consequential decisions require review by the accountable human owner.
 
−Summarize:
+INPUT AND EVIDENCE RULES
 
−* Role and responsibilities
−* Strategic priorities
−* Current calendar pattern
−* Recurring meetings
−* Decision backlog
−* Delegation options
−* Energy constraints
−* Communication channels
−* Non-negotiables
−* Current friction points
−* Missing inputs
+1. Classify material as one of: supplied fact, user-reported observation, assumption, unknown, or conflict.
+2. Never convert an aspiration, tentative meeting, proposed delegation, or inferred preference into a confirmed fact.
+3. If role scope, calendar availability, strategic priorities, non-negotiables, planning horizon, or success criteria are absent or materially contradictory, list up to five blocking clarification questions. Then provide only a provisional, unscheduled framework; do not invent specific times or capacity.
+4. If a useful operational input is missing, preserve it as unknown, state the effect on the recommendation, and continue only where bounded progress is safe.
+5. If sources conflict, record both versions, identify the decision owner needed to resolve the conflict, and avoid silently choosing one.
+6. Use conservative assumptions explicitly. Do not invent team members, authority, deadlines, meeting purposes, energy patterns, response-time obligations, or available hours.
 
−### 2. Operating Principles
+WORKFLOW
 
−Create practical operating principles for the executive.
−Include:
+1. Normalize the operating context
+- Extract responsibilities, priority outcomes, fixed commitments, movable commitments, recurring meetings, deadlines, communication expectations, decision obligations, support capacity, energy constraints, and protected non-work commitments.
+- Note time zones, travel, fragmented blocks, preparation time, transition time, and after-hours obligations when supplied.
+- Identify calendar entries whose purpose, owner, required attendance, or recurrence is unclear.
 
−* How priorities should be chosen
−* How decisions should be handled
−* How delegation should work
−* How meetings should be evaluated
−* How communication should be managed
−* How strategic work should be protected
−* How follow-through should be tracked
+2. Establish a realistic capacity baseline
+- Estimate scheduled meeting time, protected focus time, communication-processing time, management time, decision time, buffers, and unallocated capacity only when the supplied calendar supports the calculation.
+- Show the calculation method and label estimates.
+- Flag overcommitment, double counting, insufficient transition time, recurring spillover, excessive context switching, and plans that consume all nominal capacity.
+- Preserve enough buffer for urgent operational work rather than optimizing the calendar to full utilization.
 
−### 3. Weekly Cadence
+3. Translate strategy into weekly commitments
+- Convert strategic priorities into no more than a realistic number of weekly outcomes based on available capacity.
+- For each outcome, define why it matters, the executive’s required contribution, a next observable deliverable, a proposed block, dependencies, and the consequence of deferral.
+- Distinguish strategic work from routine administration and urgent operational coverage.
 
−Design a weekly cadence with:
+4. Triage decisions and delegation
+- Assess each supplied decision by impact, urgency, reversibility, information readiness, dependency, accountable decision owner, and review requirements.
+- Separate decisions the executive must own from recommendations, consultations, notifications, and delegable preparation work.
+- For delegation, define the outcome, owner, authority boundary, deadline, check-in point, acceptance evidence, escalation trigger, and retained executive responsibility.
+- Do not recommend delegation where authority, competence, confidentiality, or accountability is unclear without flagging the risk.
 
−* Weekly planning block
−* Strategic work blocks
−* Decision review block
−* Team alignment block
−* Delegation review block
−* Communication processing windows
−* Buffer time
−* End-of-week review
−* Recovery or low-energy work periods, if relevant
+5. Evaluate meetings and communication
+- Evaluate recurring meetings using purpose, decision or coordination value, required attendees, preparation burden, cadence, duration, and viable asynchronous substitute.
+- For any proposal to remove, shorten, combine, delegate, or convert a meeting, state the benefit, trade-off, affected stakeholder, operational risk, trial period, and approval needed.
+- Define channel-specific processing windows only from supplied communication expectations. Preserve a clearly bounded path for genuine emergencies.
 
−### 4. Decision and Delegation System
+6. Design the weekly cadence
+- Place planning, strategic work, decision review, team alignment, delegation follow-up, meeting preparation, communication processing, buffers, low-energy work, and weekly review around fixed commitments and stated energy constraints.
+- Avoid overlapping blocks and unexplained capacity. Provide an alternative cadence when the preferred design depends on unresolved constraints.
 
−Create a system for:
+7. Define a controlled rollout
+- Separate recommendations into proposed, authorized, scheduled, executed, observed, verified, blocked, and rejected states.
+- Start with reversible trials where possible. Identify who must authorize calendar, meeting, communication, or delegation changes.
+- Specify rollback conditions for trials that cause missed coverage, slower critical decisions, stakeholder confusion, delegation failure, or unsustainable workload.
 
−* Capturing decisions
−* Prioritizing decisions
−* Deciding what the executive must own
−* Deciding what can be delegated
−* Assigning owners
−* Setting deadlines
−* Tracking follow-up
−* Escalating stuck items
+REQUIRED DELIVERABLE
 
−### 5. Calendar Redesign
+### 1. Input and Evidence Ledger
+Create a table with: item, supplied value or observation, evidence classification, source, confidence, conflict or gap, effect on plan, and clarification owner.
 
−Recommend calendar changes.
−Create a table with:
+### 2. Executive Operating Diagnosis
+Summarize role scope, strategic obligations, fixed commitments, current cadence, decision load, delegation capacity, communication load, energy constraints, friction points, and non-negotiables. Separate supplied facts from assumptions and unknowns.
 
−* Current calendar issue
−* Recommended change
−* Reason
−* Impact
−* Effort
−* Risk
−* What to protect
−* What to remove, shorten, delegate, or batch
+### 3. Capacity and Constraint Map
+Provide:
+- A weekly capacity calculation with method and assumptions
+- Fixed versus movable commitments
+- Focus-time availability
+- Meeting and communication load
+- Buffer and transition needs
+- Overcommitment or fragmentation findings
+- Constraints that prevent precise scheduling
 
−### 6. Meeting and Communication Rules
+Do not present estimated capacity as measured fact.
 
−Create rules for:
+### 4. Operating Principles and Trade-offs
+Define concise rules for priority selection, executive ownership, decision handling, delegation, meeting acceptance, communication response, strategic-work protection, urgent-work coverage, and follow-through. For each important rule, state the trade-off or failure mode it controls.
 
−* Which meetings should stay
−* Which meetings should be shortened
−* Which meetings should become async updates
−* Which communication channels should be checked when
−* What requires immediate response
−* What can wait
−* What should be delegated
+### 5. Proposed Weekly Cadence
+Create a table with: day or frequency, proposed time window, block type, intended outcome, duration, energy fit, dependencies, flexibility, buffer, and evidence status. Include weekly planning, strategic blocks, decision review, team alignment, delegation review, communication windows, preparation, buffer, low-energy work where relevant, and end-of-week review.
 
−### 7. Priority and Follow-Through Dashboard
+If exact scheduling is blocked, provide sequence and duration guidance without inventing clock times.
 
−Design a simple weekly dashboard with:
+### 6. Calendar Change Register
+Create a table with: current issue, current evidence, proposed change, reason, expected benefit, trade-off, effort, operational risk, stakeholder impact, approval owner, trial period, rollback trigger, and current status. Cover what to protect, move, batch, shorten, delegate, convert to asynchronous work, or consider removing.
 
−* Top strategic priorities
−* Decisions pending
−* Delegated items
−* Follow-ups owed
−* Meetings to prepare for
−* Risks or blockers
−* Energy warning signs
−* Wins and lessons
+### 7. Decision and Delegation Register
+Create a table with: item, type, impact, urgency, reversibility, information readiness, executive role, proposed owner, authority boundary, deadline, check-in, acceptance evidence, escalation trigger, human review gate, and status.
 
−### 8. Review Ritual
+### 8. Meeting and Communication Protocol
+Specify:
+- Criteria for keeping, shortening, combining, delegating, or converting meetings
+- Required agenda and pre-read rules where appropriate
+- Channel-purpose mapping
+- Proposed processing windows
+- Definition and route for urgent matters
+- Response expectations supported by the supplied context
+- Delegation and escalation rules
+- Stakeholder approvals needed before changing established practices
 
−Create a weekly review ritual.
−Include:
+### 9. Weekly Priority and Follow-Through Dashboard
+Design a lightweight dashboard containing: weekly outcomes, protected strategic blocks, decisions pending, delegated outcomes, follow-ups owed, meetings requiring preparation, blockers, capacity or energy warnings, wins, lessons, and items requiring human review. Keep administration proportionate to the executive’s available time.
 
−* Questions to ask
−* Metrics or signals to check
−* Decisions to close
−* Delegated items to review
−* Calendar adjustments
−* Communication cleanup
−* Next-week priority selection
+### 10. Weekly Review Ritual
+Provide a time-boxed checklist that reconciles planned versus observed work, closes or reclassifies decisions, reviews delegation evidence, identifies missed follow-ups, checks workload and calendar drift, records lessons, selects next-week outcomes, and captures unresolved risks. Distinguish unavailable observations from negative results.
 
−### 9. Implementation Plan
+### 11. Rollout and Control Plan
+Organize actions into first 24 hours, first week, and first month. For each action include: proposed owner, authorization needed, execution step, expected observation, evidence to collect, decision date, rollback condition, and status. Identify what to test, simplify, stop proposing, or review with an assistant, chief of staff, manager, or team lead.
 
−Create a practical rollout plan.
−Include:
+### 12. Verification and Acceptance Record
+Create a table with: acceptance check, baseline evidence, expected observation, actual observation, evidence source, result, and unresolved issue.
 
−* First 24 hours
−* First week
−* First month
−* What to test
−* What to simplify
−* What to stop doing
−* What to review with an assistant, chief of staff, manager, or team lead
+At minimum, test whether:
+- Proposed blocks fit without overlap and respect fixed commitments
+- Weekly outcomes fit the supported capacity estimate
+- Essential operational and emergency coverage remains available
+- Every delegated outcome has an owner, authority boundary, deadline, and escalation path
+- Consequential decisions have an accountable human review gate
+- Meeting changes state stakeholder impact and trade-offs
+- The dashboard and review ritual can be maintained with low administrative overhead
+- Assumptions, conflicts, and unknowns remain visible
 
−### 10. Final Handoff
+Unless implementation evidence is supplied, record actual observations as not observed and results as unverified. Do not describe the operating system as tested, adopted, approved, completed, or effective merely because the plan has been drafted.
 
+### 13. Final Handoff
 Provide:
−
−* Recommended operating system summary
−* Calendar rules
−* Delegation rules
−* Decision rules
−* Review checklist
−* Missing inputs
−* Assumptions made
−* Human review points
−
−Verification:
−Before finalizing, confirm that:
+- Recommended operating-system summary
+- Calendar rules
+- Decision rules
+- Delegation rules
+- Meeting and communication rules
+- Weekly review checklist
+- Blocking questions
+- Assumptions, conflicts, and unknowns
+- Human authorization points
+- Proposed next action and responsible owner
+- Clear statement that ChatGPT produced recommendations only and did not execute calendar, communication, delegation, or organizational changes
 
−* The system fits the real calendar and does not require unrealistic administrative overhead.
−* Strategic priorities, decisions, delegation, energy, communication, and follow-through are addressed.
−* The recommendations are specific to the provided role and constraints.
−* High-impact decisions include human review gates.
−* The system can be converted into calendar blocks, checklists, and delegation rules.
−* Any assumptions and missing inputs are clearly listed.
+FINAL QUALITY CHECK
 
−Begin now. If required context is missing, state the missing inputs first, then continue with conservative assumptions.
+Before returning the deliverable, reconcile all proposed blocks against supplied fixed commitments and capacity. Confirm that every recommendation traces to supplied evidence or an explicit assumption; every consequential change names an authorization owner; every trial has observable acceptance evidence and a rollback condition; and every completion or effectiveness claim is supported by supplied execution evidence. Correct inconsistencies before finalizing.