Team Rotation Against Knowledge Silos

Knowledge silos break under turnover. The 6-month rotation that prevents siloing without slowing teams down.

Structure

Each engineer rotates focus area every 6 months. Not teams; focus areas within a team.

Old focus area gets a successor; outgoing engineer is on-call for questions for 30 days.

Documentation is required at handoff; the rotation forces documentation that would not otherwise happen.

Benefits

No single person becomes irreplaceable on any one system.

Cross-pollination of patterns. Engineers carry good practices from one focus area to another.

Resilience to turnover. When someone leaves, the team has multiple owners.

Limits

Specialised areas (database internals, distributed systems algorithms) cannot rotate as freely. Those areas have permanent owners but secondary engineers shadow.

Rotation cost. The first month after a rotation is less productive. The annual cost is real.

Not for tiny teams. Below 5 engineers, the rotation overhead exceeds the benefit.