Challenge

In my organization, I work within IT helping tie together IT strategy with Business strategy to deliver  results.  I am often challenged with the role of “translator” by making clear to sales associates what  capabilities are offered on an IT side and making business goals clear to more technical IT resources that  are charged with delivering technical solutions.

In a recent example that occurred while I was taking this course, we were tasked with reimagining what  some of our financial reporting could look like.  The challenge was to allow business to clearly articulate  the problem while also working within the constraints of what is possible while also showing what is  additionally available outside of standard table like reporting that has historically been done at our  company in this space.

Selection

For this particular problem we chose Visualization.  While we used multiple tools throughout the  process, I feel the most helpful tool was visualization.  We chose this because from the start we could  work with our business stakeholders to document user journeys.  It was important for us to visualize  form the beginning what kinds of users were going to be using this financial dashboard and what were  their expected results.

Application

We started by mapping a flow chart that visualized multiple user types accessing the same legacy  financial chart, exporting it to excel, and performing their own individual analysis to get their own value  out of the data.  Through this journey mapping visualization tool, we were able to visually map out each  of these journeys showing what each user type needed from the dashboard.

From here, we were able to draw some mock reports around what it could look like to provide users the  answers to the questions they were asking on the first page of the dashboard rather than having them  do additionally analytics on their own.

Insight

Through this process we have realized that visualization is a key tool to have in our toolset.  Additionally,  we’ve quickly realized (as also pointed out in the videos) that visualization is key not only at the start of  the design thinking process, but throughout the entire process.  At each step along the way, visualization  truly helped communication and get the point across that we were trying to accomplish.

Approach

In my opinion, the visualization approach was the key to our success, but I think other tools could have  also been used to reach similar outcomes.  One specifically that would work well in this situation would  be storytelling.  In my role, it is important to play the “translator” role between technical IT resources  and strategic focused business resources.  In many cases, the begin the design thinking process, it takes  a storytelling approach to layout problems in clear stories that are easy to understand by all  stakeholders.


Challenge In my organization , I work within IT helping tie together IT strategy with Business strategy to deliver results . I am often challenged with the role of “ translator ” by making clear to sales associates what capabilities are offered on an IT side and making business goals clear to more technical IT resources that are charged with delivering technical solutions . In a recent example that occurred while I was taking this course , we were tasked with reimagining what some of our financial reporting could look like . The challenge was to allow business to clearly articulate the problem while also working within the constraints of what is possible while also showing what is additionally available outside of standard table like reporting that has historically been done at our company in this space . Selection For this particular problem we chose Visualization . While we used multiple tools throughout the process , I feel the most helpful tool was visualization . We chose this because from the start we could work with our business stakeholders to document user journeys . It was important for us to visualize form the beginning what kinds of users were going to be using this financial dashboard and what were their expected results . Application We started by mapping a flow chart that visualized multiple user types accessing the same legacy financial chart , exporting it to excel , and performing their own individual analysis to get their own value out of the data . Through this journey mapping visualization tool , we were able to visually map out each of these journeys showing what each user type needed from the dashboard . From here , we were able to draw some mock reports around what it could look like to provide users the answers to the questions they were asking on the first page of the dashboard rather than having them do additionally analytics on their own . Insight Through this process we have realized that visualization is a key tool to have in our toolset . Additionally , we ’ve quickly realized ( as also pointed out in the videos ) that visualization is key not only at the start of the design thinking process , but throughout the entire process . At each step along the way , visualization truly helped communication and get the point across that we were trying to accomplish . Approach In my opinion , the visualization approach was the key to our success , but I think other tools could have also been used to reach similar outcomes . One specifically that would work well in this situation would be storytelling . In my role , it is important to play the “ translator ” role between technical IT resources and strategic focused business resources . In many cases , the begin the design thinking process , it takes a storytelling approach to layout problems in clear stories that are easy to understand by all stakeholders .