How to Design Meetings That Get Things Done
Meetings were once an act of sabotage. Insights from Rebecca Hinds and her book “Your best meeting ever”
When I welcomed Rebecca Hinds onto The Workplace Podcast to discuss her book Your Best Meeting Ever: 7 Principles for Designing Meetings That Get Things Done, I knew we were about to explore a topic that affects every organisation, every team, and nearly every employee. Meetings are one of those things that sit at the centre of working life, yet they are rarely treated with the seriousness they deserve. We often complain about them, joke about them, endure them, and fill our calendars with them, but we do not often stop to ask the deeper question: what are meetings actually for, and why do so many of them fail to move work forward?
That was what made this conversation with Rebecca so valuable. It was grounded in research, practical in application, and refreshingly honest about just how dysfunctional meetings have become in many organisations. As I said during our conversation, I was struck not only by the quality of Rebecca’s research but by how practical and useful her book is. It tackles a subject many people dread, but it does so in a way that is engaging, actionable, and deeply relevant to the modern workplace.
Very early in our conversation, I told Rebecca just how much I admired the book. I said, “who knew, you could write such a practical and interesting book on this dreaded subject sometimes of meetings.” That line captures the challenge perfectly. Meetings are often seen as inevitable, ordinary, and beyond repair. Rebecca makes a very different case. She shows that meetings are not just routine calendar entries. They are one of the most important products an organisation creates, and if we designed them with more intention, discipline, and clarity, they could become a major source of performance rather than frustration.
Meetings were once sabotage. Now they are business as usual.
One of the most memorable parts of Rebecca’s book, and one of the first things we discussed on the podcast, was the extraordinary story she uses to open it. Rebecca describes the Simple Sabotage Field Manual, written in the World War II era by the Office of Strategic Services, the precursor to the CIA. This manual advised ordinary citizens living in enemy territory on how to inject inefficiency and disruption into enemy systems.
What is so striking is that many of the sabotage tactics now read like normal organisational life.
As Rebecca explained, “the meetings around deploying meetings as weapons of sabotage, dragging things out, using channels, you know, injecting bureaucracy. These are our most effective ways to derail the enemy, and yet now we deploy them as business as usual.”
That is both funny and alarming. It is funny because it is recognisable. It is alarming because it reveals how normalised dysfunction has become. The very behaviours once identified as deliberate sabotage are now woven into the daily fabric of organisational work. Endless meetings. Too many attendees. Bureaucratic detours. Status updates that go nowhere. Poorly designed follow-ups. Overuse of synchronous time. If that is not sabotage, it certainly feels like it.
Rebecca’s observation invites a more courageous conversation in organisations. If poor meetings once served as a tactic to derail performance, then we should stop treating bad meetings as a minor inconvenience. They are not harmless. They sap energy, fragment attention, delay decisions, create frustration, and often deepen confusion instead of resolving it.
The scale of the problem is impossible to ignore
We also discussed how dramatically the volume of meetings has increased over time. I mentioned that in the 1960s, executives spent fewer than 10 hours a week in meetings, whereas now that figure is more than double, at 23 hours per week. Rebecca clarified that these numbers apply particularly to executives, but the trend is clear: meeting time has risen sharply.
What is more concerning is that this increase in volume has not been matched by an increase in quality. Quite the opposite. Rebecca pointed out that not only are meetings more common, they have become even more dysfunctional, especially since the pandemic.
That matches what I have seen in organisations. On the podcast, I shared an example from my own work. Around 15 years ago, I was working with a senior management team that was burnt out, under strain, and increasingly prone to conflict.
As I tried to understand what was going wrong, one issue kept surfacing: meetings. When I finally asked how many hours they were spending in meetings, the answer was staggering. Thirty-three hours a week. On top of that, they were working 70-hour weeks. It was no surprise that burnout, conflict, and poor decisions were emerging. Their calendar was not supporting work. It was swallowing it.
This is why Rebecca’s work matters. Meetings are not peripheral to organisational life. They shape it. They influence energy, productivity, attention, trust, decision-making, and morale. If meetings are poorly designed, the rest of the organisation pays the price.
We are not teaching people how to run meetings
One of the points I feel strongly about, and one Rebecca agreed with, is that meeting management competency should be a prerequisite for promotion. We promote people into managerial and leadership positions, and then expect them to run meetings well with little or no training. In many organisations, training on meetings is either absent or badly outdated.
Rebecca was very clear on this point. “No, we’re not,” she said when I asked whether organisations are really developing people to run meetings effectively. She went on to explain that meeting management is too often seen as remedial, as though it is such a basic skill that anyone should be able to do it. But that assumption is false. A meeting is not simply getting people together to talk. A good meeting is designed with purpose, structure, and clarity. It requires judgment. It requires discipline. It requires facilitation. And increasingly, it requires a level of collaboration skill that organisations are still undervaluing.
I found Rebecca’s framing especially useful here. She said that meetings should be treated like products. That is a powerful idea. We would not launch a product without thinking carefully about its purpose, design, users, value, and outcomes. Yet many organisations continue to schedule meetings with little more thought than a calendar click. As Rebecca put it, meetings “shouldn’t be neglected, like overstuffed drawers.”
That image stays with me. Because many calendars do look like overstuffed drawers: cluttered, inherited, rarely reviewed, and filled with things no longer serving a clear purpose.
The case for a meeting reset
One of the most practical ideas Rebecca shared was what she calls a “meeting doomsday,” a 48-hour calendar cleanse where employees delete recurring meetings and rebuild from scratch. This approach was inspired in part by what happened at Dropbox, where recurring meetings were wiped from calendars and employees had to intentionally add back what was truly necessary.
Rebecca told me that the deeper value of this is not just the time savings, though those can be significant. In one case, employees saved 11 hours per person per month. The real value is the reset in mindset. It gives people permission to question inherited assumptions and ask, perhaps for the first time in years, whether a meeting actually deserves to exist.
That word permission is important. In many organisations, people know that the calendar is bloated. They know meetings are being overused. They know some meetings are no longer useful. But there is a social and emotional barrier to changing anything. Rebecca captured this brilliantly when she spoke about the guilt associated with cancelling meetings. A meeting is not just a time slot. It often feels like a relationship, an expectation, or a signal of inclusion. Cancelling it can feel personal.
That is why interventions matter. They give people a reason and a structure for doing what they already know should happen.
Interestingly, Rebecca noted that the biggest time savings in these interventions often do not come from deleting meetings altogether. They come from redesigning them. An hour becomes 50 minutes. A 30-minute meeting becomes 25. Eight people become four. Weekly becomes monthly. That is such a useful reminder. Improvement does not always come through elimination. Sometimes it comes through more thoughtful design.
Declining meetings without guilt
This leads naturally to another issue many people struggle with: how to say no to a meeting. Rebecca’s guidance here was simple but important. She emphasised the value of scripts, not as robotic responses but as practical supports that help people push back respectfully and constructively.
She spoke about how meetings are “very human activities,” and because they involve synchronous presence and belonging, people often feel guilty declining them. We can start to feel that we are not just rejecting the meeting, but somehow rejecting the person who invited us.
That is why pre-written scripts can help. They lower the emotional barrier. They give people language such as: can we try this over email instead? Or: I’ve noticed we don’t get to the key business results during this meeting; what if we tried this instead?
What I like about this is that it shifts the conversation from compliance to contribution. Instead of passively accepting every invitation, employees can begin to evaluate whether their presence is genuinely needed and whether the meeting is the right format. That is a more adult, more intentional, and more collaborative culture.
Calling out a bad meeting takes courage and skill
Another powerful theme in our conversation was what to do when you are in a bad meeting, especially if you are not the most senior person in the room. Rebecca drew on Amy Edmondson’s advice here: lead with curiosity.
Rather than accusing or criticising, a less powerful person can say something like: I’ve noticed we spend half the meeting on status updates and don’t get to the real discussion.
What could we do differently?
This is a subtle but important move. It names the problem without escalating it. It invites reflection rather than defensiveness. It supports change without threatening status. Rebecca explained that in organisations with strong psychological safety, people can be more direct. In less safe environments, curiosity is often the wiser path.
I really liked her point that the best result is when the meeting organiser comes to feel that the improvement idea is their own. That is smart, practical organisational influence. It is not about winning the point. It is about making the meeting better.
On the podcast, I connected this to a coaching approach: name the problem and pair it with a solution. If meetings regularly run over time, perhaps the agenda needs tightening. Perhaps a timekeeper role is needed. Perhaps some content should move out of the meeting entirely. The point is to move from complaint to design.
The 4D CEO test: a practical filter for deciding whether a meeting is needed
One of the most useful tools Rebecca shared is the 4D CEO test for deciding whether something deserves to become a meeting.
A meeting should only happen if its purpose is to debate, decide, discuss, or develop. That is the first filter.
Then it should also pass the CEO test. The content should be complex, emotionally intense, or a one-way door decision.
This is an elegant framework because it forces discipline. Too many meetings exist because nobody asks the most basic question: why does this require synchronous discussion? Rebecca explained that complexity matters because when ambiguity is high and there are many unknowns, real-time interaction is often the best way to work through them. Emotional intensity matters because persuasion, empathy, body language, and human nuance are hard to handle well through purely asynchronous communication. The “one-way door” idea, borrowed from Amazon, matters because some decisions are so consequential that the cost of misalignment is too high to leave to loose, fragmented communication.
What I find especially helpful is Rebecca’s reminder that most decisions are actually two-way doors. They are reversible. That means they do not always warrant a meeting. This is a challenge to the organisational habit of gathering people live for every issue, regardless of stakes, complexity, or emotional nuance.
Coordination neglect and the hidden cost of poor collaboration
One of the concepts from Rebecca’s book that I found particularly insightful was coordination neglect. She described it as the natural human bias to underestimate how much coordination is actually required to move work forward.
That feels deeply true. People tend to think first about their own individual tasks, not the system-level coordination needed to connect the work across functions, roles, and time zones. Rebecca made the point that this is becoming even more significant in the age of AI, where people can increase their own personal productivity in ways that may actually create more noise, more duplication, and more inefficiency for the wider team.
Her example of the notetaker bot was especially striking. One person sends a bot to a meeting to save time. Then everyone does it. Soon the meeting is full of bots and distractions, while genuine human engagement declines. Individual productivity may look improved on paper, but collective productivity suffers.
This is where I believe Resolution Intelligence is highly relevant. On the podcast I mentioned that I am a co-creator of Resolution Intelligence, which helps people navigate conflict in the workplace through the orientations of people, process, and progress. In that framework, the collaborator sits in the process piece. That matters enormously for meetings. Good meetings do not happen by accident. They require people who can work the process well, create clarity, hold the structure, and help others engage productively.
Rebecca’s emphasis on facilitation connects strongly to that. She made the point that meetings need ownership. Someone must be responsible for the success of the meeting. In some cases, that means a dedicated facilitator. In other cases, technology may increasingly help. But the principle remains the same: without clear facilitation, meetings drift. Voices dominate. Agenda discipline slips. Time expands. Accountability diffuses.
From a Resolution Intelligence perspective, the facilitator and the collaborator are not optional extras. They are essential roles for keeping people aligned around process so that progress becomes possible.
Clear asks versus lazy asks
Rebecca also shared a brilliant practical distinction between a clear ask and a lazy ask. This came from work she had seen in an organisation where collaboration health formed part of performance reviews.
I found this especially important because it reinforces the idea that collaboration should be assessed and valued. Rebecca noted that desk workers or knowledge workers now spend 90% to 95% of their time collaborating post-pandemic. Yet many organisations still do not formally evaluate how well people collaborate.
A lazy ask is vague, context-free, and burdensome for the recipient. A clear ask is specific, time-bound, and rooted in context. It explains what is needed, by when, and why it matters. This becomes even more important when teams work across different time zones or rely on asynchronous collaboration.
Again, this is where meetings often become a crutch. People schedule a meeting because they have not done the thinking required to make a clear ask in writing. Rebecca’s point is that better collaboration often starts before the meeting. It starts with clearer communication, stronger context, and more intentional use of tools.
The role of asynchronous communication
A major theme running through our conversation was that organisations often use meetings to compensate for weak asynchronous systems. Rebecca was clear that this is not just about having the right tools. It is also about the norms around them.
Slack, email, and similar tools can be used asynchronously, but in many workplaces they are not. Instead, they become engines of rapid response, interruption, and anxiety. Rebecca highlighted the importance of being clear not only about which tool should be used for what purpose, but also about response expectations. Is the desired response time a minute, an hour, or a day? Are we using shared channels or direct messages? Are our requests clear?
This matters because strong asynchronous cultures create alternatives to unnecessary meetings. And when those alternatives are missing, the calendar fills up.
Rebecca also mentioned Loom-style videos as an effective alternative for one-way information sharing. That is another helpful challenge to organisational habit. Just because information is important does not mean it needs to be delivered live in a meeting. If something is primarily informational, it may be better delivered asynchronously, where people can watch in their own time, at their own speed, and revisit key sections.
Why lateness, multitasking, and oversized meetings damage trust
We also spoke about some of the everyday behaviours that people find deeply frustrating in meetings: lateness, multitasking, and too many attendees.
Rebecca’s point on lateness was especially clear. Even being a few minutes late changes the emotional tone of a meeting. People start to feel resentment because lateness symbolises, regardless of intention, that one person’s time matters more than everyone else’s.
She explained that lateness usually has one of two causes. Either people are overbooked and physically cannot get from one meeting to another on time, or they do not believe the meeting is important enough to prioritise punctuality. In both cases, the meeting design or the wider system needs attention.
Multitasking is similarly revealing. Rebecca noted how common it is for people to double-book themselves, text during meetings, or work on a second screen. In many cases, this is not just bad behaviour. It is feedback. It signals that the meeting is not engaging, relevant, or necessary for that person. And if that is true, perhaps they should not be in the meeting at all.
That links directly to another important idea Rebecca shared: keeping meetings small. Once you get beyond seven or eight participants, social loafing begins to kick in. People feel less accountable because there are so many others present. As Rebecca put it, the goal is to ensure that everyone is a stakeholder, not a spectator.
That is such a useful line for leaders. A good meeting is not a theatre audience. It is a place where the right people are present for a clear purpose, with defined roles and an expectation of contribution.
Stand-up meetings and the power of simple design choices
I also loved Rebecca’s discussion of stand-up meetings. At first glance it sounds almost too simple, but the research is fascinating. Standing meetings tend to run shorter, sometimes up to 25% shorter, because people do not want to prolong discomfort. But Rebecca also highlighted another effect: when people are standing, they become less territorial. The space feels more shared. The discussion becomes more collective.
That is a brilliant example of what I might call meeting design with behavioural intelligence. Sometimes small changes in physical setup can meaningfully change how people interact. It is not always about adding complexity. Sometimes it is about stripping meetings back and creating conditions that support brevity, shared ownership, and focus.
Social lubrication matters more than many leaders realise
One of the most valuable parts of our conversation was Rebecca’s point about social lubrication and what she called the “high school cafeteria effect.” In hybrid and remote organisations especially, social connection has declined, and loneliness at work is at an all-time high.
Rebecca was clear that this is not a soft issue. It is essential to trust, collaboration, and performance. People do their best work when they feel connected to a team. In remote and hybrid contexts, that means building relationships that go beyond narrow task interactions. Shared interests, informal bonds, and cross-functional encounters all matter.
She also made a strong point about silos. Innovation suffers when teams only interact with people just like themselves. Engineering stays with engineering. HR stays with HR. IT stays with IT. Yet creative work and innovation often emerge when different viewpoints collide.
That is why small interventions, like pairing people from different departments in taxi rides to off-sites, can matter. They are not random extras. They are part of designing healthier collaboration networks inside organisations.
Better one-to-ones create better careers
We finished by touching on one-to-ones with managers, an area that is so often overlooked. Rebecca shared a powerful practice from Jade Bonacolta: bring three wins from the past week, three priorities for the next week, where you are showing leadership, and one new idea for the team.
I thought this was brilliant because it makes the one-to-one far more intentional. It helps employees document contribution, think strategically, and show initiative. Rebecca pointed out that sharing three wins gives managers useful material for performance reviews. Sharing priorities shows forward thinking. Bringing one new idea signals creative contribution beyond the day-to-day.
That is a simple framework, but a very strong one. It turns the one-to-one into a conversation about impact, leadership, and growth rather than just a loose check-in.
Final reflections
My conversation with Rebecca Hinds reinforced something I have believed for a long time: the quality of meetings is not a trivial issue. It is a leadership issue. It is a collaboration issue. It is a culture issue. And increasingly, it is a wellbeing issue too.
What Rebecca offers is not just a critique of bad meetings, but a practical path towards better ones. She reminds us to raise the bar on what deserves to be a meeting. She challenges us to treat meetings like products, not calendar clutter. She gives us tools like the 4D CEO test, the distinction between clear asks and lazy asks, the value of facilitation, the need for stronger asynchronous systems, and the importance of designing for contribution rather than attendance.
For me, there were also strong links to Resolution Intelligence. Better meetings require attention to people, process, and progress. They require collaborators who strengthen the process, facilitators who guide the conversation, and leaders who understand that clarity reduces friction. They require the courage to call out dysfunction, the wisdom to redesign inherited habits, and the discipline to create structures that genuinely move work forward.
As Rebecca said, meetings are “the most important product in our organization.” That line alone should cause leaders to pause. If that is true, and I believe it is, then meetings deserve far more care, skill, and intentionality than they currently receive in many workplaces.
I thoroughly enjoyed this conversation with Rebecca, and I strongly encourage readers to explore her book Your Best Meeting Ever. There is far more in it than we could cover in one episode, and it offers practical ideas that organisations can start applying immediately.
If this conversation resonates with you, I would encourage you to listen to The Workplace Podcast episode featuring Rebecca Hinds and to continue supporting the podcast by listening, commenting, and sharing it on social media so that we can keep bringing more global experts and practical workplace insights to a wider audience. If this topic is relevant for your team or organisation, you can also contact william@yellowwood.ie to book me, William Corless, for a workshop on this topic. Connect with me on LinkedIn
Listen to podcast here:

