- Wikis dissolve voice and authorship. Use them where there are rewards and incentives at a team level, where a team is being held accountable for a result.
- Blogs and forums preserve voice and authorship. Use them where knowing who said what is important.
- Start with frequently updated information that is also frequently accessed:
- Meeting agendas and minutes (avoiding the bottleneck of the designated note taker and/or overlapping amendments in different e-mails that then have to be reconciled),
- Early and still evolving specifications
- Project status in a dynamic environment
- Use many small team level wikis, each for a distinct project or purpose, where the team membership is clear and there are shared incentives for cooperation and success.
3 thoughts on “Use Wikis for Team Projects”
Pingback: Knowtu » links for 2010-02-23
Pingback: SKMurphy » Matt Perez on How Nearsoft Leverages Yammer
Pingback: SKMurphy, Inc. Delegation Needed For Growth - SKMurphy, Inc.