Back to Blog & Insights

Networking

Give a New Collaboration a Charter You Will Revisit

A short working charter can expose assumptions before a cross-company project starts. Its real value comes when partners revisit it using evidence from the work.

By WWA Editorial Team 4 min read
Two cross-company partners reviewing a working charter beside plans for a trade-show installation

A cross-company project can look aligned while its partners are quietly operating from different assumptions. One team expects rapid approvals; the other protects time for technical review. Each believes the other owns a critical decision. By the time the mismatch becomes visible, missed handoffs and frustrated messages have already started shaping the relationship.

A short working charter can surface those assumptions before work begins. It should not be a ceremonial statement about collaboration or a substitute for project planning. It is an operating agreement: why the group exists, who is responsible for what, how decisions move, when people respond and what happens when disagreement threatens progress.

Settle the operating questions early

Begin with purpose. Describe the specific result the partners are creating and the boundaries of the assignment. Then connect each role to an identifiable responsibility. Naming one company as the “creative lead” is not enough if nobody knows whether that authority includes budget changes, technical substitutions or client-facing approvals. The charter should identify who recommends, who decides, who executes and who must be consulted for recurring categories of work.

Decision rules deserve equal attention. Partners can define which choices require joint approval, which belong to one role and how they will handle a decision that cannot wait. Response norms should cover channels as well as timing: where urgent issues go, where final decisions are recorded and what silence means. Conflict handling can remain simple, but it should name the first conversation, the people involved and the point at which an issue is escalated.

Research supports treating the charter as an aid to interaction rather than a promise of performance. An Academy of Management Learning & Education study of 1,891 global virtual teams found that charters improved early process measures but did not directly improve final output quality. Research in the Journal of Applied Psychology also linked charter quality with task cohesion among 239 self-managing project teams, while finding that its performance contribution depended on team conditions.

Write for the project you actually have

Consider a clearly illustrative collaboration between an event producer and a fabrication partner building a trade-show installation. Before design development starts, they agree that the producer owns the client brief, presentation schedule and final client communication. The fabricator owns structural methods, material feasibility and shop sequencing. Changes affecting appearance go to the producer; changes affecting safe, feasible construction go to the fabricator; cost or schedule changes require both.

Their charter also states that routine questions belong in a shared project channel, approvals must be recorded in the project file and urgent production issues receive a direct call. If the partners disagree, the responsible leads meet first with the drawings, constraints and decision deadline. If they cannot resolve the issue, each company appoints one senior decision-maker. These terms turn vague expectations into observable working behavior.

Schedule revision before strain appears

The partners should book a mid-project charter review when they create the document. Waiting until conflict erupts makes revision feel like a verdict on someone’s performance. A scheduled review frames it as normal project maintenance. That approach is consistent with research in Small Group Research, which reported that mid-project charter revision supported by feedback and coaching improved commitment, satisfaction and individual effectiveness compared with a one-time charter.

The review should use evidence from the work. Repeated approval delays may show that decision rights are too broad or that the wrong person is approving. Questions appearing in several channels may indicate that communication norms are unclear. Rework can expose a missing handoff. Decisions repeatedly escalated beyond the named leads may reveal that their authority is insufficient. A changed client request, compressed schedule or newly discovered production constraint can also make the original agreement obsolete.

Revise only what the evidence challenges. Clarify an owner, narrow an approval category, change a response path or add a missing escalation point. Keep the charter short enough to consult during real work, and record the revised terms where both partners can find them. The goal is not to predict every complication. It is to give collaborators a shared operating model, then improve that model once the project shows how the partnership actually behaves.

Sources