This transcript was produced by robots and left as-is. Accuracy and elegance are not guaranteed.

I

Saturday morning, a carpenter I’d never met was coming by to look at some space. We were going to build a shed. No contract yet, no quote, nothing on paper, just a first look at the yard before either of us decided on anything.

An hour before he was supposed to arrive, he texted me. He didn’t have time to come by this morning anymore. Could we push it till later in the week?

I’d blocked out part of the day around that window. We don’t even live in the house yet. So I told him right then that the late notice wasn’t going to work for me.

Forty-five minutes later, he texted back. He was sorry, a last-minute change of plans on his end. That’s why he couldn’t make it.

Now, on the surface, that looks like the story resolving itself. Guy flakes out, guy apologizes, you move on and reschedule. That’s how most people read an apology, as the thing that cancels out the mistake. It doesn’t.

An apology for missing a commitment isn’t a correction to the pattern. It’s a second data point confirming it. One thing happened to him that morning, a last minute change of plans. But he was slow to tell me about it twice. Once when he gave me an hour’s notice instead of more, and again when it took him another 45 minutes to actually explain why. Both times I was the last to find out.

Neither time did he manage it in advance.

Had he apologized initially, with the notification, maybe the story would have turned out different.

But this lack of managing timelines, it shows up everywhere. Sometimes it’s done to us, sometimes we’re the ones doing it to somebody else. A new hire’s first missed deadline. How do they react? Are they proactive about it? A brand new client’s first scope push. How do you react? Are you managing it in advance?

So back to the story. That evening I cancelled the shed. Not swapped for a different carpenter, cancelled the project entirely.

I want to be honest about something before I explain why. This carpenter wasn’t the first trade to miss the mark on us this year. Our house renovation has run through a string of subcontractors who all handled schedule problems the same way. Decide first, notify late, if at all, apologize after the fact sometimes. By the time he texted me, I’d already spent months absorbing that exact pattern from other people.

He didn’t get a clean, isolated reaction. He got it all at once. Both barrels. Is that fair to him? Not entirely. If he’d been the first flaky trade I dealt with this year, I’d probably give him a second date, see what happens.

Unfortunately, he caught the accumulated weight of everyone who came before him, and none of that was his doing.

The accumulated frustration wasn’t noise sitting on top of a clean read, though. It’s also what let me read him correctly in the first place. A first meeting is a clean signal about the other person, maybe the cleanest one you’re going to get. But reading it right takes more than the meeting itself. It takes judgment, built from every other trade, hire, or vendor who’s shown you the same pattern before.

I didn’t recognize what that cancellation meant because I was some kind of neutral instrument. I recognized it because I’d already watched the same shape play out more than once with different people on the same project. That judgment is built through time and experience: observing, failing, getting knocked down and getting back up.

Gut instinct isn’t the opposite of experience. It’s experience running fast enough to feel instant.

Engineers in particular get the small sample part of this a bit backwards. We’re trained to distrust one data point. Don’t overreact, we tell each other. And most of the time that’s correct. But the presence of that one data point should at least heighten our awareness.

The reaction to the signal was amplified by context that had nothing to do with him. But the signal itself was real, and real signals are worth separating from how loudly you respond to them. Every meeting after that first one, he’d have been managing my impression of him. That one, he wasn’t managing anything. He was just being who he actually is when a Saturday morning got inconvenient. That part doesn’t need a track record of other trades to be true.

The same split applies whenever you’re bringing someone new into something that matters. The first commitment, before any relationship’s built up around it, tells you something true about how they operate under pressure. Whether you act on it, by finding someone else or by walking away from the whole thing, is a separate question. It’s one that depends on judgment, context, and probably how many other people have already shown you the same thing this year.

Don’t mistake a fast reaction for an unfair one just because it arrived quicker than a first meeting seems to deserve. Sometimes fast is just what recognition looks like once you’ve already paid for the slow version a few too many times.

That goes both ways though. I’ve been on the other side of that read myself.

I think back to one of the first impressions I got to make right at the beginning of my career. I had talked to my prospective boss a couple of times on the phone and a couple of times by email back in the very, very early days of email. We were set to meet for the very first time at Smitty’s at 6:30 in the morning, ahead of a day where we’d be heading out to site afterwards. I missed that part completely.

I didn’t think about it. Didn’t ask what site meant. So I showed up in a suit and tie, ready to wow my new boss. It may or may not have been effective for him. I did get the job, but later that morning when I showed up at a filthy, coal-fired power plant in a suit and tie, I made a very different impression on the operators and crew out there.

But I still got the job and it started a career that’s lasted almost three decades.