Practice note · AI companion · human control

What an integrated AI companion should do in strategy work

A practical guide to using AI across connected strategy work without hiding the method, weakening evidence or outsourcing strategic judgement.

InnovationFlow Research & Practice4 September 20269 min read

The strategic value begins beyond a standalone chat

A general-purpose chat can draft text, summarise a document or answer a question. Strategy work is harder because each activity depends on context created elsewhere: the purpose of the process, accepted evidence, earlier choices, the method being used, the people involved and the decision that must follow.

Research on roadmapping systems frames roadmapping through interconnected purpose, process, structure, participation and implementation. An AI companion becomes more useful when it can work within those connections rather than receiving a fresh, manually assembled briefing for every prompt. [1]

That distinction separates an integrated companion from a generic writing assistant. The companion should understand where the team is in the process, what information has already been accepted and which method or decision boundary applies next.

Five useful jobs for an AI companion

The most defensible role is assistance with process, structure and continuity. The companion should reduce the friction around strategic work while leaving the evidence, interpretation and decision visible to the people responsible for them.

  • Design the flow: translate an objective into a proposed sequence of methods and explain why they fit.
  • Explain the method: provide contextual guidance, examples and useful questions where the work is happening.
  • Work across the workspace: summarise evidence, compare perspectives and identify gaps or duplication across connected tools.
  • Create structured proposals: place candidate trends, SWOT items, ideas, relationships or roadmap actions in the relevant tool.
  • Support continuity: prepare reviews, surface changes and help the team reconnect decisions to their original rationale.

Explain the method without becoming the authority

Management tools are valuable because they structure attention and discussion, not because completing a template guarantees a good decision. Research on toolkit design emphasises human-centred, modular, visual and facilitated approaches that can be configured for the problem and context. [2]

Work on self-facilitating templates also shows how guidance can be embedded into a working medium. AI can extend that idea through explanations, examples, checks and suggested next steps. It should still expose why a method or sequence is being proposed and allow an experienced facilitator to change it. [3]

A companion should therefore say what a method is for, what information it needs, what a useful output looks like and where the common traps are. It should not present generated content as evidence or imply that following a framework removes the need for judgement.

Keep proposals separate from accepted strategic work

Fluent output can look more certain than it is. If an AI-generated item silently becomes part of an organisational record, later users may not know its source, who reviewed it or why it influenced a decision. Integration without governance can therefore make the strategy less trustworthy rather than more coherent.

The NIST AI Risk Management Framework treats governance as a cross-cutting function and emphasises documented roles, responsibilities and processes for managing AI risk. In strategy software, a practical expression is to treat generated work as a proposal until an authorised person accepts, edits or rejects it. [4]

  • Identify what the AI proposed and keep its status visible.
  • Apply the same role and workspace permissions used for human contributions.
  • Preserve relevant source context and the route into downstream tools.
  • Record who accepted or changed material work.
  • Let people reject a suggestion without disturbing the underlying record.

How this boundary works in InnovationFlow

InnovationFlow uses one integrated AI companion across the connected workspace. It can read relevant workspace context, help create and connect a strategy flow, explain methodology, summarise work, identify gaps and add structured proposals to the appropriate tools.

Proposed work enters the same governed workflow as other contributions. Facilitators review what should become part of the strategic record, and workspace permissions continue to apply. Approved external AI clients can use the same structured tool surface through the Model Context Protocol connector.

These are current product capabilities, not claims that AI produces better strategies by itself. The value is lower process friction, stronger continuity and clearer structure while accountable people retain the strategic decision.

Prompts that test whether the companion is truly integrated

A useful product demonstration should use connected work rather than a generic brainstorming prompt. The following requests reveal whether the companion understands the process and can act within appropriate boundaries.

  • Create a connected flow from market signals to roadmap initiatives and explain why you chose each method.
  • Explain how to turn these SWOT factors into defensible strategic options using TOWS.
  • Summarise the accepted evidence in this workspace and identify important gaps before the roadmap review.
  • Propose roadmap items from the selected strategic choices, but leave them for facilitator review.
  • Show which assumptions and upstream decisions support this initiative.

A practical evaluation checklist

When evaluating AI in strategy or roadmapping software, ask for one end-to-end demonstration. Start with a strategic objective, build a small flow, work with real evidence, create a proposal, review it and follow an accepted item into the roadmap.

  • Context: can the AI use connected workspace information without manual copy-paste?
  • Method: can it explain why a tool or sequence fits the objective?
  • Structure: can it create usable items in the correct tools rather than only returning prose?
  • Traceability: can users follow a proposal back to its source and forward into a decision?
  • Control: do permissions and explicit human review apply before material changes are accepted?
  • Continuity: can the AI help with later reviews and changes without losing the earlier rationale?
  • Openness: can approved external AI clients work through the same governed interface when needed?

References

  1. [1]Phaal, R., Chaskel, C., Gonzalez Nakazawa, R. and Ross, J. (2024). Roadmapping Roadmapping: Strategic planning for roadmapping systems. Frontiers of Engineering Management, 11(3), 516–527. Source ↗
  2. [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 ↗
  3. [3]Phaal, R., Kerr, C., Ilevbare, I., Farrukh, C., Routley, M. and Athanassopoulou, N. (2016). On self-facilitating templates for technology and innovation strategy workshops. Centre for Technology Management Working Paper Series, No. 8. Source ↗
  4. [4]National Institute of Standards and Technology (2023). Artificial Intelligence Risk Management Framework 1.0. NIST AI 100-1. Source ↗

Practitioner support

Talk to an experienced practitioner

Ask about roadmapping, facilitation or applying a method in your organisation. Your question goes directly to the InnovationFlow team.

Sent securely to hello@innovationflow.app.