Comments on: The dark side of collaborative cultures https://gettingthingsdone.com/2017/06/the-dark-side-of-collaborative-cultures/?utm_source=rss&utm_medium=rss&utm_campaign=the-dark-side-of-collaborative-cultures David Allen's GTDĀ® Methodology Sun, 23 May 2021 23:29:05 +0000 hourly 1 https://wordpress.org/?v=6.9 By: Nida Rasheed https://gettingthingsdone.com/2017/06/the-dark-side-of-collaborative-cultures/#comment-57951 Tue, 20 Jun 2017 09:46:30 +0000 https://gettingthingsdone.com/?p=15966#comment-57951 This is a really interesting idea.

I work at Avaza, and one of the most common questions I get asked is why we don’t allow multiple users to be assigned the same task.

It’s quite simple. At the end of the day, one person has to be responsible for making sure the work is being completed. Based on project workflow, this may be multiple people over the course of time, but at any one point, you have to say – Hey Brad, you’re responsible for taking forward this work right now!

So yes, at the end of team meetings, there should be clarity on who is responsible for carrying what forward. And at the end the responsibility should fall on one person, not the whole team. Otherwise nothing gets done.

]]>