Effective learning requires connecting new information to existing models — not just receiving it. Always Be Connecting is the structure, not the slogan.
Most learning fails not because the content is poor, but because it arrives without attachment points. Information enters working memory, finds nothing to anchor to, and dissipates. You finish the book, the lecture, the thread — and three days later you can reconstruct the gist but not the argument. The ideas didn't integrate. They passed through.
This is not a memory problem. It's an architecture problem. The information was delivered but not connected. Connection is the mechanism of retention, not repetition.
The Learning Sandwich has three layers:
The slogan is deliberately borrowed from Glengarry Glen Ross — where it stands for something cynical and extractive. The reframe is intentional. Always Be Connecting is the same compulsive structure applied to intellectual production rather than sales. It's the same pathology, redirected: you cannot encounter new information without immediately asking where it connects. This is not a discipline. It becomes a reflex.
The danger of the reflex is premature integration — connecting too quickly, before you've understood what's actually new. The Learning Sandwich builds in a mandatory "During" layer precisely because the "Before" and "After" layers create pressure to collapse the middle. Don't. The middle is where the learning happens. The friction of not-yet-connected is the signal that you've encountered your entropy surface.
The response-gated drip mechanic in Playable Worlds is a structural implementation of the Learning Sandwich. Each chapter ends with a prompt. The reader can't proceed until they've written at least 75 words in response. That response is the "After" layer — the model revision, not a summary. The next chapter's "Before" layer is built into how Marvin's agent note for that chapter is framed.
The design assumption: readers who skip the sandwich retain less, engage less, and are less likely to finish. Not because they're lazy — because the architecture didn't give the new information anywhere to land.
Organizations fail to learn for the same reason individuals do: they receive information without connecting it. The post-mortem that produces a doc no one reads is the organizational equivalent of a book that goes unfinished. The connection layer was skipped. The model never updated.
The institutional fix is the same as the individual fix: build connection into the architecture of how information arrives, not as a follow-up discipline after the fact. If the architecture doesn't require a connection event, one won't happen.
"Most people have only a vague sense of what makes their audience happy to support them, so they're left hoping someone somewhere will be generous for no particular reason. Once you understand how and why people like your work, you can make it much easier for them to act on that."
— Visakan Veerasamy. This is a Learning Sandwich observation: Visa diagnosed why most pitches fail not because they lack content, but because they skip the connection layer for the audience.
The Learning Sandwich underlies the Hopper chapter in Playable Worlds (debugging as model revision, not error-fixing) and the Lovelace chapter (the distinction between computation and what computation is for). The drip mechanic is its direct implementation. The Entropy Press founding reader experience is designed around it.
The Learning Sandwich is built into the architecture of the Playable Worlds reading game. Each chapter requires a response before the next arrives.
Join the reading game →