[devnexus 2026] how to run 1 on 1s for everyone

Speaker: Alex Riviere (@fimion@notacult.social)

See the DevNexus live blog table of contents for more posts


Bad One on Ones

  • How was the conference?
  • Anything you want to talk about?
  • Ok, Talk to you next month

Assumption

  • Collaborative environment
  • Small team
  • Non-hostile environment (aka if your manager is trying to get you fired)
  • Ideal situation. Ok to not want to do some of these when lower trust

Types of one on ones

  • Manager to employee (or team lead to team member)
  • Peer to peer. People you work with
  • Employee to Manager. Employee leads meeting.

Expectations

  • Both parties state their expectations for the meeting
  • What’s important to you
  • ex: open and honest about how work makes you feel, clear understanding of work responsibilities or bring up if not, bring up if work not on track
  • ex: don’t surprise me. “I’m going to talk to you about X in 5 minutes”
  • ex: I want you to help me level up
  • ex: I need brace when I mess up

Notes

  • Have notes from last meeting on one side of screen and notes from this meeting on other side.
  • Good when answers are the same from previous time.
  • If answer changes, ask for more information.

Always ask

  • Am I living up these expectations for you? Usually the answer is yes.
  • Are there any expectations you want to edit or add? Circumstances change over time.

Manager to Employee

Meets monthly for up to an hour. Sometimes take 15 minutes, but can use up to an hour. Could be every two weeks if junior/need more involvement. That one is shorter.

  • Check in on role. – Do you feel like you clearly understand your role in the business? Are you being asked to do work that doesn’t align with your role? What do you think about the company’s culture/vision/direction? Are you feeling burned out at all? What’s something you are doing a lot of today that you weren’t doing a year ago? (also can use these for annual review). Do you see any opportunities to change your role? What kind of impact do you feel you are making? Are you doing meaningful or important work?
  • Reserve a time for a specific topic or question – What’s something I do that annoys you? (ok to say nothing) What technologies are you interested in that you wish you could be using at work? What issues do you think we should be prioritizing that we aren’t currently? Team specific question: (ex How do you think our QA process could be better)
  • Set and track goal process – individual (employee wants to do) and assigned (from company) goals. Also can use for annual review as well)

Peer to Peer

He allocates 30 minutes; sometimes uses 15. Ok to be quarterly. Ensure next one scheduled before end prior one

  • Fortering relations – Do you feel like you clearly understand my role in the business? Both answer this question. Are we asking too much/little of your team
  • Retro checkin – What challenges have you faced since the last meeting? What went well since our last meeting. Cover schedule for next x days (a few days more than the meeting cadence to ensure enough notice)
  • Vibe check – Are you feeling burned out/how’s it going?
  • Track goals – Accountability buddies. Each have one goal want to achieve and check in on it

Employee to Manager

  • What is coming up in the next x months that I should be aware of?
  • Are there any tasks that you have concerns about our progress on?
  • Are there things we are doing that concern you? (could be just one person or the team). Allows answer to be “no”
  • What are things we are doing that you like?
  • Is there anything we didn’t already cover that you want to talk through?

Other notes

  • Track action items – carry forward if not done between meetings
  • Repetitive by design
  • Can add questions based on the person or level. ex: ask a junior what struggling with
  • Never cancel a one on one. Ok to move, but don’t cancel as won’t communicate effectively.

Slides: https://github.com/fimion/1-on-1s-for-everyone

My take

It feels like it would be repetitive to ask the same questions every month. But these are great ideas of things to think about and bring up!

the problem with attending team/project meetings on vacation

I was recently discussing the impact of attending team/project meetings while on vacation with someone. Seemed like a good blog post.

Vacation is supposed to be about taking a mental and physical break. This means that tangential work things (taking a video course, obtaining a cert) etc don’t fall under the scope of this blog post. Those are career related but help you and not just your current employer. Similarly, work things that aren’t related to your current team/project also don’t fall within this scope. Whether one considers Toastmasters, employe networks, a town hall to be something they do on vacation, I feel like they fall in a different impact bucket that team/project meetings. (although some of the impacts overlap)

Personal impact – not recharging

It’s harder to recharge if working during your vacation. Plus vacation belongs to you. A Fast Company article includes the phrase “as simple as answering emails or as involved as taking meetings and creating deliverables”. So taking meetings (the subject of this blog post) is one of the more impactful things. The article lists the many personal downsides of working on vacation from burnout to being more creative.

I like that they use the word “disconnect.” It’s hard to disconnect while simultaneously joining a team/project meeting!

I know some people will say they don’t care about personal impact so my blog post is mostly about impact to others.

Team impact – coverage and opportunity

If a specific person doesn’t miss a meeting, you don’t know where coverage and skill gaps exist on the rest of the team. It’s easier to have the person who knows a topic the most answer or take notes or make a decision. Vacations are the most common way to address this. The person who is going to be on vacation during a meeting knows this in advance so has the opportunity to remind others what is important and what person X would bring up. It also lets people exercise the muscle of stepping up and not replying on person X. (Sick time accomplishes the same thing but isn’t often scheduled so adds stress to the person covering)

Team impact – feedback

When Person X returns, the others who attended the meeting, brief person X. This is an opportunity for feedback. Person X learns what happened. Everyone else gets more ideas of what they might have said. Even if a “decision” was made that was flat out wrong, it can be revisited now that person X has pointing out something critical that nobody else noted. (Obviously this doesn’t apply to contract negotiation.)

Team impact – learning to not experience everything

We can’t experience everything first hand. Vacation generally involves missing some meeting we wanted to attend. For example, I will be missing my team’s next retrospective and sprint review. I would like to be at those meetings. But I also trust my teammates to tell me what I need to know. So I know it’ll be ok to miss them.

Team impact – pressure to others

When one person “volunteers” to work on his/her time off, other’s on the team feel the pressure to do so. It doesn’t matter if that is the intent. It becomes a convention that (often newer or weaker) team members feel that working on vacation is now the floor of what is acceptable. And high impact things (team/project meetings and deliverables) are the worst because they are so visible. It’s not like anyone knows if someone skims (and doesn’t reply to) email.

Team impact – expectations

Similar to pressure to others, the pressure can exist on the other side. If it is seen that person x will attend team/project meetings on vacation, other meetings may be scheduled ignoring people’s schedules because of an expectation they will attend.

What about partial vacation days?

Where I work, we are allowed to take vacation in units of 2 hours. It’s interesting how this interacts with the “time away to recharge.” The answer is surprisingly well. I do take some longer vacations. But I also take a lot of 1-2 days or partial days. For example, I take 2-4 hours off to go to “Broadway in Bryant Park” in the summer. Or I’ll work 8:30-10:30am on a Friday morning before spending the rest of the day at the pool with my friends. The key is that I’m focused on what I’m doing and have 100% forgot about work on my vacation time. So even though it is short, my fun thing is my focus, not work. Taking 6 hours off and working 2 hours to attend a meeting is planning around the meeting which has the same problems listed in the above sections.

What about mandatory consecutive leave?

I haven’t worked in a place that has consecutive leave requirements. However, I am aware that some banks require a week or two in a row. My understanding is that it is about preventing shady things from happening. It’s hard to have an unofficial process in place if someone is out that long. I’m not a fan of mandatory consecutive leave because I take a lot of shorter vacation. But not being allowed to work certainly solves this problem!

What about management?

This article is about staff positions where there is a team. It’s different for managers, CEOs, owners, etc. What’s awkward is when these people attend meetings on vacation, they make others feel like others need to as well.