Temporary teams create repeated startup costs
In project-based work, the organisation may know everyone's grade, skills and past projects. That still does not tell a newly formed team how responsibility will be taken, who needs more context, how quickly people tend to decide or what kind of communication prevents friction.
Because project teams are repeatedly recombined, those questions are answered again and again through trial and error.
Knowledge collaboration has real boundaries
Recent research on multi-team consulting projects identifies spatial, cognitive and social boundaries that can make knowledge collaboration harder. Earlier work on projects involving both employees and external consultants also found that knowledge sharing can follow in-group and out-group patterns.
This matters because a project can contain excellent individual expertise and still struggle if people do not understand where knowledge sits, who owns what and how the group will work together.
Start each project with three layers of context
- Work context. What is the project trying to achieve, what are the major constraints and what decisions matter?
- Role context. Who owns which part of the work, and who has the final call?
- People context. What should colleagues know about how each person tends to work, communicate and make decisions?
The third layer is often the least explicit, even though it can affect the first two every day.
Do not over-standardise project teams
The point is not to force every project into the same working style. A due-diligence team, a creative strategy project and a long technical transformation may need different operating rhythms.
Instead, give the team a common way to surface the differences that matter. Then let the project choose its own agreements around decision rights, communication, review points and ownership.
Preserve context between projects
When a project ends, the team should not have to lose everything it learned about how people work. A portable professional profile can carry useful context into the next team, while the new team still needs to decide what applies in the new situation.
This is especially useful for organisations that depend on fluid staffing, project rotations and frequent collaboration across offices or disciplines.