Reflection – Visualization

Challenge:

Visualization is the most used tool for my product design phase. As I have worked as consultants for  many customers, visualization helped me to work with multiple stakeholders to understand the problem  statement of the product and the flow before we start building the solution or MVP (Minimum Viable  Product). As my customer base is diverse from different domains and also working with different teams,  it is very important that everybody understand what we are trying to solve. One such scenario I had to  build a analytical solution for a SaaS based application. As the application already had reporting solution,  it was always the question how the analytical tool can help.

Selection:

I always start with showing graphs and charts on the problem statement. I create wire frames and  designs so that I can tap into people’s visual imagination. This helps me draw conversations, align on the  ideas. Which in turn help me solve problems. Visualization tool is tried and tested for me. For my  analytical tool, I started showing graphs and presentations on utilization of present data and how it  affects the delivery. Which helped me to get everyone acknowledge the challenges with present  reporting system. So, I chose the Visualization tool as people can relate to the problem statement.

Application:

I started the process by showing the amount and variation of data we handle through the application.  Then showed all stakeholders the data which we have how we are utilizing. We had lot of space  allocation and lease data which can show how the utilizations are happening. But with present reporting  capability of the tool the gaps and challenges we are having. I created a live example with the data  captured from the application and ran the scenarios to show the gaps and how much effect on  utilizations. This helped me get all the stakeholders understand the problems.

As there were different teams so I had to reach out to stakeholders separately and discussed only the  related scenarios. Each team received a customized problem statement with scenarios. There I took  customer interviews with stakeholders. Did whiteboard sessions where we used lot of data point  mapping and charts, these activities helped the teams to align with my though process. The activities  included them analyzing – 1. What is missing from the report result? 2. How much utilization benefits  they are losing? 3. Key Insights they use for day to day activities? These activities were plotted on white  board and charts, sticky notes and anyone can refer to it.

I record commonalities in the insights of each group, and then additional insights that come from the  group discussion on an additional copy of the graphic. Then I went on a session where all the groups  came together, and we drew the same problem statement together as the teams were aligned. I  archived all the charts, diagrams, flows and even sticky notes for future development references. In turn  it acts a reference tool for my whole development process.

Insight:

What I have learnt from visualization exercises is, people relate to images better. They don’t have to  read through pages or listen hours of boring sessions. These activities let everyone contribute and we  can define the problem at ease. This re-inforces the understanding of the problem and give a very wider  view on proposed solution development. I record commonalities in the insights of each group, and then  additional insights that come from the group discussion on an additional copy of the graphic. Every  stakeholders can then understand the risk and variables of the existing problem statement.

Approach:

I have made this a regular activity and visualization as a critical component before starting of any  product design. This is starting point of design strategy activities. In turn it acts a reference tool for my  whole development process.

