How To Dev - Innovation Matrix by domain, and Entity identification

Figure: Example of Innovation Matrix

 

Starting from the development of a different Innovation Matrix for each domain: mobility, energy, parking, gov services, etc. (see the image above). The goal is to identify the current practices, their problems, the possible improvements foresee, eventual criticisms, and also the assess the risks connected to the application of changes to present modalities of doing the activities, and thus the effective pros and cons of any possible or requested change. The approach is a specialization of the Innovatrix of [ https://timreview.ca/article/1225 ]. Details on the compilation of the Innovation Matrix can be recovered from  https://www.snap4city.org/download/video/course/sys/ and its detailed versions presented at the Snap4City workshops.

As a first step the where for each column (of the last tree on right in table of the figure above) the main Actors are identified. For example: operator, city users, decision makers, etc. The compilation can be performed during a workshop in live or on some open board online, such as MIRO platform. The workshop should involve: Experts of the domain specific, Experts of different customers segment, Operative people, ICT people, Decision Makers, etc. The Innovation Matrix table is compiled by using stickers during workshops in which the moderator is pushing the group to answers to the following questions.

• Current State           
  
  • Needs  
    • How do we prioritize these needs?
    • How many times per day they need those services?
  • Current Practices           
    • What are the current practices to satisfy the above needs?
    • What are the pains/cons of the current practices?
    • What are the gains/pros of the current practices?
    • Is there any signage about the need to change current practice?
  • Value proposition (current)            
    • How much (measurable) is used the current solution?
    • Why is it used or so diffused?
• Future State             
  
  • Value proposition (Future)             
    • What could be accepted, what it should be available with the new solution with respect to the current, … the benefits?
    • What (measurable) impact would you need for the customer segment?
    • Which could be a measurable index of success, with reference value?
  • Solution             
    • What are the components of a possible solution, app, Dash, etc.?
    • How do these components differ for the different customers segments (which kind of profiling)?
  • Value Capture
    • What value (non-monetary/monetary) do you receive in return from customer segment?
    • Short vs long term value capture?
  • Key Partners
    • Who are your key partners (unit, team, subcategory)?
    • How to interact with stakeholders (how do you plan to promote, make evident, make it available and accepted)?
• Barriers
  
  • What are the barriers for adoption, usage?
  • Is a workaround possible?
  • How will we work around these barriers?

As a result, for each domain, that means for each Innovation Matrix table, a document section has to be created according to the following schema (for each Actor or for the first consumptive column):

• Target Segments:
  
  • users and their characterization.
• Benefits for identified user categories.
• Actions towards them and the possible solutions
  
  • Variations on Actions.
• Other Actions to be verified: non clear aspects if any, verification needed to finalize the actions to be performed.
• Data Identified:
  
  • the data that could and would be the first to be ingested,
  • understood and verified if they are suitable for the purpose.
  • Any missing data?
• Means of Communication with user categories for promoting the new approach.