Build a goal hierarchy that stays connected from year to today

The short answer

Each goal horizon should answer a different question: long term defines direction, the year defines a measurable state, the quarter defines the current strategic bet, the month defines an outcome, the week defines proof and the day defines action. Every lower level should name the higher-level goal it supports.

Give every horizon one job

1. Long term - direction Describe the durable position or life condition you want, without pretending to know the exact route.
2. Year - state Define a measurable end state that would prove meaningful movement in the direction.
3. Quarter - bet Choose the main mechanism you believe can change the annual trajectory.
4. Month - outcome State what the current bet must produce this month.
5. Week - proof Ask what observable result would validate or invalidate the monthly approach.
6. Day - action Choose the controllable work that creates the next proof.

Use the why-now test

For every weekly goal, ask which active monthly, quarterly or annual goal it supports and why it matters now. If there is no clear answer, it may be maintenance, an attractive distraction or an unrecorded strategic change.

Do not copy the same output into every level. Seven trials this week is not a useful annual goal. The levels should form a causal chain, not a stack of repeated targets.

Questions

What if a daily task supports several goals?

Link it to the goal whose current constraint it most directly reduces.

Can the hierarchy change mid-quarter?

Yes, but record the evidence and decision that caused the change.

How many annual goals should be active?

Few enough that the quarterly bet and weekly priorities remain unambiguous; three to five is usually plenty.