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.
AI-proposed rows can be reviewed in the incoming panel before acceptance. If the content already belongs to a specific method, such as PESTLE or a Decision Matrix, add it directly there when practical. Table Input is useful when the reusable table itself has a purpose.
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.
Original InnovationFlow illustration. Example values and software behaviour are explained in this guide; method sources are listed below.
Understand the method
The parts in plain language
Prepare the source
Use one row per item, clear headers, consistent types and stable identifiers. Remove accidental formatting and explain coded values.
Illustrative example
Use ISO dates and a documented status list rather than mixed free-text dates and colours.
Map fields
Connect source columns to target fields based on meaning. Confirm required fields, units, defaults and how unmatched values are handled.
Illustrative example
Map “initiative lead” to owner only after confirming it identifies a person rather than a department.
Review candidates
Preview validation errors, duplicates and relationships before records become accepted tool content.
Illustrative example
Rows with unknown parent identifiers enter a review queue instead of silently losing the link.
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 source rows and headers, or define the structured notes you want to capture.
- 2
Import data or review AI-proposed rows in the incoming panel.
- 3
Check full text, source context, field types and identifiers.
- 4
Map accepted rows to the intended downstream tool and review that handoff.
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.
Practical interpretation guidance from InnovationFlow. Refer to the method sources below for the underlying approach.
What a useful output looks like
Common pitfalls
- A successful import does not guarantee correct semantic mapping.
- For method-specific content, add it directly to the relevant tool where possible. Use Table Input when a reusable table is useful.
- Keep original documents available: selected rows do not carry every page of source context.
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.