My title through the Fargo years was project lead, and for a long time I thought that meant what the org chart implied: schedules, scopes, status calls. Somewhere in this stretch I figured out what it actually means. It means you are the person who answers. When the client calls — good news, bad news, three a.m. news — the voice that picks up is the voice accountable for the whole thing. Everything else about leading projects is decoration on that.

Two skills turned out to be the real job, and neither is in a computer science curriculum.

Estimation is a form of honesty. A lead who says “three weeks” under pressure, knowing it’s six, hasn’t managed expectations — they’ve borrowed trust at a brutal interest rate. Learning to say the true number with the reasoning attached, to a face that wanted a smaller one, took me years — and it’s now the entire basis of this practice’s published pricing and the canoe-plan rule that every number carries its why. The habit was forged here, one uncomfortable conference room at a time.

Translation is the deliverable. The client speaks business; the build speaks systems; the lead is the isthmus between the lakes. Most project failures I’ve witnessed — and most rescues I take now — trace to a translation failure: nobody lied, but the two languages never actually met, and the gap compounded quietly for months. Sitting in that seat for years is why every Dead North engagement puts you directly with the person doing the work. I didn’t remove the layers on principle alone; I was the layer, and I know exactly what gets lost in it when it’s staffed carelessly.

The tax of the seat is real too. The person who answers carries every open loop in their head at once, and I learned my limits the honest way — by finding them. Take care of the room, sure. You’re part of the room.

Next: The polyglot years — .NET, PHP, and refusing to be a one-tool builder.