The Lego Block Method

Nobody builds a Lego castle by molding their own plastic. The blocks exist. You assemble.

Writing works exactly the same way, and almost nobody treats it that way — which is why “I should write more” is the most commonly broken promise in professional life. I want to take the romance out of writing in this letter, because the romance is the problem.

The blank page is a factory with no inventory

Picture the standard attempt. You block out Tuesday evening. You open a document. Cursor, white space, and a job title’s worth of pressure: you’re the expert, so this had better be good.

What you’re actually attempting in that moment is four distinct jobs simultaneously: remembering what you know about the topic, selecting which parts matter, structuring them into an order, and phrasing them into sentences. Any one of those is honest work. All four at once, live, from memory, is a performance — closer to improv theater than to how any other professional deliverable in your life gets made.

You’d never run a client project this way. You’d never walk into a boardroom and design a strategy from a standing start with no materials. Yet this is somehow the standard method for the writing that’s supposed to represent your thinking to the world — and when the performance stalls, the diagnosis is always personal: writer’s block, no discipline, not a writer.

The diagnosis is wrong. The factory didn’t have a bad shift. The factory had no inventory.

Blocks change the job

Now run the same Tuesday with a month of capture behind you — the ugly inbox from Letter 02. In it: the question your client asked about why their SOPs never stick, your four-sentence answer from the call, a captured annoyance about a LinkedIn guru’s take on documentation, a decision you made for a different client that contradicts the standard advice.

Notice what those scraps are. They’re not notes about the topic. They’re pre-fabricated units of your actual thinking — each one already selected (it mattered enough to capture), already phrased in your voice (you said it before you saved it), already tested (a real person heard it and paid for it). They’re blocks.

With blocks, Tuesday evening is a different job. You’re not performing. You’re assembling: pick the question, pull the three blocks that relate, arrange them. The four simultaneous jobs collapse into one sequential one, and the one that remains — arrangement — is the easiest of the four and the only one that actually benefits from you sitting at a desk.

This is the entire secret of the experts who publish every week while running real practices. They are not more disciplined than you. They are not faster writers. They have inventory, and they’ve stopped confusing writing with authorship. Authorship happened during the week, in fragments, while they worked. Writing is just the assembly shift.

The three-slot stack

Assembly needs a jig — a fixed structure that receives the blocks so you’re not inventing form and content at the same time. Mine has three slots, and it’s deliberately crude:

1. The question — verbatim, the way a real person asked it. Not “Thoughts on documentation strategy” but “Why do my SOPs never stick?”
2. What most people get wrong about it — the standard advice and why it fails. You have this block; it’s usually the annoyance you captured.
3. What you actually do instead — your answer, the one you gave on the call, with the example attached.

Question, wrong way, your way. It’s not sophisticated. It doesn’t need to be — that shape is the skeleton of nearly every useful expert piece ever written, because it’s the shape of consultation itself. It’s what you already do in the room; the stack just does it in public.

The rule for the assembly pass: stack the blocks and stop. No transitions. No smoothing. No introduction that clears its throat. You are explicitly forbidden from making it good. Rough drafts don’t die from being rough; they die from the polishing session that never gets scheduled. A rough stack that exists is ahead of every polished piece the other experts in your field are still planning to write someday.

Why fifteen minutes is enough

The fifteen-minute claim sounds like productivity-guru math, so here’s why it’s real: the fifteen minutes only ever pays for arrangement. Remembering happened at capture. Selection happened at capture. Phrasing happened on the call, before capture. You front-loaded three of the four jobs into moments when they were nearly free — the insight was right there — and what’s left genuinely is a quarter hour of moving blocks into slots.

People who try to write in fifteen minutes from a blank page fail, correctly, every time, and conclude short sessions don’t work. Short sessions don’t work for performances. They’re the natural size for assembly.

Do this today

Fifteen minutes, one stack:

1. Take the client question you captured after Letter 01 — your seed asset.
2. Pull two or three inbox blocks that relate to it.
3. One note, three slots: the question, what most people get wrong, what you do instead. Stack. Stop.

Read it back once. It’s rough, and it exists — and “exists” is the only property that matters at this stage, because everything downstream (the AI interrogation in the next letter, the shipping protocol in the one after) operates on drafts that exist and is powerless over drafts that don’t.

If you’re doing this without the pre-wired system, the Vault is free — inbox, stack templates, and the prompts already in place. If you’d rather have the whole pipeline installed and running in your business in three weeks, that door is here.

— Frank