explaining things

How do you explain a complex, honestly boring technical subject so someone leans in instead of glazing over? I think about this constantly, because the gap between the people who build technical things and the people who live with their consequences is mostly an explanation gap.

The trick, as far as I can tell, is that fun is not decoration on the explanation; it is the explanation. A LEGO brick explains discrete aggregation better than a lecture. The lEgoarCh film, a cathedral solving into bricks, explains that pipeline better than the diagram of the pipeline does. When an idea lands, it's usually because someone found the toy inside the concept.

Fig. 17 · One idea in two representations: a process diagram, and the same process as three stacked bricks.

So I hold my own work to it: if I can't make the boring part captivating, I don't understand it well enough yet. And it matters beyond taste. The subjects that decide how buildings treat people read as the most boring ones, standards, data layers, scoring models, and they'll only get argued about by more than five people if someone makes them worth looking at.