this post was submitted on 20 Feb 2024
90 points (90.2% liked)
Programming
17025 readers
97 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Here's one I learned from a past manager:
Stress that everyone needs to pitch in and make themselves useful at all times, but do not share any information at all
Make sure the work is not broken down into clear tasks. Make sure nobody else has access to the stakeholders. Make people ask separately for every single account or access credential they need, and respond with incredulity that they don't already have it.
Give the impression that there are no processes. When someone submits work, criticise them for not following the process.
Each day, schedule meetings so you are impossible to contact until the early afternoon. That way you can interrupt any request for information by asking the person what work they did in the morning. The goal is to close the loop by making people scared to talk to you, so they blame themselves for not knowing anything.
Mushroom management is an amazing way to break an org. Keepem in the dark and give them shit, and no one will feel comfortable accomplishing anything.
Even better stress that things really need to get done, and why it's critical that it happens, but constantly question whether that is something THEY should be doing.