Phillip Santillan – Reflection assignment – Visualization

Challenge and Selection

The tool that I have found consistently useful throughout my career thus far is visual thinking or  visualization. Whether it is in a group or just me, as an individual, trying to demystify a problem space, the  act of putting abstract ideas a figures or diagrams, opens the minds for a more constructive and productive  interaction. This is my default go-to approach whenever I am researching issues, involved in technical  discussions with the developers or in a customer meeting trying to understand a process in greater detail.  Putting words into graphics like straw man, geometrics shapes enhances the quality of output making.

Application

Using Visualization in Root cause analysis.

When researching a problem reported by a user, I being my investigation gathering the facts around the  event. These could be logs, audit traces, print outs, anything. Then I try to piece the flow of events one  after another in chronological event of say time. When I feel I have a hunch of where the root cause is or  whenever I am completely stuck in my analytical track, I resort to visualizing the journey of events. As a  process, I always deliberately, set the key statement aside, temporarily. Then I start drawing the facts  ‘what I know’ say in boxes. Engaging in this process, has multiple benefits, almost immediately I can see if  I have made false assumptions, or reveals that I need to look for more data, or it simply solidifies the  inferences drawn.

Another benefit of this visualization practical is that almost immediately I can see if the processes /events  are indeed working as designed (not a defect) else these actions serve are valuable aids to recreate the  issue. These pictures many a times have been attached to problem-statements which are sent for defect  fixing. Visualizing issues and documenting them also helps the testing teams down line who can now  inspect these visuals and prepare their test cases accordingly.

Customer Interactions

I have found visualization is a great tool in breaking down communication barriers. When meeting clients,  using props like post-it notes, charts etc., serve as great aids in understanding the requirements, both  expressed and unexpressed. Many a times, I have used these visual tools to map solutions to  requirements, thus saving a lot of time and effort. Functional diagrams, flow charts, Visio mind maps, are  all tools I have used both understand and explain complex concepts. On many instances, the group or  individual can see errors or missing pieces and quickly correct course when explaining requirements to  us. Another benefit of using a multi nodal visual approach, is that the core verbal discussions become  healthier and productive.

Technical Discussions

On many an occasion, I have used the post it notes, flip chart diagrams mentioned above, to serve as  supporting documentation in technical discussions with the development team. These visual aids then  spur the process of demystifying the requirements. Many a times, these aids help me recollect vital points  and fill the gaps in our recollection. Visualization takes on a different flavor when we discuss technical  challenges. Using white boards, flow charts to represent process flows, design diagrams allow me to  understand the technical challenges in a much better form. Taking a photo of these visual artefacts, and

using them as aids to the documentation, helps me when we are composing the training and information  material later in the project.

Insight and Approach

What I have learned in the course and the experiences from my professional life lead me to conclude that

1. Graphically representing abstract ideas, greatly hastens the process of unbundling complexities.

Be it an attempt to understand what is, or when exploring different options under what if, creating  a low fidelity what wows or trying to find out what works, a visual artefact becomes  polymorphous.

2. A visual artefact is also a great attention grabber. Being the focal point of the conversation, it

enables collaboration and collective thought and action.

3. It helps in overcoming obstacles like analysis paralysis, when one is stumbling around abstract

ideas.

4. By allowing the mind to work freely, it unshackles ideas at many levels. Morphing ideas and

thoughts into graphics, helps us convey our ideas more effectively


Phillip Santillan – Reflection assignment – Visualization Challenge and Selection The tool that I have found consistently useful throughout my career thus far is visual thinking or visualization . Whether it is in a group or just me , as an individual , trying to demystify a problem space , the act of putting abstract ideas a figures or diagrams , opens the minds for a more constructive and productive interaction . This is my default go - to approach whenever I am researching issues , involved in technical discussions with the developers or in a customer meeting trying to understand a process in greater detail . Putting words into graphics like straw man , geometrics shapes enhances the quality of output making . Application Using Visualization in Root cause analysis . When researching a problem reported by a user , I being my investigation gathering the facts around the event . These could be logs , audit traces , print outs , anything . Then I try to piece the flow of events one after another in chronological event of say time . When I feel I have a hunch of where the root cause is or whenever I am completely stuck in my analytical track , I resort to visualizing the journey of events . As a process , I always deliberately , set the key statement aside , temporarily . Then I start drawing the facts ‘ what I know ’ say in boxes . Engaging in this process , has multiple benefits , almost immediately I can see if I have made false assumptions , or reveals that I need to look for more data , or it simply solidifies the inferences drawn . Another benefit of this visualization practical is that almost immediately I can see if the processes /events are indeed working as designed ( not a defect ) else these actions serve are valuable aids to recreate the issue . These pictures many a times have been attached to problem - statements which are sent for defect fixing . Visualizing issues and documenting them also helps the testing teams down line who can now inspect these visuals and prepare their test cases accordingly . Customer Interactions I have found visualization is a great tool in breaking down communication barriers . When meeting clients , using props like post - it notes , charts etc . , serve as great aids in understanding the requirements , both expressed and unexpressed . Many a times , I have used these visual tools to map solutions to requirements , thus saving a lot of time and effort . Functional diagrams , flow charts , Visio mind maps , are all tools I have used both understand and explain complex concepts . On many instances , the group or individual can see errors or missing pieces and quickly correct course when explaining requirements to us . Another benefit of using a multi nodal visual approach , is that the core verbal discussions become healthier and productive . Technical Discussions On many an occasion , I have used the post it notes , flip chart diagrams mentioned above , to serve as supporting documentation in technical discussions with the development team . These visual aids then spur the process of demystifying the requirements . Many a times , these aids help me recollect vital points and fill the gaps in our recollection . Visualization takes on a different flavor when we discuss technical challenges . Using white boards , flow charts to represent process flows , design diagrams allow me to understand the technical challenges in a much better form . Taking a photo of these visual artefacts , and using them as aids to the documentation , helps me when we are composing the training and information material later in the project . Insight and Approach What I have learned in the course and the experiences from my professional life lead me to conclude that 1 . Graphically representing abstract ideas , greatly hastens the process of unbundling complexities . Be it an attempt to understand what is , or when exploring different options under what if , creating a low fidelity what wows or trying to find out what works , a visual artefact becomes polymorphous . 2 . A visual artefact is also a great attention grabber . Being the focal point of the conversation , it enables collaboration and collective thought and action . 3 . It helps in overcoming obstacles like analysis paralysis , when one is stumbling around abstract ideas . 4 . By allowing the mind to work freely , it unshackles ideas at many levels . Morphing ideas and thoughts into graphics , helps us convey our ideas more effectively