Be honest about how you actually read newsletters. You open a long Substack, your eyes jump to the first paragraph, then to a bolded line halfway down, then to the end. You're not reading — you're foraging, hoping to catch the gist by accident. Sometimes it works. Often you close the tab with a vague sense of what it said and a nagging feeling you missed the actual point.
That's the real problem with a long inbox: not that you don't read, but that the skimming most of us do is unreliable. You skip the dense paragraph that held the whole argument. You linger on an anecdote and miss the conclusion. Blind skimming saves time and costs comprehension, which is a bad trade on the posts that turned out to matter.
There's a better way to triage, and it's the thing we built Read & Explain for. The idea is simple: instead of skimming with your eyes and hoping, let the post get walked through — the key points pulled out, marked on the page, and narrated to you in a minute or two.
Skimming vs. a guided walkthrough
When you skim, you're doing two hard jobs at once: deciding what's important and reading it, at speed, with no map. Your brain takes shortcuts, and the shortcuts are where you lose the thread.
A walkthrough splits those jobs. Something else does the "what's important" pass first — finds the claim the piece is built on, the sentence that turns the argument, the takeaway at the end — and then walks you through just those, in order, while marking them right on the original text. A circle around the core idea. A line under the crux. A highlight on the conclusion. You're not foraging anymore; you're being handed the spine of the piece and shown where each part lives.
Two minutes of that tells you more than five minutes of blind skimming, and it tells you the right things.
What this does to a full inbox
Here's where it earns its place. Most newsletter backlogs aren't forty posts you need to read in full. They're forty posts you need to make a decision about: read now, save for a real sit-down, or let go.
A quick walkthrough makes that call for each one in about a minute:
- "That's the whole point — I'm done." Plenty of posts give you everything you needed in the gist. You close it satisfied instead of guilty.
- "This is good, I want the full thing." Now you read it properly, knowing it's worth the time — and you already have the map, so the full read goes faster.
- "Not for me." Archive it without the low-grade guilt, because you actually know what it said.
Forty obligations become forty fast decisions. The pile moves.
The trick is keeping the original in front of you
A plain text summary — the kind you'd get from pasting a post into a chatbot — has a quiet failure mode: it floats free of the source. You read the summary, you don't really trust it, and you end up re-reading the original anyway to check. Now you've done the work twice.
Marking the gist on the original page fixes that. Because the key sentences are circled and highlighted right where the author wrote them, you can glance from the point to the surrounding text in one motion — verify it, get the nuance, drop back out. You get the speed of a summary with the trust of the real thing. It ends up looking like a post a sharp editor went through with a pen, which is exactly the artifact you want when you're triaging fast.
How to do it
I use the CastReader Chrome extension (free to start, works in Edge):
- Open the Substack or newsletter post.
- Hit Read & Explain instead of reading top to bottom.
- In a minute or two you get the walked-through gist — narrated, with the key points marked on the page.
From there you decide: done, full read, or archive. If it earns a full read, you can switch to straight narration and listen to the whole Substack post while it scrolls and highlights along. The same walkthrough mode works right on Substack articles, too.
The point
"I'll skim it later" is usually a lie we tell ourselves, because the skim — when it finally happens — is unreliable and you know it. Replace the blind skim with a guided one: let the post show you its own spine, decide in a minute whether it deserves more, and stop carrying a backlog of things you half-read and fully forgot.
Two minutes per post. The right two minutes.