Le Réducteur de Changement de Contexte : Transformez une Liste de Tâches Désordonnée en un Plan Quotidien par Lots
Pourquoi ce prompt est important
Research on workplace interruptions (Gloria Mark, UC Irvine) found it takes an average of 23 minutes to fully regain focus after a context switch. Someone who alternates between deep work and shallow admin four or five times in a single day — a completely normal pattern for anyone managing their own unsorted task list — can lose over an hour and a half of effective focus to switching costs alone, on top of the decision fatigue of constantly re-deciding what to do next. A batched plan front-loads that decision once, in the morning, instead of dozens of times throughout the day.
À quoi nous l'utilisons
It's Monday morning and you're staring at 14 unsorted items across your inbox, task manager, and sticky notes — three of them need deep focus, five are quick admin, four are messages you need to reply to, and two are calls. You also have three fixed meetings scattered between 10am and 3pm. Instead of tackling tasks in the order they arrived (which means bouncing between deep thinking and shallow replies all day), you want one realistic plan before you open your first tab.
Prompt
Act as a productivity systems consultant who specializes in cognitive-load-aware scheduling for knowledge workers. Context: - My energy/focus pattern: [YOUR ENERGY PATTERN — e.g. "sharpest 9-11am, foggy after lunch until 2pm, second wind 4-6pm"] - My fixed commitments today: [LIST YOUR MEETINGS/CALLS WITH TIMES] - My raw, unsorted task list: [PASTE YOUR TASK LIST HERE — one per line, don't pre-sort them] Task: Group these tasks into batches that share the same cognitive mode (deep creative/analytical work, shallow admin, communication/social, reactive/inbox). Assign each batch to a time-of-day slot that matches my stated energy pattern, working around my fixed commitments. Minimize the number of times I switch between cognitive modes across the day. Constraints: - Create no more than 4 batches total. - Every batch must include a one-sentence rationale explaining why those tasks belong together. - Do not schedule deep/analytical work immediately after a meeting or right before a fixed commitment — treat those transition slots as shallow-work buffer zones. - If a task doesn't fit cleanly into any batch, flag it explicitly rather than forcing it in. Output format: A table with columns: Time Block | Batch Name | Tasks | Rationale. Follow the table with a short "Watch out for" section (2-3 bullets) flagging any risky transitions or tasks that were hard to place.
Résultat
| Time Block | Batch Name | Tasks | Rationale |
|---|---|---|---|
| 9:00–10:00am | Deep Work: Q3 Roadmap | Draft Q3 feature prioritization doc; review competitor pricing analysis | Both require uninterrupted analytical thinking and benefit from your sharpest focus window before the 10am meeting. |
| 10:00–11:30am | [Fixed] Standup + Design Review | — | Fixed commitments — treated as a hard boundary. |
| 11:30am–12:30pm | Shallow Admin Buffer | Approve 3 expense reports; update project tracker; clear calendar invites | Placed right after meetings since you're already in a reactive, lower-focus mode — no benefit lost by doing shallow work here. |
| 1:30–2:00pm | [Fixed] Client Call | — | Fixed commitment. |
| 2:00–3:00pm | Reactive/Communication | Reply to 4 pending Slack threads; respond to legal's contract question; send follow-up to client from the call | Grouped because your stated post-lunch fog makes this the wrong window for deep work, but you're already primed for conversational mode right after the call. |
| 4:00–5:30pm | Deep Work: Second Window | Finish competitor pricing analysis (carryover); outline next sprint's technical spec | Your stated second wind (4-6pm) is the only other slot with enough uninterrupted runway for analytical work. |
Watch out for:
- The 12:30–1:30pm slot is unaccounted for — if that's your lunch break, good. If not, treat it as a shallow-work overflow buffer, not a place to start anything deep.
- "Review competitor pricing analysis" spans two batches (morning start, afternoon finish) — this is intentional since it's genuinely a 90-minute task, but confirm you're comfortable resuming analytical work mid-task rather than finishing it in one sitting.
- You listed "brainstorm Q4 offsite ideas" as a task, but it didn't fit any batch cleanly — it's creative-generative rather than analytical or administrative. Consider giving it its own 20-minute slot rather than folding it into deep work, since forcing it alongside roadmap work may dilute both.
Cas d'usage : C'est lundi matin et vous regardez 14 éléments non triés dans votre boîte de réception, votre gestionnaire de tâches et vos notes autocollantes — trois d'entre eux nécessitent une concentration approfondie, cinq sont des tâches administratives rapides, quatre sont des messages auxquels vous devez répondre, et deux sont des appels. Vous avez également trois réunions fixes dispersées entre 10 h et 15 h. Au lieu d'attaquer les tâches dans l'ordre où elles sont arrivées (ce qui signifie passer de la réflexion profonde aux réponses superficielles toute la journée), vous voulez un plan réaliste avant d'ouvrir votre premier onglet.
Pourquoi c'est important : La recherche sur les interruptions au travail (Gloria Mark, UC Irvine) a révélé qu'il faut en moyenne 23 minutes pour retrouver pleinement sa concentration après un changement de contexte. Une personne qui alterne entre travail profond et tâches administratives superficielles quatre ou cinq fois par jour — un schéma tout à fait normal pour quiconque gère sa propre liste de tâches non organisée — peut perdre plus d'une heure et demie de concentration effective rien qu'en coûts de changement, sans compter la fatigue décisionnelle liée au fait de devoir constamment décider quoi faire ensuite. Un plan regroupé avance cette décision une fois, le matin, au lieu de dizaines de fois au cours de la journée.
Ce prompt utilise une structure Rôle + Contexte + Tâche + Contraintes + Format de Sortie. Le choix de conception clé est de forcer le modèle à traiter les réunions comme des limites strictes et à signaler explicitement les tâches qui ne s'intègrent pas bien — un prompt qui force silencieusement chaque tâche dans un lot ordonné cacherait les points de friction exacts (comme une tâche qui s'étend sur deux lots, ou une tâche créative qui ne devrait pas être mélangée avec un travail analytique) qui font réellement dérailler une journée.