The first thirty seconds of someone explaining their work

A small ordering choice that reveals what somebody has been paying attention to.

There’s a thing people do when they talk about their work that tells me I can trust their judgment. It happens in the first thirty seconds, it’s subtle enough that most people never register it consciously, and I’ve been watching for it for about eight years.

They lead with why before they show you what.

The first thing out of their mouth is closer to “I built it this way because we’ll need to scale it next quarter” than “here’s what I built”.

Why the ordering carries information

Most people go the other way, and it’s completely natural. You made a thing, you’re a bit proud of it, so you show it. Here’s the feature, here are the buttons, here’s the flow. Then, if somebody asks, you explain the choices.

That ordering is optimised for execution. It assumes the interesting part is the artefact, and that the reasoning is supporting material available on request.

Execution is exactly the part that’s become cheap. A model will build what you describe, follow the standards, apply the patterns, and ship faster than any of us. Which means when somebody leads with the artefact, they’re leading with the commodity and holding back the scarce thing, usually without realising the ratio has flipped underneath them.

When the reasoning comes first, you’re watching someone demonstrate the part that’s still hard to get, before they show you the part that isn’t.

The two details that separate real reasoning from a performance of it

This is where it gets more interesting, because plenty of people have learned to lead with a reason. Not all of those reasons carry information.

Watch how specific it is. Generic reasoning sounds like “I built it this way because it’s best practice”, which tells you somebody read something once and is applying it uniformly. Real reasoning is bound to your constraints. “I built it like this because we need to extend it for mobile next quarter.” “Given the timeline, and that users need one-handed access, this pattern handles both.” That reasoning could not have been said about any other project, which is exactly what makes it evidence.

Watch whether they volunteered it. Nobody asked. They led with it because they assumed you’d want to understand the thinking, which is a completely different posture from explaining yourself once challenged. One is teaching. The other is defending. They produce almost identical sentences and they feel nothing alike in a room, and everyone present can tell the difference even if they couldn’t articulate it afterwards.

Where the signal misleads

I want to be careful, because I’ve watched this become a performance too.

There are people who’ve learned that leading with rationale reads as senior, and who now front-load a justification onto work that wasn’t really reasoned through. The reasoning was reverse-engineered after the fact and it sounds identical, because articulate people can construct a plausible why for almost anything.

The way you catch it is by asking what they considered and rejected. Genuine reasoning has discarded options attached to it, and the person can usually tell you what would have changed their mind. Retrofitted reasoning tends to have exactly one path, and it’s the path they took.

And on the other side, some excellent people lead with the artefact simply because they’re shy, or because they were trained in an environment where explaining your reasoning unprompted read as arrogance. The signal is real and it isn’t universal, and I’ve been wrong about people in both directions.

Trying it on your own work

Next time you present something, lead with the reasoning. Before showing what you built, say why you approached it that way, and give the actual constraint you were working around rather than the tidy retrospective justification.

It feels slightly wrong at first, because most of us were trained to show the artefact and let it speak.

Right now a large part of the industry is either panicking about AI or racing to master the tooling, and both of those are bets on execution getting faster. However good you get at building, and however fast you ship, that’s no longer where the scarcity sits. It sits in the judgment about what should exist and why.