Design Thinking for Analytics

Data Rocks

Learn how to use a proven and repeatable framework for approaching analysis. I’ll walk you through the 5 stages of design thinking and give some specific examples that you can implement in your analysis.
Last Episode:
https://datarockspodcast.buzzsprout.com/1276397/5224414-what-is-data-and-what-is-the-big-deal

Timeline:
00:53 - Intro
06:03 - Stage 1: Empathy
09:30 - Stage 2: Define
14:32 - Stage 3: Ideate / Brainstorm
15:37 - Stage 4: Prototype
17:50 - Stage 5: Test
18:58 - The Last Record
Today’s Interesting Data Fact:
https://uxdesign.cc/3-things-you-probably-didnt-know-about-design-thinking-and-why-they-matter-for-business-5fa89b885c9c
SNL Skit:
https://www.youtube.com/watch?v=cVsQLlk-T0s&t=154s
For Further Reading:
https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process
https://uxplanet.org/its-an-approach-not-a-process-66e348489fe1
Key Information Checklist:
Scope

• Broad: Display information about the entire organization.
• Specific: Focus on a specific function, process, product, region, etc.

Business Role

• Strategic: A high-level, broad, and long-term view of performance
• Operational: A focused, near-term, tactical view of performance

Time Horizon

• Historical: Looking backwards to track trends
• Snapshot: Showing performance at a single point in time
• Real-Time: Monitoring activity as it happens
• Predictive: Using past performance to predict future performance

Customization

• One-size-fits-all: Presented as a single view for all users
• Customizable: Let users create a view that reflects their needs

Level of Detail

• Summary: Presenting only the most critical top-level information
• Drillable: Providing the ability to drill down to detailed numbers to gain more context

Point of View

• Prescriptive: The analysis specifically tells the user what the data means and what to do about it
• Exploratory: Users have the latitude to interpret the results as they see fit

The Last Record:

1. Design thinking is an iterative process and doesn’t have to be so rigid. If you’ve worked with a group long enough that you know their tendencies, feel free to shorten the empathize stage. Also, if you’ve gained consensus with your first sketch, don’t worry about sketching more advanced prototypes.
2. Give them what they need, not what they want. It’s important that you solve the problem and set up your audience for success. By giving them what they want rather than what they need, you open the door to scope creep and questions down the road.
3. Make sure you understand the key information needed during the define stage. See notes above. Also, be sure to repeat the question back using, “What I am hearing is...”
4. Wire-framing is a helpful tool when trying to gain consensus on a project. The key is to get this into the hands of your stakeholders as fast and early as possible so that you get alignment, and can start gathering the data needed to provide your solution.
5. During the testing phase, you want the user to try all possible scenarios and show you where there are problems, not simply tell you that it’s broken.