Leaders who stay close to the craft

Good engineering leadership treats leaders who stay close to the craft as practice — repeated, observable, coachable.

Hands-on does not mean doing everyone’s job. It means knowing where the system will tax the team and being willing to renegotiate scope when reality asks for it.

Trust compounds when leaders absorb uncertainty without dumping it as urgency onto the people closest to the code.

Buy-versus-build debates should start from ownership. If nobody on your team can operate the failure mode, you did not buy a capability — you rented a demo.

A useful leadership move is to make the work visible: write the decision, name the owner, set the review date. Theater thrives in fog.

Coaching means staying close enough to feel drag — latency in decisions, vague ownership, reviews that teach nothing — then clearing it without taking the keyboard permanently.

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.

On leaders who stay close to the craft, 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.

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.

The practical next step is small: pick one workflow, name an owner, and make the outcome observable next week.