InnovationFlow product capability
Table Input
Table Input turns spreadsheets, CSV files and structured notes into mappable strategy items.
Beginner-friendly guide · 4 min read
What Table Input does
Table Input turns spreadsheets, CSV files and structured notes into mappable strategy items.
Table Input brings rows from spreadsheets, CSV files or structured notes into a strategy flow. It offers a familiar bridge for teams with useful existing data while making field mapping and review explicit.
The most important work occurs before acceptance: cleaning headers, understanding units, preserving identifiers and deciding what each column means in the target method.
This is an InnovationFlow product capability. It supports the evidence boundary between familiar tabular work and method-specific tools while keeping translation and review visible.[1][2]
This guide describes the role of the capability in a governed strategy process. It does not present the software feature as a named academic method.
Preparation, mapping and review protect meaning as rows enter the flow.
| Title | Owner | Horizon | Status | Meaning check |
|---|---|---|---|---|
| Remote diagnostics | Product | 2027 | Active | Valid |
| Energy reporting | Operations | 2026 | Review | Valid |
| Partner service | Commercial | 2028 | Draft | Map field |
Map column meaning, validate candidates and accept them into the target tool.
InnovationFlow explanatory schematic, synthesised from the method sources[1][2].
Understand the method
The parts in plain language
When to use it
- When a team already has useful spreadsheet or CSV data.
- When structured notes need to feed several strategy tools.
A practical workflow
- 1
Inspect and clean the source rows and headers.
- 2
Import the data and confirm field types and identifiers.
- 3
Map source fields to the intended downstream schema.
- 4
Review candidate items before they become accepted method content.
Fictional worked example
Example: importing a legacy roadmap
This example is illustrative rather than a reported case. A team brings initiatives from an established spreadsheet into the roadmap.
Observation:Dates use three formats and several names are duplicated.
Implication:Standardise dates and add stable identifiers before import.
Observation:The spreadsheet “phase” column mixes status and lifecycle stage.
Implication:Split or review values rather than forcing one target field.
Observation:Invalid dependencies are flagged in preview.
Implication:Resolve them before committing the import.
From analysis to decision
How to interpret the result
- 1Do not confuse successful parsing with correct meaning.
- 2Keep rejected and corrected rows explainable.
- 3Preserve source identifiers for updates and lineage.
The interpretation guidance is an InnovationFlow synthesis of[1][2].
What a useful output looks like
Common pitfalls
- A successful import does not guarantee correct semantic mapping.
- Preserve stable identifiers and source context where available.
References and method basis
- [1]Phaal, R., Kerr, C., Oughton, D. and Probert, D.R. (2012). Towards a modular toolkit for strategic technology management. International Journal of Technology Intelligence and Planning, 8(2), 161-181. Source ↗Peer-reviewed research
- [2]Kerr, C., Farrukh, C.J.P., Phaal, R. and Probert, D.R. (2013). Key principles for developing industrially relevant strategic technology management toolkits. Technological Forecasting and Social Change, 80(6), 1050-1070. Source ↗Peer-reviewed research
This guide synthesises the named sources into practical questions for strategy and innovation work. It does not claim that using a tool by itself produces a successful decision.