Skip to main content
Ethan Reed·

Sorted my tasks by cognitive load and mapped them to my energy curve - deep work only in the mornings

Classifies all your tasks by cognitive demand and creates an energy-matched batching schedule for sustainable productivity.

Cognitive Load Task Batching System

You are a cognitive ergonomics specialist. Help me batch my tasks by cognitive load. Here is my complete task list: {{all_tasks}}. For each task, I need to know: (1) Cognitive load tier (Deep/Heavy cognitive, Moderate cognitive, Light cognitive, Automatic/Habitual), (2) Required mental resources (creative, analytical, administrative, social), (3) Recovery time needed after, (4) Best time of day match based on typical cognitive demands. My peak cognitive hours are: {{peak_cognitive_hours}}. My low-energy hours are: {{low_energy_hours}}. Create: (A) A cognitive load classification table for all tasks, (B) An ideal daily schedule mapping task tiers to energy levels, (C) A 'cognitive budget' — max deep cognitive hours per day before diminishing returns, (D) Recovery activity suggestions between heavy tasks, (E) Warning signs of cognitive overload to watch for. Base on cognitive psychology research.

Ergebnisse

Classified your 9 tasks by cognitive load and mapped them to your energy curve (peak 8–11am, trough 2–4pm). Your cognitive budget is ~4 deep hours/day — past that, output degrades. ## A. Cognitive load classification | Task | Tier | Mental resource | Recovery after | Best slot | |------|------|-----------------|----------------|-----------| | Write the product strategy doc | Deep | Creative + analytical | 20 min | 8–10am | | Debug the billing edge case | Deep | Analytical | 15 min | 9–11am | | Design review feedback | Moderate | Analytical + social | 10 min | 11am–12pm | | 1:1s with reports | Moderate | Social | 10 min | 1–2pm | | Sprint planning prep | Moderate | Analytical | 10 min | 10–11am | | Email + Slack triage | Light | Administrative | none | 12pm / 4:30pm | | Expense report | Automatic | Administrative | none | 2–3pm (trough) | | Calendar cleanup | Automatic | Administrative | none | trough | | Reading saved articles | Light | Absorptive | none | trough | ## B. Ideal daily schedule - **8:00–11:00 (peak):** one deep task only (strategy doc OR debugging — never both). - **11:00–12:00:** moderate (reviews, planning). - **12:00–12:30:** light comms batch. - **13:00–14:00:** social-moderate (1:1s). - **14:00–16:00 (trough):** automatic/admin only. - **16:30:** final comms sweep. ## C. Cognitive budget **Max 4 deep hours/day.** Stacking a third deep task = sharply diminishing returns and spillover fatigue tomorrow. ## D. Recovery between heavy tasks After a deep block: 10-min walk, no screens, hydrate. Do not chain two Deep tasks without a real break. ## E. Overload warning signs Re-reading the same paragraph, irritability, opening Slack reflexively, "productive procrastination" (reorganizing instead of doing). When you notice these → stop deep work, switch to admin or take the break.

Modell: Claude Sonnet 4

10 Likes3 SavesScore: 6

1 Kommentar

Chloe Adams·

Been after a good workflow automation prompt for a while, this nails it.

    Wir verwenden Cookies, um dein Erlebnis zu verbessern. Analytics-Cookies helfen uns, Prompt2Love weiterzuentwickeln. Einstellungen