Your board keeps asking for more new products, faster, with less waste. Meanwhile the teams doing the work are drowning in ideas, workshops and tools that don’t connect. If that sounds familiar, ISO 56002 can help you impose just enough structure to make innovation repeatable without smothering it.
As auditors, we often meet firms that are genuinely inventive but can’t show how they choose bets, manage risk or learn across projects. This guide translates the standard into practical steps, explains how assessment works, and sets out what evidence gives confidence to an external reviewer.
What ISO 56002 actually asks you to build
ISO 56002 is guidance for an innovation management system, built on the same high-level structure used by other ISO management standards. It doesn’t dictate specific methods. Instead, it expects you to define and run a coherent system that fits your context and strategy.
- Context and ambition: Clarify why you innovate, where, and the level of risk you will tolerate.
- Leadership and roles: Assign accountability for innovation outcomes and governance, not just workshops.
- Planning and portfolio: Set criteria to select, prioritise and stop initiatives aligned to strategy.
- Support: Provide skills, data, budget rules and a framework for collaboration and IP.
- Operation: Run a clear opportunity pipeline from discovery to scaling, with decision gates.
- Performance and learning: Measure outcomes, learn systematically and improve the system itself.
In practice, this often means codifying practices you already use, joining them up, and agreeing who makes which decisions at each stage. For example, a manufacturer we assessed had great hackathons and a busy lab, but no criteria for moving from pilot to scale. Their system formalised those criteria and reduced late-stage surprises.
Certification, assessment and what’s realistic
A straight word on certification. ISO 56002 is a guidance standard, not a requirements standard like ISO 9001. There is no widely recognised accredited certification scheme dedicated solely to ISO 56002 at present. However, organisations can still seek an independent conformity assessment against the guidance, and many integrate ISO 56002 practices within their existing certified systems.
At UKCTL we provide a structured assessment and, where the system meets the guidance, issue a certificate of conformity to ISO 56002 on a non-accredited basis. Some clients combine this with accredited certification to related standards (e.g. quality or information security), so the governance and improvement mechanisms are consistent. If you want to explore that route, you can learn more about our ISO 56002 certification approach and how it fits with your current system.
What good looks like: practical elements to put in place
Ambition, guardrails and governance
Set a plain-language innovation ambition your teams can repeat. Define guardrails: target domains, risk appetite, budget thresholds. Establish a governance rhythm with inclusive decision forums that don’t become theatre.
- Publish selection criteria that balance strategic fit, desirability, feasibility and viability.
- Record decisions and assumptions at each gate to aid learning and accountability.
- Assign an executive sponsor for the system, not just individual projects.
Opportunity pipeline with real gates
Map a simple end-to-end pipeline. Discovery, concept, validation, pilot, scale. Keep it light but real. Each gate should trigger a decision, not a tick-box ceremony.
- Define evidence expectations for each gate (customer insights, technical tests, unit economics).
- Use short experiment plans and success criteria rather than long business cases too early.
- Stop or recycle ideas openly to protect capacity and avoid zombie projects.
Capabilities, tools and enabling services
Don’t leave people to improvise. Provide the minimum viable toolset and support services.
- Create a playbook covering methods your teams actually use and understand.
- Offer coaching and design/data support for early-stage teams to speed up learning.
- Clarify IP, vendor and data policies so compliance doesn’t stall experiments.
Measures that matter
Balance activity measures with outcomes, and link them to decisions. Vanity metrics will sink you in an audit and in management review.
- Track pipeline health (throughput, time-in-stage, kill rates) to manage flow.
- Monitor outcome metrics (adoption, margin impact, risk reduced) once scaled.
- Review learning quality by checking documented assumptions and experiment results.
How to prepare: a staged, workable plan
If you’re starting from scratch, resist grand designs. Build a backbone quickly, then iterate. A three-phase plan works for most organisations.
- Baseline and scope: Map current practices, pain points and overlaps with existing systems (e.g. quality, project, portfolio management).
- Design the lightest system that could work: Define ambition, governance, pipeline, roles and key artefacts; pilot them in one unit.
- Roll out and evidence: Extend to other units, refine measures, and embed reviews; keep artefacts consistent and retrievable for assessment.
Assign a coordinator to keep documents and evidence in one place. It can be a SharePoint site, a wiki or your project tool, so long as you can show traceability from idea to decision to outcome.
Evidence auditors look for
External reviewers don’t expect perfection. We do look for coherence, consistency and learning. The following artefacts, if current and used, help us see the system at work.
- A documented innovation policy/ambition aligned to strategy and context.
- Defined roles and responsibilities, including governance forums and decision rights.
- A clear pipeline map with gate criteria and templates for key artefacts.
- Examples of opportunity records showing discovery work, assumptions and tests.
- Portfolio overviews linking initiatives to strategy and resource allocations.
- Records of gate decisions, including stopped initiatives and rationale.
- Training or coaching materials and evidence of participation.
- Supplier and partner arrangements relevant to experimentation and scaling.
- Metrics dashboards and management review minutes with follow-up actions.
- Improvement logs showing changes made to the system based on lessons learned.
We also sample real projects. Expect us to trace two or three initiatives from idea to current status, checking whether the stated process matches reality.
Common pitfalls and how to avoid them
We see patterns across sectors. A few to watch for, with simple fixes.
- Process theatre: Templates exist but are not used; solve this by piloting with one live team and pruning unnecessary artefacts.
- No stopping power: Projects rarely end; add explicit stop criteria and make ending a project a positive outcome when learning value is captured.
- Isolated innovation: Innovation sits outside business-as-usual; wire governance into budgeting and product roadmaps so scale-up is possible.
- Overly rigid gates: Heavy documentation too early; set evidence ladders that increase with maturity, not at day one.
- Metrics without decisions: Reports are produced but unused; make metrics drive specific portfolio and resource decisions, or drop them.
How an ISO 56002 assessment typically runs
Because ISO 56002 is guidance, the assessment focuses on whether your system is appropriate to your context and consistently applied. A typical sequence looks like this.
- Readiness review: A short, remote check of scope, key documents and planned evidence.
- Stage 1 assessment: Documented system review and interviews to confirm design, scope and implementation status.
- Stage 2 assessment: On-site or virtual sampling of real initiatives, governance meetings and records to verify effective operation.
- Findings and actions: Clear nonconformities or improvement opportunities with agreed timelines.
- Ongoing surveillance: Periodic reviews to check the system is maintained and improved as your context changes.
Timing and assessment effort depend on your size, scope and how distributed your innovation activity is. Organisations with a single central team can be assessed faster than those with multiple business units and external partners. Agree the scope early and avoid making everything a pilot at once.
Making it stick
The best systems start small, prove value and then quietly become part of how the business runs. Treat ISO 56002 as a way to codify good habits and stop poor ones. Keep the pipeline simple, the governance honest, and the measures tied to decisions. Review the system quarterly, not just before an assessment, and make incremental adjustments rather than big-bang redesigns.
If you’d like to talk through where you are and what an assessment would involve, the team at UKCTL would be happy to help. No hard sell. Just a practical conversation about scope, timing and what evidence you already have.