Why Your 1-on-1s Feel Like Dentist Appointments
Howdy. Quick poll.
Your weekly 1-on-1 with your manager is in 15 minutes. What's your gut reaction?
A) Mild dread B) Scramble to remember what you did this week C) Copy-paste your Jira tickets into a bullet list D) All of the above
If you answered D, congratulations. You're using the most powerful career development tool available to you as... a status report you could've Slacked.
The Status Update Trap
Here's what a typical engineer's 1-on-1 looks like:
Manager: "So, what are you working on?" You: "Finishing the auth migration. Should be done by Thursday. Also fixed that flaky test in CI." Manager: "Great. Anything blocking you?" You: "Nah, we're good." Manager: "Cool. See you next week."
Total time: 8 minutes. Both of you leave feeling like you wasted 8 minutes. Because you did.
This isn't a 1-on-1. This is a human API call that returns a JSON blob of task status. And you've got an entire ticketing system that does this better.
What a 1-on-1 Is Actually For
Your 1-on-1 is the one recurring meeting where the agenda is yours. Not the team's. Not the sprint's. Not the roadmap's. Yours.
It's your time to:
- Get feedback that's too nuanced for a Slack message
- Signal your ambitions so your manager can create opportunities
- Surface concerns before they become resignations
- Build the relationship that determines how your work gets interpreted
That last one is the big one. Let me explain.
The Interpretation Layer
Every piece of work you do passes through an interpretation layer before it reaches the people who decide your career trajectory. That layer is your manager.
Same PR, two interpretations:
- Manager who knows you well: "Kyle refactored the payment service proactively. That's senior-level ownership. He identified tech debt and fixed it without being asked."
- Manager who doesn't know you: "Kyle spent two days on a refactor that wasn't on the sprint. Not sure that was the best use of time."
Same work. Completely different career outcomes. The variable isn't the work — it's the relationship.
Your 1-on-1 is where you build that relationship. Or don't.
The Fishing Guide Framework
I grew up fishing in Texas. And the best fishing guides I ever hired all did the same thing: they asked questions before they started the boat.
"What are you hoping to catch today? Bass or crappie?" "You been out much this season?" "Any techniques you want to try, or you want me to call the shots?"
They weren't wasting time. They were aligning expectations so the day would actually be good for me, not just efficient for them.
Your 1-on-1 should work the same way. Come with questions, not just updates.
Five Questions That Transform Your 1-on-1
Swap your bullet-list status report for these:
1. "What's one thing I could do differently to be more effective?"
This takes guts the first time. But it signals that you're coachable — which is the single most valued trait in any employee, at any level. And you'll get real feedback instead of waiting for the annual review to find out you've been doing something wrong for 11 months.
2. "Where do you see the biggest risk on our team right now?"
This elevates the conversation from your individual tasks to the team level. It shows you're thinking beyond your own lane. And the answer usually reveals priorities that aren't in any Jira board.
3. "I'd like to work toward [specific goal]. What would I need to demonstrate to get there?"
Promotion? Tech lead role? More architecture work? Don't hint. State it plainly and ask what the path looks like. Your manager can't advocate for something they don't know you want.
4. "Is there context I'm missing on [recent decision]?"
This is the non-confrontational way to say "that decision seemed weird and I want to understand it before I form an opinion." It builds trust because it shows you assume good intent before jumping to criticism.
5. "What's taking up most of your time right now?"
Asking about their world is underrated. It builds empathy, gives you context on why certain things are slow, and often reveals ways you can help — which is how you get noticed.
The Awkward Transition
If your 1-on-1s have been status updates for two years, you can't suddenly walk in with deep philosophical questions. That's weird.
Transition gradually. Next week, keep 5 minutes of status updates and add one real question. The week after, shift the ratio more. Within a month, you'll have a completely different meeting.
And here's the thing: your manager will probably be relieved. They don't want to sit through status updates either. They just don't know what else to do with the time if you don't bring something.
The Compound Effect
A good 1-on-1, every week, for a year, is 52 deposits into the most important professional relationship you have. That's 52 chances to:
- Show your judgment
- Demonstrate self-awareness
- Build mutual trust
- Align on expectations
Compare that to the engineer who treats it like a dentist appointment — something to endure every few weeks, saying as little as possible, just trying to get through it.
Who do you think gets the promotion?
This Is Just One Channel
Your 1-on-1 is just one of many communication channels you navigate as an engineer. There's code review, standups, design reviews, cross-team collaboration, incident response, and half a dozen other contexts where your social skills directly impact your career.
The Developer EQ book breaks all of these down through the lens of audio production — because mixing a track and mixing with humans have more in common than you'd think.
If you want to practice these conversations in a safe environment, the live cohort runs real 1-on-1 simulations. We pair up, roleplay both sides, and debrief. It's the closest thing to reps you can get without an actual time machine.
This is part of the Developer EQ series on social skills for engineers.