The "One Team" Mindset in Cross-Organizational Projects

PMBOK v8 Definition

When project teams form across different organizations based on a contract, strategic partnership, or other business relationship, such arrangements often require more up-front work to establish a "one team" mindset; ensure project team members understand how everyone contributes to the project; and establish other enablers that integrate skills, capabilities, and processes. This concept appears in the context of Team Performance Domain and addresses the maturity of project team culture when teams operate across organizational boundaries.

Why It Matters for the Exam

This concept frequently appears in PMI exam questions about hybrid and multi-organizational project environments where team members come from different companies or departments. Questions test your understanding that cross-organizational teams require deliberate upfront investment in team integration, not just contractual agreements. Expect scenario-based questions where you must identify the correct approach when a project involves a strategic partnership or outsourced work.

Key Points to Remember (for the exam)

• Core Requirement: Cross-organizational arrangements require more upfront work than single-organization teams to establish team cohesion
• Three Essential Enablers:
  1. Establish a "one team" mindset
  2. Ensure understanding of how everyone contributes
  3. Integrate skills, capabilities, and processes
• Common Challenge: Teams from different organizations may have more formalized and less flexible roles depending on contract terms
• Key Differentiator: Unlike co-located teams, cross-organizational teams need explicit integration enablers rather than assuming natural collaboration
• Critical Success Factor: The upfront investment in team integration directly impacts the unique culture of the project team
• Relationship to Coordination: This applies to both centralized and decentralized coordination approaches, but is especially critical when teams cannot self-organize due to contractual constraints

Typical PMI Exam Example

A project manager is assigned to a joint venture between Company A and Company B. Team members have never worked together and have different organizational cultures. What should the project manager do FIRST? Answer: Invest upfront time to establish a "one team" mindset, clarify how each member contributes, and integrate their skills and processes.

PMI Exam Traps

• Trap: Confusing "one team" mindset with simply having team-building activities

  • Reality: It requires deliberate integration of skills, capabilities, and processes—not just social bonding

• Trap: Assuming cross-organizational teams can use the same approach as single-organization teams

  • Reality: Cross-organizational arrangements require more upfront work and may have more formalized, less flexible roles

• Trap: Thinking contractual terms alone ensure team collaboration

  • Reality: Contracts create structure, but active enablers (shared understanding, integrated processes) are needed for true collaboration

• Trap: Believing this only applies to predictive (waterfall) projects

  • Reality: This applies to all project environments, but is especially critical for projects with high variability where centralized decision-making has less time

Important PMI Connections

Quick Review Questions

1. A project involves a strategic partnership between two companies. What three enablers must the project manager establish upfront to ensure team integration?

2. How does the maturity of project team culture differ between single-organization teams and cross-organizational teams?

3. Why might cross-organizational teams have more formalized and less flexible roles compared to internal project teams?

4. In which type of project environment are collaborative teams most critical, and how does this relate to the "one team" mindset?

5. What is the relationship between contractual terms and the need for upfront integration work in cross-organizational arrangements?

PMBOK v8 Reference

Section 3.7 - Team Performance Domain (Sub-section: Maturity of Project Team Culture)