Day-shape: why one persona has many jobs, and your UI needs to know which one is loaded
Most users don't have one job — they have several, and they shift between them across the workday. Designing for 'the user' without day-shape means designing for the average of all their jobs, which usually fits none of them well.
Most design work treats the persona as a person with a job. The warehouse manager. The inventory planner. The support lead. The job defines the cognitive requirements — time pressure, working memory load, expertise level, stakes of error — and the design follows from those requirements.
The problem is that most users don't have one job. They have several, and they cycle through them across a workday. The warehouse manager who reviews exceptions in the early morning is doing a different job than the same manager who runs a capacity check before lunch or handles a supplier escalation in the afternoon. Same person. Different job. Different cognitive profile. Different interface requirements.
This is what day-shape captures: the sequence of jobs a persona moves through in a typical day, the transitions between them, and how the cognitive state shifts at each transition.
Why day-shape changes what "good design" means
The design implications of day-shape are concrete. A manager doing exception review at 8am is in a triage mode: high volume, fast decisions, low deliberation per item. The layout that supports this is a decision surface — inline actions, clear priority signals, minimal ceremony. The goal is throughput.
The same manager doing capacity planning at noon is in a deliberation mode: lower volume, more time per item, higher consequence per decision. The layout that supports this has more context, more space for analysis, less pressure toward quick commitment. The goal is accuracy.
If the product conflates these jobs — building one layout that tries to serve both — it typically serves neither. The decision surface is too fast for deliberation. The analysis view is too slow for triage. Users adapt by building workarounds: they export to spreadsheets, they screenshot data for reference, they context-switch out of the tool rather than through it.
Pattern: day-shape is the sequence of jobs a persona cycles through in a typical workday. Each job has different cognitive requirements. A product that knows the day-shape can surface the right interface at the right moment instead of averaging across all of them.
How day-shape is captured in project memory
During discovery — the first call where TheDesignAgent infers the product's context — day-shape is one of the fields built into the persona profile. For each persona, the profile includes: who they are, their cognitive characteristics (working memory, expertise, time pressure, multitasking demands), and their day-shape — an ordered or loosely-ordered map of the jobs they do and when.
A warehouse manager's day-shape might look like: exception review (morning, high urgency, triage mode) → fulfillment oversight (late morning, monitoring mode) → inventory reconciliation (noon, deliberation mode) → supplier coordination (afternoon, communication mode) → shift close (end of day, summary mode). Each of these has a different load profile. The discovery output captures all of them.
The active_job_id in each subsequent call then identifies which job in that map the current artifact is serving. The score reflects how well the artifact serves this specific job, not the average of all the jobs in the day-shape. A layout that's excellent for exception review will score differently when evaluated against inventory reconciliation — because the job requirements are different.
Implications for navigation and layout switching
Day-shape awareness opens a design direction agents rarely reach: interfaces that shift state rather than sending the user to a different tool. If the product knows the user's day-shape, and the user's context shifts from triage mode to deliberation mode, the interface can adapt: surface more context, change the action prominence, show the analysis view instead of the decision surface.
This isn't a magic "mode" toggle. It's a design decision about which jobs the product can serve and how the transition between them is handled. Some products legitimately serve one job and should be designed for it. Others serve the full day-shape and should be designed for transitions.
The first step is knowing the day-shape exists. Most agent-built products don't reflect it because the prompt didn't include it. The build agent received "build a tool for the warehouse manager" and built for the warehouse manager as a single undifferentiated job. Day-shape is what's missing from that prompt — and what TheDesignAgent's discovery process tries to recover from context, even when it wasn't explicitly stated.