this post was submitted on 24 Aug 2023
391 points (98.0% liked)
Asklemmy
43945 readers
786 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My company started prioritizing developer time by heavily discouraging meetings with devs before noon, and one day a week is supposed to be meeting free. We also just don't respond to pings before noon now unless it's an absolute emergency. Took managers a bit to catch on, but my efficiency has honestly skyrocketed and I'm loving it.
Yeah we do no-meeting Thursdays.
Problem is when SLT decides they want a demo of progress and see all this "free time" called focus time on our calendars and stick a 30m meeting about 1 hr before lunch.
Mark it as busy in the calendar, that might keep them away. If marking the whole day is suspicious, make 1-2 hour marks with 10-20 minute gaps (or longer as long as it doesn't allow sticking a meeting in). Then make these "appointments" weekly and set the subjects(focus time) to private.