I have a tab problem.
Not a browser tab problem — or not only that. I mean the cognitive equivalent: dozens of articles I've "read" in the sense of opening them, skimming the first three paragraphs, and moving on. Newsletters I've flagged for later that have no later. Podcasts I listened to at 2x speed while doing something else, retaining nothing except the ambient feeling of having been exposed to information.
For years I called this staying current. It isn't. It's the appearance of learning with most of the substance extracted.
How Professors Actually Do It
I kept noticing something about the academics I know. They're not the most current people in their field in terms of raw exposure to new information. But they're the deepest — they can synthesize across sources, hold tensions between competing theories, explain something they haven't thought about in six months as if they taught it yesterday.
The difference isn't intelligence. It's architecture.
A professor doesn't learn reactively. They design their knowledge acquisition at the semester level. What are the topics this term? What are the canonical sources? What questions will the material need to answer? That design work happens before any reading starts. Then the reading is purposeful — feeding a pre-designed architecture rather than accumulating randomly.
At the end of a semester, they've produced something: a syllabus, a course, a set of lectures. The synthesis is the deliverable. It's what converts exposure into retrievable knowledge.
Most knowledge workers — myself included, until recently — do none of this. We consume reactively, continuously, with no synthesis rhythm and no designed output. The information flows in and never consolidates.
What I Was Actually Doing
Every morning: three newsletters, a few tweets, an article someone sent, half a podcast episode. Maybe an hour total. At the end of the week I could tell you roughly what the conversation in my space had been about. I could not tell you anything specific. Nothing had compounded.
The problem is attention residue, but applied to information. Gloria Mark's research on interrupted attention is usually cited for task-switching — the 23 minutes to return to deep focus after an interruption. But the same mechanism operates on information consumption. Every piece of content you encounter is an interruption to your existing mental model. If the content doesn't connect — if there's no synthesis moment that integrates it — it leaves a residue: a half-formed update that's neither fully processed nor fully discarded.
Multiply that by 30 pieces of content per day and you get a cognitive substrate that's perpetually unsettled. You've been exposed to everything and absorbed nothing.
The Switch
I moved to a weekly synthesis session.
Friday afternoon — after the week's content has accumulated and before I'd have spent the weekend trying to catch up — I open Claude and run what I've started calling a Professor Brief:
Here's what I've been reading this week: [links and titles]. Here are the questions I've been circling: [2-3 specific questions]. Synthesize what's relevant, surface any tensions or contradictions, and tell me what I'd actually want to remember from this.
What comes back isn't a summary. It's a synthesis — organized by question rather than by source, with explicit notes on where sources agree, where they conflict, and what's still genuinely unclear. It's the note you'd take if you were preparing to teach the material.
That brief takes about 20 minutes to prompt and read. It replaces what used to be an hour of daily consumption that never consolidated.
What Compounds and What Doesn't
The critical insight from the Professor Model: consumption doesn't compound. Synthesis does.
A tweet you read on Monday doesn't inform a decision on Thursday unless you've processed it into something retrievable. A podcast you half-listened to while running doesn't build on itself across episodes unless there's a structure holding the pieces together.
Synthesis compounds. A weekly brief that you actually read and retain becomes a foundation for next week's brief. Over time, the questions you're asking get sharper because you're building on accumulated understanding rather than re-encountering the same surface-level discourse week after week.
The professors I mentioned aren't more current than their more reactive colleagues. They're deeper. And depth, in most domains, is more useful than currency.
The Professor's Output Problem
There's a second half of this that took me longer to see.
Professors produce. The synthesis isn't just for their own understanding — it becomes a course, a paper, a lecture. The act of producing output is what seals the learning. You don't know what you know until you've had to explain it to someone else.
Most reactive consumption produces no output. You've read and moved on. Nothing is tested, nothing is encoded, and the half-life of the information is measured in days.
The weekly synthesis brief is a start. But the further move — the one I'm still building into habit — is to treat every synthesis as material for something. A post, a note in a system, a framework someone could read and argue with. The output doesn't have to be public. It just has to exist.
The Harder Version
The Professor Model is easy to describe and uncomfortable to fully implement.
Comfortable: reading is pleasurable. The feeling of consumption feels like learning. Your news feed has designed specifically to produce this feeling while delivering the minimum transferable information.
Uncomfortable: a weekly synthesis session requires you to confront how little of what you consumed is actually worth synthesizing. Most of it isn't. That's clarifying, but it's not comfortable.
The professors who do this well are clear-eyed about what deserves a place in their architecture and what doesn't. Most of the internet doesn't. Most newsletters don't. Most podcasts don't.
The Professor Model is also a curation problem.
What would you actually synthesize from this week if you had to? What would fall away?
This is part of The Layer — a series on building AI as the operating system beneath your decisions. Read Episode 0: The Layer.
