At team scale, the movement is the same: illuminate what is actually happening, differentiate roles and responsibilities cleanly enough to reduce confusion, then integrate those distinctions into stronger communication and coordinated action.
This work is especially natural with technical teams because much of the language already resembles systems design: architecture, dependencies, interfaces, state, debugging, refactoring, databases, and boundaries.
Five team lenses
Identity: Who are we? Which roles have become confused with the people holding them?
Heartmind: How does this team perceive, reason, feel, communicate, and resolve tension?
Collection: What values, assumptions, knowledge, history, commitments, and goals does the team carry?
Power Form: Where does agency live? Who can act? Where is energy blocked?
Personality: What recurring behaviors has the team developed over time?