When strategy lives on a shelf
Most organisations have a strategy. Ask them where it is and they will point you to a document. Ask how it shaped a specific decision made last Tuesday and the answer is usually less clear.
The problem is not intent. Strategy documents are produced with genuine purpose — capturing direction, aligning leadership, anchoring priorities. But a document that exists separately from the operational governance layer depends entirely on recall and leadership proximity to have any effect. When the organisation is small enough that everyone shares context daily, this works. When it is not, the document gets filed. People act on habit, convenience, and precedent. The strategy becomes something cited at quarterly reviews, not something consulted when a real decision needs making.
This is a corporate governance problem. Not in the narrow statutory sense — though that matters too — but in the broader sense of how an organisation ensures its strategic direction actually shapes its operations. A strategy that cannot be referenced to evaluate a decision is not governing anything; it is communicating a direction that may or may not be followed.
Why values without principles are decoration
The most predictable failure in values design is abstraction. A value that sounds meaningful but cannot evaluate a specific decision provides no governance whatsoever. “We value transparency” is not a governance tool. It cannot help anyone decide whether to raise a project risk with a client before it becomes a problem, or how to handle a situation where what is commercially convenient conflicts with what is accurate.
What makes a value operational is pairing it with a strategic principle — a statement of what the value requires in practice.
Amalia Technologies defined five values, each with an explicit principle. “Simplicity by Design” carries a principle that functions as an active filter: it drives decisions about which tools to adopt, which processes to formalise, and where to deliberately resist complexity. It gives someone a basis for saying “this proposed approach is inconsistent with our simplicity principle” rather than just “this feels too complicated.” “Structure and Organisation” is paired with a principle that treats clarity of process not as bureaucratic preference but as the precondition for real empowerment — because ambiguity forces people to escalate or guess rather than act.
The remaining three values — Respect and Safety, Creative Exploration, and Ownership and Empowerment — follow the same structure. Each names what the organisation believes; each pairs it with a principle specifying what that belief produces in practice.
Writing this is uncomfortable. It requires being prepared to say, at some later point, “that decision was inconsistent with this principle.” That is precisely what makes it useful. A values framework that no one is prepared to enforce against a real situation is not a governance framework.
The strategic cascade
A values framework alone is still incomplete. The second half of the architecture is the cascade: the structure that takes long-term direction and translates it into quarterly work.
Amalia’s cascade moves from vision and mission through values and strategic principles to three long-term goals on a three-year horizon. Financial stability through portfolio diversification. An organisational structure that genuinely supports employees. Sustainable growth through deliberate exploration of aligned opportunities. Each goal is mapped to the supporting values, creating a traceable line from stated purpose to outcomes being actively pursued.
Annual objectives are defined within each long-term goal and managed as OKRs — Objectives and Key Results. Each objective has SMART key results attached: specific outcomes, not activity counts, with defined timeframes and measurable targets. Tasks beneath each key result are tracked through the same project management processes used for client work. This is the structural choice that separates a strategy people act on from one they revisit annually: making internal strategic objectives subject to the same planning discipline and progress accountability as any other project. There is no operational reason to treat them differently. Most organisations simply do not apply the same rigour.
Corporate governance and QMS integration
The choice that distinguishes a strategy framework from a strategy document is whether it integrates with the quality management system or sits alongside it.
Running strategy and QMS as parallel systems creates two governance structures, two review cycles, and two sets of objectives. In most small organisations, one gets maintained and one gets filed. In larger ones, it creates a situation where quality objectives are developed by the quality function and strategic objectives by leadership — connected loosely if at all.
Making the strategy framework the top-level governance document for the entire QMS means quality objectives flow from strategic objectives rather than being generated independently. The QMS has genuine purpose because it serves the strategy; the strategy has operational teeth because it governs the processes that govern the work. Every QMS document — the Quality Manual, each SOP, each work instruction — traces back to the framework and derives its scope from it.
The framework also addressed statutory corporate governance obligations that most strategy documents ignore: the formal structures of a German GmbH, including shareholder decision rights, managing director authorities, and the specific documentation requirements for certain resolutions under German commercial law. Embedding these in the top-level governance document rather than treating them as a separate legal matter keeps the architecture coherent. Statutory compliance is not an afterthought to governance; it is part of it.
For life sciences and regulated industry organisations — whose clients and counterparties include regulators, auditors, and partners with their own documented governance requirements — having strategy and quality governance integrated into a single traceable structure provides a cleaner audit surface and a more defensible account of how decisions are made — and, as a side effect, lower administrative overhead and costs than maintaining two parallel governance systems.
Where things stand
The strategy framework is at version 1.0. The OKR register, roles and responsibilities matrix, and company glossary are in place. The SOP for managing enterprise strategy has been drafted, defining how the framework is reviewed, updated, and cascaded into operational planning.
The first quarterly management review has been completed. The processes behind managing enterprise strategy are being actively built. The OKR cycle is running.
What has not happened yet is a complete annual cycle. Without a full year of objectives, measurement, and strategic review, the framework has not yet proven that the design produces the alignment it is intended to create. The architecture is sound; how well it performs under a full operating year will determine where adjustments are needed.
The practical takeaway
Two things transfer to any organisation designing or rethinking its strategy framework.
The first is that values governance requires specificity that most organisations avoid. Writing values is relatively easy. Writing the strategic principle that makes each value actionable — and being prepared to apply it to real decisions — is the harder and more important work.
The second is that governance integration is a structural choice with lasting consequences. A strategy document that lives separately from the quality system, the project governance, and the planning cycle depends on individual initiative to have any effect. A strategy framework that is structurally integrated into those systems governs whether or not anyone remembers to apply it manually. For organisations operating in regulated environments where governance traceability matters, the distinction is not cosmetic.
Amalia Technologies works with life sciences and regulated-industry organisations on corporate governance design, programme governance, and the structural integration of strategy and quality management. Learn more about Programme Governance.
