Skip to content
May '265 min read

Past five, the threshold.

Working memory has a ceiling. When the week's commitments cross it, something invisible takes over, and the list-shaped tools start working against you.

Conrad
ConradOn deadlines and the design of working instruments

I have spent twenty years in work shaped by other people’s deadlines, and I can tell you the point where a week stops feeling manageable and starts feeling heavy. It isn’t a number of hours. It’s a number of open commitments, and it’s lower than most people expect.

Most productivity advice is written for the early part of the load curve. It works for a week with three deadlines on it. It quietly breaks above five, and almost nobody names the threshold.

This piece is about the mechanism underneath the shape thesis. Once you carry many commitments, your week stops reading as a list and starts reading as a shape. The reason it flips is a ceiling in working memory, and the ceiling is old, measured, and easy to feel once you know it’s there.

Working memory tops out around seven items. That’s not a soft figure. George Miller published it in 1956. Half a century of cognitive psychology has refined the number, with some saying four, some saying nine depending on the task. The exact position varies. The direction does not. Below the line, the mind keeps the open items in active hold without much background cost. Above the line, the cost climbs sharply.

And here is the part nobody mentions. It isn’t the work that gets harder. It’s the holding.

What it feels like above the threshold

A person with three deadlines on their plate reads the week by glancing at a list. The contract goes out Tuesday, the report is due Thursday, the call is Friday. Three things. Three slots. A person holds three slots in their head with ease.

A person with eight deadlines does not. They look at the list and see eight items. The list shows the items, but it doesn’t show how they depend on each other, where the load concentrates, which days are fragile, what would slip if Tuesday slipped.

That last question, the “what would slip if X slipped” question, is the one the experienced practitioner answers instantly and the productivity-tool user cannot. The list version of the week doesn’t support it. The shape version does. The original piece on the shape thesis lives here.

Why list-tools degrade above the threshold

A list is one-dimensional, items sorted by something. The cognitive cost of holding a list is roughly linear in the number of items. Add one more and it’s slightly harder. Linear.

The cognitive cost of holding a shape, items plus weight plus dependencies plus density plus movement, isn’t linear. Doubling the number of open items doesn’t merely double the carrying cost. The load lives in the relationships between the items, and the relationships grow faster than the items do. The mind has to keep each item alive against every other item, so the cost sits in the connections, not just the count.

So when your list goes from three items to eight, you’re not a little under three times as loaded. You’re loaded well past that, and the tool that was helping at three is now actively in the way at eight, because it keeps insisting on the list view when the mind has already moved to the shape view. The re-sort cost piece walks through how that load shows up by Wednesday afternoon.

What people do, in practice

Most senior professionals develop the shape view without ever naming it. They start using the calendar differently, adding informal notes to days, not just events. They print things out. They draw arrows between deadlines on a desk pad. They keep a notebook with the week mapped as a constellation rather than a vertical list. None of these adaptations are what the tools were designed for. The user is adapting because no tool currently is.

I built Deadlinewatch starting at the threshold, not below it, because that’s where my own weeks had lived for fifteen years. In 2026 there are more deadline tools than ever, and almost all of them are still built for the part of the curve below the line. The list still lives in Deadlinewatch, sorted by date with priority items at the top, but it sits next to a view that renders the shape, so the question the mind is actually asking above the threshold, where does the work concentrate, finally has somewhere to land. The mechanics behind that get their own walkthrough.

The threshold is real

It’s been measured. It’s been replicated. It’s the cognitive event that separates a week that feels light from a week that feels heavy, independent of the actual hours of work. Tools that don’t acknowledge it leave their users stranded at exactly the moment their workload most needed help.

Past five, the list stops working and the shape takes over. So if your weeks feel heavier than the hours can explain, count your open commitments, not your tasks. The weight you’re feeling isn’t a discipline problem and it isn’t the work. It’s that you’re holding a shape with a tool built for a list. Naming the threshold is the first relief, because it moves the problem from what’s wrong with me to what’s wrong with the picture I’m using.