Figure 11: Agile adaptive roadmapping Conclusions The conclusions from Phaal and O’Sullivan are: • • • • • • There is value in using common frameworks, terminology, and methods or both public & private sectors Methods always need to be customised to context, including sector vs firm Systems-based roadmapping framework allows for ‘zoom in & zoom out’, enabling alignment, integration, and synchronisation Understanding pathways and associated enablers and barriers helps to identify scope for government support The explicit time dimension in roadmaps allows system dynamics (including policy) to be anticipated An adaptive / agile / flexible approach is recommended to accommodate uncertainty and enable learning Yuta Hirose intervention included: A definition of roadmap (a way of thinking) “A way of thinking to decompose issues by using a multi-layered structure consisting of demand (why), value (what), supply (how), and timescale (when and where) to derive solutions and map out routes for realization.” Industry 4.0 to realise society 5.0 (I4.0 is a how, S5.0 a why) From the Japanese perspective, following the structure of roadmapping, I4.0 is a “how” and the “why” is a super-smart society that they define as Society 5.0 (see figure below). 16

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents