S'inscrire gratuitement

Design a daily shutdown and next-day preparation checklist

Auteur: AILesson5 min de préparationTesté avec:ChatGPTRévisé: 2026-08-28

Réponse rapide

Close open loops, preserve context, and make tomorrow's first action easy to begin. Fournir: Workday and tools, Current shutdown friction, Tomorrow constraints. Résultat attendu: A short repeatable shutdown routine with exceptions, timing, and a ready-to-start tomorrow.

1

Ajouter votre contexte

Votre texte reste dans ce navigateur. AILesson Prompts ne l’envoie ni à un modèle ni à un serveur.

2

Votre prompt

Les champs non remplis restent visibles sous forme d’espaces réservés, afin que vous puissiez quand même copier et modifier le prompt.

Design a daily shutdown and next-day preparation checklist using the supplied workflow.

Work pattern, end time, tools, workspace, and handoffs:
[workflow]

Forgotten items, interruptions, privacy/safety needs, and failures:
[friction]

Tomorrow's appointments, priorities, dependencies, energy, and limits:
[tomorrow]

Create a normal routine that fits 10-20 minutes and a two-minute emergency version. Order actions by dependency. Include capture of loose tasks, triage rather than completion, promise/deadline verification, status/handoff updates, saving files with retrievable names, sensitive-information handling, calendar and first-task review, physical/digital reset, and a clear stop signal only where relevant. Do not require checking every inbox or planning the whole next day.

For each step give trigger, action, done condition, and skip/exception rule. Distinguish items that require a reply now from those merely captured. Prepare tomorrow's first physical action and required material, but do not make unauthorized commitments. Include a weekly maintenance item for stale tasks and routine improvement, plus a one-week trial measure for duration and missed-open-loop rate.
Essayer dans le Playground
Privé par défautL’assemblage du prompt se fait localement dans votre navigateur. Évitez de placer des informations confidentielles dans un service d’IA, sauf si votre organisation l’autorise.

De l'entrée au résultat

Un exemple détaillé

Voyez comment un contexte concret transforme cette recette en résultat utilisable.

Entrée réelle

Workday and tools
Hybrid product designer, normally stops at 18:00. Jira holds tasks, Google Calendar meetings, Slack handoffs, Drive design notes, Figma working files. Laptop must be locked and paper customer notes stored in a drawer. London teammate takes over overnight only when explicitly handed off.
Current shutdown friction
I remember promised replies after dinner, leave unnamed Figma drafts open, and start mornings searching for context. Late meetings sometimes leave only two minutes. Checking Slack can create another 30 minutes of work. Friday tasks often stay stale.
Tomorrow constraints
At 09:30 there is a usability review. Before it, priority is to compare three prototype issues and recommend which to test. Researcher may add notes by 08:45 but has not promised. My best focus is 08:30-10:00. I can spend 15 minutes on shutdown.

Exemple de sortie

15-minute normal shutdown, triggered at 17:45: (1) 3 min—capture loose promises/tasks from today's notes into Jira with source and real due date; done when notes have capture marks, not when tasks are completed. Reply now only if a hard same-day commitment would otherwise be missed. (2) 3 min—update the current Jira item with status, next action, blocker, and file link; skip Slack handoff unless a named London owner has accepted it. (3) 2 min—name/save Figma draft and Drive note with project/date, close duplicates; done when both links reopen. (4) 2 min—check tomorrow's calendar and identify conflicts only. (5) 3 min—prepare the first action: open a comparison note with the three issue IDs and evidence-link slots; write “08:30 compare available evidence; at 08:50 proceed without new researcher notes if absent.” Do not treat 08:45 notes as promised. (6) 2 min—store paper notes, lock laptop, and say “workday closed.”

Two-minute emergency: photograph no sensitive paper; instead place all paper in the locked drawer, add one Jira note containing current task/next action/file link, check the first calendar event, lock laptop. Any uncaptured thought goes on a single permitted paper capture card for next morning.

Friday maintenance: 15 minutes to review stale Jira items, broken links, and whether steps still earn their time. One-week trial: record shutdown duration and next-morning open loops discovered that were known the prior evening; target median ≤15 minutes and fewer misses than baseline, which must be measured during week one rather than invented.

Pourquoi cela fonctionne

  1. 1

    A consistent capture-and-stop sequence reduces reliance on memory without extending the workday indefinitely

  2. 2

    Preparing the first physical action lowers tomorrow's startup cost

Vérifier le résultat

  • Can the normal routine fit the time limit without doing newly discovered work

  • Does every step have a visible done condition and a useful exception rule

  • Are tomorrow's first action and materials prepared without assuming others' agreement

Utilisez-la en toute confiance

Questions fréquentes

Des réponses pratiques sur le bon moment pour utiliser cette recette, ce qu’il faut fournir et les cas où une vérification humaine reste nécessaire.

What should I prepare before using “Design a daily shutdown and next-day preparation checklist”?

For “Design a daily shutdown and next-day preparation checklist,” prepare Workday and tools, Current shutdown friction, and Tomorrow constraints. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Design a daily shutdown and next-day preparation checklist” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A short repeatable shutdown routine with exceptions, timing, and a ready-to-start tomorrow—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Design a daily shutdown and next-day preparation checklist”?

The published test record for “Design a daily shutdown and next-day preparation checklist” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Plus de façons d'explorer

Où se situe cette recette

Prompts texteProductivité personnellePour les apprenants et les enseignants

Faites avancer votre travail

AILesson · Cours recommandés

Votre prochaine étape : mettez l’IA à contribution

Passez de la compréhension de l'IA à l'action. Entraînez-vous à formuler des requêtes, à évaluer et à améliorer les résultats grâce à des leçons interactives pour le travail et la vie quotidienne.

Découvrir tous les cours
Image de couverture de L’IA pour débutants

15 leçons interactives

L’IA pour débutants

Lancez une conversation utile avec une IA, améliorez sa réponse, vérifiez l’essentiel et sachez quand c’est à vous d’agir.

Découvrir ce cours
Image de couverture de Les bases de ChatGPT

10 leçons interactives

Les bases de ChatGPT

Découvrez ChatGPT à travers trois flux de travail pratiques : mener une première conversation, travailler à partir d’un fichier, puis utiliser Projects pour réutiliser un plan vérifié dans une nouvelle conversation.

Découvrir ce cours
Image de couverture de Comment fonctionne l’IA générative

7 leçons interactives

Comment fonctionne l’IA générative

Comprenez comment les systèmes courants de chat IA apprennent des structures linguistiques, utilisent les messages actuels, construisent leurs réponses et intègrent des sources et des outils.

Découvrir ce cours