1:1 Meeting Templates That Work for Different Personality Types

2026-07-11 · 7 min read · 1:1 Meetings

Most 1:1 advice treats the meeting as a standard format you apply uniformly to every direct report. Same questions, same structure, same cadence. The problem is that people are different in ways that matter for how useful a 1:1 can be.

The engineer who processes out loud needs a different kind of space than the one who comes with a prepared list. The person who's emotionally open in professional settings needs a different approach than the one who prefers to keep work and personal concerns strictly separate. The new hire needs different conversations than the senior engineer who's been on the team for three years.

This doesn't mean abandoning structure. It means understanding what you're trying to accomplish and adapting the container.

What Every 1:1 Needs Regardless of Style

Before getting to adaptation, some things should be true of every 1:1:

It's primarily their time, not yours. You have a relationship to maintain and information you want to share, but the primary function of the 1:1 is to serve them — their development, their blockers, their experience of the work. If you're talking more than 40% of the time, rebalance.

It should feel safe. Whatever personality type you're dealing with, the meeting needs to be a place where they can say something that's true. This requires that you don't respond defensively, don't penalise candour, and follow through on what you commit to.

Something should be useful. If someone walks out of a 1:1 having gained nothing — no clarity, no blocker removed, no sense of being understood — that's a wasted meeting. Know what "useful" looks like for each person.

The Thinker Who Comes Prepared

Some engineers treat 1:1s as structured meetings. They arrive with a list, work through it, and are done. This is actually a gift — you don't have to work hard to surface what's on their mind.

What works: Let them run their agenda. Open with "what have you got?" and go through it. Add your items at the end. These engineers often prefer a consistent structure they can prepare for.

What doesn't work: Open-ended questions without direction ("how are you feeling about things?"). These can feel vague and unproductive to someone who came with a list.

Add to the structure: Occasionally ask a question that breaks the task-list frame: "Is there anything you've been sitting with that hasn't made it onto the agenda?" You'll surface things that don't fit the format they've developed.

The Processor Who Thinks Out Loud

Other engineers don't know what they think until they say it. They might arrive with nothing in particular, then talk their way into something important. These 1:1s can feel unfocused but often produce the most useful conversations if you can follow the thread.

What works: Give them space to ramble initially. Ask follow-up questions rather than changing the subject. "You mentioned X — can you say more about that?" often opens more than any prepared question.

What doesn't work: Cutting off a tangent too quickly, or pushing for bullet-pointed updates when they haven't landed on what they want to say yet.

Add to the structure: After they've processed for a while, reflect back what you heard: "It sounds like the main thing you're trying to figure out is X — is that right?" This helps them find the signal in what they've said.

The Private Person Who Keeps Work and Self Separate

Not everyone wants to discuss personal circumstances, feelings, or career anxieties with their manager. Some engineers — especially in more formal professional cultures, or in teams where this hasn't historically been safe — want 1:1s to be professional and practical.

What works: Focus on the work. Blockers, technical decisions, project feedback, career development in concrete terms. These engineers often respond well to direct, specific questions: "What's the thing that would make your work easier this month?"

What doesn't work: Pushing for emotional openness they're not comfortable with. Asking how they're "really" feeling, or probing about personal circumstances they haven't volunteered. This can feel intrusive and erode trust.

Add to the structure: Open a small door occasionally: "Is there anything about how the team's working that's been bothering you?" This is more specific than "how are you feeling?" and gives them permission to raise something without requiring emotional disclosure.

The Newer Engineer Who Needs More Guidance

Junior and mid-level engineers often need 1:1s to serve a development function more heavily than senior engineers do. They have more to learn, more uncertainty, and more need for explicit feedback.

What works: Ask about what they're learning: "What's been hardest to understand in the codebase?" "What would you have done differently on that PR?" Be generous with specific, concrete feedback. Newer engineers often don't know what they don't know — your job is to illuminate the edges of their current understanding.

Questions that help:

What doesn't work: Assuming they'll raise blockers themselves. Newer engineers often don't know that a thing is blockable, or feel uncomfortable asking for help. You need to dig.

The Senior Engineer Who Runs Themselves

Experienced engineers often need 1:1s to be less frequent and more substantive. They don't need check-ins on whether they're doing the work — they need conversations about direction, strategy, growth, and the things that can't be Slacked.

What works: More strategic questions. "What do you think the team should be doing differently in six months?" "What's the most important technical decision we haven't made yet?" "Where do you want to be in two years, and what would help us get there?" These engineers often have strong opinions about the team and the company and appreciate having a forum for them.

What doesn't work: Process-heavy check-ins that feel patronising. "Is everything on track?" asked too often signals distrust.

Add to the structure: Occasionally ask for mentorship of others — senior engineers often have useful perspective on junior team members. "How do you see Priya developing? Is there anything you think I'm missing?"

The One Thing That Adapts Everything

Learning how each person experiences 1:1s is itself a 1:1 topic. Ask directly: "Are these meetings useful to you? What would make them better?" Most people have opinions they've never been invited to share. The answer usually tells you a lot about what they need and what the meetings have been missing.