Cross-Organizational Collaboration and Partnerships, Explained

UPI Study › Courses › Project Management › Free lessons › Lesson 11.2 Free with a free account

Cross-Organizational Collaboration and Partnerships

Project Management · Chapter 11: Team Dynamics and Conflict ResolutionSection 11.2 · lesson 68 of 7315 min · free with a free account

← Defining Goals and Objectives for Project TeamsNext lesson: Stages of Team Development and Group Behavior →

Earn 3 college credits for Project ManagementRecommended for credit by NCCRS · Business 230 · self-paced · one payment, lifetime access
Enroll in Project Management · $250 →Download the syllabus (PDF)

In this lesson

Structure, govern and manage projects that span several separate organizations.

  • Compare contractor-client, consortium, joint venture and alliance structures
  • Explain how trust is built and weigh formal control against trust-based openness
  • Design shared governance with a steering group, shared objectives, escalation path and decision rights
  • Apply interface management tools to hand-offs between organizations

Free study notes

Get this lesson's notes by email

The key points and 4 practice questions with answers, in your inbox. One email, free.

One email. Unsubscribe in one click.

Transcript

Everything said in the video, section by section (2,049 words). Read along, or search it.

Opening Question

A Vibration Fault Mentioned Off the Record

On an informal call, Leila mentions something she hasn't reported in writing. The first air-handling unit failed its factory test, with a vibration fault. A retest will probably push delivery later. So why hasn't her company said so formally? And what should the client's project manager do about it? Leila is technical lead at Orrin Air, a made-up supplier. Its units are going into a new clinic on Harbor Street. Three organizations share the job: the clinic's owner, the builder, and Orrin. Three sets of managers, and one opening date.

Why Partner

What Crossing a Boundary Adds

The client's project manager is Dana, at Meridian Clinic Network. Halvard Build, another made-up firm, is the contractor, and Orrin supplies Halvard. Projects cross organizational boundaries for plain reasons. One organization lacks the specialist knowledge, the spare capacity, or a site or permission that another holds. Or it wants to share the risk of a large undertaking. A partner organization contributes work, money, knowledge, or access, while staying a separate organization. Crossing the boundary adds three things to the job. First, authority no longer runs in one line. Dana can't instruct Orrin's staff; they have their own managers. She gets cooperation by agreement, explanation, and credibility. Second, information travels through channels nobody built for this project, so it can arrive late, or filtered. Third, each partner measures success differently. Orrin counts units delivered. Meridian counts the day the clinic opens.

Collaboration Structures

Contractor, Consortium, Joint Venture and Alliance

The form of the partnership matters. A collaboration structure sets who controls the work, who carries the risk, and who answers to whom. Contractor and client: the client sets requirements and approves results, and the contractor controls how the work is done. Accountability runs one way, contractor to client. Its weakness: interests diverge, so each side protects its position, and bad news may be hidden, or turned into claims. Consortium: several organizations deliver together, each separate and responsible for its own portion, with a lead member facing the client. Its weakness: gaps and overlaps between portions, and little leverage over a member that's failing. Joint venture: two or more owners create a new, jointly owned entity, and share control, gains and losses in proportion to their stakes. Its weakness: each director also answers to a parent organization. Two loyalties can pull apart, and decisions slow when owners disagree. Alliance: partners commit to shared objectives under joint governance and open information, often with linked gains and losses, without necessarily forming a new entity. Its weakness: it depends on trust, and without discipline it can blur who's accountable. Real arrangements mix these features, and their legal form is a matter for lawyers. The pattern: the more control and risk are shared, the more the project rests on the relationship. Harbor Street is a contractor and client arrangement, with Orrin supplying the contractor. Even so, the three must work as partners.

Building Trust

Four Behaviors That Build Trust

Between separate organizations, nobody can watch everything. So trust decides how much checking is needed, and whether problems get reported honestly. Trust is the willingness to rely on another party's commitments, in situations where you can't check or control what they do. It's built by four observable behaviors, not by a feeling. Transparency: sharing information that affects the other party, including a slipping date, or a failed test. Keeping commitments: doing what was promised, when it was promised. And when that proves impossible, saying so before the date, not after. Early and frequent contact, so that the first call about a problem isn't also the first call. And fair handling of mistakes: find the cause, and agree a proportionate remedy, with no disguised blame. Then reporting a mistake never costs more than hiding it. Trust builds slowly, through many small observations. One concealed problem that surfaces later damages it fast, because it casts doubt on everything reported before.

Control Versus Trust

Why the Supplier Stayed Quiet

Now Dana learns why Leila stayed quiet. Earlier, when Orrin reported a small slip, Tomas, Meridian's facilities engineer, called a formal review, and demanded daily written reports. Orrin's managers drew a lesson: reporting early is costly. Tomas had his reasons too. A previous contractor had hidden a problem until the last week. So Dana faces a real trade-off. Formal control means detailed written reporting, approval gates, and rights to inspect. It doesn't rest on anyone's goodwill, it creates evidence if a dispute follows, and it makes concealment unlikely. Trust-based openness means lighter reporting, and relying on partners to raise problems early. Heavy checking signals suspicion, and teaches partners to disclose only what can be verified. Which approach brings earlier, more accurate reports in a given setting is an empirical question. How much unreported risk a client should accept depends on the stakes, and on values.

Middle Course

Joint Recovery Before Formal Review

Dana takes a middle course, and she calls it a trade-off, not a solution. Milestone reporting stays in the contract. But she asks the steering group to adopt a rule: a problem reported at first knowledge triggers joint recovery planning first. A formal review is kept for problems that joint recovery doesn't solve. And she sets up a weekly call between the named contacts for each interface. The cost is real. She gives up some independent checking, and if the slip grows, the client's sponsor may see her as soft. Her reasoning: a slip known early can be absorbed in the plan, and a slip hidden until delivery can't. She records the decision, for review at the next checkpoint.

Shared Governance

Steering Group, Shared Objectives, Escalation Path

Governance is how authority is assigned, decisions are made, and performance is overseen. Shared governance means the partners hold that authority jointly. Three parts make it work. First, a joint steering group: senior people from each partner, chosen for their authority to commit their organizations. Omar, Meridian's operations director, sits on it, beside a Halvard director. They set direction, approve major changes, and settle what the teams can't. Second, shared objectives: a small set of outcomes every partner has agreed to, owned by no single one. Without them, each organization optimizes its own result, like a supplier's delivery date at the expense of the clinic's opening date. Third, an escalation path: the agreed levels an unresolved issue climbs. First the interface contacts. Then a joint review by the project managers. Then the steering group, whose decision is final. Escalation isn't failure. It's how a problem reaches someone with the authority to resolve it. A true dispute, where positions are incompatible, needs a conflict process instead.

Decision Rights

One Decider for Every Decision Type

Next, decision rights. For each type of decision, they name who recommends, who decides, and who must be consulted. The recommender studies the question and proposes an answer, usually because it holds the facts. The decider has the authority to choose. A consulted party is asked before the decision, and advises, but doesn't decide. Writing this down matters, because nobody can assume another organization's manager will defer. Harbor Street's table has exactly one decider per row. Any change to the shared objectives or the opening date goes to the steering group. A design change within the agreed scope: Dana decides, on Halvard's recommendation, after consulting Orrin if its equipment is involved. The order of site work: Halvard's project manager decides, because Halvard carries the risk of its own method. And stopping work for a safety concern: Halvard's site manager decides at once, and tells Meridian afterward. Waiting for a meeting would defeat the purpose. Two deciders on a row produce delay, and none produces drift. The method: classify the decision first, then read across its row.

Quick Check

A Roof Unit Move That Delays Opening

Quick check. Orrin proposes moving one unit to a different spot on the roof. It stays within the agreed scope. But the move would push the clinic's opening back by a week. Who decides? Pause, and decide. The steering group. Once the opening date would move, the decision changes type, and only the steering group can decide it. Without the date change, it would be a design change within scope, and Dana would decide. And it was never site sequencing, so Halvard's project manager doesn't own it.

Interface Management

Contacts, Hand-Offs, Documents and Logs

Failures between organizations cluster at interfaces: points where work, information, or responsibility passes from one organization to another. Each side assumes the other has the matter in hand. Interface management controls those points with four tools. Named contacts: one person per organization for each interface, with a named deputy for absences. They answer the question: who do I call? A defined hand-off: a written statement of what passes, in what condition, by when, to whom, and how receipt is confirmed. Shared documents: one controlled version both sides use, like a drawing register, or a list of open decisions. And an interface issue log: every problem at an interface, with its owner, date raised, status, and next step. Nothing is lost between meetings, and repeat problems show up.

Quick Check

Drawings Sent but Never Received

Quick check. Halvard says it sent the final ceiling drawings to Orrin on Monday. Orrin says nothing arrived, and both are certain. Which interface tool would have prevented the argument? Pause, and decide. A defined hand-off. It names what passes, to whom, and by when, and how receipt is confirmed. Monday's drawings would be confirmed, or chased, the same day. Named contacts tell you who to call, and an issue log records the problem once it exists. Neither confirms that the drawings arrived.

Shared Risk and Reward

Linking Partners' Gains and Losses

Some partnerships also tie money to the shared outcome. A shared risk and reward arrangement links the partners' gains and losses. All benefit when the project goes well, and all carry part of the cost when it doesn't. Its purpose is aligned interests. When a problem is a shared loss, partners solve it together, instead of arguing over whose fault it was. A sound one agrees what counts as success, and how it's measured, by methods all can inspect. It agrees how the outcome is divided, and who rules on disputed measurements. It has limits. A measure that's easy to count can be met without the real benefit, and an arrangement that seems to punish disclosure teaches concealment. And it can't replace trust, governance, or interface management. It only adds a motive to use them. The specific terms are a matter for lawyers.

Culture and Practice

When Complete Means Different Things

Then there's culture: an organization's shared habits about how work is done, how decisions are made, and what may be said to whom. Working practices are its routine methods, formats, tools, and calendars. Differences are normal, and harmless, until they're discovered by accident. Orrin calls a drawing complete when it's ready for comment. Meridian calls it complete when it's approved. Each follows its own practice faithfully. So the partners write a working agreement early: how they'll communicate, meet, share documents, record decisions, and raise problems. It extends ground rules across organizations. To surface differences, ask about practice directly. Hold a kickoff where each side explains how it reviews, approves, and reports, and try a small joint task while stakes are low. Some writers rate cultures on fixed dimensions. Supporters value the shared vocabulary; critics say individuals vary too much within any group. Asking about actual practice works either way.

Partnership Checkpoints

Reviewing Relationship Health by Phase

Finally, the partnership needs check-ups of its own. A partnership checkpoint reviews the relationship's health: trust, governance, decision rights, and interfaces, as well as cost and schedule. At initiation, ask: can we state shared objectives, and does the structure match the control and risk each partner will carry? At planning, ask: could anyone say, for each type of decision, who recommends, who decides, and who is consulted? During execution, ask: is bad news arriving early, and does the log show the same interface failing again? At closure, record the state of the relationship, because the same organizations may well work together again.

Case Resolved

Changing What an Early Report Costs

Back to Leila's vibration fault. Her company stayed quiet because an early report had once been answered with a formal review. Dana didn't demand more reports. She changed what an early report costs, and accepted less independent checking in return. Was that right? It depends on the stakes. A manager who weighed the old contractor's concealment more heavily could reasonably have tightened control instead.

Key Takeaways

Structure, Trust, Governance and Interfaces

To recap: the collaboration structure sets who controls the work, who carries the risk, and who answers to whom. Trust is built by transparency, kept commitments, early contact, and fair handling of mistakes. Shared governance needs a steering group, shared objectives, and an escalation path. And every decision needs exactly one decider, while every interface needs contacts, hand-offs, shared documents, and a log.

About Project Management at UPI Study

Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Business courses Every course with PRO →

Why take it here

Why students take Project Management with UPI Study

How projects are planned, run and closedProject Management teaches how to deliver work on time and on budget: scope, schedules, the critical path, budgets and earned value, risk, contracts, monitoring and closing a project, and leading the team. It is a common course in business, management and engineering degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Cross-Organizational Collaboration and Partnerships

What is the difference between a joint venture and a consortium?
In a joint venture, two or more owners create a new, jointly owned entity and share control, gains and losses in proportion to their stakes. In a consortium, several organizations stay separate, each responsible for its own portion, with a lead member facing the client. Joint ventures can slow when owners disagree, while consortiums risk gaps between portions and little leverage over a failing member.
How do partner organizations build trust on a project?
Trust is built through four observable behaviors: transparency about information that affects the other party, keeping commitments or warning before a date is missed, early and frequent contact, and fair handling of mistakes with proportionate remedies. It grows slowly through many small observations. One concealed problem that surfaces later damages trust quickly, because it casts doubt on everything reported before.
What are decision rights in a multi-organization project?
Decision rights name, for each type of decision, who recommends, who decides and who must be consulted. Each type should have exactly one decider, because two produce delay and none produces drift. For example, a steering group decides changes to the opening date, while a site manager can stop work for a safety concern at once. Classify the decision first, then read across its row.
What is interface management between organizations?
Interface management controls the points where work, information or responsibility passes from one organization to another, where failures tend to cluster. It uses named contacts with deputies, defined hand-offs stating what passes, by when, to whom and how receipt is confirmed, one controlled set of shared documents, and an interface issue log tracking each problem's owner, status and next step.

About the Project Management course

How many college credits is Project Management?
Project Management (Business 230) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Project Management cost and what is included?
$250, paid once, with lifetime access: all 73 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Project Management take?
It is self-paced with no deadlines. The 73 lessons total about 15 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Project Management.

73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Project Management →Download the syllabusEvery course with PRO →
Project Management
3 credits · NCCRSEnroll →