Maya Patel·
Dumped my fragmented calendar in and got a time-blocked week that protects my morning deep work
Creates a personalized weekly schedule with protected deep work blocks, meeting clusters, and energy-aligned task scheduling.
Time Blocking & Deep Work Designer
You are a productivity architect who designs schedules for knowledge workers. Create a personalized time-blocking system for {{person_name}}, a {{job_title}}. Their most cognitively demanding work is: {{deep_work_tasks}}. Their energy peak hours are: {{peak_hours}}. Recurring commitments include: {{recurring_commitments}}. They work from {{work_hours}} in a {{work_location}} environment. They struggle with: {{productivity_challenges}}. Deliver: (1) An ideal weekly template showing time blocks for: deep work, shallow work, meetings, email/communication, breaks, learning, planning, (2) A daily schedule showing how to cluster meetings to protect focus time, (3) Deep work block scheduling aligned to energy peaks with pre-work rituals, (4) An email/communication batching schedule, (5) A task batching strategy by cognitive load (high/medium/low), (6) Transition rituals between different types of work, (7) A weekly review template for planning the week ahead, (8) A daily shutdown ritual and next-day preparation routine, (9) An interruption management protocol, (10) A quarterly time audit framework to continuously optimize. Include specific time ranges and make it realistic.
Ergebnisse
# Time-Blocking System — Elena, Staff Software Engineer
**Deep work:** architecture design + complex coding. **Energy peak:** 09:00–12:00. **Recurring:** daily standup 10:15, Tue/Thu team syncs. Works **08:30–17:30**, hybrid. **Struggles:** meeting fragmentation, reactive Slack.
## Ideal weekly template
| | Mon | Tue | Wed | Thu | Fri |
|-|-----|-----|-----|-----|-----|
| 08:30–09:00 | Plan | Plan | Plan | Plan | Plan |
| 09:00–11:30 | Deep | Deep | Deep | Deep | Deep |
| 11:30–12:00 | Email | Email | Email | Email | Review |
| 13:00–15:00 | Shallow | Meetings | Shallow | Meetings | Shallow |
| 15:00–16:30 | Deep | Code review | Deep | Code review | Buffer |
| 16:30–17:00 | Shutdown | Shutdown | Shutdown | Shutdown | Weekly review |
## Key rules
- **Standup at 10:15** sits at the *edge* of the morning block, not the middle — protects 09:00–10:00 flow.
- **Meetings clustered** Tue/Thu afternoons; Mon/Wed/Fri are maker days.
- **Email/Slack batched** at 11:30 and 16:00 only; notifications off otherwise.
## Rituals
- **Deep-work pre-ritual:** close tabs, headphones, write the one outcome.
- **Transition:** 5-min walk between deep and shallow.
- **Daily shutdown:** review done, set tomorrow's top 3.
**Task batching:** high cognitive load → mornings; low (admin, expenses) → late afternoon. **Interruption protocol:** Slack status "focus until 11:30," urgent = phone. **Weekly review (Fri):** clear inbox, plan next week's blocks. **Quarterly time audit:** track a week, compare to template, adjust.
Modell: Claude Sonnet 4
19 Likes7 SavesScore: 11
1 Kommentar
Anna Hofmann·
Okay this project management output just fixed my week.