From management tools to a connected digital innovation toolkit

Strategy and innovation teams rarely suffer from a shortage of frameworks. SWOT, scenarios, roadmapping, portfolios, value chains, capability maps and hundreds of specialised matrices are readily available. The difficult work is deciding which perspective the problem needs, how several tools should fit together and how their outputs should influence an actual decision.

Phaal, Farrukh and Probert catalogued more than 850 predominantly matrix-based management tools and classified recurring structures. Their work was motivated partly by the proliferation problem: many named tools vary in presentation while performing related cognitive functions, and practitioners receive limited guidance on quality, selection, application and integration. [1]

That distinction is important for digital innovation software. A navigation menu containing fifty tools demonstrates breadth. It does not demonstrate that the organisation has a coherent toolkit. Coherence comes from purpose, selection, configuration, sequencing, facilitation and the movement of information between activities.

The early catalogue work sought generic structures beneath named management tools. This matters because generalisation makes comparison and reuse possible. Instead of treating every published matrix as a unique method, a toolkit designer can ask what function the structure performs and what information it needs. [1]

Phaal, Kerr, Oughton and Probert then proposed a workshop-based modular toolkit for strategic technology management. Their starting point was that individual approaches offer particular perspectives on understanding, analysis, decision and action, but frequently overlap and have unclear interfaces. Functional modules could be combined to address different management challenges without inventing a monolithic process for every situation. [2]

Kerr, Farrukh, Phaal and Probert developed the argument into seven principles for industrially relevant toolkits. The paper drew on more than 200 research and commercial engagements and emphasised tools that are human-centric, workshop-based, neutrally facilitated, lightly processed, modular, scalable and visual. Its practical premise was to start small and iterate fast. [3]

The principles were not written as software requirements. Read carefully, however, they expose why digitising a paper template is not enough. The tool must support people doing difficult strategic work together, and the toolkit must remain configurable to the decision and organisational context. [3]

Roadmapping has an unusual integrative property. Its time axis and layered architecture can place evidence, strategic drivers, products, technologies, capabilities, initiatives and resources into a common prospective frame. Other tools can help populate a layer, challenge a relationship or resolve a choice, while the roadmap synthesises the wider narrative. [7]

Kerr, Phaal and Thams made this proposition explicit through a collaborative design engagement with the LEGO Group. Their 2017 conference paper presents roadmapping as a platform for developing management toolkits and reports a prototype in which related tools were configured around a roadmap hub. The case demonstrates a design possibility in one organisational setting, not a universal result for every toolkit. [5]

Related research on customising and deploying roadmapping at the LEGO Group reinforces the need to adapt a reference process to organisational context. A baseline can accelerate initiation, but local language, roles, processes and constraints determine whether the approach becomes usable practice. [6]

Our interpretation is that a digital toolkit should give each management activity a focused working surface while preserving stable identities and relationships underneath. A trend accepted in environmental scanning should not become an unrelated sentence when it enters SWOT. A strategic response selected through TOWS should not lose its rationale when it becomes a business aim or roadmap item.

This creates a distinction between interface modularity and information continuity. Users may need different canvases, tables, prompts and visual structures for different cognitive tasks. The organisation still needs one connected account of where an item came from, how it changed, what it influenced and who made the decision.

Phaal, Chaskel and colleagues describe roadmapping systems in terms of interconnected purpose, process, structure, participation and implementation. For digital design, that suggests the workflow itself should be configurable and inspectable. It should be possible to see not only the content in each tool, but how tools form a system for a particular strategic purpose. [8]

Templates can carry some of the guidance that a facilitator would otherwise provide. Work by Phaal, Kerr and colleagues on self-facilitating templates explores how visual prompts and embedded instructions can help groups organise strategic discussion with less intervention. [4]

Digital software can extend that idea through contextual explanations, walkthroughs, examples, validation and suggested next steps. It can also go too far. Guidance becomes counterproductive when it forces an inappropriate sequence, supplies content as if it were evidence or makes the interface the authority in a contested decision.

A strong digital toolkit therefore supports different modes. New users can receive more scaffolding; experienced facilitators can configure or reduce it; contributors can understand the immediate task without learning the whole system. The goal is not a self-driving strategy process. It is a lower-friction environment for responsible human judgement.

AI creates new possibilities for a modular toolkit. It can help a practitioner translate a management question into a proposed sequence of tools, locate relevant evidence, identify duplicated items, suggest links and summarise gaps across several working surfaces. These are useful forms of assistance because the toolkit-selection problem itself creates cognitive load.

The same capability creates governance risks. A generated workflow can look authoritative without explaining why its tools were selected. A generated item can travel through several modules until its uncertain origin is forgotten. The platform should expose the proposed logic, identify AI contributions and require people to accept decisions that affect the organisational record.

Do not evaluate only the number of frameworks. Choose a real strategic question and ask the vendor to configure a small toolkit around it. Follow evidence into analysis, a decision and a roadmap. Change an assumption, involve a second team and inspect whether the resulting history and relationships remain understandable.