AI Ready
Workday card, MethodKit for AI Readiness
Card 3 of 48 · MethodKit for AI Readiness
  • ThemeYour Work
  • CardCard 3 of 48
  • Questions5 to explore
Your Work

Workday

Describe what a typical workday looks like for you (e.g. yesterday)

A workday description is a map of where your time, attention, and decisions actually go.

Think about what you did yesterday. The sequence of tasks, the interruptions, the context switches, the things you dealt with that were never on a list. That pattern, more than any job description, is what a full picture of someone's work looks like.

AI tools that are given a real workday description can start to understand what a normal day demands: how often context switches happen, what the recurring decisions look like, where time goes versus where it is supposed to go. That is the kind of texture that makes AI help feel relevant rather than generic.

A workday description is also a useful prompt for yourself. The things that fill your day but never appear on a list are often exactly the things where AI could take load off, if you could make them visible enough to describe.

Make it visibleWrite down what you did yesterday, hour by hour or task by task, in three to five sentences. Note where you switched context, what interrupted you, and what you dealt with that was never on a list. Keep this as a running description you can share with AI tools to give them a grounded picture of your day.

Why AI needs this

Each part of your work matters to AI in a specific way. Some of it is context a tool needs before it can help, some of it is work a tool can take on, and some of it is judgment that should stay with you.

Where the time really goes

A workday account shows the gap between scheduled work and actual work, and that gap is often where the most impactful AI assistance hides.

Recurring patterns a tool can learn

If you describe your day often enough, a tool starts to recognize your rhythms and can anticipate context rather than requiring it to be re-explained each time.

Decision frequency and type

How many decisions a day involves, and how much of the day is reactive versus planned, tells a tool a great deal about when to be brief and when to be thorough.

Hidden load that does not appear in tasks

The coordination, the translation between teams, the pastoral conversations: these rarely appear in task lists but they shape the day, and AI needs to know they exist.

Questions to explore

Use these on your own or in a group. There are no right answers, only better conversations.

  1. What did you actually spend most of your time on yesterday, compared with what you planned to do?

  2. Which parts of the workday are predictable and which are genuinely reactive?

  3. Where do you find yourself doing the same kind of thinking or communicating over and over?

  4. What slows the day down most, and is it structural or one-off?

  5. If you could hand one hour of yesterday to an assistant, which hour would it be?

Readiness traps

  • People tend to describe an idealized workday rather than a real one. Asking about yesterday specifically produces a much more accurate picture than asking about a typical day.
  • The invisible work (explaining, chasing, re-explaining, coordinating) tends to be left out of workday descriptions but is often the most time-consuming part of the day.
  • A workday changes significantly by role seniority, team size, and working mode. A solo contributor's day and a team lead's day require different AI contexts.