Collaboration metrics examine first-pass acceptance, iteration loops, rework, and review effort. They assess joint delivery effectiveness rather than raw output volume.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Collaboration metrics reveal how well people or agents work together by examining collaboration through observable signals.
The approach comes from organizational research and software development, where team performance is considered over time, dependencies, and shared outcomes. Thoughtworks describes its application to coding agents through interactions, handoffs, and the value created by agent collaboration.
Imagine a relay-race log: it records more than the finish time, including handoffs, waiting, and dropped batons. That makes collaboration friction visible.
Measurable events provide clues about collaboration.
Handoffs, waiting, and blockers show how work moves through a system.
Metrics are connected to quality and impact rather than activity alone.
Collaboration metrics help teams spot coordination problems and improvement over time. Isolated metrics can distort behavior; they need context, qualitative review, and safeguards against surveillance.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.