Reflection assignment – Storytelling 

 Challenge 

 One of our clients wants to perform an upgrade for their IT systems . This system culminates both IT   and Business - related topics and as such impacts the business processes when updated . Within the   company , there was a severe disconnect between the business and IT side . There is no communication ,   needs and wants are not expressed properly , and everyone works within their own silo . For a successful   upgrade plan , there is a severe need for alignment , communication , and cooperation between   Business and IT and within them as well . The business side has many time - consuming projects planned   in the next few years . The IT side will require resources of business to successfully upgrade and   implement . Our biggest hurdle is convincing all sides of the company that they are part of the same   team and share the same mission . This may not seem like it fits in innovation , but the IT system is   what ’s called a PLM system chich also aids and improves the processes set in place for innovation and   development of new ideas . 

 Selection 

 The obvious tool for this is of course storytelling . We must create a common ground between all facets   of the company and thus by including them in the same story we hoped to connect them and facilitate   collaboration . Storytelling allows the stakeholders to express their concerns and discuss where and   most importantly when the upgrade can take place . By creating this cultivated upgrade goal , we hoped   to forego all immediate rejection and move toward possible options/ 

 Application 

 To create the right story , we first had to gather information on the clients and their current projects .   We found out , as said above , that the business side has little time in the upcoming years . They blatantly   rejected any resource requests that we made at the start . This meant we had to dig deeper and by   including IT stakeholders we managed to explain the necessity of the upgrade . Planting the seed of   necessity in the business , they let us into their projects and more importantly it informed us of current   issues they had . Together with business we transformed the story to make sure that it was n’t “ just ” an   upgrade but along the way we could alleviate their concerns and even make some quick wins . The   story grew from a simple upgrade to a company wide involved project where every part has their say ,   and their responsibilities . 

 Insight 

 The easiest way to summarize the insight we gained is : “ When people feel they are part of something ,   they will push their own limits to make sure it will be successful ” . While a story is a very strong and   important connector between people , there will always be different angle from which they view the   story . Involving people in the story brings them closer together and grants them an inside view of the   other and of the whole . It was only at the point we actively involved and made people from business   responsible that they not only helped but actively looked for better solutions . 

 Approach 

 Now the first stages are complete , the story will have to be adapted to the transforming reality . This is   the most dynamic of the tools and will aim to keep including those people necessary for the success of   the project . Key to this will be the feeling of shared responsibility and that will only be possible when   people not only are , but also believe that they are part of the same team . 


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: Reflection assignment – Storytelling 

 Challenge 

 One of our clients wants to perform an upgrade for their IT systems . This system culminates both IT   and Business - related topics and as such impacts the business processes when updated . Within the   company , there was a severe disconnect between the business and IT side . There is no communication ,   needs and wants are not expressed properly , and everyone works within their own silo . For a successful   upgrade plan , there is a severe need for alignment , communication , and cooperation between   Business and IT and within them as well . The business side has many time - consuming projects planned   in the next few years . The IT side will require resources of business to successfully upgrade and   implement . Our biggest hurdle is convincing all sides of the company that they are part of the same   team and share the same mission . This may not seem like it fits in innovation , but the IT system is   what ’s called a PLM system chich also aids and improves the processes set in place for innovation and   development of new ideas . 

 Selection 

 The obvious tool for this is of course storytelling . We must create a common ground between all facets   of the company and thus by including them in the same story we hoped to connect them and facilitate   collaboration . Storytelling allows the stakeholders to express their concerns and discuss where and   most importantly when the upgrade can take place . By creating this cultivated upgrade goal , we hoped   to forego all immediate rejection and move toward possible options/ 

 Application 

 To create the right story , we first had to gather information on the clients and their current projects .   We found out , as said above , that the business side has little time in the upcoming years . They blatantly   rejected any resource requests that we made at the start . This meant we had to dig deeper and by   including IT stakeholders we managed to explain the necessity of the upgrade . Planting the seed of   necessity in the business , they let us into their projects and more importantly it informed us of current   issues they had . Together with business we transformed the story to make sure that it was n’t “ just ” an   upgrade but along the way we could alleviate their concerns and even make some quick wins . The   story grew from a simple upgrade to a company wide involved project where every part has their say ,   and their responsibilities . 

 Insight 

 The easiest way to summarize the insight we gained is : “ When people feel they are part of something ,   they will push their own limits to make sure it will be successful ” . While a story is a very strong and   important connector between people , there will always be different angle from which they view the   story . Involving people in the story brings them closer together and grants them an inside view of the   other and of the whole . It was only at the point we actively involved and made people from business   responsible that they not only helped but actively looked for better solutions . 

 Approach 

 Now the first stages are complete , the story will have to be adapted to the transforming reality . This is   the most dynamic of the tools and will aim to keep including those people necessary for the success of   the project . Key to this will be the feeling of shared responsibility and that will only be possible when   people not only are , but also believe that they are part of the same team .
### Output: 