Most companies have a plan for the year. Far fewer can point at one person and say which part of that plan belongs to them. The gap between the two is where goal setting breaks, and it rarely breaks because the plan is wrong. It breaks because nobody translated it.

Cascading goals means one thing. Every level below the company plan can say what it contributes and how that will be checked. Done properly it removes meetings instead of adding them.

The levels a goal passes through

Purpose: why the company exists. It almost never changes.
Strategy: where the company wants to be in one to three years.
Company goals: four to six for the year, owned by the management team.
Department and team goals: what this unit contributes, with its own measure.
Individual goals: three to five per person, each traceable to a team goal.
The review: what actually happened, measured against what was agreed.

The test for the whole chain is one question. Ask anyone in the company what they are working on this quarter and what it contributes upwards. If the answer needs more than two sentences, the chain broke somewhere above them.

What makes a goal measurable

A goal is measurable when two people who dislike each other would still agree at the end about whether it was reached. That bar is higher than it sounds.

A number and a direction: from 12 to 8, not "reduce".
A date. A goal without a deadline is a nicely worded wish.
One owner. A person, not a department.
A source of truth agreed in advance: which report, which system, which query.
Something the owner can actually move with their own work.

Write the agreement down, with the measure, the date and the owner, in a place both sides can open at any time. A goal agreed only in conversation gets reconstructed at the end of the cycle from two memories, and the two memories reliably differ.

Two kinds of goals look measurable and are not. The first is made of activities, such as "run four workshops". You can complete it without anything changing. The second is made of outcomes nobody on the team controls, such as a market share figure. Activities belong in the plan, not in the goal.

A check-in rhythm people actually keep

Quarterly cycles with monthly check-ins fit most companies. A quarter is long enough for a goal to mean something and short enough that a bad goal does not cost a year.

Weekly: the owner updates progress where the goal lives. Two minutes, not a meeting.
Monthly: the team looks at the goals that are off track, not at all of them.
Quarterly: close the cycle, record what happened, set the next goals.
Yearly: the review conversation, based on the record instead of memory.

The monthly meeting survives on one rule: goals that are on track are not discussed. Reading out green items is the most common reason people stop showing up.

Why self-updating progress beats status reports

In many companies the status of a goal is assembled by hand. A manager asks four people, four people write four paragraphs, somebody turns them into a slide, the slide is presented, and by then it is a week old. The effort of reporting is larger than the effort of updating, and it lands exactly when nobody has time.

The alternative is simple. The owner maintains the number where the goal is stored, and every level above reads the same number. Then the roll-up is arithmetic rather than a meeting. Three things change. The number is current. Nobody polishes it on the way up. And the monthly conversation can be about the two goals that are stuck.

This works under two conditions. Updating has to be genuinely quick, and an early red light must not hurt anyone. A goal that turns red in week three and recovers shows a system that works. A goal that stays green until the final week shows a system nobody trusts.

Where cascading goals usually fails

Too many goals

Fifteen goals per person is a task list with ceremony. Three to five is the number people can hold in their head. If everything is a goal, the chain tells nobody what may be dropped when the quarter gets tight.

Goals nobody can influence

Company revenue as a personal goal for someone in customer support is not a goal, it is a mood. People stop caring about numbers they cannot move, and they are right to.

Goals that change mid-cycle

Priorities do change, and an obsolete goal should be closed rather than carried along. But closing it has to be visible and dated, with a reason. Quiet edits to targets after the fact destroy the system faster than a missed number ever will.

Goals written once and never opened

If goals live in a document that is opened twice a year, they are not goals, they are minutes. Progress has to be visible where the work already happens.

How the goal chain works in Persohap

In Persohap, company goals cascade through six levels, from the company purpose down to the individual review. Progress updates roll up automatically, so no status meeting and no status report is needed for that.

The same progress carries into the review. Goal progress counts 30 percent of the performance score and kudos count 15 percent, both counted automatically. The remaining 55 percent is graded by the manager against measures each department publishes before the round starts. There is no forced curve and no quota, so a whole team may be at the top. Employees control three consents, and HR sees distributions rather than individual scores.

See how goals and reviews fit together