The Conductor Problem

Someone asked me a strange question recently.

“If you could never do one part of your job again, which would bother you the most?”

There were several options.

Solving hard technical puzzles.
Designing architecture.
Teaching complex ideas.

All very appealing.

But the one that stuck with me was this:

Coordinating people to make things happen.

Which surprised me slightly.

Because I genuinely enjoy technical puzzles.

But when I thought about my best workdays, the pattern was obvious.

They weren’t the days where I solved the hardest bug.

They were the days where the whole system started moving smoothly.

Momentum appearing across the team.

Projects aligning.

Ideas connecting.

It reminded me of orchestras.

Not because I know anything about music.

But because the metaphor fits.

In an orchestra every musician is already extremely skilled.

The conductor doesn’t play the instruments.

They shape the timing.

The pacing.

The energy of the whole system.

Their job is not to produce the music.

Their job is to make the music possible.

Technical Lead roles feel a bit like that.

You’re not necessarily the best violinist.

You’re the one paying attention to the whole room.

Where the sound is building.

Where it’s drifting.

Where the next entrance should happen.

And sometimes the entire system changes because of a single small cue.

Which is fascinating.

Because it means the real work isn’t control.

It’s awareness.