Team: Getting Things Done with Others
- Thread starter mcogilvie
- Start date
In addition to the hardcover book, I purchased the Audiobook. I like to listen to books and then review pages for relevant content. I find it aids my memory of small details. Ed Lamont is the narrator for the audiobook and his calming voice makes him a pleasure to listen to.
While the book includes a restatement of the principles of GTD, there's a lot of new information based on teams and related dynamics as well as just what has changed since GTD came out in 2001.
While the book includes a restatement of the principles of GTD, there's a lot of new information based on teams and related dynamics as well as just what has changed since GTD came out in 2001.
TesTeq
0
After reading 100 hundred pages of #TeamGTD on my Kindle I must say that it is a very good GTD book. It even contains a short refresher on GTD methodology in the appendix.
There's one metaphor that I am thinking about after reading five steps of GTD workflow for teams: let's think about a team as a person – one more member of a team. Or a "soul of a team" if a team as a member of a team sounds too recursive…
Just as each member of a team, a team itself has to maintain its own GTD system with lists and workflows.
What do you think about this metaphor? @DavidAllen @Ed Lamont @John Forrister @Eric Mack @mcogilvie
There's one metaphor that I am thinking about after reading five steps of GTD workflow for teams: let's think about a team as a person – one more member of a team. Or a "soul of a team" if a team as a member of a team sounds too recursive…
Just as each member of a team, a team itself has to maintain its own GTD system with lists and workflows.
What do you think about this metaphor? @DavidAllen @Ed Lamont @John Forrister @Eric Mack @mcogilvie
gtdstudente
Registered
Last edited:
schmeggahead
Registered
I have the kindle and audible versions. Kindle doesn't recognize audible narration. I have it working on another book but the Team book doesn't seem to recognize it.
I see a slew of issues with Kindle narration and did a number of those solutions which fixed it for other books.
Wondering if these books are setup for that.
Clayton.
Tools are only as reliable as they are.
I see a slew of issues with Kindle narration and did a number of those solutions which fixed it for other books.
Wondering if these books are setup for that.
Clayton.
Tools are only as reliable as they are.
TesTeq
0
@gtdstudente It is suggested that each team member should do her/his weekly review before the team's weekly review meeting. On the other hand it is not mandatory that each team member's personal system has to be strictly GTD compliant. The requirement is: everybody should know all her/his commitments and has full personal situational awareness
gtdstudente
Registered
I like your "soul of a team" illustration. In the end, it is about accountability, so as TEAM explains, if you become aware that there is an action or responsibility that falls on a team (say, HR) then the next logical question is WHO (representing our team, HR) has that action to complete (On behalf of the team). At least that is the way I see it so far.
Ger80C
Registered
Still reading, but constant "gold nuggets" being found on a lot of pages.
I highly recommend this to everyone who is interested in GTD:
Keep in mind that a "team" is a very loose and broad definition so dont be shy if you do not work in a big organization with many "teams" - if you have clients, customers, an assistant, or a family - you have teams in your life.
I highly recommend this to everyone who is interested in GTD:
Keep in mind that a "team" is a very loose and broad definition so dont be shy if you do not work in a big organization with many "teams" - if you have clients, customers, an assistant, or a family - you have teams in your life.
Yes! More than one person aligned to an outcome and you have a team. Of course, gaining that alignment is one of the challenges of working with teams, one which David and Ed address in their chapters on Vision and NPM, respectively.
TesTeq
0
@Ger80C @Eric Mack I love this symmetry and simplicity:
- Project = two or more actions to achieve a successful outcome
- Team = two or more people dealing with a situation or a project
TesTeq
0
I've published my TeamGTD book review (in Polish): https://biznesbezstresu.pl/2024/05/27/teamgtd-pierwsza-recenzja-najnowszej-ksiazki-davida-allena/
I like the book! It's insightful and clear. Appendixes (about GTD, groupware and hybrid/remote work) are great.
The only minor problem appears on page 249 of the Kindle edition ("Why delegate?"). I don't understand the math. It is written that: "Given that the total team [of 100 persons] would double its productivity if each member only did 1 percent more than they are currently doing (…)".
I think these percents don't add. If every member increases its productivity by 1% the whole team increases its total productivity by 1% too. Not by 100%. If every team member produces 101 pages in May while she or he produced 100 pages in April, the whole team of 100 persons increases its output from 10 000 to 10 100 pages, not to 20 000.
I like the book! It's insightful and clear. Appendixes (about GTD, groupware and hybrid/remote work) are great.
The only minor problem appears on page 249 of the Kindle edition ("Why delegate?"). I don't understand the math. It is written that: "Given that the total team [of 100 persons] would double its productivity if each member only did 1 percent more than they are currently doing (…)".
I think these percents don't add. If every member increases its productivity by 1% the whole team increases its total productivity by 1% too. Not by 100%. If every team member produces 101 pages in May while she or he produced 100 pages in April, the whole team of 100 persons increases its output from 10 000 to 10 100 pages, not to 20 000.
David Parker
GTD Connect
Even though the only team I’m in is the family, I'm already finding insights and parallels in this new book that I can take advantage of and learn from. It is providing a new perspective on GTD and another proof of its underlying ubiquitousness.
