# squad

## A team owning a critical part of your product

Best fit when the work is ongoing, tightly connected to the system, and too important to keep staffing ad hoc.

## When the work is not really a project

Some problems are too large, too connected, or too persistent to treat as a short engagement. They need a team that can stay close to the system, make decisions with context, and keep improving the area over time.

## Bleu Squad

A stable team with ownership of a product or infrastructure area your users depend on.

- Not staff augmentation
- Stable ownership over time
- Continuous product and engineering progress without heavy management overhead

## What a Squad typically owns

- A product surface or workflow your users depend on
- A critical internal system or data layer
- The backlog around a neglected but high-value area
- The reliability, performance, and maintainability of that area over time
- Documentation and clean knowledge transfer as the work evolves