Watch One, Do One, Teach One — the Surgeon's Loop for Learning Anything

Baltimore, the 1890s. At the new Johns Hopkins Hospital, William Stewart Halsted was building something that didn't exist yet — the surgical residency, a system for turning students into surgeons by graduated, supervised practice. Out of that system grew a maxim, polished by generations of residents into three beats of folklore: see one, do one, teach one. Watch a procedure performed. Perform it yourself. Then teach it to the resident coming up behind you.

As surgical pedagogy it has been debated, revised, and hedged with supervision ever since — as it should be; the stakes are arteries. But as a general method for learning, it may be the most portable three-step loop ever devised. And I've come to believe it fits a weaver's mind better than almost anyone else's, because each step corrects one of our characteristic failure modes.

Watching, capped at one, corrects the endless-input problem — the eleventh tutorial, the fourth survey course. Doing, defined as one artifact, corrects the missing finish line — the learning that never condenses into anything you could hold. And teaching corrects the deepest one: the invisibility. All that knowledge, real and hard-won, that no one else can see.

Take the steps in order, because each one changes what the knowledge is to you. Watching makes you a spectator. Doing makes you a maker. Teaching makes you an owner.

Watch one — the number is the discipline

Consuming an example first is the obvious part. What's not obvious is the number. One.

The weaver's failure mode at this step isn't ignorance; it's connoisseurship. Eleven tutorials bookmarked, three courses sampled, a considered opinion forming about which instructor explains it best — and no stool built, no scraper written, no song played. Watching has one fatal property: it feels like learning while demanding nothing. Barbara Oakley's Learning How to Learn gives the feeling its proper name — an illusion of competence. A fluent explanation, fluently followed, produces recognition. Recognition impersonates recall almost perfectly, right up until you're alone with the empty page.

So find the single best worked example you can — one full walkthrough by someone who genuinely has the craft — and watch it the active way: pause before each step, predict what comes next, notice the moves that surprised you. Then stop collecting. The example is scaffolding, not the building. Watching is for shape, never for competence.

Do one — where the sprint gets its output

Now make one thing. Not the exercises at the end of the chapter — an artifact, small and real, with your name on it. One scraper that scrapes. One stool that holds weight. One recorded song, one mailed postcard, one bad but complete watercolor.

If you run your learning in curiosity sprints — and if you've read that essay, you know I think you should — this step is where the sprint's visible output comes from. The finish line you name in advance is precisely a "do one." The loop and the sprint are the same machine seen from different angles.

And the gap between watched and made is where the actual learning lives. Everything the example silently handled — the error message it never triggered, the wood that splits where the video's didn't, the verb that refuses to conjugate — turns out to be the real course content, arriving in your order, calibrated to your hands. You cannot get this from a twelfth tutorial. You can only get it from the first artifact.

This is what "project-based learning" gets right, underneath the education-conference branding. The project is not a way of applying knowledge you acquired somewhere else. The project is the acquisition — the artifact is simply what the learning looks like from outside. Keep it small enough to finish and real enough to fail. Both properties are load-bearing.

Teach one — the rung almost everyone skips

Then the third step, which nearly every self-directed learner omits — because it feels optional, or presumptuous, or like something you earn the right to do later. Who am I to teach this, four weeks in?

But notice what the surgeons understood. The resident teaches the procedure while it is still fresh enough to remember what was hard — which is exactly what makes them a better explainer of it than the chief who mastered it twenty years ago and can no longer see the difficulty. Recency is not your disqualification. It is your qualification. And the teaching step is the fastest route to retention we know of, for three distinct reasons.

It forces retrieval

In 2008, Jeffrey Karpicke and Henry Roediger published a now-famous result: students who practiced retrieving material remembered far more a week later than students who spent the same time re-studying it — and the re-studiers were more confident while being worse. Rereading strokes the material; explaining has to reach in and pull it out, in your own words, in working order. Teaching is retrieval with a witness.

It finds gaps with surgical precision

The Feynman technique — this loop's most famous cousin — is exactly this step, formalized: explain the idea in plain language, as if to a newcomer, and keep going until you hit the sentence you cannot finish. That sentence is not a vague feeling of shakiness. It is an address. You now know exactly which page to go back to, and nothing else diagnoses a gap so cheaply or so precisely.

It converts private knowledge into public evidence

This one matters to a weaver more than to anyone. Your recurring problem is knowledge without receipts — competence the résumé can't show and the interview can't surface. A teaching artifact is a receipt. Researchers call the inward half the protégé effect — students who learn in order to teach learn measurably more — but the outward half compounds just as hard: the explainer you wrote is proof a stranger can inspect. It is the difference between claiming a thread and showing the weave. How that becomes a career story is the subject of Skillweaving.

The ladder — teaching without an audience

The usual objection arrives right on time: but I have nobody to teach. You don't need an amphitheater. You need one rung of this ladder, starting from the most private.

1. Write the one-page cheat sheet for your future self. Audience of one, guaranteed sympathetic. It still forces the compression real teaching demands — what goes on the page when only one page is allowed?
2. Write the explanation nobody asked for. A note, a post, a README — published anywhere at all. The act of making it public, even to an audience of zero, changes how honestly you have to write it.
3. Explain it to one friend, out loud. Faces find gaps that text cannot. The polite frown of a confused friend is precision instrumentation.
4. Answer one forum question from a stranger. A real problem with real stakes — and the strongest retrieval of all, because their situation never quite matches the tutorial's.

Notice the scale, too. You are not teaching the field; you are teaching the one thing you just did — how you built the scraper, what actually made the bread rise, the three chords and the strumming trick. Teaching one is like watching one: the number is the discipline, and it keeps the step honest and small enough to happen.

One rung closes the loop. And if you're mapping this onto a four-week sprint: week one is for watching, weeks two and three for making, week four for teaching — and the sprint's written archive entry and the teaching artifact can be the very same document.

Teaching artifacts are threads

Here is the part that only becomes visible years later. Of everything a sprint produces, the teaching artifact has the longest afterlife. The git cheat sheet becomes the onboarding doc at a job that doesn't exist yet. The explanation of gluten chemistry you wrote after the sourdough month resurfaces in a talk about emulsions, or patience, or why systems fail at their boundaries. Other projects pull these threads — that is what a loom is for — but only if they're filed where your future self can find them. Mine go into the Idea Ledger, one entry per artifact, same book every time. (The notebook I designed around that ritual is in the Library.)

As an Amazon Associate, we earn from qualifying purchases.

One loop, this month

Whatever has its hooks in you right now — the fermentation videos, the synth tutorials, the birdsong app — run the loop once, all three steps, at whatever scale the month allows.

Watch one, closely, and stop. Make one, badly, and finish it. Explain one, to anyone on the ladder, and notice — as the explanation leaves you — how much more of the thread stays behind than ever stayed from watching alone.

The surgeons built this loop because arteries don't forgive fake knowledge. Your stakes are gentler, but the standard is worth stealing. You are not learning for an operating theater. You are learning for keeps — and the loop is how a thread becomes yours.