Guide 3: Four engineering habits that work on a job site

Not everything transfers

Plenty of what I know from software doesn’t help at all on a job site. Nobody wants a sprint planning meeting at 7 a.m. next to a dumpster. But a few habits carry over almost exactly, and they’re the ones that prevent repeat mistakes.

1. Checklists over memory

Pilots and surgeons use checklists because memory fails under pressure. Deploys are the same, and so is closing out a job. Write the steps down once, then run the list every time.

Good candidates for a checklist:

• Loading the truck the night before
• Walking a job with the customer at the end
• Everything that has to happen before you send an invoice

Keep them short

If a checklist runs longer than a phone screen, people stop reading it. Put only the steps someone has actually missed before.

2. Blameless postmortems

When a deploy breaks, good teams ask what in the process let this happen? rather than who messed up? The same question works when a job runs over or a customer is unhappy.

After any job that went sideways, write three lines:

1. What happened
2. Why the process allowed it
3. The one change you’ll make so it can’t happen the same way again

3. Write the handoff down

In software, if it’s not written down it didn’t happen. On a crew, verbal handoffs get lost between the office, the truck, and the site. A short written note per job, covering scope, access, materials, and anything odd about the site, saves more time than any tool.

4. Ship in small batches

Small, frequent releases are easier to check than one giant one. On a job, that means quick check-ins with the customer at natural stopping points instead of one big reveal at the end. Problems show up while they’re still cheap to fix.

---

Where it breaks down

The trades run on relationships, trust, and showing up when you said you would. No process replaces that. These habits are only there to make the reliable part easier, so you have more attention left for the people part.