And how has this changed from job to job or role to role for you?
For further actions, you may consider blocking this person and/or reporting abuse
And how has this changed from job to job or role to role for you?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (25)
meetings
| /
| /
| /
|/ ____ years of career
This is sad reality but it is natural.
The more you rise the ladder the less you code and more you discuss ideas/architecture/how things should work. Over the time you manage more teams that have more people involved which means more time to synchronize and get everybody on board -> more meetings.
What advice would you give someone who wants to manage their career in a direction that limits meetings — even if it means giving up on title and salary opportunities to some extent?
From the top of my head
I was pretty meeting heavy when I was in a lead engineer role, but I still managed to get 4-6 hours daily to focus on code.
Some things I did to help balance meetings with getting things done:
Way too many. I've got several roles and projects in the company I work for and I love working in each and every one of them, but sometimes the amount of meetings is overwhelming. This week will be especially rough with a whopping 21 calendar entries for tech discussions, dailies, sync meetings, tech talks, planning meetings, tactical meetings (we do Holacracy) and a pitch preparation or two. Usually it's around 10-13 meetings per week, though.
When I was a Mechanical Engineer it was solid meetings, making it hard to get work done. I moved over to software and I now have about 1 meeting per day with a lot of working sessions with my team done on the fly. I end up in a Teams call for a good 80% of my day.
Finally there are functional/technical refinement meetings (1h each, as many as needed) where a small team prepares user stories, define requirements, raise issues in spec/architecture/etc before it is planned for the next sprint.
Sometimes it feels like a lot, but if we don't have these meetings, then devs would have to figure this stuff out during a sprint and the overall delivery time would be longer. So most of them are useful planning meetings, which can be tedious, but we try to limit to 1h so everyone stays sharp.
I think it's important to define the term more clearly to get good answers.
Is every Teams/Slack/Zoom call with more then one more person a meeting? Even if the context/content is preparing/planning/pairing on a ticket?
When there are team rituals, is the length and frequency working for the goals that the ritual is trying to reach?
And last but not least, are the right people invited? Minimize "mandatory meetings" and if a whole group is invited, make it clear (over and over again) when a "relevant discussion" is only for the people that are interested.
And be brave about giving feedback to organiser(s) or even saying "No" if you think it's not relevant for you.
I think it's good to regularly think about/question those things, in a way that's a hygiene thing.
By the way, providing meeting notes for people that didn't have the chance to join makes it easier to jump on and off, or get involved when it's relevant.
3-4 meetings per week.
We try to keep content and knowledge transfer asynchronous through documentation to limit the number of meetings needed
As I am lucky and control my own diary I have gone from an average of 10 per week to an average of 2 over the last year (including zoom calls!)
I literally just say no to a meeting if it can be done via an email or a quick phone call and ask to see an agenda before attending a meeting (if there isn’t one then I will ask for one before confirming attendance).
It caused a few arguments early on while I enforced this, but now I feel like I have a better relationship with clients as I am now more available for clients queries etc. as I have so much more time.
When I was an engineer very few just usual ceremonies. Planning, retrospectives, design, kickoffs. As a product manager, unless you guard your calendar you can sign yourself up for too much. I do reverse pilots and let meetings that recur auto expire to see if its noticed. Nir Eyal has great content on managing one's schedule. It's too easy to sleepwalk your week and execute then totally whiff on strategic work.
It varies depending on what projects I'm booked on, but usually around 10-15 or so?
5 x common morning dev coffee type meeting
5 x random meeting
3 x client meetings for different projects
The common meeting is something that wouldn't have happened in the office, but working remotely it helps keep us all connected with what else is going on in the team. People I'd sit next to but not share work with for months aren't lost to the ether.
I have had much more meeting-heavy months, certainly, and at one point last year I'd say nearly half my working time was spent in one meeting or another, but these days I'm back to programming :)