| Content Levels | |
| Register for free access to papers, case studies, and almost 50 templates. | |
| Subscribe for complete access: $14.95 monthly or $149/year | |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Abstract
The spec you're supposed to review has gone missing; there are three different versions of the project plan floating around and the remote team doesn't have any of them. Clearly, email is not enough. It's time to take the tools management process seriously.
What this is
Collaboration is central to team work—reviewing deliverables, communicating status, dealing with issues—but it doesn't come easily. This paper by Tony Christopher of Digital Places proposes that the solution to these frustrations lies not just in the tools, but in how the organization goes about implementing them, and how seriously they take the tools management process.
Why it's useful
Talk to team members from any given project long enough and the same frustrations are heard again and again: "I can't find that spec I'm supposed to review." "Where's the latest version of the project plan?" "Our remote team members aren't getting all the docs!" These cries are obvious signs that email is not enough. Valuable knowledge and needed information is too often buried in widely scattered inboxes where it can't be found, let alone transmitted for the benefit of future projects.
As an alternative, this paper outlines a five step approach toward creating a Networked Tools System that will allow organizations to truly capitalize on networked tools, instead of ending up with a robust but unused server-based repository.
How to use it
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy