A whitepaper on attention

Attention

Every plan quietly assumes someone's time. This shows, in ten slices per person per cycle, where that time is already promised, who is being asked for more, and who has none left to give.

Problem, options, proposal and a working prototype, in one offline file. Go to the strips

The problemPlans are made of people who are already busy

Every initiative plan lists names. Nobody adds them up. The principal architect appears on six plans, the security architect on five, the one engineer who understands the order service on four. Each plan is reasonable. Together, they describe a week nobody could work.

The cost appears as slips nobody can explain: reviews that wait a fortnight, decisions that stall because the one person who can make them is in other meetings, and focused work that never happens because the day is cut into pieces.

Drucker's first instruction to executives was to know where their time actually goes, because it is never where they think. His second was concentration: knowledge work needs large, continuous blocks of time, and effective people do first things first, one thing at a time. 37signals built its product process on the same belief. Shape Up gives each piece of work a fixed appetite, runs it in six-week cycles followed by a cool-down, and keeps teams dedicated rather than shared.

OptionsHow organisations try to see it

ApproachWhat it measuresWhy it fails
TimesheetsHours, after the factMeasures the past, invites fiction, and says nothing about requests
FTE spreadsheetsPercentages per projectFalse precision; nobody knows if 0.3 of an architect is a lot
Resource management toolsBookings by the hourHeavy, and owned by a central team rather than the people involved
Ten slices a cycleAgreed and requested attentionCoarse by design; the point is the pattern, not the arithmetic

The proposalTen slices, agreed or asked

Each person's attention in a cycle is ten slices. A slice is roughly half a day a week, but nobody tracks that: the ten slices exist to make trade-offs visible, not to account for hours.

Slices come in two states. Agreed slices are promises the person has accepted. Asked slices are requests from an initiative that nobody has said yes to yet. Most planning conflict lives in the asked slices, and most plans treat them as if they were agreed. Showing them separately turns an assumption into a conversation.

Unused slices are slack, and slack is healthy. Shape Up's cool-down exists because people need time that isn't promised to anyone: to fix small things, to think, to help a colleague. A person with every slice agreed has no room for the unexpected, which always arrives.

Four patterns worth a conversation

LimitsWhat it is not

It is not time tracking, performance measurement or a staffing system. Slices are declared, not measured; they are only as honest as the conversation behind them. Data stays in this browser; sharing is a later step.

The strips

A sample organisation is loaded. Open a person to agree, decline or add slices, or switch to initiatives to see who each one rests on. Everything is saved in this browser.

Over their attention

More agreed and asked than ten slices.

    Hidden bottlenecks

    Asked for by three or more initiatives.

      Fragile and fragmented

      Spread over more than three initiatives, or an initiative resting on one person.