Why Project Networks Beat Project Teams
By Jonathon Cummings and Carol Pletcher
March 23, 2011
Finding the expertise to handle complex, knowledge-intensive team projects is challenging. That’s where a project network comes in.

Projects that are nonroutine, complex and require sophisticated knowledge are a challenge to managers in organizations today. The required expertise to tackle such knowledge-intensive projects is often unexpected, complicated, subjective and distributed across the organization. Managers in organizations often assemble project teams to work on such tasks, since day-to-day work by an individual employee is less likely to achieve the desired results.
To research the factors that affect the success of teams working on knowledge-intensive projects, we studied an established companywide recognition program for project teams at a large multinational food company. As part of that study, we surveyed 1,304 members of project teams in the company to identify key characteristics that promote success in knowledge-intensive work. We then compared responses from the project teams regarding how they went about their work with the company’s assessment — through the judging of the team recognition program — on the significance of the projects’ outcome.
About the Research >>
About the Research
An established team recognition program at a large multinational food company offered us a unique opportunity to study knowledge-intensive work teams between 2004 and 2008. At any given time, the company had hundreds of project teams engaged in knowledge-intensive work. Many of these project teams submitted their achievements into the companywide recognition program. As a result of the company’s emphasis on using project teams to solve nonroutine problems, to work on complex tasks and to function in ambiguous and uncertain environments, the submissions for the recognition program provided a rich source of information on how project teams involved in knowledge-intensive work accomplish their goals. All six of the matched cases described in the article came from the recognition program.
In addition to the detailed insight gleaned from the matched-pair case studies, the 177 submissions to the team recognition program during the time period of our research provided a rich and unique opportunity to study knowledge-intensive teamwork empirically. More than 60% of the project teams had members from at least two business units, and project teams had an average lifetime of slightly more than one year from beginning to end. Each project team’s submission was classified by the