One-on-one meetings are recurring conversations between a manager and an employee that create room for individual support, feedback, and direction. For engineering managers, they are an opportunity to understand the person behind the work -- not just the state of a project. But putting a meeting on the calendar does not tell either person how to make that time useful.
A new team member might need context. Someone else might want to think through a difficult interaction. Another person might want clearer expectations about what comes next. These are different needs, and treating them as interchangeable is where a supposedly helpful meeting can start feeling like another obligation.
My approach is to give people room to steer while staying accountable for supporting them. That means listening, noticing what we have neglected, and following through. It does not mean requiring everyone to arrive with the same agenda or asking people to disclose their private lives.
What One-on-One Meetings Are For
The purpose is broader than collecting information. An engineering manager needs to understand what is happening across a team, but team-level awareness does not automatically translate into individual support. Knowing that a project is progressing tells you little about whether someone understands their responsibilities, needs feedback, or feels stuck working with another team.
One-on-one meetings give that individual context somewhere to go. They can help you understand what the person needs from you and what you need to clarify together. The useful outcome might be a decision, a better understanding of a problem, or agreement about something to revisit. It need not be a new task every time.
I discuss this flexibility in my Code Commute episode about using one-on-one time. There is no single correct conversation for every person at every point in their career. A meeting can be useful without resembling the previous week's discussion.
That is not an argument against preparation. It is an argument against confusing preparation with compliance. Look at what the discussion makes possible for that individual:
- A tidy agenda is not proof that someone received support.
- An informal conversation is not proof that time was wasted.
The conversation's value is not determined by how polished it looks from the outside.
Share the Conversation, Not the Manager's Accountability
I like opening the floor to what is top of mind for the employee. That leaves room for something I might not have anticipated instead of making my priorities the only available topics. Someone closest to a problem may see an important detail that never appeared in a team update.
Some people bring notes and clear topics. Others do not. In my discussion about supporting new direct reports, I explain why I would not build a system that depends on every person bringing that structure. What works well with one employee may not work with the next.
Employee agency still matters. People can identify concerns, ask for context, or say that the current conversation is not helping. But the manager has authority and responsibilities the employee does not share equally. Calling it an employee-led meeting should not become a way to blame them when feedback or support never arrives.
As the manager, you can notice that a subject has disappeared and make room for it. Two responsibilities remain yours even when the employee is steering:
- Bring relevant observations rather than wait indefinitely for a request.
- Notice neglected subjects instead of assuming silence means they do not matter.
With a quieter person, that is particularly important: a short answer does not establish that they are disengaged or that they have no needs.
This connects to a broader question in hands-on management: how do you stay close enough to help without making everything depend on your intervention? In the meeting, give people room to explain their situation before deciding what your involvement should look like.
Let Topics Change as Needs Change
A helpful conversation is responsive to the person and the moment. Someone joining a team may need an explanation of how work fits together. Someone comfortable in the role may care more about a collaboration problem or a responsibility they would like to explore. The same person can need different things a month later.
That is why I do not treat technical or work-related questions as automatically inappropriate. If the manager has relevant context, asking them can be a sensible use of time. The question is whether the conversation addresses a real need or is simply filling the space because neither person knows what else is possible.
Consider two hypothetical situations where different conversations could be useful:
- An engineer understands their assignment but not why it matters to the business.
- An engineer understands the business purpose but needs clarity about their own responsibilities.
Talking through the missing context could help either person make decisions. Neither situation is a reason to require every meeting to include a business briefing.
Learning can also be a useful subject. A person may want to understand an area outside their current work or discuss how to develop a skill through actual responsibilities. The distinction between learning at work and learning at home is relevant here: development does not have to be framed entirely as something the employee does after hours.
The goal is not to rotate through a compulsory menu. It is to avoid letting habit decide every conversation. Notice what is useful now and what has been absent long enough to deserve attention.
Keep One-on-One Meetings From Becoming Only Status Updates
There is nothing inherently wrong with discussing project progress. During an intense period, the project may genuinely be what someone wants to talk about. A blanket prohibition on status can make you dismiss the very thing occupying their attention.
The problem is the recurring pattern where status becomes the entire relationship. If each conversation repeats information available elsewhere and ends there, feedback, concerns, and future direction may never get space. You know what shipped, but not what support the person needed along the way.
A hypothetical example helps show the distinction. An employee describing a delay might just be reporting a date. They might instead be trying to explain that two teams have incompatible expectations. The first could belong in a routine update; the second may deserve a conversation about context and support. Listen before sorting it into a category.
Where routine updates already have a suitable channel, you can avoid duplicating them in full. Where they do not, that is a communication gap to understand rather than a reason to reprimand the employee. The manager should help establish a workable alternative.
You can also acknowledge the current pressure while agreeing to revisit a neglected subject. That keeps flexibility from becoming permanent drift. Keep the distinction clear:
- Work discussion can address a real need, even when it includes status.
- Repeated status-only discussion can leave other needs unaddressed.
The issue is not whether a particular week included status; it is whether the recurring conversation still serves the person.
Listen Before Turning Every Concern Into an Answer
As engineering managers, we can be eager to help by offering solutions. I know I need to practice listening more and asking questions instead of immediately jumping to answers. Being able to respond quickly is not the same as understanding what someone needs.
If you consume the discussion explaining your response, the employee has little room left to examine their own thinking. Sometimes helping them consider options is more useful than handing over your preferred answer. Sometimes they need information or a decision that only you can provide. Neither approach should become an automatic rule.
Consider a hypothetical disagreement about ownership. Before proposing a resolution, you might ask what each side believes they own and where that understanding diverged. That gives you a better starting point than assuming the issue is reluctance to collaborate.
My earlier article on being a human sounding board explores listening as a leadership practice. It is an earlier perspective, not a prescribed meeting format. The useful connection is making room for someone else's thinking rather than treating your response as the centerpiece.
Helping also requires clarity about the request. Different needs can sit behind the same concern:
- Understanding the situation without deciding on an intervention yet.
- Thinking through options together.
- Taking an action that needs the manager's involvement.
These are distinctions to explore, not choices the employee must settle before speaking. They do not need a complete solution before raising a problem. You can work together to clarify what help would mean.
Discuss Feedback and Direction Without Making Every Week a Verdict
Feedback and career direction belong in the relationship, but they are not the same conversation. Feedback can concern something recent and specific. Direction asks whether the work and opportunities fit where the person wants to go.
A recurring meeting does not require a fresh overall assessment every week. If little has changed, asking for a global verdict repeatedly can produce the same reassurance without much insight. A discussion tied to a particular piece of work has something more concrete to examine.
Managers should not wait for every employee to request that discussion. If you have a relevant observation, bring it. If you need time to think before responding usefully, say so and follow up rather than disguising an incomplete answer as a complete one.
Most people I work with are interested in promotion or career advancement. That is my experience, not a rule about everyone. Start by understanding the individual's goals. Someone may want broader responsibility; someone else may want to deepen their expertise without pursuing the same path.
For example, a manager could ask, "Looking ahead, what kinds of responsibilities would you like to explore?" This is one possible question, not a required script. Leave room for the person's own answer. Informal leadership in software engineering can be relevant when someone is interested in contributing beyond their current assignments, but it should not be imposed as everyone's goal.
Be clear about what you can support and what remains uncertain. Helping someone understand expectations is different from guaranteeing a promotion. Useful guidance should not depend on promising an outcome you cannot control.
Protect the Time While Allowing Flexibility
Weekly is my usual cadence. The appropriate balance is something the manager and employee work out together, not a universal requirement. The important distinction is between having reliable access to support and merely having a recurring invitation.
Managers should try to protect that time. Exceptions happen, and moving a meeting is not automatically a failure. If you cancel, ideally reschedule or reach a mutual understanding of the circumstances instead of allowing the conversation to disappear without explanation.
Repeated moves can signal that the meeting is not valued, even if that was not your intention. A manager's workload may explain the pressure, but it does not remove the need to support people. The pattern deserves attention rather than another assumption that next week will be easier.
Reliability also includes remembering what was discussed. If each meeting starts from scratch because previous concerns have been forgotten, an unchanged calendar will not solve the problem. Continuity comes from your attention between conversations as well as your presence during them.
Remember Commitments Without Documenting Everything
My notes are ad hoc. I use Obsidian or Supernote for my own notes, and agreed shared actions may go in the Teams chat. That describes my practice, not a recommendation to adopt particular products or a standardized system.
The purpose is to remember what matters without losing the conversation while capturing it. A brief reminder about an agreed action can be more useful than extensive notes that are never revisited. If you committed to something, you need a way to remember it that works for you.
Shared actions and private notes are not interchangeable. Not everything belongs in a shared record, especially personal information someone volunteered. Agreeing on a next step does not mean every detail of the discussion needs to be collected alongside it.
I have written about how my one-on-one approach evolved in an earlier period. That historical account is not my current notes process. The continuing lesson is to examine whether the approach serves the relationship rather than preserve it simply because you once adopted it.
Follow-through need not mean every problem was solved. It can mean:
- Reporting what you learned.
- Explaining a constraint that affects the next step.
- Acknowledging that a commitment is still outstanding.
Leaving people to guess what happened is different from being honest about an unresolved issue. That distinction matters when the answer is incomplete, not only when you have good news.
Build Connection Without Requiring Personal Disclosure
People are individuals, not interchangeable roles. Personal connection can matter, but it does not have to happen in one specific meeting or through discussion of someone's private life. You can show interest and respect without requiring a personal update.
Sharing is always optional. Trust, respect, and safety may lead someone to volunteer context, but disclosure is not evidence they are participating correctly. If someone chooses not to share, do not interpret that as a relationship problem they must fix.
Treat volunteered personal information as private. Do not turn it into a routine team update or an unnecessary shared note. Respecting that boundary is part of how you behave, not a legal guarantee of confidentiality.
Recording and AI notes are off by default in my one-on-ones. Extremely rare exceptions require both sides opting in because note capture would help them focus on the discussion. Convenience for the manager alone is not a reason to make recording routine. Nor should participation in the meeting be treated as consent to capture it.
Frequently Asked Questions
These common questions reflect the same principle: adapt the conversation while keeping support and boundaries intact.
How often should engineering managers hold one-on-one meetings?
Weekly is my usual cadence, but manager and employee should find a workable balance. Protect the agreed time while allowing exceptions. The aim is dependable support, not satisfying a universal frequency rule.
Does every one-on-one need a prepared agenda?
No. Preparation can help, and some employees prefer bringing topics or notes. A manager should not rely on everyone doing that. Bring relevant observations yourself and leave room for what matters to the person.
Are status updates a bad use of one-on-one meetings?
Not necessarily. Work can be genuinely top of mind, and discussing it can be useful. Watch for a repeated status-only pattern that crowds out support, feedback, and direction, especially when routine updates already have another suitable channel.
What if an employee has very little to say?
Do not equate quietness with disengagement. Make space, offer relevant feedback or context, and learn what works for that individual. The manager's responsibility does not disappear because the employee did not arrive with a topic.
Should employees discuss personal issues with their manager?
Only if they choose to. Personal sharing is never mandatory, and a working relationship does not require disclosure. If someone volunteers personal context, treat it as private and avoid collecting or distributing unnecessary details.
Should one-on-ones be recorded or summarized with AI?
My default is no recording or AI notes. Extremely rare mutual opt-in exceptions may help both people focus, but they are not a routine practice, a product recommendation, or a confidentiality guarantee.
A Useful Conversation Can Look Different Each Week
One-on-one meetings work best as an adaptable part of the working relationship, not a formula everyone must perform. Give the individual room, stay accountable as the manager, and pay attention to whether your conversations are still meeting real needs.
You do not need a perfect agenda or an answer to every problem. You need enough attention to understand what matters, enough clarity to establish what happens next, and enough continuity that the next conversation builds on the last.