Lightning Talks Make Mokumoku Learning Stick

Did you learn something new recently?

Most people reading a blog like this would say yes. Now the harder question: did you tell anyone about it?

That’s where a lot of people hesitate. I think that small pause marks a real fork in the road for how much an engineer actually grows.

Mokumoku sessions are a genuinely good system

In the tech community, it’s common to hold “mokumoku-kai” — silent co-working sessions where everyone gathers and quietly studies or works on their own thing, side by side. Study and personal projects tend to be lonely, and it’s easy to lose momentum on a tired day. But something about sitting in a room where everyone else is quietly grinding pulls your hands back to the keyboard. As a system for making learning stick, mokumoku sessions are excellent, and I genuinely like them.

The one thing that’s wasted

There’s just one thing that bothers me about mokumoku sessions: the learning tends to stay locked inside your own head.

You spend real time learning something, but if you never put it outside yourself, it stays sealed in there. The fact that you learned it remains true, but input alone fades faster than you’d expect. “I felt like I understood it when I read it” turns into “I can’t quite explain it” a few days later. That’s not rare — it’s the default outcome of pure input.

What makes learning stick is the act of recalling it

I think the thing that actually turns a fact you read into something you own is the act of recalling it. Not just reading or listening, but pulling out of your own head what you learned, why it works that way, and what the key point was. Add that recall step, and the knowledge gets noticeably stronger. Pairing learning with recall is, I think, one of the best ways to maximize what you actually get out of studying.

This is where lightning talks come in

A lightning talk (LT) is usually a short, 3-to-5-minute presentation where you share something you learned, noticed, or tried. Mokumoku sessions and lightning talks are often held together, and I think that pairing makes a lot of sense: the mokumoku session is input, and the lightning talk is output that forces you to recall and put it into words. Learning something and, on the same day, recalling it, articulating it, and telling someone else — that’s a genuinely strong loop for retention.

The person who learns the most is the one giving the talk

The value of a lightning talk isn’t really “teaching someone else.” The person who benefits the most is actually the one speaking. Trying to explain something to someone else exposes the parts you only half understood, forces you to organize the order of your explanation, and makes you define, in your own words, what the point actually was. If someone asks a question, you find the holes in your own understanding.

Content that would otherwise just pass through you suddenly gains resolution the moment you decide to explain it to someone in three minutes. There’s a real gap between feeling like you understand something and being able to explain it, and a lightning talk closes that gap. It’s the same instinct behind From Funeral to Adventure: A Manager’s Real Art of Asking — a question aimed at drawing out someone’s own understanding does more than a question aimed at moving them.

Self-improvement matters a lot for engineers. But sharing what you learn with the outside world matters even more, for two reasons.

First, explaining deepens your own understanding, as I just described — the act of trying to speak is itself strong learning.

Second, learning becomes an asset once it’s shared. Knowledge inside your head fades no matter what. But turn it into a lightning talk deck, an article, or a note, and it stays — helping future you, and possibly someone else too. Once you put a piece of learning outside yourself, it stops being a fragile memory and becomes something reusable. That’s the same idea behind Why Your Retrospectives (KPT) Don’t Stick — Fixing “Write It and Forget It”: a record only becomes an asset when it’s built to resurface later, not just written once and buried.

Maybe you’re thinking: speaking in front of people is embarrassing, I don’t know enough to present, or I don’t even have a topic.

But a lightning talk isn’t a stage for polished, complete knowledge — it’s a place to share what you learned. A command you discovered today, a bug you hit and how you fixed it, a concept you don’t fully understand yet but found interesting — small learnings like these are often exactly what helps someone else. And if you get something wrong, you can just correct it later. Putting something out, getting feedback, fixing it, and making it stronger is the same posture behind “Black Box Thinking” — Life Is Too Short to Experience Every Failure Yourself: a culture that detects, reports, and reuses failure instead of hiding it.

Three minutes is enough to start

The idea of “giving a lightning talk” can feel heavy, but three minutes is plenty to begin with. A simple template works fine:

What I learned today
What I didn’t understand
What I figured out
How I’ll use it tomorrow

That alone makes a solid lightning talk. Short talks lower the bar to prepare, and lowering the bar makes it easier to take the first step.

Closing thoughts

Mokumoku sessions are a genuinely good system — they make it easier to keep learning going when you’d otherwise be alone. But stopping there leaves something on the table. Learning gets stronger when you recall it, put it into words, and share it outside yourself. That’s the role a lightning talk plays.

Study during the mokumoku session, then talk about it in a lightning talk. Understanding deepens, learning becomes an asset, and it feeds the next thing you learn. You don’t need to be perfect — if you’re wrong, you can fix it. Why not start by sharing one small thing you learned, in three minutes?

Next time you’re at a mokumoku session, try asking yourself one question before you leave: if I had three minutes to tell someone what I learned today, what would I say? Just holding that question changes how you learn — and that shift adds up more than it looks like it will.