Innovation isn't a mindset. It's a skill. And skills can be taught

Introducing a new Innovation Skill Framework: 5 principles for disciplined entrepreneurship in practice

Most organisations that say they want to innovate mean it. The problem isn't intent. It's that those same organisations rarely clearly define what innovating well actually looks like — what skills it requires, how you develop them deliberately, and how you know when someone is getting better at it.

That gap is what the Innovation Skill Framework was built to close.

I developed and launched the framework inside a large UK Government Department, where the stakes are real, the constraints are significant, and the definition of success isn't profit — it's genuine public value. The framework was designed to give practitioners a meaningful development path, and give leaders the language and tools to build innovation capability intentionally, rather than hoping it happens.

It had to be practical, jargon-light, and genuinely useful to both the individual trying to grow and the manager trying to support them.

Built around principles, not methods

The framework isn't built around tools or techniques — design thinking, lean startup, agile — though all of these have a place within it. It's built around 5 core principles: the beliefs and behaviours that, when genuinely practised, most reliably determine whether an innovation succeeds or fails.

A framework built around 30 principles is a wishlist, not a framework — and wishlists don't change behaviour

We started with a longlist of over 30 candidates. Everything from creativity and storytelling to systems thinking and resilience. All important. All, in some sense, relevant. But a framework built around 30 principles is a wishlist, not a framework — and wishlists don't change behaviour.

The filter we applied was ruthless: which principles are most consistently absent in innovation work? Which ones, if skipped, most reliably cause projects to fail? Which are genuinely non-negotiable? 

Five survived.

1 Customer empathy

Know who your customers are and understand what they're genuinely trying to achieve. The evidence we look for: that you've actively and intentionally built empathy with real people, and used what you learned to shape what you design — not just consulted them at the end.

2 Mission model thinking

Think beyond the product or service to the whole system around it — what value it creates, what it takes to deliver it, and whether it stacks up. The evidence we look for: that you've considered desirability, feasibility and viability together, not in isolation.

3 Assumptions prioritisation

Don't try to answer everything at once. Identify your assumptions, work out which carry the most risk, and tackle those first. The evidence we look for: that you've made deliberate choices about which questions to answer when — focusing energy on what matters most, not what's easiest.

4 Experimentation & iteration

Make decisions based on the results of honest experiments, not instinct or seniority. The evidence we look for: that you've run experiments with clear hypotheses and learning goals, and iterated your design based on what you actually found.

5 Measuring impact

Prove it works before you scale it. The evidence we look for: that you've measured the impact your innovation creates early, tried different ways to achieve it, and only invested in scaling what has genuinely been shown to deliver worthwhile results.

Why these five?

Most organisations don't have an ideas problem. They have a turning ideas into real measurable impact problem.

Notice what isn't on the list. Ideation — brainstorming, creative thinking, generating ideas — didn't make the cut. Not because it isn't valuable, but because it already gets all the attention. Most organisations don't have an ideas problem. They have a turning ideas into real measurable impact problem. These five principles are the ones that address that gap.

They're also the ones that tend to be most counter-cultural. Measuring impact before scaling feels uncomfortable when there's pressure to move fast. Prioritising assumptions requires saying no to interesting questions. Customer empathy takes time that busy teams are reluctant to spend. But that discomfort is often a signal that the principle is doing its job.

The principles that challenge how your organisation normally works are usually the ones most worth holding onto.

Subscribe to be the first to receive the full report

This post is an introduction. The full framework, including skill levels, progression descriptors, evidence guides, and the design principles that shaped every decision, will be published as a complete report. I'll be sharing it here first. Subscribe to get notified the moment it's available.

In the meantime, I'm sharing the journey in more detail on LinkedIn: the decisions behind the design, the lessons from launching it, and the thinking that didn't make it into the final document. If you work in innovation, in government or elsewhere, I'd love to have you in that conversation. Follow or connect here.