Summary of "Building Composable Teams: Moving Beyond Rigid Organizational Structures"
Summary: Building Composable Teams – Moving Beyond Rigid Organizational Structures
Presenter: Love Kapoor, Staff Engineering Lead at BIT, former platform portfolio manager for a large pension fund Interviewer: Shane Hasty, MCQ Engineering Culture Podcast
Key Concepts & Frameworks
Composable Teams / Composability in Organizations
- Teams are treated as modular, composable units with clear “capability APIs”—defining what services or capabilities a team provides, who their customers are, and how to interact with them.
- Organizations should be viewed as dependency graphs rather than rigid hierarchies; each team acts as a node with dependencies on others.
- This approach enables fluid movement of headcount between teams, similar to liquidity management in finance, allowing rapid adaptation to changing market or organizational needs.
- Challenges the traditional “long-live stable team” model by promoting dynamic re-teaming and fluid team membership.
Capability API Framework for Teams
- Clearly define:
- The team’s customers (internal or external)
- The service or product the team builds (toolkits, platforms, automations, applications)
- How others consume and contribute to this service
- Use the ease of introducing change or dependency management as a health check for composability.
Home and Away Team Model (Dynamic Team Membership)
- Individuals or sub-teams rotate between their “home” team and “away” teams that depend on their work.
- Away team members actively contribute to the other team’s delivery and gain insights into their processes and customer needs.
- This model fosters cross-team collaboration, knowledge sharing, and reduces silos.
Leadership Perspective Shift
- Leaders manage portfolios of capabilities aligned with business initiatives, rather than just individuals or fixed teams.
- Focus on identifying capability gaps and strategic alignment over maintaining rigid org charts.
- Facilitates better build vs. buy decisions by clearly understanding internal capabilities and gaps.
Processes & Adoption Playbook
Starting Small & Incremental Adoption
- Begin composability adoption at the “leaf nodes” of the dependency graph—teams with few or no dependents.
- Restructure those teams first, then gradually move upstream through the dependency graph.
- Avoid big-bang reorganizations; composability evolves organically and incrementally.
Building Trust & Transparency
- Trust is foundational for composable teams—trust talented individuals to self-manage without micromanagement.
- Transparency and clarity about organizational changes, pivots, and decisions help rebuild trust after disruptions (e.g., layoffs, reorganizations).
- Clear communication of the “why” behind decisions reduces uncertainty and increases comfort.
Mentorship in Staff Engineering Roles
- Staff engineers focus on mentoring highly skilled engineers rather than managing them.
- Key skill: active listening to understand individual definitions of success and unblock career growth.
- Help engineers navigate fluid team environments by clarifying roles and capabilities.
Metrics, KPIs & Targets
While no explicit numeric KPIs were provided, key evaluation metrics implied include:
- Ease of introducing changes to dependent teams (a proxy for composability).
- Speed and fluidity of headcount movement between teams.
- Team growth and scaling velocity (e.g., a team growing from 4-5 to 40 developers).
- Employee career growth and skill diversification as a measure of team health.
Concrete Examples & Case Studies
- Love Kapoor’s experience managing platform teams supporting hundreds of developers and billions in financial transactions, emphasizing internal developer customers.
- The analogy of liquidity management from finance applied to headcount movement in organizations.
- Implementation of “home and away” teams in a prior role to improve collaboration and knowledge transfer between dependent teams.
Actionable Recommendations
- Define and document team capabilities as APIs for internal discoverability and interaction.
- Encourage leadership to think in terms of capability portfolios, not rigid teams.
- Build trust through transparency and clear communication around organizational changes.
- Start composability adoption incrementally from leaf teams in the dependency graph.
- Use rotational “home and away” team models to foster cross-team collaboration and individual growth.
- Staff engineers should mentor by listening and removing blockers aligned with individual success metrics.
High-Level Business Execution Insights
- Composable organizations enable agility and scalability in fast-changing environments, especially relevant with AI and digital transformation pressures.
- Reducing rigid headcount structures helps optimize talent allocation aligned with shifting business priorities.
- Clear capability definitions improve internal software reuse and reduce technical debt from tightly coupled teams.
- This organizational agility can be a competitive differentiator similar to early internet-era shifts.
Sources:
- Love Kapoor, Staff Engineering Lead at BIT
- Shane Hasty, MCQ Engineering Culture Podcast host
Category
Business
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.
Preparing reprocess...