When a vendor becomes your process: a field note

Good engineering leadership treats when a vendor becomes your process: a field note as practice — repeated, observable, coachable.

A purchased AI tool still needs an owner on-call for failure modes, data handling, and process fit.

Buy commodities. Build the harness that makes your team’s judgment visible: policy, evals, audit, and exit.

In practice that means shorter cycles: decide, ship a thin slice, review what broke, coach the pattern into the next person. Long programs without those loops become status machines.

Make-or-buy decisions should include the cost of undoing the choice. Soft lock-in is still lock-in.

AI compresses the typing cost of building. It does not compress the ownership cost of running what you built.

Mentorship scales when seniors narrate tradeoffs in writing. A one-paragraph decision record teaches more than a hallway conversation that evaporates.

On when a vendor becomes your process: a field note, the leadership move is to make the invisible visible: ownership, verification, and the path for the next person.

When agents join the loop, treat them like junior systems: limited privileges, explicit tools, budgets, and a human who owns the outcome. Autonomy without audit is just distributed risk.

Watch for fluent wrongness. Confidence in the output is not evidence.

I prefer written decisions over verbal ones. Memory is a poor archive, and AI tools make fluent improvisation cheap — which raises the value of durable context.

None of this requires a new framework brand. It requires attention, a short feedback loop, and the humility to change process when agents join the workflow.

Coaching is the mechanism. Process is the memory. Tools are leverage — only when ownership stays human.