🗣️ How to Run 1:1s That Actually Build Trust as a Tech Lead
Most tech leads run 1:1s. Few run good ones.
The default format — “any blockers? anything you need from me?” — feels productive but rarely builds trust. It’s a status update with extra steps.
A 1:1 that only covers work status is a meeting you didn’t need to have.
Here’s how to turn your 1:1s into the highest-leverage 30 minutes of your week.
🚨 Why Most 1:1s Fail
They fail because tech leads treat them as:
- A blocker-clearing session
- A status check
- Something to rush through
The person on the other side notices. They stop bringing up real issues, because the meeting has never made space for them.
⚠️ If your 1:1s only ever cover tickets, your team is only ever telling you half the story.
1️⃣ Let Them Set the Agenda 📋
Failing pattern: You open with your list of questions.
Better pattern: Ask “what do you want to use this time for?” — and actually wait.
Real-world example
A quiet engineer never raises anything unprompted. Once the lead starts opening with “what’s on your mind?” instead of a status question, the same engineer starts surfacing real concerns — team friction, career doubts, technical disagreements they’d been sitting on for weeks.
🔑 Silence in a 1:1 usually means the format hasn’t earned trust yet, not that there’s nothing to say.
2️⃣ Ask About Trajectory, Not Just Tasks 🎯
Every few weeks, ask something bigger than “how’s the sprint going”:
- “What’s something you want to be better at in six months?”
- “What part of the job actually excites you right now?”
Real-world example
An engineer who seemed disengaged in every 1:1 lights up when asked what they’d want to own if they had full freedom. That one question surfaces the actual mismatch — not motivation, but scope.
🧠 People don’t tell you what they want. They tell you what they think you’re asking for.
3️⃣ Say the Uncomfortable Thing Early 😬
If something’s bothering you about their work, don’t save it for a performance review.
Real-world example
A tech lead notices a pattern of missed estimates. Instead of waiting, they raise it directly in the next 1:1 — specific, kind, and early. The engineer appreciates knowing where they stand, and the pattern doesn’t repeat.
🔥 Delayed feedback isn’t kindness — it’s a debt that compounds.
4️⃣ Follow Through, Visibly 🔄
Nothing kills a 1:1 faster than raising something and watching it disappear.
Write down what you commit to. Bring it back up next time, even if it’s just “still working on that.”
🤝 Trust isn’t built in the meeting — it’s built in what happens after it.
🔚 Final Thought
A great 1:1 isn’t a status update, and it isn’t a therapy session either.
It’s the one recurring space where someone on your team gets your full, undistracted attention — and that alone is rarer than most leads realise.
Get my 3 free e-books by signing up to my newsletter and see more blogs on my site — or check out videos on the Imran Codes YouTube Channel!