1-on-1 #

In many engineering teams — including in Indonesia — the term “1-on-1” often triggers anxiety. When a manager invites an engineer to a 1-on-1, the first thought is: what’s wrong with me? This isn’t the engineer’s fault — it reflects how 1-on-1s are often run wrong: only appearing when there’s a problem, turning into a one-sided evaluation session, or never having a clear purpose. This article clears up that perception and discusses 1-on-1s as they should be: an investment conversation — a conversation investing time in individual growth and long-term team health.

What Is a 1-on-1 Session? #

A 1-on-1 session is a recurring meeting between two individuals — most commonly between an engineer and their Engineering Manager or Tech Lead — focused on two-way communication, expectation alignment, and individual development. Not daily task updates.

The fundamental differences between a 1-on-1 and a regular meeting:

// ✗ Wrong perceptions about 1-on-1s

"1-on-1 = there's something wrong with me"

"1-on-1 = a performance evaluation session"

"1-on-1 = the manager wants to criticize my work"

// ✓ What a 1-on-1 actually is

"1-on-1 = a safe space to speak honestly about work and growth"

"1-on-1 = a chance to align expectations before they become problems"

"1-on-1 = an investment of time in long-term career growth"

Why Are 1-on-1s Important in Engineering? #

Engineers Resign Because They’re Not Heard, Not Because of Salary #

This isn’t an unfounded claim. Surveys from various engineering attrition studies consistently find that the biggest factor in engineers leaving a team isn’t compensation — it’s the relationship with their direct manager and the feeling that their growth isn’t being facilitated. Consistent 1-on-1s are the simplest mechanism for preventing both.

Signs that usually appear before an engineer resigns,
which go undetected without 1-on-1s:
  - Code review contributions slowly declining
  - Less vocal in technical meetings
  - Not raising blockers because they feel it's "pointless"
  - Doing tasks with minimum viable effort
  - Starting to take time off frequently

With regular 1-on-1s, these signals can be caught long before
the engineer actually decides to leave.

Poor Alignment Is Often Mistaken for a Performance Problem #

Many “performance problems” are actually communication problems:

flowchart TD
    A[Engineer not performing to expectations] --> B{Root cause}
    B --> C[A real skill gap]
    B --> D[Expectations never clearly communicated]
    B --> E[Motivation down from issues never discussed]
    B --> F[Undetected burnout]
    
    C --> G[Needs coaching & a learning plan]
    D --> H[Needs expectation clarification — solvable in a 1-on-1]
    E --> H
    F --> H

Without 1-on-1s, managers tend to conclude every case is C (a skill gap) and respond with a PIP (Performance Improvement Plan) — when D, E, and F are far more common and far easier to resolve if caught early.

Psychological Safety Doesn’t Grow on Its Own #

Psychological safety — the condition where someone feels safe taking interpersonal risks like admitting mistakes, voicing differing opinions, or asking for help — is one of the strongest predictors of team performance. And psychological safety is built through consistent, safe interactions, not through value declarations on presentation slides.

// What grows with high psychological safety
  ✓ Engineers raise blockers faster before they become big problems
  ✓ Code reviews are more honest because there's no fear of seeming critical
  ✓ Bugs or bad decisions are admitted faster without a culture of blame
  ✓ New ideas are shared more often even when imperfect

// What happens without psychological safety
  ✗ Problems are hidden until they explode into incidents
  ✗ Engineers agree in meetings but don't execute because they actually disagree
  ✗ Nobody wants to deliver bad news to the manager
  ✗ The team looks fine on the surface but is burning out underneath

Types of 1-on-1s #

Not all 1-on-1s serve the same purpose. Understanding the types helps managers and engineers prepare for sessions appropriately.

Regular 1-on-1 (Weekly / Bi-weekly) #

This is the foundation — routine sessions that build trust and detect problems before they become crises.

Duration: 30-45 minutes
Frequency: Weekly (for new teams or engineers facing challenges)
           Bi-weekly (for established relationships)

Typical agenda (not mandatory, adjust to the situation):
  1. Check-in: How are you doing this week? (5 minutes)
  2. Engineer's topics: What do you want to discuss? (15-20 minutes)
  3. Manager's topics: Anything to share or clarify? (10 minutes)
  4. Closing: What action items did we agree on? (5 minutes)

// ✗ What is NOT regular 1-on-1 agenda

"What tasks were finished this week?"

"Why isn't story X done yet?"

"How many story points were closed?"

→ That's a sprint status meeting, not a 1-on-1

// ✓ What IS regular 1-on-1 agenda

"Are there any obstacles keeping you from working optimally?"

"Is there anything unclear about the technical decisions we've made?"

"How do you feel about this sprint overall?"

Career Development 1-on-1 #

A session explicitly focused on long-term career growth — not just this sprint’s performance.

Frequency: Quarterly or semi-annually (but can be more often if the engineer asks)
Duration: 60 minutes (longer than a regular 1-on-1)

Topics discussed:
  ✓ Where the engineer wants to grow: the IC (Individual Contributor) path or leadership?
  ✓ What skills to develop in the next 6-12 months?
  ✓ The gap between the current state and the goal — identified together, not dictated
  ✓ What opportunities in the team or projects can support that growth?
  ✓ What mentorship, learning resources, or exposure can be facilitated?

Expected outputs:
  □ A concrete growth plan (not just discussion)
  □ At least 1-2 action items doable within the next 30 days
  □ Manager commitment to facilitate the agreed opportunities

Feedback-Focused 1-on-1 #

A session explicitly focused on exchanging feedback — and this must always be two-way.

// ✗ A one-way feedback 1-on-1
Manager: "I'd like to give you feedback on your work"
Engineer: [listens, never asked to give feedback back]
→ This isn't a feedback session, it's an evaluation

// ✓ A real feedback 1-on-1
Manager: "I'd like us to share feedback with each other today.
         I have a few things I want to share,
         but I'd also like to hear how you see the way we work together."
→ Feedback flows in both directions
→ The engineer gets an equal chance to share their observations

Constructive feedback format (applies to both directions):
  ✓ Specific and behavior-based, not characterizations
  ✓ "When X happened, the impact was Y, and I'd like to suggest Z"
  ✗ "You're always slow at making decisions"
  ✓ "In the last three sprints, several technical decisions were delayed by more than 2 days
      and this made other teams wait. Are there obstacles we can help with?"

Problem-Solving / Coaching 1-on-1 #

A session called when an engineer is stuck — technically, interpersonally, or in decision-making.

Coaching principles in 1-on-1s:
  ✓ Guide with questions, don't jump straight to answers
  ✓ The goal is the engineer finding their own solutions, not depending on the manager
  ✓ Open questions are more effective than closed questions

// Effective coaching questions

"What have you tried so far?"

"What's holding you back from making that decision?"

"If you weren't afraid of being wrong, what would you do?"

"What do you think would happen if you tried approach X?"

"Who else might be able to help in this situation?"

// ✗ Approaches that weaken engineer independence

"Here's what you should do: ..."

"You should have ... from the start"

→ The engineer doesn't learn to think independently; they only learn to ask the manager

Ad-hoc 1-on-1 #

An unscheduled session needed to respond to a specific situation quickly.

When an ad-hoc 1-on-1 is needed:
  ✓ After a major production incident involving that engineer
  ✓ After organizational changes affecting roles or teams
  ✓ When an engineer shows conspicuous signs of distress
  ✓ When there's an interpersonal conflict to resolve

How to start an ad-hoc 1-on-1 without being scary:
  ✓ "I'd like to chat briefly — nothing's wrong, I just want to check in"
  ✗ "Can we talk for a bit?" [no context] → immediately triggers anxiety

Why Do 1-on-1s Often Have a Negative Connotation? #

This negative connotation doesn’t appear without reason. There are real patterns in how 1-on-1s are run that create it:

flowchart TD
    A[Negative 1-on-1 connotation] --> B["1-on-1s only appear\nwhen there's a problem"]
    A --> C["Untrained managers —\n1-on-1 becomes a one-sided evaluation"]
    A --> D["No transparency\nabout the session's purpose"]
    A --> E["Confidentiality not kept —\nwhat's discussed spreads to the team"]
    A --> F["No follow-up —\nproblems raised are never acted on"]

    B --> G["Engineers conclude:\n1-on-1 = I'm in trouble"]
    C --> G
    D --> G
    E --> H[Engineers don't dare to be honest]
    F --> H

The problem isn’t the 1-on-1 as a practice — the problem is how it’s run. And the solution isn’t removing 1-on-1s, it’s fixing how they’re done.

Best Practices for Managers / Tech Leads #

Make the 1-on-1 the Engineer’s, Not the Manager’s #

This is the most fundamental change a manager can make. A 1-on-1 should feel to the engineer like their time — not the manager’s time to communicate things that need doing.

// ✗ A 1-on-1 that feels like the manager's
Manager starts: "OK, there are a few things I want to share..."
[Manager talks for 40 minutes, engineer 5 minutes at the end]

// ✓ A 1-on-1 that feels like the engineer's
Manager starts: "What do you want to discuss today?"
[Engineer talks 25-30 minutes, manager responds and asks]
Manager at the end: "There's one thing I'd like to share too — OK?"

Target speaking ratio: 70% engineer, 30% manager

Be Consistent and Scheduled — Never Skipped Without a Strong Reason #

// ✗ Patterns that destroy trust
Sprint 1: 1-on-1 held
Sprint 2: "Busy, let's skip this week"
Sprint 3: 1-on-1 held
Sprint 4: "There's a sudden meeting, let's reschedule" — never rescheduled
→ The engineer concludes: 1-on-1s aren't important, or only appear when there's a problem

// ✓ Patterns that build trust
1-on-1s are always scheduled and very rarely skipped
If rescheduling is needed, it's done proactively and immediately rescheduled
→ The engineer knows: this is a serious investment, not a formality

Keep Confidentiality Strict #

What engineers share in 1-on-1s must not become gossip or be quoted elsewhere without permission. Once an engineer learns that what they shared in a 1-on-1 surfaced in another context, they’ll never be honest again.

// ✗ Common confidentiality violations (sometimes unintentional)
Manager at a team meeting: "Oh, [Engineer A] also told me about this..."
Manager to HR: "So during the 1-on-1 yesterday, they said..."
→ Engineer A immediately stops trusting 1-on-1s

// ✓ Keeping confidentiality
Ask first: "May I share this with [someone else] because it might help?"
If the engineer disagrees, respect their decision
Information about an engineer's personal condition must not be shared without consent

Follow Up on Every Action Item #

This is the biggest source of frustration from the engineer side: raising a problem in a 1-on-1, the manager promises to follow up, and nothing happens. This is more damaging than having no 1-on-1 at all.

// ✓ Trust-building practices
Every 1-on-1 action item is recorded (in a shared doc or notes)
At the start of the next 1-on-1, review the previous session's action items
If an action item can't be followed up on, explain why — don't stay silent

// A simple template for recording 1-on-1 action items
Date: [date]
Topics discussed: [summary]
Action items:
  - [Name] will [action] by [date]
  - [Name] will [action] by [date]
Status (filled in at the next session): ✓ / ✗ / In progress

Best Practices for Engineers #

Come with Topics, Not Empty-Handed #

The 1-on-1 is your time — use it fully. Engineers who arrive unprepared tend to spend the session on routine task updates that could have been shared asynchronously.

Questions that help prepare 1-on-1 topics:
  ✓ What obstacles can't I solve on my own?
  ✓ Are there unclear expectations making me unsure?
  ✓ Is there anything in the work environment disrupting my productivity?
  ✓ Is there a skill I want to develop that needs support?
  ✓ Are there team decisions whose rationale I don't understand?
  ✓ Is there anything I want to share about how we work together?

Use 1-on-1s to Discuss Growth, Not Just Problems #

1-on-1s aren’t only for discussing what’s wrong. They’re also — even primarily — for discussing where you want to grow.

// Growth topics you can bring to a 1-on-1

"I'm interested in trying to lead a small project in the coming sprint"

"I'd like to go deeper on distributed systems — any recommendations?"

"I feel ready for a larger scope — what's your view?"

"I'd like feedback on how I do code reviews"

Give Feedback to Your Manager — It’s Two-Way #

Many engineers don’t know they can and should give feedback to their manager in 1-on-1s. Good managers will actually appreciate it.

// How to deliver constructive feedback to a manager
Behavior-based, not personal characterizations:
  ✓ "In the last few technical decisions, I felt less involved
      in the early discussions. Is there a way I can contribute earlier?"
  ✗ "You always make decisions alone without asking the team"

Deliver with context:
  ✓ "I'd like to share something — maybe this is just my perspective,
      but I want to make sure you know"
  ✓ Focus on impact on work, not personal judgment

Questions That Open Meaningful Conversations #

The questions asked in a 1-on-1 determine the quality of the conversation. Here are questions proven to open deeper discussions:

FOR CHECK-INS:
  "How are you doing this week — on a scale of 1 to 10, and why?"
  "What's been draining your energy lately?"
  "Is there anything outside work affecting your focus?"

TO DIG INTO OBSTACLES:
  "What's most preventing you from working as effectively as possible?"
  "If you could change one thing about how we work, what would it be?"
  "Are there any decisions or processes you think don't make sense?"

FOR GROWTH:
  "What do you want to learn or try in the next 3 months?"
  "Where do you feel you've grown most lately?"
  "What can I do to help you grow faster?"

FOR FEEDBACK:
  "How can I be more helpful to you?"
  "Is there feedback you'd like to share about how we work together?"
  "Are there expectations you feel are unclear from my side?"

FOR ENGAGEMENT:
  "What's been making you excited to come to work lately?"
  "Is there a project or area you want to work on but haven't gotten to?"

1-on-1 Anti-Patterns to Avoid #

// ✗ 1-on-1s that only appear when there's a problem
Months without 1-on-1s → suddenly called in
→ The engineer is instantly defensive due to the strong association: 1-on-1 = problem
// ✓ Regular 1-on-1s are the foundation; ad-hoc ones are only additions

// ✗ The manager dominating the entire session
"I have a lot of things I need to tell you..."
[45 minutes of the manager talking]

"OK, any questions?" [2 minutes left]
// ✓ The engineer must get a larger share of speaking time

// ✗ 1-on-1s turning into status meetings
"OK, tell me the progress of stories X, Y, and Z this week"
// ✓ Status updates can be async; 1-on-1s are for things that can't

// ✗ No follow-up from session to session
Engineer raises a problem → manager promises → nothing happens
→ The engineer stops trusting 1-on-1s and starts giving only safe answers
// ✓ Every action item is recorded and reviewed at the next session

// ✗ 1-on-1s never discussing careers
Every session only covers technical issues or sprint conditions
→ The engineer feels there's no investment in their growth
// ✓ At least once per quarter, explicitly discuss career development

// ✗ Confidentiality violated — even unintentionally
The manager mentions 1-on-1 content in another context without permission
→ Years of built trust can collapse in a single event
// ✓ What's discussed in a 1-on-1 stays in the 1-on-1 unless there's explicit consent

Healthy 1-on-1 Checklist #

FOR MANAGERS / TECH LEADS:
  □ 1-on-1s scheduled regularly and consistently — not skipped without strong reasons
  □ The engineer knows the session's purpose before attending
  □ The agenda is opened to the engineer at the start: "What do you want to discuss?"
  □ The manager speaks ≤ 30% of the total session time
  □ Confidentiality kept — nothing leaked without consent
  □ Previous session's action items reviewed at the start of the next session
  □ Career and growth topics discussed at least once per quarter
  □ Feedback requested from the engineer, not just given to the engineer

FOR ENGINEERS:
  □ Come with at least 1 topic to discuss
  □ Use the session for more than just task updates
  □ Raise obstacles that can't be solved alone
  □ Share career aspirations — don't wait to be asked
  □ Give constructive feedback to the manager if there is any
  □ Follow up on agreed action items before the next session

SIGNS OF A HEALTHY 1-ON-1:
  □ The engineer arrives with enthusiasm, not anxiety
  □ The conversation feels safe — the engineer speaks honestly about difficulties
  □ Real follow-through from session to session
  □ The manager-engineer relationship grows over time
  □ The engineer feels their growth is facilitated, not just monitored

Summary #

• A 1-on-1 isn’t a sign of a problem — it’s an investment — mature organizations run 1-on-1s regularly precisely because they care about engineer growth and retention.
• The 1-on-1 belongs to the engineer, not the manager — the engineer should get 70% of the speaking time, the agenda opens to them, and topics follow their needs.
• Consistency is the source of trust — 1-on-1s constantly skipped or only appearing when there’s a problem actively damage engineers’ perception of the session.
• Status updates aren’t 1-on-1 topics — things that can be shared asynchronously don’t need to fill limited 1-on-1 time.
• Feedback must be two-way — engineers have the right and should give feedback to their manager, not just receive it.
• Confidentiality is non-negotiable — a single violation can destroy months of built trust.
• Action items must be followed up — a 1-on-1 producing no change is more damaging than no 1-on-1 at all because it creates cynicism.
• The negative 1-on-1 connotation is an implementation problem, not a concept problem — fix how it’s run, don’t remove the practice.

← Previous: Syncup   Next: Knowledge Sharing →