How do you handle so many meetings and not enough time to do actual work?
Posted by New_Contribution_226@reddit | ExperiencedDevs | View on Reddit | 103 comments
I've been a SW lead for almost a year and I'm struggling with having so many meetings in the day and not enough time to do the actual work. I end up working in the evening to finish things up and it's annoying because it's less time to spend with my wife and young son at home.
Is this just the reality of life when you climb the corporate ladder? Sometimes I miss being a code drone where I didn't have to open my laptop after coming home from work. The pay increase for being a SW lead doesn't make up for the extra time and responsibilities in my opinion.
LuxuriousBite@reddit
Decline unnecessary meetings, delegate work, manage expectations and reality with management
CountTricky6747@reddit
how do you identify unnecessary meetings?
F1B3R0PT1C@reddit
The ones where product is crowdsourcing their job by asking the dev teams about business stuff, the third “project overview” meeting in a row for a project that hasn’t started, 99% of what HR sends out, etc
historyfirst@reddit
A meeting should have a proposed agenda in the description. If it doesn’t, ask the organizer to share one before accepting.
low_slearner@reddit
All meeting invites should make the purpose of the meeting obvious. If they don't, either query it or simply decline it if you're confident enough in your position and reputation.
Diligent-Passion9119@reddit
but isn't declining meetings sometimes seen as not being a team player?
LittleLordFuckleroy1@reddit
If you’re not actually busy with things that are genuinely higher priority, yes. That’s not the situation being described.
flamay1@reddit
Decline less valuable meetings (you know the ones), intentionally schedule higher impact meetings over existing low-value meetings and delegate “due to a scheduling conflict”. You’d be surprised how much time you can get back using this strategy.
Tyhgujgt@reddit
You have to decline some meetings since you can't be everywhere at the same time. The whole point of being senior dev is figuring out which are important
andreortigao@reddit
If your company have a shared calendar of scheduling meetings, like Teams or Google for Business, you can block the slots when you're usually the most productive to focus on your tasks.
If someone requires you to be on a meeting, they'll see you're busy at that time.
cjthomp@reddit
Oh, they’ll see it…
andreortigao@reddit
If they can't respect the time for your assigned tasks, ask them to escalate through management and change the deadline of your tasks.
Maybe it doesn't work for every company, but it sure does for most I've worked in.
deepthought-64@reddit
This!
mechkbfan@reddit
Regarding unnecessary, also determine how you fit into it
Do you need to make final decision or on the other end of spectrum, can someone just send you a summary of the meeting to keep you informed?
Tervaaja@reddit
SW lead mainly communicates and delegates. Do not do the actual work.
girlwithacompiler@reddit
I found it very scary in the beginning, but saying no to some meetings has been the best thing I did to protect my efficiency. If I really really have to attend a meeting where my presence is required but not my opinion, I put do all the housekeeping stuff then, like answering emails or random workplace trainings.
LittleLordFuckleroy1@reddit
Working evenings to make it up isn’t a sustainable option unless you’re willing to let work destroy your personal life. You can do it, and it will probably help your career, but the private costs are really hard to overstate.
You need to develop muscles around priorities and boundaries. You do not need to be in every meeting. Some meetings might be beneficial to attend, but you simply cannot do all of them and also ship. Set your hours, actually rank your priorities, and be clear that only certain things will make the cut. This is a painful process, but it gets easier with time.
This said, at some level of advancement, engineering becomes coordination and consultation. Once you get into the role of lead or beyond, your time is most valuable (most leveraged) when you’re doing things other than writing code. Delegation and influence are key skills here, and you’ll find that you don’t stop needing the prioritization muscles, you’ll just be deciding what meetings to pick over others and which topics are worth thinking about.
You can also decide you don’t want to continue taking on more responsibility. Leveling out as a senior dev is perfectly respectable and probably necessary if you want hands-on implementation being a big part of your job.
vanritchen@reddit
It's not my problem if they want to pay me to be in useless meetings.
I stop at 8h of work
sharpcoder29@reddit
As a lead, your role should be delegating and making your team more productive, not doing all the work. This needs to be communicated to your company.
ProbablyBsPlzIgnore@reddit
This is the answer. The meetings are the actual work, OP needs to delegate.
Hei2@reddit
Stop doing work on your free time. You get paid to come in during work hours and do your work during them. If your work is "sit in this meeting", then you're doing just fine. If that's interfering with your ability to deliver on time, that's a problem for your manager to find a solution to. Giving up your free time to meet unrealistic expectations is a problem of your own creation.
IGotSkills@reddit
This is easy to say. When you are in an environment where expectations are high, you won't be in your job for long if you do this
Hei2@reddit
Well, I wish you the best of luck in perpetuating this culture of burning yourself out to enrich other people.
wisconsinbrowntoen@reddit
I don't care about the productivity of my company so it's up to them to reduce meeting time if they want me to do more work
Sheldor5@reddit
they will find a way to blame it on you I guarantee it
WellHung67@reddit
If you have tasks that need to get done, you decline the meetings. If that gets you negative reviews, you tell your manager you cannot go to these meetings and get X work done. Pick what I should prioritize.
Then let them decide. You can’t lose then - if they give you a bad review at that point you gotta just leave
zurnout@reddit
They will blame you if you get less work done than your peers. If everyone is slow it looks like systemic problem. If individuals fall behind then it’s easy to assign blame and move on
Bapu_@reddit
They will always find a way to blame developers for something
So nothing changed
vitek6@reddit
They didn’t.
RelevantJackWhite@reddit
"You're not gonna like the way your perf review looks. I guarantee it."
__natty__@reddit
Oh sweet, summer child. They will tell you “you are not proactively communicating lack of time for actual work” or some other bs. So at least try a few times raise a point that certain meetings are not that important and you have other work to do.
wisconsinbrowntoen@reddit
idk it's worked for years
NotACockroach@reddit
I wouldn't last another performance cycle if I did that. Does that work where you work?
dicoxbeco@reddit
This mentality is exclusive to a single engineer. If you are a team lead like OP or above, brushing that aside is non-negotiable.
Dexterus@reddit
I care about the productivity of my company that's why it's up to them to prioritise meetings versus dev time.
Euphoric-Neon-2054@reddit
Protecting your time is a large part of being effective in corporate environments, unintuitively you actually gain a lot of respect for not making yourself always available for every piece of bullshit and instead focusing on important meetings, documenting your decisions and actually shipping work.
flamay1@reddit
There’s truth to this. Playing hard-to-get can definitely bolster your reputation over time (assuming you’re delivering value elsewhere with your time)
UnluckyTiger5675@reddit
I worked through two meetings today. Got a fair bit done.
Astec123@reddit
So we had this issue in my current team for some time where we are an internal development team for the business and customers love scope creep because there's no budget costs to them demanding more from us and the managers above me are incapable of setting boundaries.
I've used a variety of ways to manage this demand over the years, because of pushy department heads, stakeholders, customers, PMs and so on seem to always want to have 'just one more thing'. The latest itteration I've felt has been the most helpful to us as a team.
The current process I use, is what we call a 'Daily dev call' which is an all day meeting for all the developers and the lead for the team. We also include my direct line manager so they can drop in the call with the stupid questions they need someone technical to answer. It runs every single day from before our starting time until after our finishing time. It means our status is unavailable/in calls whenever we're dialled into it.
The policy I've put in place is if you need help, just want some social interaction (we're almost 100% remote), need to rubber duck, have a moan or ask questions then dial in and if the people/person you need doesn't join, just make it clear you're needing them when they're free. Likewise, if you just want a quiet space to work, we've got breakout rooms set up so you can sit somewhere and not be pulled into a pointless 'update' meeting or whatever, but if the team need you, then the people who matter can join you and ask questions at a point when it's helpful to the process.
We've tried the random booking in shorter meetings with yourself, and while it does work to give focus time, it's less helpful to the broader needs of the team because it's hard to know is this person in an actual important meeting, deep in focus or just trying to get something to work and wants to be left alone while they make sense of it. The benefits of our daily calls, is that we get the ability to pull the team together as a group or 1-2-1 on an ad-hoc basis. I make no bones about everyone having to be in the call all day or even at all, if you want to sit out of the call, you're welcome to do so and if needed we can drop you a message, the only expectation is you make yourself reasonably available as appropriate to progress our goals but everyone knows a request is not required to be immediate or receive a response acknowledging it.
It's got a running chat which helps to manage if people are nipping out to pick up sick kids and so on as we have flexible working hours. The running chat also helps for me as the lead, because I've found it can inform me details of what/when things happened, as instead of a million different meeting chats, most of the core stuff is in a single chat stream. Relevant files/links/folders for projects we're working on are all in the stream of messages rather than an unsorted mess of meeting chats, even worse if you break your team into smaller sub groups that the chats may not even be meetings as the lead you were in so seeing the chatter really helps. Also in external meetings the daily call gives us a good chat that as a team we can comment about the content of the meeting we're in without customers seeing us discuss how long we're going to say their 'simple request' is going to take and so forther.
For me as the lead, it's helped me see what the teams doing, improved communication between us all and made it so customers/PMs and so forth can't just doorstop us with calls demanding answers or information. The teams more productive as they can focus when they need to. We've found meeting requests have gone from being are you free in the next 30 minutes to 'when can we arrange a call'.
CheeseburgerLover911@reddit
code drones are not valuable anymore, unless you're really freaking amazing. engineers with ownership is where things are (imo).
How many hours a day, on average, are you in meetings? break those hours down by stuff that's directly related to your work, scrum activities, vs not.
EmberQuill@reddit
A lot of the "actual work" you talk about should be delegated to others now. I'm sorry to say it, but one of the most important things a lead does is attend meetings and make (or at least contribute to) major decisions.
Franks2000inchTV@reddit
Schedule meetings with yourself. Blocks of time to actually get work done. It'll show up as busy when people try to book you, and they'll just schedule around it.
germanheller@reddit
went solo partly because of this. at my last job i had maybe 2 hours of uninterrupted coding time per day and the rest was standups, sprint planning, retros, "quick syncs" that were never quick, and status updates that could have been a slack message.
the two things that actually helped before i left: blocking 2-3 hour chunks on the calendar as "focus time" and being ruthless about declining meetings where i wasnt needed. most meetings have 8 people and 3 of them are relevant. if the agenda doesnt mention something i own i just decline with "happy to review notes after, ping me if you need my input."
the uncomfortable truth is that senior ICs get pulled into meetings because theyre the ones who know things, and saying no feels like youre not being a team player. but if you never have time to build things you stop being the person who knows things pretty fast
ObsessiveAboutCats@reddit
Very shortly before I quit my last job, we were in a big meeting (which had been going on for hours) and our exasperated boss asked the whole team what else could possibly be done to increase productivity. Without missing a beat I said "fewer long and unnecessary meetings". He just blinked at me and changed the subject but I am still riding that high.
Dro-Darsha@reddit
As a lead, meetings is your actual work. Specifically, it is leading. But leading requires communication. Of which meetings is one form.
But it sounds like you need to manage your time better. Cancel or delegate stuff that is not worth your time. That includes meetings, but also coding tasks.
bluenautilus2@reddit
I dunno dude I just had like 6 hours of meetings and now I’m laying on the ground waiting to die
throwaway_0x90@reddit
For a Lead I think the meetings are the work.
Zulban@reddit
Create your own meetings with just yourself. I call mine "focus time". Tuesday and Thursday afternoons.
Ironically, the only person to ever push to schedule meetings within these is mostly why I made them in the first place.
Idea-Aggressive@reddit
A bit ridiculous to be a lead and lacking the communication skills and ability to say “no meeting”.
ben_bliksem@reddit
I have blocked "work time" in my calendar every day from 3pm onwards. Every morning I drag it up to the top so no bs "impromptu" meetings get booked.
Works most of the time.
But as a lead (depends on your company's definition I guess) you start coding less and offloading to the other seniors. It doesn't mean senior dev + all the extra stuff.
Special-Fee-4418@reddit
I run claude code in meeting
eronth@reddit
Legit I start telling people nothing gets done if I keep getting interrupted.
mq2thez@reddit
Don’t work after hours. Period.
Meetings are work. You’re doing valuable work related to your role.
If you also need to do software dev in addition to that, you might be overscheduled or demanding too much of yourself.
Might be worth talking to your manager to get help establishing a better balance, or finding things you can take out.
ZukowskiHardware@reddit
Ive started just skipping meetings and giving justification
originalchronoguy@reddit
multi-task. Most meetings is just keeping one ear open. Now meetings have AI transcriptions with heat maps, automated to-dos. So you dont have to even actively engage.
Fickle-Tomatillo-657@reddit
Most meetings are unnecessary just like scrum in general. Management unfortunately doesn’t agree with me 😂
likeittight_@reddit
wtf you think evenings and weekends are for? Rookie
ListenLady58@reddit
This was me during 2020-2023, nonstop meetings with the same dipshits talking to each other and not letting anyone else contribute only to get mad that nobody was contributing to the conversation lol. I started doing work on the side in those meetings and only spoke when I was called on.
martinbean@reddit
Don’t do that. Your employer pays you for so many hours. It’s up to them to ensure they’re getting what they want out of you in that time. If they’re scheduling 7 hours of meetings in your 8-hour work day, then that’s on them.
Free-Huckleberry-965@reddit
Most SWEs are salary and paid for output, not hours.
martinbean@reddit
I’m salaried. My contract also states I work 40 hours per week.
Additional_City6635@reddit
This is probably company and team culture dependent. I would be very careful about expecting other people to consider and manage your time for you
At my FAANG for example I will get bombarded by requests from random devs/PMs who need info. It's up to me to say No and point them elsewhere. They understandably don't know or care whether I happen to be busy, they're just trying to get their work done and know that I have some answers.
ScriptingInJava@reddit
Once I rose up the ranks, figuring out how and when to say no to requests for my time was as important as learning to how to play the office politics game.
Fastest way to burnout is getting drowned in requests which don’t marry up to your expected outputs, then trying to play catchup.
Learn to say no!
aruisdante@reddit
Yeah, that’s always the hardest thing about rising to “staff” rank. Helping instance one people just… isn’t really worth your time, in the sense that saying you helped 100 individual developers do 100 individual tasks is not what the company is paying you to do, and will not get you a good evaluation. That’s L5 and below work. Staff employees are supposed to be finding problems where 100 employees have the same problem, and fix it. That’s the only thing they should be actually spending time doing. They might make connections to the people that can help with the instance 1 questions, but they don’t do that work themselves.
It’s a… really hard shift for people to make, especially the kind of people that actually enjoy helping people solve problems directly. I’m definitely running into that wall in my own career trying to bridge the gap from L5 to L6 at my current company. Everyone knows the company is significantly better off for all the things I do, and if I wasn’t helping all of these people solve their problems a lot of shit wouldn’t get done. But this means that you can’t just point to a couple of major top line features with full-org level impact and say “if it weren’t for aruisdante, this wouldn’t have happened, he drove this the whole way.”
mcampo84@reddit
I got much better at my job once I started saying no to things. Turns out pretending there are more hours in a day than there actually are results in underperforming.
Gondorrah@reddit
Work overtime, heh..
dramatix01@reddit
Another user posted a potential solution in this sub recently that I think is appropriate: https://www.reddit.com/r/ExperiencedDevs/s/gvDk0pbjn0.
rexspook@reddit
As a SW lead you have to accept that coding is now a smaller portion of your job duties and learn to delegate despite wanting to do it yourself. This applies to every promotion upwards. Coding becomes a smaller portion with each promotion. That is why you often see junior and mid level engineers with many more commits than leads. The leads are delegating.
Fyren-1131@reddit
I have setup a 6h meeting on thursdays that happens every week. Manager-approved me-time.
kruvii@reddit
Explain to your manager (or whoever controls your meeting schedule) that developers need 30 minutes of uniterrupted focus just to get into deep work. Meetings need to be a block in the morning or end of day, so you can get shit done.
Onedome@reddit
I’ve been a tech lead and senior for a while even before ai. You had to work late to get your commitments done. Period. Those that didn’t, always had bad excuses and blamed their juniors until they had no one else to blame.
Good news it’s much different now. Pretty soon leads will be extinct.
FaceRekr4309@reddit
“You didn’t meet your KPIs this month. What’s your excuse?”
“I have a wife and young kids.”
“Unacceptable.”
diablo1128@reddit
I don't know what "SW Lead" entails at the company you work for, but where I have worked meetings are your job as a lead. SW Lead is leading the team and that means you need to delegate work that you personal don't have to do to the people under you. Your job is no longer hands on coding every day, it's running the team appropriately.
Working at night just means you are doing two jobs. Every SWE that gets promote to SW Lead and cannot let go of the day to day coding ultimately fails at being a lead in my experience.
tevs__@reddit
One of the perks of Lead is that there are normally more tasks than time to achieve the tasks. It's great that we never feel bored, eh?
Do you know the Eisenhower matrix? This is a thought exercise to whittle down too many tasks into a plan for the most important things.
For every task, determine whether it is important or urgent, and then work out what action you will take: * Do * Delegate * Delay * Delete
Important urgent things should be done.
Unimportant urgent things should be delegated.
Important non urgent things should be delayed
Unimportant non urgent tasks should be declined
Once you start tracking your tasks, review them at the end of the day. Do tasks should have been completed that day, if not you need to delegate more. Is not enough project work getting completed by the team? Delay more than delegate. Backlog goes to the year 2101? Start declining/deleting tasks.
I actually keep a second view on my tasks, tasks to do today, tasks to do this week. If things stay too long in a particular section, I revisit the Eisenhower decision.
Do for a team lead is a little different, you may still delegate the actual work, the do in that scenario is disrupting team members scheduled work for the unscheduled thing.
ninetofivedev@reddit
I made a post about this yesterday, but you let that plate drop.
If the meetings aren't productive, quit attending the meetings. In fact, have them send you an AI summary.
You leads who think you have to sit in every meeting to just ingest context, you no longer have to.
If you're expected to be in the meetings, then you need to delegate the work you're expected to do.
Seriously, this problem is less of a problem than it was 3-5 years ago. Never has it been easier to multi-task.
Unlucky-Durian-2336@reddit
What you mean by "not enough time to do actual work"? Lol, meetings are part of my work. If system in my workplace is expecting me to spend half of my work week on meaningless meetings, I embrace it xD It's free money for doing close to nothing.
chaoism@reddit
If you have a team you lead, try to delegate work. Your "actual work" then becomes the meetings and consolidating the information and pass it to rest of the team
But yea, some meetings can pretty much be a slack message, so this is not perfect
Ivrrn@reddit
work during the meeting
mackstann@reddit
It isn't great for your mental health or performance to be splitting attention like that. And you're likely to look foolish when you're asked a question or expected to know what to do next in the meeting.
nsxwolf@reddit
Most meetings are a waste of time though for all but 2 people in it, maybe not even 2
theclapp@reddit
I’ve been lucky enough to have mostly good managers in my career. I’d probably go to my manager, explain the situation, and ask them to help me re- or de-prioritize either certain tasks or certain meetings.
If your manager sucks, this probably won’t help, alas.
nsxwolf@reddit
You just work longer hours
Agent7619@reddit
I (and my entire team) have "No meetings Friday" as blockers on our Outlook calendars. This prevents anyone scheduling anything on Friday.
AnnoyedVelociraptor@reddit
Right. Makes sure we have enough time to deploy breaking changes.
lokaaarrr@reddit
You don’t have to attend every meeting you are invited to
brianjenkins94@reddit
Re-frame your meetings as work and then you'll end up being more defensive of your time.
obelix_dogmatix@reddit
Don’t work evenings. If you enjoy meetings, attend them. If you don’t, do what many of us do. Block hours on your calendar. There are at least 4 hours blocked on my calendar every day.
tomdaley92@reddit
It's called bullshitting. You'll get rly good at it the longer you are a corporate drone
GoodishCoder@reddit
Figure out which meetings you need to be in and which ones you can miss. As a lead you should be delegating where possible.
frankster@reddit
I blocked out the morning in my calendar. I have a regular meeting with my team just before lunch. Meetings with the rest of the company only take place in the afternoon. What it means is I get some work done in the morning as i have a few hours uninterrupted (if i ignore teams/emails), but the afternoon I get almost nothing productive done.
If my schedule was spread across the whole day (e.g. 30 minutes meeting, 30 minutes non-meeting) i'd get almost nothing done, but with a few hours in the morning I am often able to get some things done in a day.
tdifen@reddit
I say no to meetings a lot and often just ask if it can be an email instead.
DWALLA44@reddit
While some employers and subsets of coworkers are prone to scheduling too many meetings, it is also on you to manage your time and understand which meetings can be skipped or declined and which you are actually needed. It is also your responsibility to understand how much work you can realistically commit to knowing how many meetings you have, you don't commit to more work than you are capable of in any given sprint.
I agree with others, don't work your evenings to catch up on work if that's not what you want to do, but it is also a skill to learn to manage your time compared with others expectations. We can't always just blame the employer or your coworkers for these things, this is on you as well, and mostly I would add.
rmb32@reddit
You could try “Pomodoro technique”. Write down a list of what you want to get done. Set an alarm timer that fits your personal concentration span (say 8 minutes). Work solidly for that time and then set a timer for a break (say 2 minutes). When a task is done, tick it off the list and take a reward break (say 5 minutes for a coffee).
Other than that, I do agree with other comments on the push-back. A healthy company shouldn’t rely on too many meetings. Especially long ones without a break. Humans need regular breaks in order to think and regroup.
nephyxx@reddit
If you are getting your work done after hours because you have meetings all day, from your employers perspective there’s no problem.
Sometimes you have to let some balls drop on the ground for anyone to fix the problem of you having too many balls to juggle in the first place. (With proper communication to your management of course)
mango_boii@reddit
Delegate tasks to your juniors.
Keep checking for progress when you are between meetings and help out if and when they are stuck.
GeorgeSThompson@reddit
Ask your boss what the expectations are and temper your meetings/dev work accordingly. Our leads write no code and just do managment. Its impossible to do 100% on both.
If its 50/50 take half the dev work and only spend half your time on managment.
ClydePossumfoot@reddit
I decline meetings that don’t have an agenda or don’t provide any context on why I need to be there.
This includes most recurring meetings that end up just being ceremony after a few weeks. I’ll just send updates/notes async.
If all else fails I’ll make a private “busy” entry on my calendar and email the calendar invite with “have a conflict, here are my thoughts/updates” lol
Antique-Stand-4920@reddit
Part of the work of any role, but leadership roles especially is figuring out how to do things in a sustainable way. Learning and enforcing your limits becomes essential.
raddiwallah@reddit
I bring it up to my manager. Have gone to the extent of counting meeting as work in standups.
Lazy-Cloud9330@reddit
Push back. Show them what your calendar looks like and ask them how you're expected to deliver any work if they keep pulling you into meetings every 5 minutes.
RelevantJackWhite@reddit
I reject meetings if I'm not critical to them or if they lack a clear agenda that would tell me if I'm critical to them. But I also don't have that many meetings tbh. Maybe other people need more drastic measures than what I take
Consistent_Photo5064@reddit
I block 3 hours a day on my calendar, as well as full Wednesday.
If someone wants me to unblock it, I relay the decision of what’s more important to my manager.
But honestly, not perfect. Ideally people wouldn’t need endless, dumb meeting to get work done.
VladyPoopin@reddit
Decline. I’d also bring it up to your manager.