EFQM and Strategy Assessors

How strategy is actually developed

Sub-criterion 1.4 examines how you develop strategy — not whether the resulting document is elegant, but whether the process that produced it is sound.

A sound process has identifiable inputs: the ecosystem analysis from 1.2, the stakeholder needs from 1.3, your capability assessment, your performance data. Strategy is where those streams converge into choices. If the inputs are missing, the strategy is opinion in a nice template.

It has the right people: not only the executive committee, but voices from the front line, from younger cohorts, from functions that see the future first. Strategy written by five similar people produces five similar blind spots.

It has rhythm: an annual refresh at minimum, with triggers for out-of-cycle review when the ecosystem shifts. Strategy as a five-year monument is obsolete before the ink dries.

And it produces real decisions — priorities with resources attached, and just as importantly, things you will deliberately stop doing.

When I assess 1.4, my first request is always the same: walk me through how the current strategy was built. The quality of that story predicts almost everything else.