LEARNING LAUNCH 

 Challenge : 

 our organization that specializes in robotics design and manufacturing , also we   started a replacement remotely platform during the pandemic year to remote all of   our work . my / our challenge is to enhance the workflow like activities , Tasks delivery ,   and project milestones delivery within the designing department so as to extend   productivity within the online channel and to deliver all tasks on time . The project   scope includes the web platform and every one milestones manager composed of 4   managers and 14 designers , also because the larger designing department and   development department , with whom we work closely . The project is restricted to   internal resources ( i.e. , budget and designers ' time ) . The project should n't exceed 10   business days and therefore the solution should include a good distribution of   working hours amongst the team members . we 'll specialize in trying to uncover what   our team members , also as key stakeholders within the larger designing department   and development department , concede to be ineffective or problematic with   reference to the workflow . 

 Selection : 

 Our team has already skilled several design thinking tools , so we are able to try the   learning launch tool . broadly , the learning launch is an experiment meant to quickly   test a thought and prototype . 

 Application : 

 For our first learning launch , we focused on the structure / execution of our online   designing tasks . especially , we wanted to ascertain if we could structure our tasks ,   projects , and processes to adapt the methods of agile project management for our   work ( e.g. , time - boxed , daily , specific meetings , reviews , etc . ) in an attempt to   become more scrum . This tested our assumption that the structure and execution   were the most causes of our workflow challenge . Our team went through a full - day   training with a Scrum project management trainer . Next , we went through some   workshops to structure our tasks and processes during a more agile way . These two   sessions occurred within a 4 days ’ timeframe . We expected to supply a document   with a transparent description of our new , more agile processes / workflow . 

 For our second learning launch , we focused on gaining clarity about our tasks and   priorities . This tested our assumption that our prioritization of tasks was the most   explanation for our workflow challenge . Our team completed an anonymous survey .   Additionally , four key stakeholders from the designing department and development   department also completed an anonymous survey . The surveys included questions on   our new , proposed process , understanding the method and therefore the   prioritization of tasks , and feelings about the change , and were conducted within a   two days ’ timeframe . 

 Insight : 

 By applying the learning launch tool , our team identified our assumptions and   designed launches to check these assumptions . Additionally , we thought through   anticipated results , expecting to seek out that a more agile approach would improve   our workflow , which both our team and therefore the key stakeholders would be   fairly receptive the new prioritization of tasks and process . 

 Our actual results were slightly different from what we anticipated : while our team   was receptive the prioritization of tasks and process , the key stakeholders within the   designing department and development department expressed some concerns .   Moving forward , our team will review this insight and incorporate it into future launch   designs . the continued incorporation of insight is especially important at this stage ,   as launches precede a full rollout within the design thinking timeline . 

 Approach : 

 Given that our team has already skilled several design thinking activities / tools and   are at this stage within the timeline , the learning launch is that the appropriate tool .   As previously mentioned , our team must review the insight gained from our first two   launches and incorporate this insight into future launch designs . Future launch   designs should reflect insight gained , progress made , and are available closer to a   compelling solution ready for full rollout . 


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: LEARNING LAUNCH 

 Challenge : 

 our organization that specializes in robotics design and manufacturing , also we   started a replacement remotely platform during the pandemic year to remote all of   our work . my / our challenge is to enhance the workflow like activities , Tasks delivery ,   and project milestones delivery within the designing department so as to extend   productivity within the online channel and to deliver all tasks on time . The project   scope includes the web platform and every one milestones manager composed of 4   managers and 14 designers , also because the larger designing department and   development department , with whom we work closely . The project is restricted to   internal resources ( i.e. , budget and designers ' time ) . The project should n't exceed 10   business days and therefore the solution should include a good distribution of   working hours amongst the team members . we 'll specialize in trying to uncover what   our team members , also as key stakeholders within the larger designing department   and development department , concede to be ineffective or problematic with   reference to the workflow . 

 Selection : 

 Our team has already skilled several design thinking tools , so we are able to try the   learning launch tool . broadly , the learning launch is an experiment meant to quickly   test a thought and prototype . 

 Application : 

 For our first learning launch , we focused on the structure / execution of our online   designing tasks . especially , we wanted to ascertain if we could structure our tasks ,   projects , and processes to adapt the methods of agile project management for our   work ( e.g. , time - boxed , daily , specific meetings , reviews , etc . ) in an attempt to   become more scrum . This tested our assumption that the structure and execution   were the most causes of our workflow challenge . Our team went through a full - day   training with a Scrum project management trainer . Next , we went through some   workshops to structure our tasks and processes during a more agile way . These two   sessions occurred within a 4 days ’ timeframe . We expected to supply a document   with a transparent description of our new , more agile processes / workflow . 

 For our second learning launch , we focused on gaining clarity about our tasks and   priorities . This tested our assumption that our prioritization of tasks was the most   explanation for our workflow challenge . Our team completed an anonymous survey .   Additionally , four key stakeholders from the designing department and development   department also completed an anonymous survey . The surveys included questions on   our new , proposed process , understanding the method and therefore the   prioritization of tasks , and feelings about the change , and were conducted within a   two days ’ timeframe . 

 Insight : 

 By applying the learning launch tool , our team identified our assumptions and   designed launches to check these assumptions . Additionally , we thought through   anticipated results , expecting to seek out that a more agile approach would improve   our workflow , which both our team and therefore the key stakeholders would be   fairly receptive the new prioritization of tasks and process . 

 Our actual results were slightly different from what we anticipated : while our team   was receptive the prioritization of tasks and process , the key stakeholders within the   designing department and development department expressed some concerns .   Moving forward , our team will review this insight and incorporate it into future launch   designs . the continued incorporation of insight is especially important at this stage ,   as launches precede a full rollout within the design thinking timeline . 

 Approach : 

 Given that our team has already skilled several design thinking activities / tools and   are at this stage within the timeline , the learning launch is that the appropriate tool .   As previously mentioned , our team must review the insight gained from our first two   launches and incorporate this insight into future launch designs . Future launch   designs should reflect insight gained , progress made , and are available closer to a   compelling solution ready for full rollout .
### Output: 