Design organizations vary in size, scope, and complexity, but the way teams are structured has a significant impact on their success. The Constellation Design Framework recognizes five key structures that shape how teams operate: Aquila (Centralized), Phoenix (Embedded), Draco (Flexible), Cygnus (Contractual), and Orionis (Hybrid). These names draw inspiration from celestial bodies, reflecting the nature and function of each structure within a design organization. Each structure offers unique benefits and challenges, depending on the organization's goals, scale, and maturity.
Team structure types
Aquila: Centralized team structure
Phoenix: Embedded team structure
Draco: Flexible team structure
Cygnus: Contractual team structure
Orionis Teams: Hybrid Team Structure
Aquila teams: A centralized team structure
Why Aquila? Named after the eagle constellation, Aquila represents leadership, vision, and stability; mirroring how centralized design teams provide a unified direction and governance across an organization.
- Description: All designers are part of a single team, working under shared leadership with unified goals.
- Benefits: Ensures consistency, promotes collaboration, and enables efficient resource allocation.
- Challenges: May lack deep integration with specific product teams.
- Ideal For: Large organizations aiming for cohesive branding and system-wide consistency.
Phoenix teams: An embedded team structure
Why Phoenix? Inspired by the mythological phoenix, this structure embodies rebirth and adaptability, much like embedded teams that integrate directly into product teams and evolve with their needs.
- Description: Designers are embedded within specific product or feature teams, closely collaborating with cross-functional groups.
- Benefits: Deep alignment with product goals, faster iterations, and stronger team bonds.
- Challenges: Risk of silos and inconsistency across teams.
- Ideal For: Small, Medium, to large organizations focused on agile product development.
Draco teams: A flexible team structure
Why Draco? Named after the dragon constellation that winds its way through the northern sky, Draco symbolizes flexibility and fluidity; ideal for teams that shift across projects and priorities as needed.
- Description: Designers move fluidly between projects and teams based on needs and priorities.
- Benefits: Maximizes resource utilization, fosters cross-pollination of ideas.
- Challenges: Requires strong coordination to avoid resource conflicts.
- Ideal For: Organizations with dynamic needs and multiple concurrent projects.
Cygnus teams: A contractual team structure
Why Cygnus? Representing the swan constellation, Cygnus signifies grace and temporary movement; just as contractual teams provide specialized expertise for short-term needs before transitioning away.
- Description: External designers or agencies are brought in to address specific project needs.
- Benefits: Provides access to specialized skills, scales teams quickly for short-term needs.
- Challenges: Limited knowledge transfer and potential disconnect with internal culture.
- Ideal For: Small organizations or those requiring temporary expertise.
Orionis teams: A Hybrid Team Structure
Why Orionis? Named after the extended family of stars in the Orion constellation, Orionis reflects a structure that blends multiple approaches, ensuring teams are adaptable while maintaining strategic alignment.
- Description: A blend of centralized, embedded, and flexible structures tailored to organizational needs.
- Benefits: Combines the best aspects of all structures, balancing consistency with agility.
- Challenges: Requires careful planning and governance to avoid inefficiencies.
- Ideal For: Large, complex organizations with diverse product portfolios.
{CD}
Version 1.0
Constellation Design by Michael Diaz is licensed under
CC BY 4.0
