My reflection on Visualization 

 Challenge 

 Often , I face challenges in gathering the idea and document it effectively and efficiently , without having a   pictorial representation or visualization it was difficult to me to address them effectively an in timely   manner . As I manage a global team in delivering solution to customers my team is often need to re - think ,   re - imagine certain tasks , process , principles this is a herculean task to get the feedback from all   stakeholders , I usually run my team meetings to report the problem directly to me as I must provide   direction / decision to complete the project or tasks at on time , when there is a problem then it requires   brainstorming from various stakeholders , to bring them all into one page this pushes think beyond what   we do from a regular operations management 

 Selection 

 I use Fishbone method to capture the large problem statement and drive the root cause analysis , I   typically used fishbone diagram for root cause analysis , a fishbone diagram combines the practice of   brainstorming with various stakeholders with a type of mind map template . It is efficient to drive   collaboration and gives space for others to voice out effectively . This also helps to run process   simplification and helps to avoid wastages . 

 Example for a fishbone diagram from my work while office was remain open , 

 Application 

 As I capture the problem statement through various sources , such as voice of customer , survey , E - mail ,   Risk reporting and meeting with individual and teams , once I have identified potential problem and to   solve , Now a days , I use https://miro.com Since its digital era and we continue to work from home for   more than year an online collaboration and visualization tool is much better idea to collaborate with team ,   the online tool helps me to brainstorm new ideas together in real time , make connections between ideas   and solutions , and much more . This is a great tool for the ideation and strategic planning process . We   also like the visual nature of creating maps and diagrams to bring our ideas to life in a digital space and   an interactive space to collaborate , update and re - navigate . Once i have setup a space for the team and   an identified problem statement , i create a blank fishbone template with a problem statement pointing on   the right and the possible root cause growing from right to left , then in an scheduled meeting we   collaborate with team to come together with ideas and capture them in right space and prioritize to solve 

 with an agreed timeline . This is the same method that has been followed in manufacturing practices to   drive LEAN for years and its effective to drive simplification in IT as well . 

 For brainstorming and driving effective results , I run KAIZEN an approach that pushes forward the   continuous improvement in delivering key outcome , 

 Insight 

 The fishbone diagram gives a visual representation over the problem statement and provides quick   insights on the root causes and potential problem solving techniques and while we go through a KAIZEN   approach it improves teamwork as I engage all the involved members , discipline on alignment and   engagement without any chaos or disagreement , improved team morale as we listen to all the involved   persons and gives space to every individual , they feel that they are empowered to voice out and feel   included , and suggestions for improvement as ideas created at all level , The more likely I am able to   achieve a sense of agreement and consensus with people 

 In real time organization need people who can see the bigger picture - those who listen , who find   patterns , and make connections . The environment around us is complex and needs us to strengthen our   ability capture and organize ideas . We always need more in - depth knowledge . We need more shared   understanding . We need more simplification and problem - solving approach . the more we are likely to   draw out conversation . In an environment where our ability to get things done and to solve problems is   dependent on other people being able to understand us and align their ideas with us in more meaningful   way . 

 Approach 

 In future , I am thinking to have regular sessions with team to drive proactive approach to any potential   problem or any unforeseen circumstance which may come as surprise . Instead of problem - based   approach will shift to proactive approach and use my team free time to grow , evolve and address   potential problems , I will keep a open fishbone dashboards which can grow in offline as well where team   can go ahead add or amend the data whenever they feel to be reported . I am also thinking to include a   scrum master to drive the initiative in a full - time space who can keep reporting on the changes and   improves continuous delivery in order to improve better user experience . 


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: My reflection on Visualization 

 Challenge 

 Often , I face challenges in gathering the idea and document it effectively and efficiently , without having a   pictorial representation or visualization it was difficult to me to address them effectively an in timely   manner . As I manage a global team in delivering solution to customers my team is often need to re - think ,   re - imagine certain tasks , process , principles this is a herculean task to get the feedback from all   stakeholders , I usually run my team meetings to report the problem directly to me as I must provide   direction / decision to complete the project or tasks at on time , when there is a problem then it requires   brainstorming from various stakeholders , to bring them all into one page this pushes think beyond what   we do from a regular operations management 

 Selection 

 I use Fishbone method to capture the large problem statement and drive the root cause analysis , I   typically used fishbone diagram for root cause analysis , a fishbone diagram combines the practice of   brainstorming with various stakeholders with a type of mind map template . It is efficient to drive   collaboration and gives space for others to voice out effectively . This also helps to run process   simplification and helps to avoid wastages . 

 Example for a fishbone diagram from my work while office was remain open , 

 Application 

 As I capture the problem statement through various sources , such as voice of customer , survey , E - mail ,   Risk reporting and meeting with individual and teams , once I have identified potential problem and to   solve , Now a days , I use https://miro.com Since its digital era and we continue to work from home for   more than year an online collaboration and visualization tool is much better idea to collaborate with team ,   the online tool helps me to brainstorm new ideas together in real time , make connections between ideas   and solutions , and much more . This is a great tool for the ideation and strategic planning process . We   also like the visual nature of creating maps and diagrams to bring our ideas to life in a digital space and   an interactive space to collaborate , update and re - navigate . Once i have setup a space for the team and   an identified problem statement , i create a blank fishbone template with a problem statement pointing on   the right and the possible root cause growing from right to left , then in an scheduled meeting we   collaborate with team to come together with ideas and capture them in right space and prioritize to solve 

 with an agreed timeline . This is the same method that has been followed in manufacturing practices to   drive LEAN for years and its effective to drive simplification in IT as well . 

 For brainstorming and driving effective results , I run KAIZEN an approach that pushes forward the   continuous improvement in delivering key outcome , 

 Insight 

 The fishbone diagram gives a visual representation over the problem statement and provides quick   insights on the root causes and potential problem solving techniques and while we go through a KAIZEN   approach it improves teamwork as I engage all the involved members , discipline on alignment and   engagement without any chaos or disagreement , improved team morale as we listen to all the involved   persons and gives space to every individual , they feel that they are empowered to voice out and feel   included , and suggestions for improvement as ideas created at all level , The more likely I am able to   achieve a sense of agreement and consensus with people 

 In real time organization need people who can see the bigger picture - those who listen , who find   patterns , and make connections . The environment around us is complex and needs us to strengthen our   ability capture and organize ideas . We always need more in - depth knowledge . We need more shared   understanding . We need more simplification and problem - solving approach . the more we are likely to   draw out conversation . In an environment where our ability to get things done and to solve problems is   dependent on other people being able to understand us and align their ideas with us in more meaningful   way . 

 Approach 

 In future , I am thinking to have regular sessions with team to drive proactive approach to any potential   problem or any unforeseen circumstance which may come as surprise . Instead of problem - based   approach will shift to proactive approach and use my team free time to grow , evolve and address   potential problems , I will keep a open fishbone dashboards which can grow in offline as well where team   can go ahead add or amend the data whenever they feel to be reported . I am also thinking to include a   scrum master to drive the initiative in a full - time space who can keep reporting on the changes and   improves continuous delivery in order to improve better user experience .
### Output: 