Process, methods, and dataflows — why splitting them is what keeps practitioners stuck, and why the Innovation Professional series builds everything on the unit that holds them together.
Most frameworks that try to explain innovation break the work at the wrong grain. Design Thinking, for all its pedagogical virtues, stops at five phases that are each larger than a single person's day. The ISO 56000 family, for all its systematic ambition, stops at management-system clauses that are larger than a single team's quarter. Between the two extremes — the workshop and the audit — the actual work disappears.
The Innovation Professional series makes the opposite bet. We break innovation into the smallest unit that still does real work, and we build the rest of the framework by stacking and connecting those units. We call that unit the process–methods–dataflow triple. It is the atom of the series.
Every capability in the Innovation Lifecycle Framework — from weak-signal scanning to portfolio review — decomposes into one or more of these triples.
A triple that has only two of these three is not a unit of innovation work. It is a fragment. Methods without a surrounding process are recipes without a meal. Processes without methods are arrows without a pen. Dataflows without either are exhaust.
Breaking the work at this grain does three things that coarser frameworks cannot:
It makes individual work legible. A junior analyst's Tuesday afternoon is a small number of triples: run a scan (process) using PESTEL (method) producing a signal list (dataflow). That sentence is also the unit of training, the unit of coaching, and the unit of review.
It makes value chains visible. Stack triples end-to-end and a value chain appears — each step providing a concrete, named increment of value to the next. "Discovery" is no longer a phase; it is eleven triples whose outputs become inputs for Delivery. When a team asks where does our work stall?, they can point to the exact triple.
It maps cleanly to enterprise architecture. The series uses ArchiMate as its structural spine, not as jargon for its own sake, but because ArchiMate's layered vocabulary already distinguishes motivation, behaviour, and information. In our model: motivation cascades into strategy, strategy guides behaviour (the processes and methods), and behaviour consumes and produces information (the dataflows). The atomic unit sits at the behaviour layer and threads the others through itself.
Once innovation work is described as triples, several practical things follow. Review becomes structural — a team can ask whether every triple has explicit inputs and outputs, and whether every output is consumed by a downstream triple or is a terminal deliverable. Method substitution becomes safe — a new interview technique slots into a triple without disturbing the process or the dataflow around it. Governance becomes operational — a quality gate is a contract on a specific dataflow, not a slogan in a policy document. Teaching becomes sequenceable — students learn one triple at a time, with the full shape of their work visible from the first week.
We give up the pleasing roundness of five-phase diagrams. The landscape of innovation described this way is less mythic and more topographic. It has many more nameable parts. It resists being captured on a single slide. This is, we argue, a feature: innovation is not simple, and frameworks that present it as simple teach a confidence that collapses on first contact with a real organisation.
The atom, in other words, is the concession the series makes to how the work actually feels from the inside. Everything else in the series — the capability model, the value chains, the governance architecture, the learning platform — is built of these atoms and their bonds.
Hansen & Kaskenpalo · April 2026