What an innovation management system is
An innovation management system is the set of decisions, roles, measures and governance that determines which opportunities an organization pursues, what it funds, what it stops, and how it establishes whether any of it produced value.
It is not software, and it is not a process document. It is the management structure around innovation work — the part that decides, rather than the part that creates.
ISO 56001 is a description of what that structure needs to contain: leadership responsibility, strategy connection, portfolio decisions, capability, and measurement. Read as requirements, it is a list to comply with. Read as a specification, it is a design brief.
Why the compliance reading disappoints
When innovation spend produces uncertain returns — some projects deliver and others do not, for reasons not well understood in advance — that is the problem organizations bring to the standard.
A compliance approach documents the processes that currently exist and demonstrates that they meet the requirements. It is entirely possible to do this accurately while leaving the underlying decision-making unchanged. The documentation describes the system; it does not redesign it.
The distinguishing question is what changed. If the same projects would be funded, stopped and measured the same way after certification as before it, the exercise produced a document.
What the system actually governs
Four things, each of which is a management decision rather than a creative one.
Strategy connection. What links a funded project to a stated business priority — and what happens to a proposal that has no such link.
Portfolio decisions. Who decides what is funded, at what level of commitment, against what criteria. Including, critically, what causes something to stop. A useful test: can anyone describe how work ends, not only how it starts?
Capability. What the organization must be able to do itself, and what it will source externally — with a stated intention about which of those changes over time.
Measurement. What result the work is meant to produce, defined before it starts, and distinguishing activity from outcome.
An organization that has designed these four has an innovation management system. Whether it seeks certification is a separate decision.
Who does what in certification
Worth stating plainly.
- A certification body audits an organization against the standard and issues certification. It must be independent of the organization it audits.
- A consultant helps an organization design, build and operate the management system. A consultant cannot certify.
- The organization owns the system, operates it, and is accountable for what it produces.
Bold Group Thailand is not a certification body and does not issue ISO 56001 certification. We help organizations build and operate the management system the standard describes. Certification, where an organization chooses to pursue it, is carried out by an accredited body independently of us.
Certification and business value are different objectives
They are compatible, and they are not the same, and confusing them is what produces the disappointing outcome.
Certification demonstrates to third parties that a management system meets a recognised specification. It is useful where customers, regulators or partners require that assurance.
Business value comes from the decisions the system changes — which work gets funded, what stops sooner, what is measured.
An organization can achieve the first without the second. It cannot achieve the second by pursuing the first. Deciding which one you are actually buying, before starting, determines whether the work is worth doing.
A practical sequence
Establish what the current system decides. Before designing anything, document how projects are actually funded and stopped today. This is usually different from the documented process, and the difference is the finding.
Clarify funding and stopping decisions. Where funding and stopping decisions are unclear, start by defining who makes them and against which criteria. Use those decisions to identify which other parts of the management system need to change.
Run it on real decisions. A management system is only testable on live funding choices. Designing it against hypothetical projects produces a design that has never been contradicted by anything.
Decide about certification separately, and later. Once the system operates, certification becomes an assessment of something real. Pursued first, it shapes the design toward auditability rather than usefulness.
Where this does not apply
Where an organization genuinely needs certification for a commercial or regulatory reason and has a working management system already, the compliance route is the correct one and this argument does not apply. The distinction is whether you are documenting something that works or hoping the document will make it work.