Team API
Product term: Team Contract
Category: core
Definition
A strict interface contract defining how teams interact with each other and the broader organization. Each team publishes its API: responsibilities, input/output formats, SLAs, and escalation paths. Team APIs eliminate implicit expectations, reduce friction, and enable swarms to form rapidly around work. They're versioned and managed like software APIs, with backward compatibility guarantees.
Key Points
- •Interface contract for team-to-team interaction
- •Defines: responsibilities, inputs, outputs, SLAs, escalation
- •Eliminates implicit expectations and reduces friction
- •Enables rapid swarm formation
- •Versioned like software APIs
- •Backward compatible to prevent surprises
Frequently Asked Questions
What should a Team API include?
Responsibilities (what you own), Inputs (what you accept), Outputs (what you deliver), SLAs (speed and quality), and Escalation (how to reach someone in an emergency).
How is this different from RACI?
RACI maps individuals to tasks. Team APIs define how entire teams interact, with published contracts and SLAs.
Who creates a Team API?
The team itself, collaboratively. It should be reviewed by teams that depend on you.
What if a team violates its API?
The Constitutional Review Board reviews violations. Repeated breaches can trigger escalation to leadership.
Related Terms
Learn more about Intelligence-Native Organizations