Skip to content
Big Picture

Coordinating Multi-Team Deployments

A platform team manages multiple desktop applications built by different development teams. Each team wants to ship updates independently. The platform team needs to ensure consistent policies, coordinate releases that affect multiple products, and maintain governance across the entire portfolio.

Without coordination, teams create inconsistent policies, duplicate infrastructure, and make it difficult for customers to understand what’s happening across the product portfolio. Manual coordination becomes a bottleneck as the number of products grows.

Big Picture provides a unified control plane that scales from single products to complex multi-product portfolios. Teams can operate independently while sharing common policies, governance models, and infrastructure. The platform team maintains oversight without becoming a bottleneck.

The Problem

Section titled “The Problem”

Platform teams managing multiple products face coordination challenges:

  • Each product team wants autonomy to ship updates
  • Different products may have different release cadences and policies
  • Customers may use multiple products and need consistent experiences
  • Platform teams need to enforce governance without blocking teams
  • Infrastructure and policies should be shared, not duplicated

Traditional approaches create problems:

  • Each team builds their own update infrastructure, creating duplication
  • Policies are inconsistent across products, confusing customers
  • Manual coordination between teams becomes unsustainable
  • Platform teams struggle to maintain oversight without blocking teams
  • Customers experience inconsistent behavior across products

When This Use Case Applies

Section titled “When This Use Case Applies”

This use case applies when:

  • You manage multiple desktop applications as a platform team
  • Different development teams own different products
  • You need consistent policies and governance across products
  • You want teams to operate independently while sharing infrastructure
  • Customers use multiple products and need coordinated experiences
  • You need to scale governance as the number of products grows

How Big Picture Addresses This

Section titled “How Big Picture Addresses This”

Big Picture provides a multi-tenant control plane where products can share infrastructure while maintaining independent release cycles. The platform team configures organization-wide policies and governance models. Individual product teams manage their own releases within those constraints.

Products share:

  • Common policy frameworks and governance models
  • Shared infrastructure for release management and licensing
  • Consistent customer experiences across products
  • Unified reporting and visibility

Products maintain:

  • Independent release cycles and channels
  • Product-specific policies where needed
  • Team autonomy for day-to-day operations
  • Product-specific licensing models

This creates a scalable model. New products can be onboarded quickly by inheriting existing policies and infrastructure. Teams can operate independently while the platform team maintains oversight through shared governance. Customers experience consistency across products without teams losing autonomy.

Big Picture also supports coordinated releases. When multiple products need to update together, the platform team can create release groups that coordinate updates across products. This enables scenarios like major version upgrades that span multiple products.

High-Level Flow

Section titled “High-Level Flow”
  1. Platform team configures organization-wide policies and governance models
  2. Product teams create products within the organization, inheriting shared policies
  3. Teams publish releases independently, following organization governance
  4. Big Picture enforces policies consistently across all products
  5. Customers experience consistent behavior across products
  6. Platform team maintains oversight through unified reporting and visibility
  7. Coordinated releases can be scheduled across multiple products when needed

Next Steps

Section titled “Next Steps”

To implement this use case: