This seems orthogonal to collaboration…creating unnecessary issues or messaging people when you already have the solution isn’t collaboration. It’s just being annoying (or maybe an overbearing mandatory “process”).
> Every time you see collaboration happening, speak up and destroy it. Say “there are too many people involved. X, you are the driver, you decide.” (This is a great way to make friends btw).
How to make friends and crush collaboration
Huh? Collaboration doesn’t mean there is no leader or primary decision maker.
> Tag who you specifically want input from and what you want from them, not just throw things out there into the void.
Yeah, this is exactly collaboration.
> Prefer to give feedback after something has shipped (but before the next iteration) rather than reviewing it before it ships. Front-loading your feedback can turn it into a quasi-approval process.
Ok, sounds like they prefer feedback from collaborators after shipping rather than before. Sure. Maybe that’s better. Both are collaboration though.
> If you are a team lead, or leader of leads, who has been asked for feedback, consider being more you can just do stuff.
A team lead who helps out someone asking for help…sounds like COLLABORATION
> When it’s your thing, you are the “informed captain.” Listen to feedback, but know it’s ultimately up to you to decide what to do, not the people giving feedback.
Again, collaboration doesn’t exclude decision making. Collaboration is not majoritarianism.
IME “collaboration” as a term means specifically what the article describes and not the more general concept that you are using. So for example yes a team lead helping someone is technically collaboration but it’s not “collaboration” as the management bureaucracy would use the buzzword. How it’s used in practice is exactly as stated in the article: a way of folding in people into a project that probably shouldn’t be involved and don’t add much value
> So if collaboration is your enemy, how do you defeat it? Here’s what we say:
> Default to shipping. Pull requests > issues > Slack messages.
This seems orthogonal to collaboration…creating unnecessary issues or messaging people when you already have the solution isn’t collaboration. It’s just being annoying (or maybe an overbearing mandatory “process”).
> Every time you see collaboration happening, speak up and destroy it. Say “there are too many people involved. X, you are the driver, you decide.” (This is a great way to make friends btw). How to make friends and crush collaboration
Huh? Collaboration doesn’t mean there is no leader or primary decision maker.
> Tag who you specifically want input from and what you want from them, not just throw things out there into the void.
Yeah, this is exactly collaboration.
> Prefer to give feedback after something has shipped (but before the next iteration) rather than reviewing it before it ships. Front-loading your feedback can turn it into a quasi-approval process.
Ok, sounds like they prefer feedback from collaborators after shipping rather than before. Sure. Maybe that’s better. Both are collaboration though.
> If you are a team lead, or leader of leads, who has been asked for feedback, consider being more you can just do stuff.
A team lead who helps out someone asking for help…sounds like COLLABORATION
> When it’s your thing, you are the “informed captain.” Listen to feedback, but know it’s ultimately up to you to decide what to do, not the people giving feedback.
Again, collaboration doesn’t exclude decision making. Collaboration is not majoritarianism.