Career conversations that change next week’s work — note 202

Good engineering leadership treats career conversations that change next week’s work — note 202 as practice — repeated, observable, coachable.

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.

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

Cross-team collaboration gets easier when you publish interfaces: who consumes what, what “done” means, and how failures are communicated. Ambiguity is expensive; clarity is a kindness.

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

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

I watch for two failure modes. First, leaders who disappear into strategy and lose the texture of the work. Second, leaders who never leave the details and never grow successors. Both produce brittle teams.

On career conversations that change next week’s work — note 202, 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.

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.

Ask your team one question in standup this week: what did we make easier to own?