How to Use Tability Check-ins to Spot Stalled Goals Early
Stalled goals are visible in Tability about three weeks before they’re visible in results: confidence drops from on-track to at-risk, updates get shorter, and the same blocker reappears in comments. Reading that pattern is a skill, and it’s the difference between using Tability as a tracker and using it as an early-warning system.
The tool gives you the trend lines. Someone has to look at them on a Tuesday rather than at quarter-end.
What does a stalling key result look like in the data?
Four signals, in the order they appear:
- Confidence drops two steps in one week. One step is noise; two means something broke.
- Update text gets shorter. “Working on it” replaces a two-sentence description. Length is a surprisingly reliable proxy for whether someone knows what to do next.
- The metric stays flat for three consecutive check-ins. Flat is not the same as slow — slow still moves.
- The same blocker appears in two check-ins with no owner named. Recurring blockers without owners are the actual problem, every time.
Pipedream-style automation isn’t needed for any of this. Tability shows the trend per key result; the reading discipline is yours.
Step 1: review trends on Tuesday, not Friday
Friday check-ins land at the end of the week, when nobody has the capacity to act. Read the confidence trends on Tuesday morning, once, for twenty minutes. Anything flagged red or dropped twice goes on a shortlist.
That shortlist is what the weekly team lead sync covers. Not a read-through of everything — three or four names.
Step 2: ask the question that produces a real answer
“How’s it going?” gets “fine”. The question that works is specific and offers an escape from optimism:
- “Which specific step is blocked right now, and who owns unblocking it?”
- “If this stays flat for two more weeks, what’s the first thing you’d cut?”
- “What would have to be true for this to hit the target — is that still possible?”
The third question is the important one. It invites a legitimate “no”, which is much more useful than a fourth week of the at-risk confidence.
Step 3: name blockers with an owner inside the check-in
A blocker without an owner is a complaint. Tability’s comment thread is the right place to fix that, because it stays attached to the key result.
Format that works: Blocker: [thing]. Owner: [name]. Needed by: [date]. Three fields, written into the comment. Anyone reading the key result later sees the whole chain.
How do you escalate without it feeling like a punishment?
Separate the review from the person. The escalation path should be about the key result:
| Signal | Action | Owner |
|---|---|---|
| Confidence at-risk 1 week | comment asking for the blocked step | team lead |
| At-risk 2 weeks | 15-min conversation, decide continue/rescope | objective owner |
| At-risk 3 weeks or red | rescope or drop the KR, update the objective | leadership |
| Two KRs at-risk same objective | treat the objective as at risk | leadership |
Rescoping is a legitimate outcome. A quarter where you drop two key results and hit four is a better quarter than one where all twelve stay at-risk and the retrospective is fiction.
What about the confidence number itself?
Tability uses on-track / at-risk / off-track. In most teams, at-risk gets used for everything ambiguous, which makes it useless. Some teams add a simple rule: at-risk requires a stated blocker, otherwise it’s on-track. That one constraint sharpens the signal considerably, at the cost of some uncomfortable honesty in week two.
When the warning comes too late anyway
Sometimes the pattern is clean and the team simply can’t move — the dependency is external, the quarter is wrong, or the goal was impossible from the start. Ninety days is short; a key result that needed six months will read as stalled from week six.
That’s a goal-setting failure, not an execution one. The fix is to write key results with quarterly-sized targets, and to say so in the retrospective instead of blaming the team. If your key results routinely need “one more quarter”, the objective design is the thing to change.
Who benefits from this practice
Objective owners running three or more key results across teams, and anyone who’s been surprised by a missed quarter they thought was fine. Teams of five who all sit in one call don’t need trend-reading — they can just talk.
Quick Summary
- Two-step confidence drops, shorter updates, and unowned recurring blockers are the early signals.
- Read trends on Tuesday, not Friday, and keep a shortlist of three or four names.
- Ask “what would have to be true” — it invites a legitimate no instead of a fourth week of optimism.
- Every blocker needs an owner and a date, written into the check-in comment.
- Rescoping is a legitimate outcome; a dropped key result beats a fictional at-risk all quarter.
Related guides
- Set up Tability OKRs without another status meeting — objectives, cadence and check-in design first.
- Build your first Pipedream workflow — automations that feed metric-based key results.
