Design Thinking for Innovation – MindMapping Tool 

 Challenge 

 I am a IT manager , working for a big organization and the challange was to replace our existing   trading system using latest technologies in our front to back IT systems . The application is used   inhouse by trading and sales desks , operations as well as by external clients , such as financial   institutes . The challange was to ensure that migration to the new system covers a smooth user   migration , selection of modern technologies , strategic design decisions and the migration can be   completed within the next 3 years . Since the system to be replaced has been developed and   enhanced over the last 20 years and the migration should be completed within the next 3 years , we   focused on identifying what our key stakeholders within our organization as well as our clients   consider as being most valuable and helpful for their daily work . 

 Selection 

 Since we were in an early state of our design thinking process we used the Mindmapping tool . The   MindMapping tool is a perfect fit , since its strength is in helping us to move from WhatIs to WhatIf .   Exactly what we needed to focus on when looking at how to replace our legacy systems . The mind   mapping tool allowed us to brainstorm requirements for our new product . The goal was not to   replace our system like for like , since here we could simply just summarize a list of functionality that   today ’s systems offers and work on a replacement . Creating a mindmap by involving stakeholders   from different areas allowed us to identify gaps and painpoints , which were not considered or seen   as too complex to accomodate in the legacy systems . 

 Application 

 First I collected the data I wanted to share with the technology and business teams , e.g , the users of   our current systems . The data showed key functionalities , major features we have worked on over   the years , incidents which were raised over the time . I also shares missed or partially implemented   requirements or dropped ideas . Since the system is used by external clients as well , I also shared   what competitors offer . For the non functional requirements I shared technology trends , e.g. the   legacy system was never designed to be supported on mobiles . 

 I laid out all the collected data as printouts , showing screenshots , tables , charts and wireframes of   previous not realised ideas on a table or put them all on a whiteboard . People then walked around in   the meeting room , looked at the presented details and thought about them . Some spent more time   at the screenshots , others were more interested in technology trends . Important is that every   stakeholder is covered and can highlight the items which are most important to them . That s why I   picked users for reviewing the galery from IT ( developers , QA , BA ) , UX design , Product Manager , First   and Second level support , Trading and Sales desk , which gives around 20 people being involved in the   design thinking process . All of them got their sticky notes , walked through the room , reviewed the   data and wrote down their ideas . Those ideas could be realizable or not working . Both was fine at   this stage . Important is that the ideas were helping us to solve our design challange . Once everyone   came up with an ideas , we split the whole group in teams of ~5 people each . The teams started with   separating different topics . The sticky notes within the teams were attached to the topics . Then the 

 next team continued , by sharing the next topic and their sticky notes . Also „ less important “ notes   were captured . 

 Insight 

 By applying the MindMapping tool we have formed topics . Ideas from different areas were   identified . For the gaps in the system that were identified , we can ask easily why we had these gaps ?   Was the old system not able to handle the requirement , or was there not enough time for the   implementation at that time ? Since we were a group of people from different areas the inputs ,   explainations and potential solutions ( What Wows ? ) were very diverse . Also , what about our client ’s   requests ? Has the market changed and do our clients have different needs today , than 20 years ago ?   What role does Social Media play today ? By having the different key stakeholder discussing the varity   of topics we are able to separate the most important ideas to form the requirement set for our MVP   ( Minimal viable product ) . 

 Approach 

 The MindMapping tool was a great approach to collect the right ideas to build a successful MVP . The   ideas we got from this approach depend on the involved key stakeholders . Ensure you have each   area properly covered , so your created Mindmap covers all relevant areas . If you have to many   people from one area , your Mindmap could diverse to much . 


EMAIL: 
ID_NUM: 
NAME_STUDENT: 
PHONE_NUM: 
STREET_ADDRESS: 
URL_PERSONAL: 
USERNAME: 

### Task: You are a PII (Personal Identity Information) Detection. Given a essays written by students, you have to identify ONLY the following:
NAME_STUDENT - The full or partial name of a student that is not necessarily the author of the essay. This excludes instructors, authors, and other person names.
EMAIL - A student’s email address.
USERNAME - A student's username on any platform.
ID_NUM - A number or sequence of characters that could be used to identify a student, such as a student ID or a social security number.
PHONE_NUM - A phone number associated with a student.
URL_PERSONAL - A URL that might be used to identify a student.
STREET_ADDRESS - A full or partial street address that is associated with the student, such as their home address.
### Input: Design Thinking for Innovation – MindMapping Tool 

 Challenge 

 I am a IT manager , working for a big organization and the challange was to replace our existing   trading system using latest technologies in our front to back IT systems . The application is used   inhouse by trading and sales desks , operations as well as by external clients , such as financial   institutes . The challange was to ensure that migration to the new system covers a smooth user   migration , selection of modern technologies , strategic design decisions and the migration can be   completed within the next 3 years . Since the system to be replaced has been developed and   enhanced over the last 20 years and the migration should be completed within the next 3 years , we   focused on identifying what our key stakeholders within our organization as well as our clients   consider as being most valuable and helpful for their daily work . 

 Selection 

 Since we were in an early state of our design thinking process we used the Mindmapping tool . The   MindMapping tool is a perfect fit , since its strength is in helping us to move from WhatIs to WhatIf .   Exactly what we needed to focus on when looking at how to replace our legacy systems . The mind   mapping tool allowed us to brainstorm requirements for our new product . The goal was not to   replace our system like for like , since here we could simply just summarize a list of functionality that   today ’s systems offers and work on a replacement . Creating a mindmap by involving stakeholders   from different areas allowed us to identify gaps and painpoints , which were not considered or seen   as too complex to accomodate in the legacy systems . 

 Application 

 First I collected the data I wanted to share with the technology and business teams , e.g , the users of   our current systems . The data showed key functionalities , major features we have worked on over   the years , incidents which were raised over the time . I also shares missed or partially implemented   requirements or dropped ideas . Since the system is used by external clients as well , I also shared   what competitors offer . For the non functional requirements I shared technology trends , e.g. the   legacy system was never designed to be supported on mobiles . 

 I laid out all the collected data as printouts , showing screenshots , tables , charts and wireframes of   previous not realised ideas on a table or put them all on a whiteboard . People then walked around in   the meeting room , looked at the presented details and thought about them . Some spent more time   at the screenshots , others were more interested in technology trends . Important is that every   stakeholder is covered and can highlight the items which are most important to them . That s why I   picked users for reviewing the galery from IT ( developers , QA , BA ) , UX design , Product Manager , First   and Second level support , Trading and Sales desk , which gives around 20 people being involved in the   design thinking process . All of them got their sticky notes , walked through the room , reviewed the   data and wrote down their ideas . Those ideas could be realizable or not working . Both was fine at   this stage . Important is that the ideas were helping us to solve our design challange . Once everyone   came up with an ideas , we split the whole group in teams of ~5 people each . The teams started with   separating different topics . The sticky notes within the teams were attached to the topics . Then the 

 next team continued , by sharing the next topic and their sticky notes . Also „ less important “ notes   were captured . 

 Insight 

 By applying the MindMapping tool we have formed topics . Ideas from different areas were   identified . For the gaps in the system that were identified , we can ask easily why we had these gaps ?   Was the old system not able to handle the requirement , or was there not enough time for the   implementation at that time ? Since we were a group of people from different areas the inputs ,   explainations and potential solutions ( What Wows ? ) were very diverse . Also , what about our client ’s   requests ? Has the market changed and do our clients have different needs today , than 20 years ago ?   What role does Social Media play today ? By having the different key stakeholder discussing the varity   of topics we are able to separate the most important ideas to form the requirement set for our MVP   ( Minimal viable product ) . 

 Approach 

 The MindMapping tool was a great approach to collect the right ideas to build a successful MVP . The   ideas we got from this approach depend on the involved key stakeholders . Ensure you have each   area properly covered , so your created Mindmap covers all relevant areas . If you have to many   people from one area , your Mindmap could diverse to much .
### Output: 