[vantassell]

Reminds me a lot of Cal Newport's ideas re: Slow Productivity. He talks a lot about how Context shifts are death for knowledge work and that a lot of offices operate via a "hyper active hive mind" that doesn't allow or value deep work.

[jen729w]

I find a timer useful for this. If you use Timery, you get a live activity on your home screen.

I don't care how long a thing takes, and I don't retrospectively analyse the time. The point is that I can only have one timer running: and that's the thing that I'm supposed to be doing.

If I notice I'm doing something else, it serves to bring me back to the task.

And at the end of the day, I do look through the list and see how often the thing I was doing changed. I try to keep that to a minimum, because every change is a context switch.

I've only been doing this for about a week, I'm still working on it, but so far it's been more helpful than not.

[al_borland]

I have too many meetings to get anything done. I'll go weeks, or months, without actually doing anything of real value. Eventually it comes to a head and I need to get things done to avoid going crazy. I go on do-not-disturb in our chat app, quit Outlook completely, and turn on a focus mode on my cell phone so people can't even call me. I'll end up working for 8-15 hours straight with no real breaks. I go to the bathroom, but keep my head in the problem, that's about it. I completely forget to eat or do anything else. I get 2 months worth of work done in 1 day.

If meetings were eliminated (or just consolidated into a single planning week), and I cloud just do deep work, I think I could work 2 days per month and be more productive than I am currently working 40+ hours per week.

I always want to send my management graphs like this to show them why having 10 projects running at a time is a bad idea...

https://res.cloudinary.com/jlengstorf/image/upload/f_auto,q_...

...but I know it will be received poorly.

The image in the article (here, since the link was broken: https://fev.al/img/2024/focus.png) is something I've sent to a boss in the past. He didn't get it.

[Flimm]

I feel for you, friend. Maybe you could share the essay "Maker's Schedule, Manager's Schedule" by Paul Graham [0]. It's been somewhat helpful when I've shared it with colleagues.

[0] https://www.paulgraham.com/makersschedule.html

[al_borland]

Thanks for sharing. I agree with everything in the essay.

When it talked about the person effectively working 2 days, once on the managers schedule, and once at night to code on the makers scheduled, I thought back and that resonated with me. I spent a decade or so doing something like that. I’d typically work 12-14 hour days. The normal work day was full of distractions and interruption, and once everyone started to leave and the meetings stopped, I started making stuff and got a lot done. At the time I thought I was just avoiding rush hour traffic, but there was a much bigger side effect in terms of productivity.

With the situation I had in 2017, this essay may have gone a long way. With my current situation I worry sharing it would have a negative impact on my job. It’s not one person I’d have to convince and coordinate with, it’s at least 4, probably more. I have 3 “stand ups” most days, which are all 30 minutes and often run long. If I were to split my day into 2 maker blocks, my mornings are shot every single day with 2-4 hours of meetings. This is usually enough to kill my whole day. 3-4 days per week usually have a meeting (or 3) in the afternoon, which kills that block as well. Some teams have office hours posted to everyone. While I rarely go, simply having them on my calendar has an impact to my ability to see that my day is clear. And of course there are all the chats I need to monitor and respond to, which never stop and might as well be meetings.

A massive culture shift is needed and I don’t feel like I’m in a position to make it. We are getting a new CIO soon, so I can hope for some positive impact there. Right now all bets are off. In the current culture, if something isn’t getting done fast enough, the go-to solution is a daily meeting to talk about it. It makes the project managers feel good and gives the appearance we’re doing all we can, but in reality it slows everything way down.

I will keep the essay in my back pocket to share if the opportunity presents itself.

[rendall]

Goodness gracious. It sounds like having you be ineffective might be advantageous to one or more people above you. Perhaps they get to blame you for their own ineffectiveness, offsetting pressures elsewhere. It truly sounds toxic. I'm sorry you're going through that.