Why a Meeting Costs More than a MacBook Pro – the Business Case for Fewer Developers in Meetings
Tags: programming, career, productivity
Published: 2022-05-06 15:37:52

Developers are famous for disdaining meetings. Meetings force us to context switch, kill our flow, and sap our job satisfaction long term. Yet, managers and scrum masters can't seem to get enough of them, and the resulting tension is all over our calendars. Paul Graham (internet) famously documented this phenomenon in his essay [Maker's Schedule, Manager's schedule](http://www.paulgraham.com/makersschedule.html).

Large organizations are especially known for overstuffing developer calendars with pointless meetings – at least pointless to developers. And when a scrum master goes rogue, a dev can have days when nothing of actual value gets done between retros, sprint plannings, demos, and process alignments.

I sat through a particularly useless meeting the other week with a meeting screen full of other devs – oddly, it was initiated by a tech lead on a different team. During the boredom, I started wondering :

-   How can we make a business case for fewer pointless meetings on our calendars?
-   How can we add more value to the meetings we attend?
-   How can we have fewer meetings of the pointless kind and more of the value-added kind?

## The Opportunity Cost

I was an accountant in my previous life, so I want to put a number on exactly how much a meeting can cost. Here's my ballpark calculation of the [opportunity cost](https://en.wikipedia.org/wiki/Opportunity_cost) of a meeting for the company, regardless of whether it is pointless.

Here are my assumptions: these are US-centric, adjust for your local market conditions:

-   The meeting is _1 hour long_, involving a PM and a team of _4 developers_.
-   The developers have an average total compensation of _$200,000 and 2 Weeks of PTO._
-   On average, an employee costs an employer _1.5X their compensation_ in other benefits.
-   An average developer is in a maximally productive flow-state on average between 4-6 hours per day, we'll use _5 hours_ for our calculation.
-   The business value-added per developer is _80% from flow state_ and _20% from non-flow state_ following the [Pareto principle](https://en.wikipedia.org/wiki/Pareto_principle).
-   This is a badly scheduled meeting in an organization with too many meetings already – cutting into flow state time. Each developer on average _wastes 30 minutes before and after_ the meeting to context switch and the time is otherwise non-value adding. (See [this study](https://www.researchgate.net/publication/317989659_Impact_of_task_switching_and_work_interruptions_on_software_development_processes#pf2) for the cost of context switching).

Using these assumptions, we see that each developer's inflow state per hour costs to the company is _($200,000 * 1.5 * 0.8) / ((52-2) * 5 * 5) =_ **_$192_** per 'flow hour'.

At a cost of 2 hours in 'flow hours' per developer and 4 developers in this meeting, the meeting's developer opportunity cost is _**$1536**_. The meeting's opportunity cost is higher than the price of a brand-new [M1 MacBook Pro](https://www.apple.com/shop/buy-mac/macbook-pro/13-inch). If the meeting was pointless, might as well cancel it and fly one of the devs to Bali instead.

In my experience, corporations with the most meetings are often also stingiest with dev equipment and educational/training expenses – a classic case of penny wise and pound foolish.

![a sea turtle swimming](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/wf0ssvxh68w50y1kvzt5.jpg)

What you could be looking at instead of your PM's screen with his favorite spreadsheet.

## Value-Added Meetings

Because of my accountant tendencies – and because I used to be a freelancer – I try my best to make sure I add enough business value to every meeting to justify my presence. Politics aside, it actually makes me feel a bit bad to only sit in on one. I hate wasting my time.

Value-added can be everything from providing actual technical perspective and expertise to simply keeping everyone on track. Cutting a 15-minute detour in an 8 developer meeting is enough value added to justify attending. Of course, it's even better if you cut the meeting short when it's going nowhere, or suggest it be canceled, to begin with.

An even better way to get value from a meeting – especially for senior devs and tech leads – is to attend for the rest of the team and write a one-page summary that can be consumed at the rest of the team's leisure.

Take the meeting from the previous section: A senior dev hashed out the issue with the PM one on one and spends an extra 30 minutes post-meeting summarizing the key points learned and decisions made. The senior dev just added $1500 worth of business value in an hour and a half of work – a real force multiplier.

## Have Better Meetings

I'm by no means a meeting expert (nor do I really wish to become one), but here are some meeting tips that work well for me:

-   **Batching meetings**: When possible, reschedule meetings to right around my team's daily standup and at the end of the day when I'm ready for a mental break. I try to keep the 11 am-4 pm block of my day free. Bonus point: the best way to batch meetings is to skip them.
-   **Have an agenda**: This is meeting 101 stuff, but it is too often ignored. Have the action items and desired meeting results spelled out ahead of time, this allows you to cut them short once a decision is made. Bonus point: be the guy who says 'sounds like we finished everything on the agenda, shall we call it?'.
-   **Separate the async from the sync**_:_ You wouldn't block the main JS thread with functions that can be resolved asynchronously, so why block a synchronous meeting going over information that can be provided via email and read whenever? Bonus point: sometimes the act of writing down the context turns a meeting into an email or slack poll.

## Final Word

Skip more meetings, make a case that the shareholders aren't paying you hundreds of dollars an hour to listen – that could get through the MBA types.

Manage your meetings, and crush the ones you choose to attend. Be a force multiplier and your team will thank you for your leadership.

If you found this post helpful, please share it with others. You may also be interested in learning about [How an MR comment hierarchy can Speed Up Delivery](https://blog.shimin.io/are-code-reviews-crippling-your-delivery-process-how-categorizing-your-code-review-comments-can-speed-things-up/) or [Use 'Disagree and Commit' to get through technical disagreements](https://blog.shimin.io/afraid-your-technical-discussion-is-hurting-team-morale-heres-a-principle-to-keep-in-mind-during-technical-disagreements/).

If you have any tips for the community about better meetings, leave a comment below or ping me on Twitter [@ItsTrueInTheory](https://twitter.com/ItsTrueInTheory).