Executive Personal Productivity Operating System

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.

INPUTS

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]

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]

Treat an explicit “None” as supplied information, not a missing input.

CHATGPT OPERATING BOUNDARIES

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.

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.

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.

INPUT AND EVIDENCE RULES

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.

WORKFLOW

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.

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. 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.

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.

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.

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.

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.

REQUIRED DELIVERABLE

### 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.

### 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.

### 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

Do not present estimated capacity as measured fact.

### 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.

### 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.

If exact scheduling is blocked, provide sequence and duration guidance without inventing clock times.

### 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.

### 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. 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

### 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.

### 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.

### 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.

### 12. Verification and Acceptance Record
Create a table with: acceptance check, baseline evidence, expected observation, actual observation, evidence source, result, and unresolved issue.

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

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
- 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

FINAL QUALITY CHECK

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.