Does the definition travel?
Could people interpret the same label differently? Write the scope, unit of observation, and exclusions in plain language.
Independent notes on team measurement
A measure should start a better conversation.
Before choosing what to count, get clear about what you want to understand. A useful measure brings the work into focus and leaves room for context.
Open the discussion guideA reading resource, not a platform. No accounts, employee records, analytics integrations, or measurement services are offered. All scenarios are illustrative.
Keep the ideas separateA signal is not
A signal is not
the whole story.
Measurement becomes easier to discuss when the observation, the aspiration, and the interpretation do not collapse into a single label.
The signal
A signal is something you observe about the work. It may reveal a pattern worth exploring. Define what it includes and excludes before using it to explain what is happening.
The aim
An aim describes a desired direction or outcome. It explains why the work matters. A convenient activity count may have only an indirect relationship to that aim.
The interpretation
An interpretation connects the observation to a possible explanation. Workload, task mix, dependencies, and changing conditions may all belong in that explanation.
A worked conversation / illustrative
The count moved.
The count moved.
What changed?
Imagine a team notices that work is passing between people more often. That observation raises a question; it does not identify a cause.
The team might explore changing work types, unclear ownership, useful collaboration, or missing information. The same signal can be consistent with several explanations.
Read the interpretation prompts →
The handoff discussion
Make the uncertainty visible.
Observation
“We are seeing more handoffs in the work we reviewed.”
Open question
“Which handoffs help the work, and which reflect missing context?”
Context to explore
“Have task types, responsibilities, or dependencies changed?”
Possible response
“Review representative examples with the people doing the work before deciding what to change.”
Before a measure becomes routineAsk what it reveals.
Ask what it reveals.
Ask what it leaves out.
A thoughtful measurement discussion includes the limits of the signal and the behaviors that attention to it might encourage.
Are like things being compared?
Notice differences in task complexity, responsibilities, tools, and dependencies. A shared label does not make situations equivalent.
What might attention change?
Consider which work may become more visible, which may disappear from view, and how people might adapt to the measure.
Keep the conversation openPractical questions,
Practical questions,
without a magic metric.
The purpose is a more useful discussion of the work, rather than a universal score for a team or a person.
Can a qualitative observation be part of the discussion?
Yes. Examples, written explanations, and the team's account of the work can provide context that a count does not contain. Be clear about how observations were gathered and what they can support.
Should a measure always become a target?
A measure can be useful for learning without becoming a target. Before making that change, discuss the aim, the signal's limits, and the behavior the target might encourage.
When should the definition be revisited?
Revisit it when the work, tools, responsibilities, or purpose change, and when people can no longer explain what a result means. A measure's usefulness depends on its context.
Use the next team conversationStart with a question
Start with a question
worth understanding.
The discussion guide helps you name the purpose, define a signal, document uncertainty, and decide how learning will lead to action.
Read the discussion guide