One scenario in which I had used the process of design thinking is in my recent work which had involved   a complete overhaul of a software application for an automotive company . The task assigned was   migration of the application – which catered to existing diesel vehicles – to that of a new set of   requirements for Electric ones .   In this design task the tools which helped me to come up with a solution    are a combination of Visualization and mind mapping . 

 Application : 

 Preparing the mind : 

 Before starting the task or the job ,   I was new   to the automobile industry and knew had to create a   learning mindset   throughout   the task .   I was working with various people with domain expertise in the   automotive sector , I knew the only knowledge that I can contribute is that of a generic mobility user ,   other than that the solution has to be developed only on listening to what the various team wanted , For   this   I had to maintain a learning mindset and hope that the solution will grow as I   discuss . 

 What is : 

 I felt the task had a too narrow definition – a conversion of software - which had eliminated the   possibility of seeking out solutions in other directions . Therefore I took a step back , and   wanted to   understand What is that the organization intends to do with the application , who are going to be its   customers , users . On discussion with the previous application developer and the   business unit head for   electric , the various personas were listed down . The list of various personas was quite a lot both   internally within the company and externally – people who buy / use the product- . 

 It is here the tool of visualization came to help , given a long list of personas making the eco - system of   extremely complex , the best way in which individual persona / stakeholder can contribute the list of   features they need in the application , plus demand for what data / information they need from other   personas – i.e. the interaction they intend to have via the application - , is not by going and interviewing   each team and jotting down points , but by involving them in a more interactive way . So I took a   whiteboard made a diagram of the ecosystems , invited different teams and as we ran through different   stakeholders told them to write on a sticky note – what data they wanted – and paste it .   This process   had significantly reduced the time it took for me to run behind teams for inputs , and also gave me a   clear way to look at it , where the data flow / the needs were clearly visible . 

 What if : 

 Once the visualization part was complete , The end result was a big mind map in the white board , which   had set up the table for a good brain storming session . The initial task of conversion to new set of   requirements were done , however the question   was whether that what all the stakeholders wanted   just a simple application , on thinking I thought of the idea of a control room kind of solution was   needed for various teams to walk in and get the data they wanted – such as productivity , performance 

 of the vehicle – and not login to an application as they were . This idea / concept of a new control room   came out of only by brain storming on the visualization map laid out . What started out as a simple   conversion assignment , a new solution was developed . This on discussion with the management   was   the What wows solution . The initial trial or the Proto stage is on the way and till now the productivity of   teams and ease of operation has increased , thus garnering a good feedback . However an area for   improvement would be to efficiently manage and scale the control center quickly , which on gathering   more data would be implemented before the final roll out . 

 Insight and learnings : 

 On hindsight maintain a learning mindset is a great positive advantage while beginning a task and as you   carry forward the task , as the problem unveils itself . Visualization completely helped in breaking down a   complex problem and made interaction much easier . The visualization board created a mind map which   facilitated to brainstorm very effectively thus leading to a new solution . Thus , the whole design process   not only helps you to efficiently provide solution but also give an effective solution too . 


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: One scenario in which I had used the process of design thinking is in my recent work which had involved   a complete overhaul of a software application for an automotive company . The task assigned was   migration of the application – which catered to existing diesel vehicles – to that of a new set of   requirements for Electric ones .   In this design task the tools which helped me to come up with a solution    are a combination of Visualization and mind mapping . 

 Application : 

 Preparing the mind : 

 Before starting the task or the job ,   I was new   to the automobile industry and knew had to create a   learning mindset   throughout   the task .   I was working with various people with domain expertise in the   automotive sector , I knew the only knowledge that I can contribute is that of a generic mobility user ,   other than that the solution has to be developed only on listening to what the various team wanted , For   this   I had to maintain a learning mindset and hope that the solution will grow as I   discuss . 

 What is : 

 I felt the task had a too narrow definition – a conversion of software - which had eliminated the   possibility of seeking out solutions in other directions . Therefore I took a step back , and   wanted to   understand What is that the organization intends to do with the application , who are going to be its   customers , users . On discussion with the previous application developer and the   business unit head for   electric , the various personas were listed down . The list of various personas was quite a lot both   internally within the company and externally – people who buy / use the product- . 

 It is here the tool of visualization came to help , given a long list of personas making the eco - system of   extremely complex , the best way in which individual persona / stakeholder can contribute the list of   features they need in the application , plus demand for what data / information they need from other   personas – i.e. the interaction they intend to have via the application - , is not by going and interviewing   each team and jotting down points , but by involving them in a more interactive way . So I took a   whiteboard made a diagram of the ecosystems , invited different teams and as we ran through different   stakeholders told them to write on a sticky note – what data they wanted – and paste it .   This process   had significantly reduced the time it took for me to run behind teams for inputs , and also gave me a   clear way to look at it , where the data flow / the needs were clearly visible . 

 What if : 

 Once the visualization part was complete , The end result was a big mind map in the white board , which   had set up the table for a good brain storming session . The initial task of conversion to new set of   requirements were done , however the question   was whether that what all the stakeholders wanted   just a simple application , on thinking I thought of the idea of a control room kind of solution was   needed for various teams to walk in and get the data they wanted – such as productivity , performance 

 of the vehicle – and not login to an application as they were . This idea / concept of a new control room   came out of only by brain storming on the visualization map laid out . What started out as a simple   conversion assignment , a new solution was developed . This on discussion with the management   was   the What wows solution . The initial trial or the Proto stage is on the way and till now the productivity of   teams and ease of operation has increased , thus garnering a good feedback . However an area for   improvement would be to efficiently manage and scale the control center quickly , which on gathering   more data would be implemented before the final roll out . 

 Insight and learnings : 

 On hindsight maintain a learning mindset is a great positive advantage while beginning a task and as you   carry forward the task , as the problem unveils itself . Visualization completely helped in breaking down a   complex problem and made interaction much easier . The visualization board created a mind map which   facilitated to brainstorm very effectively thus leading to a new solution . Thus , the whole design process   not only helps you to efficiently provide solution but also give an effective solution too .
### Output: 