"Strategy-led" is thrown around a lot. Most uses mean: we have a strategy, and we also have work, and we think they're probably related. That's not strategy-led work. That's optimistic assumption.

Real strategy-led work has a structural definition, not a cultural one: every task was created in response to a goal, its progress is visible against that goal, and when the goal changes the work changes.

The three requirements

Goals exist in the same system as work. Not in a separate document, not in a different tool. The goal and the work meant to prove it live in the same place, with a visible connection. When goals and work are in different systems, the connection is theoretical — it existed at the moment of planning and has degraded every week since.

Work is created from goals — not goals retrofitted to existing work. Most quarterly planning works backwards: teams present what they're planning to do, then someone maps it to the OKRs it "supports." This is goal theater. In strategy-led work, the question is reversed: what does this goal require? The tasks flow from the objectives.

Retrofitting goals to existing work is a ritual. Creating work from goals is a discipline.

The connection persists — it's not a one-time mapping exercise. Most companies do goal-work mapping at the start of a quarter. By week six, new work has been added that nobody mapped to anything. By week ten, some original tasks are finished and the goal they served has nothing attached. The connection was a snapshot, not a living link.

Strategy-led work requires that the connection is maintained continuously — which means it needs to be built into the system, not the process. If maintaining the link requires a human to remember to update two tools, it will degrade. If the link is structural, it persists.

Why it matters for prioritization

When work is genuinely strategy-led, prioritization becomes observable rather than a judgment call. You can see which work is attached to a high-priority goal and which isn't. Which goals have no work attached at all. The prioritization framework becomes the goal hierarchy — visible in the work.

This is what Vindaris means by traceable work. Not work that's been tagged, but work you can trace from task to goal to outcome in both directions, because the connection is structural.