Smash Company Splash Image

December 24th, 2017

In Business


One-on-one meetings are underrated, whereas group meetings waste time

(written by lawrence krubner, however indented passages are often quotes). You can contact lawrence at:

I have had good results with a style of management where I mostly have one-on-one meetings. These meetings can be just 15 minutes, or maybe 30 if there is a serious issue that needs to be discussed. If I’m leading a small team (less than 20 people) I’ll have meetings with each person at least once a week, but with key players more often than that.

During a one-on-one meeting, I can ask tough questions, and the person I’m talking to can offer a long answer, without fear of boring the rest of the team, since the rest of the team is not there to be bored. And the person can speak without being interrupted by some third person. They can offer negative opinions about their co-workers, without worrying that their co-worker will find out and retaliate. They can also offer positive opinions about their co-workers, without the too obvious incentive of their co-worker hearing their praise.

If a person is running late on a project, the best way to find out the reason is to have a one-on-one meeting with them. They are free to incriminate themselves, in ways that I find useful. For instance, they might put all the blame on someone else. After the meeting I will investigate their accusations and discover the truth. Is the other person to blame? If I conclude that the other person is not to blame, then I know I have a person on my team who both runs late and dishonestly blames other people for their problems. Where possible, I will remove such people from my team. But what if it turns out they were right, that this other person is really the cause of all of the problems? In that case, I’ve learned something important, and I’ve learned it because of the freedom to speak that people have when they are alone with me. If I’d called a group meeting, and that other person was in the room, it’s unlikely that anyone would have told me the truth. Instead I would have heard some vague excuses.

What if someone finishes a project much faster than I expected, or with much higher quality than I was expecting? I definitely want to talk to that person alone, one-on-one. I want to ask them some very specific questions, so I can get a sense of how much more work I can give them. I also want to hear their ideas about what we should do next. I also want to know if they got help from someone else, and do they enjoy working with that other person, and should I henceforth assign tasks to them together? If someone on my team reliably impresses me, then I’ll want to get an accurate idea of how much more work or responsibilities I can give them. And these kinds of detailed conversations can only happen in one-on-one situations. It would be awkward to try to have these conversations while other people are in the room.

You might be thinking, “What is wrong with group meetings? I love group meetings. I get to talk to everyone at once, which is much more efficient than talking to each person one at a time.”

If you feel that way, I should warn you, I’m about to attack your deeply held beliefs. Get ready.

I once had a client who insisted that the marketing team should meet with the tech team once a week, to collaborate on the creation of marketing copy that would be informed by those who understood the technology. This is good in theory, but less people would have been more productive. As it was, during the typical meeting we had 15 people in the room, most of whom were bored. The conversation was typically dominated by the 3 most opinionated marketing people. Imagine this going on for 20 straight minutes:

AMY: Consumers are saturated with advertisements. The only way to break through is to connect with them at an emotional level. That’s why we need to consider long-form advertising. We need to tell stories that…

HENRY: No, no, no! Nobody has time to read a story! If you write more than 10 words then you’ve failed. We need a slogan that is memorable, something we can use in every ad, something that…

AMY: Studies show that people don’t remember facts, they remember emotions, we need to connect with those emotions, that is why we need to consider…

HENRY: Great, so we come up with 10 words that pack an emotional wallop, but we don’t write a damn novel, nobody has time to read anymore, nobody…

AMY: I read a novel a week, sometimes two — some people crave stories and look for stories and we should give them ads that they actually enjoy and want to share with their…

SUSAN: People don’t want stories so much as they want authentic, we really need to forge a connection with them that feels authentic; if we indulge in some silly fiction that’s just going to…

HENRY: If we find the right 10 words, it will resonate with them as authentic, that’s our job, to find the 10 words that feel authentic! What do you think we are doing…

AMY: Authenticity is not a pack of Ramen noodles, we can’t create it in 10 minutes, it’s something that takes time and…

So who is right, and who is wrong? You’ll need to figure this out, but you don’t need to do so while 12 other people are in the room. If you are the manager who is overseeing this, it is up to you to get people back to work.

Among marketers, the debate over facts versus emotions versus slogans versus stories will go on forever. 50 years from now they will still debating the right strategy. You need to make a decision. You might hold a brief meeting with both Amy and Henry to be sure you understand their points of view, but don’t let yourself get sucked in. Sometimes you can wait till a consensus emerges, but often you can not and should not wait that long. Pick a strategy, and go with it. Don’t hold meetings where unrelated people are forced to listen to people who like to pontificate.

Have you ever been in a group meeting where half the room was not participating? Of course you have! That’s the norm for group meetings! I’ve had many clients where I was dragged into such meetings several times a week. I could look around the room and I saw many people who were obviously daydreaming. They were bored. None of the information being discussed was relevant to their work. More so, they had nothing to contribute, or, worst of all, they were not allowed to contribute!

Why do such meetings happen? There are 2 main reasons:

1. the manager is lazy and undisciplined and so invites everyone rather than thinking hard about who they actually need to speak to

2. the manager is an egotist who likes to force people to listen to the manager’s words

The lazy and undisciplined manager can improve their style of management by thinking hard about who they really need to talk to about a particular subject. They can then pursue one-on-one meetings with those people. The lazy and undisciplined manager finds it easier to simply order everyone to show up, and then they figure out who they actually need to hear from while the meeting is going on. This is efficient for the manager, but inefficient for everyone else, and therefore inefficient for the firm.

Some managers are egotists. Just like me, they can look around the table and see who is daydreaming. I’ve known many managers who feel that if an employee daydreams, then the employee is to blame for inattentiveness. But I would flip that. If you need to be sure that a specific worker understands a specific task, then have a one-on-one meeting with them. If you are disbursing general information to the whole team, send an email. If you frequently monopolize the attention of employees who don’t truly need to hear what you are saying, then you have bad managerial habits — the good news is that you now know what you need to do to become a better manager.

Ego is the enemy of productivity. A group meeting is fertile ground for ego. Often the top manager is to blame, but not always. Sometimes it is the people you’ve invited. You only need two egotists with strong opinions and suddenly your meeting is derailed with a 30 minute argument about a new fad theory regarding marketing/technology/consumers/sales. I’ve seen debates go on for as much as an hour, with most of the room clearly restless and disaffected. A bad manager allows these debates to continue. A good manager is smart enough to end these debates early. A great manager doesn’t allow such debates to exist, because they don’t hold the kinds of meetings where this behavior is possible.

If I ever need to announce something to a large group, I can send an email to everyone. I don’t need to get them altogether in a room. Even if I thought gathering people together was the best strategy, how would I handle the fact that on any particular day I might have key workers who are sick, or taking care of a sick child, or working remotely? How do you handle that? Do you send them an email? Have a one-on-one meeting with them later? If so, why not make that your primary strategy? Email for announcements, and one-on-one meetings for serious information exchange, has the advantage that, as a strategy, it scales well. It’s the best strategy when you have a team of 5, and also when you have a team of 5,000. (Obviously you don’t have one-on-one meetings with each of the 5,000 people, but you have one-on-one meetings with the managers who oversee the teams formed from those 5,000 people.) More communication can and should be done by email or chat — we are lucky enough to enjoy an abundance of options nowadays, and we should take advantage of them.

Once in awhile you have to coordinate activity between people. In these cases, you can allow yourself a meeting where three people attend (you and two other people). You can then act as referee while they figure out how to work with each other. But if you need to do this often, it might indicate that one of them is being obstructionist. Ideally, you can delegate much of the work of getting them to work together. If you can’t delegate that work, think about why that is. Which of those two people seems unwilling to accept the responsibility that you are trying to delegate?

What happens when two groups of people need to work together? Shouldn’t you get the two groups together, so they can all talk to each other? No! This is never productive. If you try this, most of the people in the meeting will be bored. They will be daydreaming, while two or three people work through the real details. So if two groups need to work together, the right approach is to get one person from each group, and have a meeting of yourself and those two people. Once they’ve worked out the details, you can delegate to them the responsibility of explaining the new plan to the groups they came from. And, again, if they can not be trusted with this responsibility, then you need to have a long talk with whoever is being obstructionist. And if they continue to be obstructionist, even after you spoken to them several times. then you need to get rid of them.

Is there a good use for group meetings? Yes! Group meetings are useful for brainstorming sessions. Peter Drucker touches upon this in 1985 book, Innovation and Entrepreneurship. Especially as a company becomes larger, there is a risk of ossifying into rigid habits. Drucker emphasizes that it must become a regular discipline to get together the best engineers, sales people, product people, managers, and have them brainstorm about how to take advantage of the possibilities that they see in front of them. A brain storming session is a rare situation where you want everyone in the room to talk, and you want as much diversity of opinion as possible. But I have rarely been invited to a group meeting where the goal was to brainstorm. In the overwhelming majority of cases when I’ve been invited to a group meeting, the focus has been on operations and execution, and this is where group meetings are terrible.

A brainstorming session needs to be focused on generating ideas. Be wary if the conversation drifts to some seemingly urgent short-term subject. I recently worked for a client where the top leaders invited each other to every meeting, and every meeting had a bit of brainstorming, but also some conversation about operations, budgets, and execution. Most of the time, this mixing of subjects suggests a lack of discipline on the part of the leaders. In the short term, you won’t notice any penalty for this style of leadership. But 2 years later, you will be asking “Why haven’t we made any progress during the last 2 years?” and the problem will be the undisciplined way that every meeting covers all subjects and ideas.

A final word about one-on-one meetings. Food is important. Getting away from the office is important. There is the old joke that French managers don’t have meetings, instead they have dinner. American managers would be wise to import this habit. I’ve seen the occasional sales team go out for drinks, and sometimes when the tech or marketing team works late, they later go out to celebrate. All of that is great. And socializing away from work is a rare case when having a whole group together can be a healthy thing, because it is a situation where efficiency is not the goal. But as a manager, one-on-one socializing has advantages. Think about the legitimate(*) reasons you might invite an employee to lunch — perhaps you are considering them for a big promotion and you need to get to know them better to be certain they are ready for the new responsibilities. Or you want someone’s opinion about someone else who you are considering for promotion, and you hope that a meal will create the ambiance that encourages them to speak freely. Whatever the reason, all the arguments in favor of one-on-one meetings still apply.

(* As we were reminded all through 2017, there are plenty of illegitimate reasons why a manager might invite an employee to a one-on-one lunch or dinner. As soon as a manager does such a thing, they become the enemy of the long-term health of their firm, and I can only hope they are soon fired.)

[ [ UPDATE ] ]

Interesting conversation on Hacker News about this.

[ [ UPDATE 2018-04-03 ] ]

Vlad Brown has translated this to Russian:

Встречи «один на один» недооцениваются, а групповые встречи тратят время


Check out my book:


December 4, 2018 9:22 am

From lawrence on Docker is the dangerous gamble which we will regret

"GK, thank you for writing, but I don't understand what you mean when you write: "However, at that point you..."

December 4, 2018 7:14 am

From GK on Docker is the dangerous gamble which we will regret

"A development VM is a fine choice, provided that it comes with tools that make it just as easy to run commands..."

November 30, 2018 7:04 pm

From lawrence on Docker is the dangerous gamble which we will regret

"GK, thank you for writing. About this part: "That thing is writing portable shell scripts. The moment you n..."

November 30, 2018 1:41 pm

From GK on Docker is the dangerous gamble which we will regret

"The fat binaries article was nice, but full blown fat binaries are not really necessary. Whats needed is that ..."

November 27, 2018 1:13 am

From lawrence on Object Oriented Programming is an expensive disaster which must end

"Andres Moreno, thank you for writing. Among other points to be said, I'll say I'm almost heart broken about Py..."

November 26, 2018 9:11 pm

From Andres Moreno on Object Oriented Programming is an expensive disaster which must end

"I am stunned! Why did it take so long to show that the Emperor has no clothes? I got bit by the Lisp bug early..."

November 23, 2018 8:24 am

From Just An Observer on Hillary Clinton keeps making the same mistakes

"Similar to the "Let's dump Nancy Pelosi, since the Republicans don't like her" talk we hear all the time...."

November 22, 2018 11:49 pm

From Free Speech Message Board on Zed Shaw is angry (abstraction and indirection)

"Americans used to think hippies were lazy fruits for dropping out during the Vietnam War, but maybe the hippie..."

November 19, 2018 5:13 pm

From Justin McGuire on To start with, tran­sient query surges are no longer a prob­lem?

"I think the idea is that a surge in traffic results in more messages on the queue, which can be handled at a n..."

November 19, 2018 12:45 pm

From J on Docker is the dangerous gamble which we will regret

"What are everyone's recommendations for fat binary bare metal deployments preferably with hooks into continuou..."

November 19, 2018 11:07 am

From lawrence on Has the Internet destroyed our ability to read?

"Gábor Hidvégi, I agree with "too many pieces of information" especially small pieces of information. Most of t..."

November 19, 2018 10:50 am

From Gábor Hidvégi on Has the Internet destroyed our ability to read?

"The problem is that too many pieces of information reaches us (thanks mostly to the internet), and our brain a..."

November 19, 2018 10:19 am

From Gábor Hidvégi on What's wrong with Hacker News

"I think the problem is broader: web 2.0 failed. One part of Web 2.0 was about "user content", everyone is c..."

November 12, 2018 9:44 pm

From Roberto on Poland was shockingly liberal during the 1400s

"Also check out Laurentius Goslicius:ła_Goślicki Richard Cal..."

November 7, 2018 6:04 pm

From Henry Longmore on Why not use asserts in Python?

"Thanks for the article. I used to mock Eiffel for its "Design By Contract" as that seemed to be the only good ..."


Pingback: New top story on Hacker News: One-on-one meetings are underrated, whereas group meetings waste time – ÇlusterAssets Inc.,

December 25, 2017
2:11 pm

By Mark Steb

I STRONGLY DISAGREE WITH THIS MANAGEMENT STYLE. You should not use one to one meetings to play the blame game. You should spend those meetings listening, not figuring out who you want to blame for failure.

December 25, 2017
2:16 pm

By lawrence

Mark, thank you for writing. I thought I was clear about the scenario that I was describing, which is when a project is running late. As a manager, those above will hold me responsible for the project running late. There is no question about the fact that I have to take 100% of the blame when a project runs late. It is my fault. But I also need to fix the situation. And that means figuring out what went wrong. And that often means figuring out who failed to get some work done. Sometimes our estimates were wrong. Other times someone didn’t work hard enough. Other times someone else actively sabotaged the project. Whatever the problem is, it is my responsibility to figure it out. And if someone specific played a negative role, it is my job to educate them. If I’ve had to educate them many times, and they don’t seem to be adjusting their behavior, then I need to get rid of them.

December 28, 2017
4:23 am

By Ian

And who are you to educate them? How do can you find yourself the power to decide if someone in your team is behaving correctly or incorrectly?

What you are doing is pouring your ego over your team and create a sense of terror and backstabbing ambien which is a contradicting practice to make people work.

Stop bossing around and get to work with your team and spend less time trying to feed your ego.

December 28, 2017
11:00 am

By lawrence

Ian, thank you for writing. You ask “And who are you to educate them?” Presumably that is my job, if I have been appointed as manager? If I am the leader of the tech team, then I need to educate people on the tech team.

Perhaps I should spell out how many times I’m willing to try to educate someone, before I decide to fire them. I cover this in my book How To Destroy A Tech Startup In Three Easy Steps:

We had someone on staff who I tried to educate during May, June and July of 2015. By the time August came around, I was ready to fire them. There must be some limit on how many times a person can fail a team and yet still be kept as part of the team.

As I say in the book, the situation is very different in those companies that have a formal apprenticeship program. If the difficult individual had been in an apprenticeship program, and I was his teacher, then the responsibility for his success would be on my shoulders. In that case, I might work with him for a year, and if he did not learn what he needed to learn, at least part of the blame would rest with me. But outside of apprenticeship programs, I think stricter limits should apply, at least in the USA.

December 29, 2017
12:29 pm

By Will Pemble

Your recount of a marketing meeting is a great example of circular conversation. Busy people rarely have time for this. As a leader, you clearly want to achieve a particular result. Here is where the art and science of delegation is crucial. Getting it right means you can trust your team to achieve the results you need, without having to check up, follow up, micromanage.
Will Pemble

December 30, 2017
8:25 pm

By lawrence

Will Pemble, I agree. The key issue is delegation. To be productive at the personal level, we must learn to delegate. For the whole company to be productive, everyone in the company who has an important skill needs to learn to delegate what work they can, so they can spend most of their time using the skill they have that no one else has.

Pingback: Professional Development – 2017 – Week 52 – Geoff Mazeroff

January 1, 2018
12:14 pm

By Sergei

This is too much witch hunt. If you have a one on one just so you can figure out who to blame for a problem then you are not focused on progress. You waste too much time on blame. A good manager supports their team.

January 3, 2018
4:52 am

By Rodrigo Dias

I agree with management through O3 (I’ve written about it here, but I still see the value in group meetings. Group meetings bring you something that O3 never achieve, which is the sense of belonging. I you’re building a culture, creating moments where everyone is together is really important. I’ve experienced that a well managed group meeting can be a really powerful way to align everyone towards a goal. Sending an email can be more efficient, however doesn’t create the same commitment.

January 3, 2018
5:50 pm

By lawrence

Rodrigo Dias, thank you for writing. I should have emphasized the bit about the French going to dinner. I agree that it is sometimes necessary to get a group together to build a culture of solidarity. But I’d rather do that away from the office. In the office, we should be careful not to waste people’s time by dragging them into meetings that they don’t need to be part of. What is efficient for the manager is not always efficient for the business, especially if the manager demands the presence of several people, so the manager can be effective with their own time, but is wasting the time of everyone else.

January 5, 2018
4:49 pm

By lawrence

Also worth reading is this article which reminds me how many terrible managers there are. If you run a large company, you should remember that many of your managers are probably in need of further training:


But an astounding number of managers report that the hardest part about talking to employees is talking to them at all.

In 2016, a survey of more than 2,000 US adults (paywall) asked managers what they found most difficult about communicating with employees. Some 37% of managers said they found it hard to give negative feedback to workers about their performance, 20% said they struggled to share their own vulnerability, and another 20% disliked being the messenger for company policies.

But a full 69% of respondents said that they found “communicating in general” to be the hardest part about communicating with employees.

That’s alarming, because one of the primary things employees say they need to feel engaged and productive at work is regular, meaningful communication with their managers. The percentage of US managers who say they don’t like talking with employees mirrors the 67% of US workers who say they’re not engaged at work. That figure comes from the most recent Gallup survey of the US workplace, the company’s annual in-depth report on more than 31 million workers across US industries.

January 7, 2018
5:14 pm

By lawrence

I had another thought about this.

I think many businesses tend to promote extroverts, on the assumption that they have great social skills, and therefore will make great managers. But that is false reasoning.

This is probably especially true in the USA, which already has a culture that rewards extroverts. Sales culture has had a big impact on American business culture, so we end up in the strange situation of sales culture having an influence in all the departments that have nothing to do with sales.

An extrovert might love the attention they get from telling a story, but a craving for attention doesn’t make a person a great manager.

More so, a person might be an extrovert because they have no capacity for internal dialogue, so they must be talking to someone else simply to hear their own thoughts. But a lack of internal self-reflection is actually a serious flaw in a manager.

Likewise, a person might be an extrovert because they love to entertain people, but that doesn’t mean they will be able to handle the hard tasks of managing, especially when it is necessary to confront people for bad behavior or poor performance.

All the same, an extrovert will probably be talented at entertaining their superior, and therefore their superior is more likely to promote them. Thus so many businesses end up in the strange situation of having a great many extrovert managers who don’t really know how to manage.

January 7, 2018
8:12 pm

By lawrence

A good article here:

If great managers seem scarce, it’s because the talent required to be one is rare. Gallup finds that great managers have the following talents:

They motivate every single employee to take action and engage them with a compelling mission and vision.

They have the assertiveness to drive outcomes and the ability to overcome adversity and resistance.

They create a culture of clear accountability.

They build relationships that create trust, open dialogue, and full transparency.

They make decisions that are based on productivity, not politics.

January 11, 2018
8:51 am

By Karthik Raghunathan

the great kathy sierra has covered one aspect of this in one of her posts :

Pingback: Why Group Meetings Can Be Time Wasters with Lawrence Krubner - Simple Leadership

Pingback: Newsletter 65 – Losing Earth | import digest

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>