Goal-setting rituals have a way of becoming rituals. The offsite. The OKR workshop. The cascade. The read-out. The check-in cadence. All of it feels like alignment. Often, none of it is.

Here are the six signs that your goal-setting process has become performance.

Sign 1: The goals are written after the work is planned

If your team writes its OKRs in the third week of the quarter — once the engineers are already allocated and the roadmap is already set — the goals are describing what you were going to do anyway. That's not target-setting. That's retroactive justification.

Real goals are written before the work. They create constraint. They force choices. If the writing process doesn't cause anyone to change their plan, the goals aren't setting direction. They're decorating it.

Sign 2: Every goal is green by end of quarter

A goal-completion rate above 80% sounds like a great team. It's more likely a sign of sandbagging. If no goal ever fails — across quarters, across teams — the goals are being written to be achievable, not to be stretching. That's not goal-setting. That's forecast-labeling.

The right completion rate for ambitious goals is somewhere around 60–70%. Goals that were always going to happen aren't goals. They're plans in disguise.

Sign 3: Nobody can say which work is moving which goal

Ask your team lead: "Which three work items are most directly moving our top KR this week?" If the answer takes more than thirty seconds, the goals aren't connected to the work. They're running in parallel. Two separate layers — the goal layer and the work layer — with no structural connection between them.

That structural gap is where strategy goes to die. The goal says "increase net revenue retention." The work that happens this week has nothing to do with it — because nobody ever made the connection explicit.

Sign 4: The check-in is a status meeting disguised as a goal review

If your weekly or monthly goal check-in consists primarily of people reporting what they did last week — not what's at risk, what decision is needed, what's been 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 result in at least one changed decision isn't a goal review. It's a ceremony.

Sign 5: Goals migrate quietly to next quarter

The quarter ends. Three KRs are incomplete. In the next quarter's planning, those three goals — reworded slightly — reappear. Nobody names this. Nobody asks why they moved. They just moved.

Goals that migrate without a post-mortem are goals nobody was actually accountable for. If there's no story of what happened and what changes next quarter, the goal was a hope, not a commitment.

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 — then you've created a two-speed organization. Leadership thinks in goals. Teams work in tasks. Neither layer knows what the other layer is for.

That's not misalignment. That's two organizations sharing a floor plan.

What to do if you recognize your team in this list

Start with Sign 3, because it's the most structurally fixable. Every work item a team produces this week should be labeled with the goal it's supposed to move. If it can't be labeled, it should be questioned: is this work supposed to be happening?

That one change — tracing work to outcome — exposes the others. Goals get written before the work because the work requires a goal to exist. Check-ins become decisions because the system shows what's stalled, not just what got done. Migration becomes visible because the system shows which goal has had no active work for three weeks.

The fix isn't a better OKR template. It's a structural connection between the goal and the work that proves it.