Running Technical One-on-Ones That Actually Help People Grow

The problem

Some one-on-ones look important because they are on the calendar.

But in practice, they change nothing.

They become a mix of:

• delayed status update
• generic career talk
• social check-in with no direction

None of that is necessarily bad.

The problem is calling that a technical one-on-one and expecting real technical growth from it.

If the conversation does not improve:

• context
• judgment
• autonomy
• risk reading

it may still be pleasant.

But it is underused.

Mental model

A technical one-on-one does not exist to review every ticket.

It exists to improve how the person thinks and operates.

Short version:

the best technical one-on-one trades micro-status for judgment calibration.

That completely changes the kind of questions worth asking.

Breaking the problem down

What should not dominate the conversation

If the one-on-one is full of:

• “what did you do yesterday?”
• “where is that task at?”
• “did you finish that thing yet?”

something is misplaced.

Those topics need to show up in the normal flow of work:

• daily
• Slack
• PR
• planning

If the one-on-one depends on those topics to exist, it becomes a rebroadcast meeting.

What usually creates more value

Topics that usually create more value:

• where the person got stuck when making a decision
• which error pattern keeps repeating
• which context they still do not see
• what kind of autonomy they can already handle
• which next jump would make a real difference

That kind of conversation improves maturity, not only execution.

The focus is not to lecture all the time

Another common mistake is turning the one-on-one into a mini lecture.

You talk 80% of the time.

The person leaves with a lot of advice.

And almost no real diagnosis.

A strong one-on-one usually requires more curiosity than shine.

Better questions:

• “what felt most confusing here?”
• “where did you feel you were deciding without enough criteria?”
• “what would help you handle this with less dependence next time?”

Feedback needs to point to mechanism

Weak feedback:

• “you need to be more strategic”
• “you lacked ownership”
• “you need to improve communication”

That teaches almost nothing.

Useful feedback usually connects:

• observed behavior
• effect produced
• concrete adjustment

For example:

“You brought the problem early, which was good. But you came back with the question too open. Next time, try bringing two options with trade-offs, even if neither is fully ready yet.”

Now there is something trainable.

Growth is not only about correcting weakness

Some one-on-ones only exist when something went wrong.

That makes the conversation feel like an audit.

Good leadership also uses the one-on-one to expand strength:

• create space for more scope
• increase decision sophistication
• expose the person to new context
• calibrate the next bet

Simple example

Imagine someone on the team delivers well, but always comes back asking for validation before any architecture decision.

A weak one-on-one would be:

• repeating that they need more confidence

A good technical one-on-one would be:

1. isolate where confidence breaks exactly
2. discover whether the gap is context, experience, or boundary clarity
3. agree on a next problem where they decide first and align later
4. define which kind of risk still needs escalation

Now growth has become a concrete experiment.

Common mistakes

• Spending the whole time on status that should already be visible.
• Giving overly generic advice.
• Focusing only on weakness and forgetting scope expansion.
• Talking too much and investigating too little.
• Treating the one-on-one as a ritual instead of a tool.

How a senior thinks

People who lead well usually use the one-on-one to answer:

• what does this person already do well on their own?
• where do they still need extra context?
• which mistake keeps repeating?
• which next step increases autonomy without creating irresponsible risk?

Notice the pattern.

The goal is not to leave the conversation feeling “I was a good mentor.”

The goal is for the other person to operate better afterward.

What makes the conversation worth it

A good technical one-on-one usually leaves at least one of these things clearer:

• how to think
• how to decide
• when to escalate
• which next level to try

If none of that became clearer, the conversation was probably pleasant but weak.

A technical one-on-one is not a premium status meeting.

It is one of the few places where leadership becomes real growth, if you use it well.