Coaching juniors through AI-assisted workflows — note 168

Coaching juniors through AI-assisted workflows — note 168 sounds like a strategy slide until you watch a team try it under real load.

Mentorship that works looks like smaller loops: a review comment that teaches a pattern, a design note that names tradeoffs, a career chat that changes next week’s assignment.

Sponsor publicly, critique privately, and keep a written trail of growth so progress is not a vibe.

Process should be light enough to change. If your AI workflow cannot be updated when a model, connector, or compliance rule changes, you do not have a workflow — you have a ritual.

Juniors do not need motivational speeches. They need safe chances to own a slice, fail without shame, and hear specific feedback.

With AI in the loop, mentorship shifts. You coach verification, skepticism, and taste — not just syntax.

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 coaching juniors through ai-assisted workflows — note 168, the leadership move is to make the invisible visible: ownership, verification, and the path for the next person.

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

Team literacy matters more than individual clever prompts. Shared harnesses beat private magic.

Psychology shows up in engineering as safety to ask questions. Without it, AI only accelerates confident mistakes.

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.

Lead for continuity. Leave systems and people that still work when you are not in the room.