Think inside your AI world.
Is this a real miss or a timing lag?
A key result short of target at the line might be a real miss, or it might be lagging a delay you already knew about — a payment cycle, a launch that shifted, a metric that reports late. Through Unl the read judges it against the timing you built into the target, so a lag isn’t mistaken for a failure.
Not every shortfall is a miss. Some are timing — the result is coming, just later than the raw date suggests, for a reason you anticipated. Hold that timing in Unl and the read tells a lag from a miss, so you respond to the real ones and wait out the expected ones.
A shortfall has two explanations
When a key result lands short, the honest first question is why. A genuine miss means the work didn’t deliver; a timing lag means it did but the metric hasn’t caught up — revenue booked but not yet recognised, sign-ups that convert on a delay, an outcome tied to an event that moved. These demand opposite responses, and the raw number can’t tell them apart.
So reacting to every shortfall as a miss overreacts to lags, and treating every shortfall as a lag excuses real misses. The distinction needs the timing assumptions behind the target, which the tracker does not hold.
The timing makes the call
Say your key result — forty renewed contracts — is at thirty at quarter-end, apparently a miss. But you ratified a timing note: a third of renewals land in the first fortnight of the following quarter because of when contracts anniversary. The read returns: not a real miss — you’re on pace once the known renewal lag is accounted for, tracking to forty-one, so this is timing, not shortfall.
Without the timing note, thirty of forty reads as a clear miss and triggers a scramble. With it, the read correctly calls it a lag, and you wait out the fortnight instead of overhauling a process that is working.
Not a licence to excuse misses
The same read is strict where it should be. A shortfall with no timing reason behind it is called a real miss plainly — the timing note only excuses lags you anticipated in advance, not ones invented after the fact to soften a number. You can’t retrofit a lag to launder a genuine miss, because the timing had to be set before the result.
So “real miss or timing lag?” gets a disciplined answer: judged against the timing you built in ahead of time, so anticipated lags are waited out and genuine misses are named, with the reason for each.
A shortfall is a real miss or a timing lag, and the raw number can’t tell them apart; through Unl the result is read against the timing you built into the target in advance, so an anticipated lag is called a lag and a genuine miss is named plainly — you respond to the real ones and wait out the expected ones, without retrofitting a lag to excuse a miss.
Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. The reach lane is live: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.
Read further
Questions people ask
Is my key result a real miss or just a timing lag?
It depends on the timing you built into the target. A shortfall can be a genuine miss or a result that’s coming late for a reason you anticipated — a renewal cycle, a delayed conversion. Through Unl the read judges the number against your ratified timing, so a lag isn’t mistaken for a failure.
How do I avoid panicking over an OKR that's behind at the line?
Record the timing assumptions when you set the target — the known delays in when the metric lands. Through Unl the read accounts for them, so a key result short because of an anticipated lag is called a lag with its projected true finish, rather than triggering a scramble over a working process.
Can't a timing lag just be an excuse for a miss?
Only if you let it be set after the fact — which the read doesn’t. The timing note must be ratified before the result, so an anticipated lag is honoured while a genuine miss with no prior timing reason is named plainly. You can’t retrofit a lag to launder a shortfall.
How does Unl tell a real OKR miss from a timing lag?
It reads the result against the timing you built into the plan, not the raw shortfall at the line. So a result behind because its wins land late reads as on-plan, while one behind on its own schedule reads as a genuine miss.
What this is
Think inside your AI world — you stay in command
Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.
It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.
Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:
Alpha is invite-only · free at launch.