Goal-setting rituals have a way of becoming, well, rituals. The offsite. The OKR workshop. The cascade. The read-out. The check-in cadence. All of it has the texture of strategic alignment. Often, none of it is.
The clearest test is also the cruellest. If you removed your goal document from the system tomorrow morning — every OKR, every KR, every red/amber/green dot — would anyone's Tuesday change? If the honest answer is no, the process has become performance. Below are the six signs that get you there.
Sign 1: The goals are written after the work is planned
If your team writes its OKRs in the third week of the quarter — after the engineers have already been allocated, after the roadmap is already locked, after the next two sprints are already groomed — the goals are not setting direction. They are describing what was going to happen anyway. That isn't target-setting. It's retroactive justification.
Real goals are written before the work, because real goals create constraint. They force someone in the room to give up something they wanted to do. If the act of writing your goals doesn't cause anyone to change their plan, the goals aren't doing the job goals exist to do.
Sign 2: Every goal is green by end of quarter
A goal-completion rate above 80% sounds like a high-performing team. It is almost always a sign of sandbagging. If, across multiple teams and multiple quarters, no goal ever fails, the goals are being written to be achievable rather than to be stretching. That isn't goal-setting. It's forecast-labelling.
The right completion rate for genuinely ambitious goals is somewhere between 60% and 70%. Goals that were always going to land aren't goals. They're plans wearing a goal costume.
Sign 3: Nobody can say which work is moving which goal
Ask any team lead, on any Tuesday: which three work items are most directly moving our top key result this week? If the answer takes more than thirty seconds, the goals are not connected to the work. They are running in parallel. Two layers — a goal layer and a work layer — sharing nothing but the floor of the building.
That structural gap is where strategy quietly dies. The goal says "increase net revenue retention by eight points." The work happening this week has nothing visible to do with NRR — because nobody ever made the connection explicit, and the system never required them to.
Sign 4: The check-in is a status meeting in goal-review clothing
If your weekly or monthly check-in consists mostly of people narrating what they did last week — not surfacing what's at risk, what decision is needed, what was learned — it's a status meeting with a goal deck on the screen. The form is goal review. The function is reporting. A goal review that doesn't end with at least one changed decision isn't a goal review. It's a ceremony with a recurring calendar invite.
Sign 5: Goals migrate quietly to next quarter
The quarter ends. Three key results are incomplete. In the next quarter's planning, those three KRs — reworded slightly, sometimes promoted to objectives — reappear as if they were new. Nobody names the migration. Nobody asks why they moved. They just move.
Goals that migrate without a post-mortem are goals nobody was actually accountable for. If there is no story about what happened, what we learned, and what changes next quarter, the goal was a hope rather than a commitment — and the next version of it will be the same hope, just with a different start date.
Sign 6: Leadership presents goals; teams execute tasks
If the people writing the goals are not the people doing the work — if goals are set at one altitude and the work happens at another, with no structured connection between them — you have built a two-speed organisation. Leadership thinks in objectives. Teams think in tickets. Neither layer fully understands what the other layer is for.
That isn't misalignment. That's two organisations sharing a floor plan.
What to do if you recognise your team in this list
If three or more of these signs apply to you, the temptation is to redesign the OKR template. Don't. The template is not the problem.
Start with Sign 3, because it is the most structurally fixable, and because fixing it exposes the others. Every work item a team produces this week — every ticket, every initiative, every project — should be labelled with the goal it is supposed to move. If the team lead can't make the connection, the work itself should be questioned. Is this work supposed to be happening at all? If yes, against which objective?
That single change starts to fix the rest by accident. Goals get written earlier because the work needs a goal to exist against. Sandbagging becomes harder because the connection between the work and the KR shows the math. Check-ins become decisions because the system surfaces what's stalled, not just what got done. Migration becomes visible because the system shows which goals have had no active work for three weeks.
The fix is not a better OKR template. The fix is a structural connection between the goal and the work that's supposed to prove it.
The Vindaris view
Goal theater is what happens when the goal layer and the work layer are maintained by different people, in different tools, on different cadences. The instant they live in the same system — same graph, same surface, same Tuesday — the theatre runs out of stage. You can't sandbag a goal when the work attached to it is visible. You can't migrate a KR silently when the system shows it has been unattended for two months. You can't run a check-in as a status meeting when the system has already surfaced what's actually changed.
Goal-setting is supposed to change what your team does on Tuesday. If yours doesn't, the question isn't whether your goals are well-written. The question is whether your goals are connected to anything at all.