Know whether the work is working without building another dashboard nobody reads.
A charter is one team’s editable account of its purpose, work, measures, authority, roles, and guidelines. A measure is one signal that helps the team see whether its work is moving in the intended direction.
Particulars keeps the number beside its purpose, source, recent readings, and the person who responds when it changes. The team can act on the signal because its meaning stays attached.
You already have plenty of numbers. The hard part is knowing which ones should change the work.
Your dashboard fills with numbers because the systems can retrieve them: page views, tickets closed, features shipped, meetings held, sentiment, revenue, and cost. Every number may be accurate while the collection says very little about whether one team is making its intended contribution.
The problem is usually the missing connection between purpose, action, and evidence. A team needs to know why this number matters, exactly where it comes from, and which choice could move it. A target also needs a named trade-off, or people will learn to improve the number while making the work worse.
Particulars keeps that meaning with the team. You can read why the team watches the signal, which direction it wants to move, who owns the response, and when a source changed enough to break the comparison.
Know what kind of promise each number makes.
A team can use evidence to learn without pretending one number contains the whole performance of the team or the people inside it. The labels below change what the organization is asking of the signal.
Measure
A signal that helps the team notice change. It may be quantitative or observed, leading or lagging, precise without being complete.
Target
A chosen threshold or ambition. It can focus action, but it can also distort action when treated as the whole value.
KPI
A signal chosen for sustained management attention. It still needs a team, a source, and a person who knows what to do when it moves.
Contract
A number tied to compensation, evaluation, funding, or employment. This changes how the measure will be produced and interpreted.
Connect the signal to a choice the team can make.
Begin with purpose and direction
Every measure says which way the team is trying to move it: up, down, hold steady, or simply watch for now while the team learns. Writing the direction down keeps the team honest about what it actually wants. It also avoids the trap where every number on the dashboard is supposed to go up forever.
A Host Onboarding team might increase complete listings, decrease time to first inquiry, maintain severe-quality incidents below a boundary, and learn which interventions predict a successful first reservation. Together the signals describe the contribution better than “ship five features.”
Keep the source and definition attached
Write down the system, population, calculation, refresh cadence, steward, and known discontinuities. A source definition is part of the measure, not an implementation footnote. When the definition changes, comparison may break even if the chart remains smooth.
Keep the reading and interpretation distinct. A reading records the value, time, and source state. A note records what the team believes changed, what remains uncertain, and what could disprove the explanation.
Use a small, plural view
One number rarely contains the work. Pair speed with quality, growth with harm, automation with correction, and efficiency with load transferred elsewhere. A lagging outcome needs evidence that can change action sooner.
Connect each measure to a named role and a recurring choice. When time to first inquiry rises, the Host Onboarding lead reviews the last four weeks, checks listing completeness by market, and decides whether to change the onboarding flow or investigate the source first. A measure becomes useful when someone specific knows what to do next.
A measure with its source, owner, and next decision
Particulars keeps readings beside the measure’s direction and source. The team sees the current value without losing the population, refresh state, source change, and reason the signal matters.
A short interpretation can say what the evidence suggests, who will look next, and which decision may follow. The reading stays separate from the team’s explanation of it.
Complete listings published within seven days
Most of the increase appears after the new photo-quality guidance. Review severe-quality incidents after two weeks.
Know who will notice a change and what they can do about it.
Measures connected to teams, decisions, and history can reveal a missing steward, a source that went stale, or a team watching activity without evidence of value. They can also show where improving one number moves cost or harm into a neighboring team.
Particulars keeps local evidence and meaning legible enough for people to judge, revise, and retire the measures that no longer serve the work.
- See when a source change makes earlier readings incomparable.
- Pair an outcome with the constraints that prevent narrow optimization.
- Retire a signal deliberately when the purpose, source, or decision path moves.
“A measure gives the team a disciplined way to notice what the work may be doing and decide what to examine next.”
— The Particulars thesis