The roadmap is not the result

Search and rescue innovation sits across organisations, technical domains and operating realities. At the time described by the case, the RNLI wanted a shared view of how current and emerging technologies could contribute to its lifesaving mission. The challenge was therefore one of strategic coordination: gathering knowledge that no single participant held and turning it into choices that a wider network could understand. [1]

Disclosure: the project was delivered with IfM Engage at the University of Cambridge, with InnovationFlow founder Dr Clemens Chaskel serving as lead consultant. It took place before InnovationFlow was created and is therefore a roadmapping-practice case, not a software case.

This distinction matters. Roadmapping is easily mistaken for the visual artefact at the end. Research instead characterises it as a structured strategic lens: the map matters because the act of mapping makes relationships, timing and strategic intent discussable. [2]

The public case reports that more than 70 organisations participated in RNLI roadmapping workshops and that the approach was transferred into the organisation so further workshops could be facilitated in-house. It also describes subsequent activity across unmanned aerial systems, communications, donations and an emerging digital ecosystem. [1]

One especially instructive outcome concerned man-overboard technologies. The workshop surfaced substantial commercial investment in the field, supporting a decision not to continue investing scarce financial and human resources in a bespoke system. That is a strategic benefit often lost when roadmaps are presented only as plans for doing more: a good roadmap can also provide a reasoned basis for stopping, waiting or partnering. [1]

Workshop-based roadmapping is valuable partly because it brings technical and commercial perspectives into the same structured conversation. The resulting alignment cannot be inferred from a polished chart alone; participation, facilitation and the way disagreements are resolved affect the credibility of the output. [3]

For practitioners, this creates an uncomfortable but productive requirement: a roadmap should record not only what was agreed, but enough of the underlying evidence and rationale to make later review meaningful. Otherwise the organisation inherits an attractive picture whose assumptions are invisible.

Physical cards and large-format charts are effective workshop media because they are immediate and socially legible. They are less effective as durable organisational memory. Once outputs are transcribed into slides or spreadsheets, links between evidence, decisions, ownership and subsequent changes are easily weakened.

Research on maintaining roadmaps treats changing internal and external conditions as a central operational problem. A roadmap represents a view at a point in time; without a review mechanism, it can become obsolete while still looking authoritative. [4]

The RNLI example supports a broad use of roadmapping: not merely scheduling technology projects, but coordinating an ecosystem around mission, uncertainty and choices. The practical design test is whether the approach helps people combine perspectives and then retain enough structure for the strategy to remain usable.

That leads to requirements for any continuing process - whether maintained through meetings, documents or digital systems. It should preserve relationships, distinguish evidence from judgement, make ownership visible, support explicit review and connect strategic intent to resource decisions. These are implications for current practice and digital support, not claims about tools used in the earlier RNLI project.