Something I've noticed is that the folks who tend to over-collaborate tend to be pretty bad at coordinating workshops — they don't have a good grasp on condensing ongoing collaboration into discrete, managed, events.
Which is understandable, because running workshops can feel like you're herding cats. And even when you've had the opportunity to develop the skills for it, your company (and client) culture might not give you the (soft) authority to do the actual cat-herding; it takes active buy-in to pull off.
Agree mostly, collaboration can lead to cool insights and can be fun, but it doesn't scale. I can't collaborate with every team who's output I'm using, nor can I offer bespoke support for anyone using my work.
Collaboration for novel products is necessary and often fruitful, but over time, as requirements clear up, should be replaced by more efficient processes.
Just made that up. Think of an org as a tree and you need something from an organizational cousin, it gets escalated two levels up and delegated two levels down. Uses up a lot of a scarce and expensive resource (management time) and you're playing a game of telephone.
Buuuut nobody is miffed because their authority was questioned.
aanzeijar@reddit
Don't you just love it when agile coaches are telling you how to program?
TheOtherZech@reddit
Something I've noticed is that the folks who tend to over-collaborate tend to be pretty bad at coordinating workshops — they don't have a good grasp on condensing ongoing collaboration into discrete, managed, events.
Which is understandable, because running workshops can feel like you're herding cats. And even when you've had the opportunity to develop the skills for it, your company (and client) culture might not give you the (soft) authority to do the actual cat-herding; it takes active buy-in to pull off.
Wonderful-Wind-5736@reddit
Agree mostly, collaboration can lead to cool insights and can be fun, but it doesn't scale. I can't collaborate with every team who's output I'm using, nor can I offer bespoke support for anyone using my work.
Collaboration for novel products is necessary and often fruitful, but over time, as requirements clear up, should be replaced by more efficient processes.
malcolmbastien@reddit
Those are good points!
I think I missed talking about the dynamics of collaboration over time in the post.
If you don't mind, could you explain the "up the hierarchy, down the hierarchy working model" a bit? I haven't heard that term before.
Wonderful-Wind-5736@reddit
Just made that up. Think of an org as a tree and you need something from an organizational cousin, it gets escalated two levels up and delegated two levels down. Uses up a lot of a scarce and expensive resource (management time) and you're playing a game of telephone.
Buuuut nobody is miffed because their authority was questioned.