Here's an invented day. Dana isn't a real person — just familiar parts, assembled.
She's a senior analyst. Standup at 9:15, then forty minutes of triage: Slack threads, two documents to comment on, an inbox that regenerates as fast as she clears it. A review meeting before lunch, a stakeholder call after. The gaps between meetings go to "getting ahead" on a deck. By six she has handled everything, and her handled-things list is genuinely impressive. On the train home she tries to name one thing she understands tonight that she didn't understand this morning.
Nothing comes.
That gap has a structure, and the structure is the subject of this post. Knowledge work looks like it feeds the mind's need to learn and understand — the cognitive tier, in the eight-tier frame we work from (a practical lens adapted from later Maslow, not settled science). Our reading: the way the work is organized converts curiosity into throughput, and the deficit hides precisely because the work resembles thinking.
The resemblance trap
Deficits in other needs tend to announce themselves through absence. A thin belonging tier eventually looks like an empty weekend. An empty stomach is not subtle. The cognitive tier at work fails differently, because the workday isn't empty of cognitive material — it's stuffed with it. Words, numbers, decisions, judgment calls. Triaging an inbox uses the same organ that follows a question.
Call it the resemblance trap: work made of cognitive materials passes for work that feeds cognitive needs, the way small talk is made of the materials of friendship without being friendship. The trap defeats your internal audit. Ask "did I think today?" and the answer comes back yes, constantly, obviously. It's the wrong question. The right one: did today contain a problem I didn't already know how to solve?
That's the line between the two kinds of work. Work that is cognitive has a specific shape — an open problem, held long enough that you end the day able to do or understand something you couldn't at breakfast. Work that looks cognitive is settled expertise running at speed: routing, summarizing, choosing among options you already understand, reacting well. The second kind is real work, worth paying for, often what the job actually needs. But it's throughput. It draws on the cognitive account without depositing into it.
We've written before about why curiosity dims in adulthood generally — the competence economy that pays you for what you already know, the information intake that impersonates inquiry. That post is about life at large. This one is about the narrower case with sharper teeth: the workplace, where the competence economy isn't a drift but the deal itself. Nobody hired you to learn. They hired you for output, and output pressure converts curiosity into throughput not by accident but by design.
(Writing does the same thing, incidentally. Assembling sentences about thinking isn't thinking — a fact this draft demonstrated to its author more than once.)
Meeting hours, maker hours, and what each can pay
Split the working week into two kinds of hours. Meeting hours are for coordination: alignment, updates, decisions made together, being reachable. Maker hours are the ones where you're alone with the work. The distinction is borrowed from an old argument in software about schedules — we want it for a different job, which is tier accounting.
Because here's the thing: a good meeting is not a failure. Run your calendar through the question "which needs can this hour pay?" and meetings do fine — in other tiers. A meeting can pay belonging: shared context, people who notice when you're off. It can pay esteem: being the person a certain kind of question comes to. It can even pay a kind of safety, in the form of knowing what's coming next quarter. Those payments are real.
What a meeting is structurally built for, though, is moving conclusions between heads. And receiving conclusions is intake — the same intake-not-inquiry problem the rest of modern life has, wearing a calendar invite.
Cognitive income has a requirement the other tiers don't: one problem, one head, held continuously past the point where what you already know runs out. That can only happen in maker hours. And it doesn't happen automatically even there — a maker hour spent clearing the queue or formatting the deck is throughput too. So the week's real cognitive payroll is a multiplication: maker hours, times the ones that contain an open problem, times the ones long enough to hold it. Any zero zeroes the product.
Run Dana's invented week through the multiplication and you can see where it dies. Her calendar shows maybe twelve maker hours — respectable. But eight of them went to the deck and the queue: throughput, factor two is small. And the remaining four arrived as fragments between meetings, none longer than forty minutes: factor three approaches zero. Twelve hours of apparent thinking time, a cognitive payroll near nothing, and no single hour anyone could point to as the problem. That's what makes it structural rather than personal — every individual hour was spent reasonably.
The last factor — long enough — is where the strongest evidence lives.
What switching actually costs
Sophie Leroy, an organizational researcher, gave the mechanism a name in 2009: attention residue. In her experiments, people worked on one task and then switched to another. Those who switched away from an unfinished task kept part of their attention on it — the leftover engagement was measurable — and they performed worse on the next task. Even finishing didn't reliably clear it. Only finishing under time pressure, which forces a felt sense of closure, let attention move on cleanly. The plain version: attention has inertia. You switch. It lingers.
For the week's accounting, this changes what a fragmented hour is. Five scattered fifteen-minute gaps aren't a chopped-up 75 minutes of thinking. Each fragment starts partly occupied by the ghost of whatever preceded it. The calendar counts the minutes. Attention doesn't get them all.
Here's the honest boundary on that study, because it's carrying weight. Leroy's experiments were lab tasks measured over minutes, and what they show is that switching degrades immediate performance on the next task. She didn't study curiosity, learning, or anyone's long-term wellbeing, and the finding is not the internet's "multitasking makes you dumber." The bridge from her mechanism to our frame — that a day structured as constant switching can't hold one problem long enough for it to become genuine inquiry, and that this is how a workplace quietly starves a cognitive need — is our inference. We'd rather own that plainly than let a good study appear to prove more than it does.
Why the cognitive deficit hides
Two things keep the shortfall invisible, and neither of them is anyone lying.
Depletion feels like income. Dana ends her day mentally spent, and spent feels like used, and used feels like fed. But the exhaustion of forty context switches and the exhaustion of four hours inside one hard problem aren't the same event, however similar they feel from the couch. One is friction. The other is income. There's a test that doesn't rely on the feeling, and it's the train-home question: what do you understand tonight that you didn't this morning? A day of real cognitive income has an answer. A throughput day has a list of things you handled.
The scoreboard counts throughput on purpose. Look at what your role actually measures. If it's responsiveness, items closed, and velocity — then an open question with no deliverable attached shows up as a cost in every column. The conversion of curiosity into throughput isn't a villainous manager; it's ordinary metrics doing their ordinary work. Which is why "just be more curious at work" is advice aimed at the wrong altitude. It asks you to swim against a current the job was built to produce.
The trap runs at the yearly scale too. Job titles say thinking — analyst, engineer, strategist. Whether the role still contains problems you don't know how to solve in year three is a separate question, and the title can't answer it.
A week of honest accounting
None of this requires quitting, and none of it starts with the job description. It starts with a count.
1. Count the real maker hours. For one week, mark every block that meets two conditions: forty-five minutes or more without switching, and a problem inside it you didn't already know how to solve. Use the calendar plus honesty — memory alone will flatter the week. And treat the result as a heuristic, not a verdict: a launch or a crisis zeroes anyone's count for reasons that aren't structural, so a single bad week proves nothing. The number is a hypothesis about your job's cognitive payroll.
2. Finish before you switch. The nearest thing to a practical handle Leroy's experiments offer: residue cleared when a task was finished under conditions that produced a felt sense of closure — mere finishing didn't reliably do it. So when a switch is coming, don't let it catch a task mid-air. Break work into chunks small enough to finish, and close one before you turn. Our extension, not her finding: even a stopping point you choose — this section done, this question written down — seems like a better place to be interrupted than wherever the ping found you. Worth testing on your own attention.
3. Consolidate; don't sprinkle. If the residue logic holds, one two-hour block is worth more than the same minutes scattered, so trade for contiguity wherever you have any control at all. Then protect the block for the right cargo: put the open problem in it, not the queue. Throughput survives fragmentation fine. Inquiry doesn't. Spending your one protected block on email is guarding an empty safe.
4. Ask what the job is designed to pay. If the count comes back near zero for several ordinary weeks, that may not be a personal failing. Some roles are coordination all the way down, and they pay other tiers honestly. Whether yours is one of them is an audit we've already built — which tier is your job designed to fill? runs it across every work-relevant tier, cognitive included, and this post won't re-run it. And if the answer turns out to be "this job will never pay much into this tier," the move isn't despair, it's sourcing: the rewilding practices in the curiosity post linked above are built for exactly that, off the clock.
One structured read, if counting isn't enough
The cognitive tier is one of eight that NexTier's assessment reads, and it's the one that's hardest to audit from inside a busy week — a demanding job impersonates a fed cognitive tier better than it impersonates anything else. If you'd like the structured read, the assessment covers all eight, so you can see whether the thinking-shaped job is actually paying the thinking need. If not, the whole method above runs on one week, a calendar, and two honest conditions per block. Either way the useful move is the same: stop asking whether the work feels smart, and start counting what it pays.
—
This post is part of a series on personal development organized around what we call Maslow's extended hierarchy — our synthesis of his later work. Source: S. Leroy, "Why is it so hard to do my work? The challenge of attention residue when switching between work tasks" (Organizational Behavior and Human Decision Processes, 109(2), 2009). This post is educational content, not medical or career advice.