Skip to content

The one-on-one is your most important meeting as a manager. They are the focal point of your team's relationship with you, and they are your best point of leverage to enact any changes you want to make.

When we talk to managers outside of Clearbit, one of the first questions we ask is how they run one-on-ones. Surprisingly, most have no system; instead, they run ad hoc, unstructured one-on-one meetings (often with hand-wavy justifications).

In our experience, this is a mistake. A one-on-one should be prepared for and highly structured to make the most use of the time available. This might seem onerous at first, but over time you will realize that the opposite is true; the structure is freeing. It lets you get the mundane topics quickly out of the way, and then focus on more blue-sky thinking.

The purpose of a one-on-one

A one-on-one serves a few purposes:

  1. Relationship building, creating an atmosphere of trust between you and your team, where it’s clear that you care personally about them
  2. Feedback giving and receiving, so people understand how they're performing and their areas of growth. This goes for you as well - if you're not getting feedback, then elicit it!
  3. Information sharing, especially highlighting the status of immediate goals. Most of this can be pre-written (and even pre-read) to save time.
  4. Top tasks accountability, ensuring that people do what they have committed to doing by being an accountability partner (rather than a micro-manager).
  5. Career growth, talking through people's aspirations and helping them get there

Effective one-on-ones are like immune systems for companies. They’re critical for bubbling up and resolving issues that could otherwise spiral out of control. They’re also crucial in giving feedback to people so everyone is clear on how they’re performing.

Asking questions

Remember, one-on-ones aren't there for you to micromanage your team. Instead, you should be a sounding board that your team can use to bounce ideas off and come up with their own solutions. Ask questions rather than make statements. Help people come to their own conclusions; it's the only way they'll truly become independent.


β€œWhen the supervisor thinks the subordinate has said all he wants to about a subject, he should ask another question. He should try to keep the flow of thoughts coming by prompting the subordinate with queries until both feel satisfied they have gotten to the bottom of the problem.”

- Andy Grove, High Output Management

The Coaching Habit suggest six questions you can ask to help stimulate the conversation:

  1. The kick-start question: "What's on your mind?"
  2. The AWE question: "And what else?"
  3. The focus question: "What's the real challenge here for you?"
  4. The foundation question: "And what do YOU want?"
  5. The lazy question: "How can I help?"
  6. The strategic question: "If you're saying YES to this, what are you saying NO to?"
  7. The learning question: "What was most useful for you?"


When people commit to doing something, it's very important that you hold them accountable to that. Ensure that any commitment is written down in Asana with an owner and a due date to remove all disambiguation. We call these Impeccable agreements .

You are your team's accountability partner. Make it clear that broken commitments are not acceptable.

Since they are now committed to keeping all of their agreements, it's very important for them to be careful about the things they say β€œyes” to. If they agree to too many things, they will stretch themselves in a way that will result in broken agreements.

Organizing one-on-ones

The first one-on-one meeting should occur soon after the onboarding process is complete. We recommend starting with a recurring 30-minute meeting every week; you can always make it longer down the road, if required.

We recommend doing all of your one-on-ones back to back on a single day. This is efficient, requires less context switching, and allows you to spot patterns you might otherwise miss.

The maximum amount of direct reports is seven. More than that, and you’re going to spend all your time in one-on-ones.


We are using Asana to track one-on-ones. Use our Asana template to create a new project and give access to both the manager and the team member. We recommend using the naming convention Manager / Employee.

It looks like this:


The key to running an effective one-on-one is preparation. This lets you run your one-on-ones in 30 minutes, whizz through procedural work, and get to the more meaty topics (where the fun happens).

The four parts of preparing a one-on-one are:

  1. Update
  2. Issues & proposed solutions
  3. Topic
  4. Feedback

Let's talk about each of them.


Your report will pre-write an update detailing what has happened since the last one-on-one. Updates should be added as comments to the Update task. Create a commitment with your report to do this every week prior to the one-on-one. Ideally, the update should include β€œwhat went well” and β€œwhat could improve,” grouped around your report's OKRs.

  1. Track progress toward KPIs. Any KPI that’s lagging should be turned into an issue below.
  2. Bubble up any pertinent information about how your goals have gone (e.g., What new information did you gather about the customer? The product?).

Here's an sample update from our Growth team:


O1: Sprint toward Q4 revenue goal


  • HubSpot integration launch went well. Achieved 95% of target leads.
  • Dynamic Forms Webinar pushed 100 leads
  • Homepage A/B test going live today


  • We have 2-3 more weeks to drive Q4 demand. Feels like we're not on track to hit our goals.
  • Moving blog to primary domain is proving to be a PITA
  • Shipped some sloppy copy / assets in the sprint

This update will be read in silence at the beginning of the one-on-one (or even better, pre-read) so that everyone is synchronized on the state of the company. Once you get in the habit of pre-written work, you can even read updates prior to the meeting (and comment on them) to save time.

Issues and proposed solutions

Issues are typically things that are blocking your reports’ work and need your assistance or insight.

Any issues that crop up should be written up in the issue style and created as Asana tasks under the Issues section. Ideally, they also have a proposed solution that you can quickly approve. For example:



Leadership team is not putting expenses in the right category from their corporate credit cards. This is causing lots of extra admin overhead for our accounting team.

Proposed solution

Leadership team moves entirely onto Airbase (should have already received physical cards).


Topics are open-ended points of discussion that your report wants to cover. This is usually where the magic happens, where blue-sky thinking flows, and where creativity is unleashed.

Prompt your report to create topics prior to the meeting. This will encourage some prep work and time to think from both parties.

Topics should have a good description that you can quickly read to gain context, but not necessarily contain a conclusion.


Ideally, feedback should be prepared beforehand by both parties. This allows for more considered feedback rather than off-the-cuff ideas. But, even if you haven't prepared anything, still make sure you do it at the end of the one-on-one.

Feedback should be in the Like that / Wish that format.

  1. Like that… Say what you liked about the team member’s actions since the previous meeting? Be specific. During the week, actively look for actions to compliment.
  2. Wish that… What do you wish would change? Be as specific and vulnerable as possible.
  3. It's required that... behavior that needs to change/improve, otherwise the next step is Performance improvement plans (PIP).

We separated out 'wish that' feedback and critical PIP level feedback because we were finding that some people were constantly afraid there were going to be put on a PIP.

It is important to also elicit negative feedback about your or the company’s actions. Do this any way you can, be very thankful for it, and then act to resolve the stated issues quickly. This is the key to making a team member feel heard and valued.

While we have a culture of feedback, we have found it difficult to elicit feedback from reports back to their managers. When asking for feedback, be sure to leave several seconds so the other person has time to think and respond, versus feeling the urge to close the awkward silence too soon.

Read our chapter dedicated to feedback before giving or receiving any feedback: Feedback.


Run one-on-one meetings according to the following template.

  1. Kick off the meeting by asking your team member about the highlight of their week. This doesn't need to be restricted to work; anything will do. This gets everyone in a great headspace and builds on your relationship.
  2. Then read your team member's prepared update in silence. Read the entire thing before asking any questions. This update should be grouped around their OKRs for the quarter, and be split into β€œwhat went well” and β€œwhat could improve” sections around each objective.
  3. Next, go through your team member's issues (and proposed solutions). Try to keep to a few minutes for each issue and not get bogged down in minutiae. For clear asks, give an immediate response or create a follow-up task. Otherwise, we recommend helping people come to their own conclusions, which will foster a sense of healthy independence.
  4. Next, talk about topics. These are more open-ended discussions and time for blue-sky thinking.
  5. Now ask, "What are the three most important things you want to get done by this time next week?" Remember, ideally you are not telling people what to do; they should get used to figuring this out for themselves. Preferably whatever they come up with should be related to their OKRs. Jot down the three tasks in Asana, and set the owner and due date for the next one-on-one. Hold people accountable. If tasks are not completed, ask why, and then ask for a β€œhabit” so that this never happens again. This ensures that your team is working to a regular accountability cadence, and it encourages their minds to be focused on their top priorities.
  6. Lastly comes feedback. We have written a whole chapter on this (Feedback), but the key aspect is that if there is any critical feedback, there is mutual trust that it will be shared.
  7. Then high-five. This seals any commitments and leaves the meeting on a good note.
Highlight of the week2 minutes
Read prepared update (in silence)5 minutes
Questions regarding update3 minutes
Issues & proposed solutions5 minutes
Topics5 minutes
Top tasks5 minutes
Prepared feedback5 minutes
High five