"Productivity" can be a frustrating term. Because there are things we have to do and things we want to do. When I supported my own code I'd "feel" like a produ

"Productivity" can be a frustrating term. Because there are things we have to do and things we want to do. When I supported my own code I'd "feel" like a productive day was when I programmed (what I wanted to do) versus support (which I has to do.) When I (finally) realized that support was part of my job, I could see that as productivity. 30 years on I'll still wake up with an idea of what I'm working on today, the get hijacked by a bug report or whatever. Come the end of the day I still haven't started my plan for the day, but nevertheless I was productive. I kinda see zoom meetings in the same way. Mostly I'm on mute, multi-tasking some other mundane thing, but just being in the meeting is 'being productive' - at least to the people scheduling the meetings. So now, if a manager asks me "what did I accomplish" I start by boasting about my meeting productivity. "I was in 14 meetings this week, for 10 hours of my time. I did ad-hoc support for 4 issues raised by other managers. I spent 3 hours this week on this project. In those 3 hours I did xxxx." One colleague of mine had 11 meetings scheduled for a day. Clearly he got a lot of work done because meetings are work... But i digress. To be more "productive" whatever that means to you, figure out what distracts you and cut back on that.