RESTRICTED 

 Hi , 

 My name is Ahmed from Brazil and I work in the local IT department of a big Pharmaceutical and   Agribusiness and this is my first contact with Design thinking . 

 1 . Challenge : Describe your challenge , including all relevant information . 

 In the pharmaceutical area we have several problems on our relationship with the 

 departments . Most of the time the users believe that IT is responsible for all problems that they   have system related and that we should solve issue immediately of before it happens ( like   predict the future ) . Most of the issues are related by a system used for more than 10 years   without governance by global or local IT team . Most of the time when we have a project that   require a system enhancement the business is not clear on the requirements and as the project   goes on the departments keep changing the requirements that seems that IT is not organized . 

 2 . Selection : In your own words , briefly describe the tool you selected ( e.g. , what it is 

 and why you selected it for your challenge -- including any appropriate video lecture   references ) . 

 For this assignment I will try to use the Storytelling tool to try to bring the point of view of 

 the IT and the departments to understanding the reason of the problems and how solve them .   Most of the discussions of the past are issues related to the sequence of evets . 

 3 . Application : Describe how you applied the tool you selected to your challenge ( e.g. , 

 what you did and how the tool was applied effectively or ineffectively ) . 

 To be able to get the 2 points of view I started planning individual interviews where I gather 

 the experience of both parties and how they would suggest to solve the issue in future projects .   Once the individual interviews are done and the data is collected / analyzed I would plan an   integrated brainstorm with them with the points suggested as solution for the issues to see the   feasibility and a plan to be followed in future projects . 

 4 . Insight : Describe the insight you gained from applying the tool you selected to your 

 challenge ( e.g. , how an insight affected your thinking about the challenge and about   design thinking more broadly ) . 

 Based on this exercise I was able to see that most of the issue happened due to several 

 reasons . 

 •   From the beginning the responsibility of the IT and Departments on the project is not   clear that lead to a confusion on who should raise each type of problem and the affect   that it can have . 

 o To solve this issue , we were able to plan meetings on the beginning of the 

 project explaining the goal of the project , the responsibility of each participants . 

 •   The IT does n’t know the process of the departments . 

 o To solve a meeting is planned where the business has to explain how the process 

 is done today ( as is ) and what they expect in the future ( to be ) . The IT team can   pitch in and explain technical constraints and explore further in details the   process executed . The result of this meeting has to be fully documented to avoid   issues on the future of change of the scope of the project . 

 •   The departments do n’t know the IT steps to be followed . 

 RESTRICTED 

 o IT will have to explain on the time line the steps to be done and from which 

 point in time the required changes can not be changed anymore . 

 5 . Approach : Describe what you might do differently next time -- applying the same tool 

 you selected or a different one -- and the reason(s ) why . 

 In this process we had the participation the employees from IT and the department involved 

 in doing the activities on the daily basis , for future reference I would also get the supervisor and   managers on the meetings to keep the process clear to all levels . 

 O also would promote meet ups between the departments and IT even without a specific 

 project in mind to start a more friendly relationship between the IT and departments gradually   over time . 


EMAIL: 
ID_NUM: 
NAME_STUDENT: Ahmed
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: RESTRICTED 

 Hi , 

 My name is Ahmed from Brazil and I work in the local IT department of a big Pharmaceutical and   Agribusiness and this is my first contact with Design thinking . 

 1 . Challenge : Describe your challenge , including all relevant information . 

 In the pharmaceutical area we have several problems on our relationship with the 

 departments . Most of the time the users believe that IT is responsible for all problems that they   have system related and that we should solve issue immediately of before it happens ( like   predict the future ) . Most of the issues are related by a system used for more than 10 years   without governance by global or local IT team . Most of the time when we have a project that   require a system enhancement the business is not clear on the requirements and as the project   goes on the departments keep changing the requirements that seems that IT is not organized . 

 2 . Selection : In your own words , briefly describe the tool you selected ( e.g. , what it is 

 and why you selected it for your challenge -- including any appropriate video lecture   references ) . 

 For this assignment I will try to use the Storytelling tool to try to bring the point of view of 

 the IT and the departments to understanding the reason of the problems and how solve them .   Most of the discussions of the past are issues related to the sequence of evets . 

 3 . Application : Describe how you applied the tool you selected to your challenge ( e.g. , 

 what you did and how the tool was applied effectively or ineffectively ) . 

 To be able to get the 2 points of view I started planning individual interviews where I gather 

 the experience of both parties and how they would suggest to solve the issue in future projects .   Once the individual interviews are done and the data is collected / analyzed I would plan an   integrated brainstorm with them with the points suggested as solution for the issues to see the   feasibility and a plan to be followed in future projects . 

 4 . Insight : Describe the insight you gained from applying the tool you selected to your 

 challenge ( e.g. , how an insight affected your thinking about the challenge and about   design thinking more broadly ) . 

 Based on this exercise I was able to see that most of the issue happened due to several 

 reasons . 

 •   From the beginning the responsibility of the IT and Departments on the project is not   clear that lead to a confusion on who should raise each type of problem and the affect   that it can have . 

 o To solve this issue , we were able to plan meetings on the beginning of the 

 project explaining the goal of the project , the responsibility of each participants . 

 •   The IT does n’t know the process of the departments . 

 o To solve a meeting is planned where the business has to explain how the process 

 is done today ( as is ) and what they expect in the future ( to be ) . The IT team can   pitch in and explain technical constraints and explore further in details the   process executed . The result of this meeting has to be fully documented to avoid   issues on the future of change of the scope of the project . 

 •   The departments do n’t know the IT steps to be followed . 

 RESTRICTED 

 o IT will have to explain on the time line the steps to be done and from which 

 point in time the required changes can not be changed anymore . 

 5 . Approach : Describe what you might do differently next time -- applying the same tool 

 you selected or a different one -- and the reason(s ) why . 

 In this process we had the participation the employees from IT and the department involved 

 in doing the activities on the daily basis , for future reference I would also get the supervisor and   managers on the meetings to keep the process clear to all levels . 

 O also would promote meet ups between the departments and IT even without a specific 

 project in mind to start a more friendly relationship between the IT and departments gradually   over time .
### Output: 