Someone who only ever reads on their iPad mini will call it “her Kindle.” Not because she’s confused about what she owns, but because she’s being accurate. The device does one job, so it gets named after the job. The box it came in doesn’t get a vote.
The Question Underneath Everything You Own
That small slip of language points at something larger, and the question it points at is simple and slightly uncomfortable: what problem does this solve? It comes out of jobs-to-be-done thinking — the idea, popularized through Clayton Christensen’s milkshake research, that people don’t buy products so much as hire them to do a specific job. The milkshake at a fast food restaurant wasn’t competing with other desserts. It was competing with anything else that could be consumed one-handed during a long commute. Understand the job and the product makes sense. Ignore the job and you end up building something that technically serves everyone and actually fits no one.
Why Doing Everything Means Doing Nothing Well
The same logic explains why a device that can do everything often ends up doing nothing particularly well. Give a tablet one job and it becomes excellent at it. Load it with every app you own and it becomes a smaller, worse version of your laptop. Deciding in advance that certain apps simply don’t go on a certain device isn’t deprivation — it’s a forcing function. It’s the difference between a tool with a purpose and a tool with options.
This scales past hardware, too. You can’t launch a course, publish a book, and rebuild a business in the same month without diluting all three. Everything everywhere all at once is a fun film and a terrible operating principle. Nothing lands.
The Unused Thing Is a Project, Not a Nuisance
Here’s where it gets less abstract. That device you stopped using, sitting in a drawer or the corner of a desk — it isn’t inert. It’s an open loop. And in David Allen’s framing it isn’t even a single task, it’s a capital-P project: check the trade-in value, decide whether to trade or sell or hand it down, then act on whichever. Multiple steps, quietly unresolved, that you’ve been carrying for months while telling yourself it’s a small privileged problem not worth the attention.
Capturing it doesn’t close it either. Writing “figure out what to do with the iPad” on a list gets it out of your head, but the loop stays open until there’s a plan attached — until you know the boundaries of the thing. That’s the part people skip, and it’s why capture alone never quite delivers the relief it promises.
Noticing Is the Actual Skill
The deeper version of this isn’t a question you ask about objects. It’s a habit of noticing at all.
Consider a rule worth borrowing: only take your phone out of your pocket when you intend it to do a specific thing, do that thing, and put it away. Not because the apps are evil — they are engineered to hold you, and pretending otherwise is naive — but because engaging with them is still a choice you’re making. Deleting Instagram doesn’t help much when Safari and a URL bar are sitting right there. The constraint that works isn’t removal, it’s intention: what am I picking this up for?
The Uncomfortable Extension
The same question survives being pointed at people, though it sounds colder out loud. What problem does this friendship solve? What problem does this arrangement solve? It isn’t a cost-benefit audit of the humans in your life. It’s a prompt to think about why we invest where we invest, and to notice honestly when something has stopped doing the job it once did.
It also applies to defaults nobody ever asked you to agree to. Couples sharing a bed is a fairly recent arrangement in human history, driven substantially by not having enough rooms — and yet most people never examine it, because examining it feels like admitting something is wrong. Two people with opposite sleep schedules, one a light sleeper and one arriving at 1am, might be solving an actual problem by sleeping separately. The only thing standing in the way is what other people would assume.
None of this requires a system. It requires the double-take: the willingness to stop, walk back, and look at something you’ve been walking past. That’s what productiveness actually looks like — not more optimization, just enough space to notice what’s actually there.
