Everyone has worked with someone who commits confidently in a meeting and then delivers something that does not match — different priorities, different understanding, different reality. The uncertainty itself is the cost: every commitment from that person needs re-verification, and the overhead compounds. The question is whether you can see this risk early. You can — by measuring the consistency signal.

What the signal measures

Every professional presents two channels of information:

  • The shown channel — what they say their approach is: the rules they state, the values they claim, the way they describe their own decisions.
  • The operating channel — what they actually do when tradeoffs appear: which option they take when both choices are good and mutually exclusive.

Consistency is the measured gap between the two. It is not a character judgment. It is a forecasting property: how accurately you can predict someone's operating behavior from their stated approach.

Why it matters for efficiency

Consistency reduces coordination cost. High-consistency partners align behavior with their stated approach, enabling smoother workflows without constant verification. Low-consistency partners leave every commitment carrying uncertainty, and the organization spends energy re-confirming scope, re-reading signals, and adding approval layers. That overhead is real, and it compounds across every interaction.

How to measure it from data

  1. Collect a stated-approach sample. In conversation or planning, ask how they would handle a specific scenario — a missed deadline, a conflict with a stakeholder, a tradeoff between speed and quality. Record the rule they state.
  2. Collect an operating sample. Observe three to five real decisions under tradeoffs, not hypotheticals. Good observation points: when resources are tight, which part do they protect? When two teams' interests collide, how do they coordinate? When a small early mistake surfaces, do they correct it immediately or set it aside? Record what they actually chose, including the cases where the choice cost something. Note that fluent articulation is not evidence — people who describe their process smoothly are often simply practiced at presentation; the operating sample is the evidence.
  3. Rate the gap. On a scale of 1 to 5, how closely do the two samples track? For example, a partner who stated "speed over polish" and then repeatedly chose speed under pressure scores 5 — their stated approach is a reliable forecast. A partner who stated the same rule and then regularly reversed it under similar pressure scores 2.

How consistent is your own record?

Three questions — that's how long it takes to see the decision profile behind how you commit and verify. TangoEra's free check maps how you weigh trade-offs, risk, and time horizons.

See my decision profile

What to do with the score

  • High consistency (4-5): low monitoring overhead. Plan against their stated approach directly; reserve verification for genuinely high-stakes decisions.
  • Low consistency (1-2): build verification into the workflow — explicit checkpoints, written scope, independent confirmation on handoffs. Do not rely on repeated verbal commitments, because the data shows they do not reliably track.
  • Either way, re-measure after real stakes. The first score is a hypothesis. Consistency is not a permanent property; it shifts with role, pressure, and context. Re-scoring after three to five real interactions tells you whether the signal is stable.

The consistency signal turns an impression into a measurement. It does not tell you whether someone is good or bad — it tells you how much of their operating behavior you can forecast, and how much verification the collaboration needs.

Your data indicates the consistency level. The verification design is up to you.