Insight Design, Part 1

  • View
    218

  • Download
    11

Embed Size (px)

DESCRIPTION

What good is data if it doesn't become information? And what good is it if it doesn't answer the burning questions? What good is it if it's irrelevant to the ones who need it most? Avoid demonstrating with certainty that you don't understand the question or the people asking it by practicing Insight Design.

Text of Insight Design, Part 1

  • INSIGHT DESIGN, PART 1 ROB SAENZ, BUSINESS INTELLIGENCE EXPERT
  • AVOIDING THE FAILURE TO COMMUNICATE OR
  • ONCE UPON A TIME... We reviewed our finished work with our customer and heard...
  • THAT LOOKS UGLY PLEASE FIX IT
  • THERE ARE ALWAYS TWO POINTS ON THE CONTINUUM For each feature
  • POINT #1 PERFECT
  • POINT #2 GOOD ENOUGH
  • POINT #1 PERFECT
  • PAIN*STAKING DESIGN AKA
  • ABSOLUTELY. IT WILL TAKE US JUST... CAN we fix it?
  • Weeks Months Years?
  • POINT #2 GOOD ENOUGH
  • 80%* OF YOUR APP IS JUST DATA ! *made up number We could say,
  • SPEED TO MARKET IS A FEATURE We could say,
  • THE TRUTH IS
  • POLISH & SPEED COMPETE ON THE CONTINUUM
  • DONE IS TOO LATE TO ASK QUESIONS
  • ASK THE QUESTIONS AT THE BEGINNING
  • TIMECOST SCOPE
  • TIMECOST MIND READING
  • YOU CANT AFFORD TO GUESS
  • THIS? Do they want
  • WF DASH out of the box
  • OR THIS?
  • custom
  • WINDOWS OR MAC? Do they want
  • CHOCOLATE OR VANILLA?
  • DESKTOP OR MOBILE?
  • APP OR MICROSITE?
  • WHY SO MANY ?????S
  • ITS ALL ABOUT THE USER
  • ITS ALL ABOUT THE PEOPLE UNDER OUR CARE
  • Leah Buleys The User Experience Team of One Dev Patnaiks Wired to Care
  • Start listening tours Design with your people Become your customers They say
  • BREAK THIS DOWN, PLAYA ! **Translation: Lets get practical. Id like an example. **
  • 1. Enter Business Problem. 2. Business Analyst writes email requesting extract. 3. Business Analyst waits. Data Analyst reads request and makes unnoticed assumptions. 4. Data Analyst writes SQL. Emails Excel. 5. Business Analyst, disappointed she got what she asked for but not what she needed, asks for even more data than shell need, just in case. 6. Data Analyst pulls all the data and struggles to get it to the BA. (its too big to email now).The system sighs. 7. Business Analyst apologizes, assures the Data Analyst it was a one-off 8. Data Analyst knows hes wrong/lying, saves SQL for next time. 9. Repeat 1-7 ad nauseum The OLD way
  • 1. Enter Business Problem. 2. Business Analyst comes to Data Analysts desk & explains what she needs. 3. Data Analyst asks how the data will be used and if it is related to the thing they worked on last week together. 4. Business Analyst explains how she will turn it into charts and bullet pointed conclusions & yes, use it with last weeks data. 5. They whiteboard and use Excel to sketch a prototype. 6. Data Analyst builds a prototype of charts and bullet pointed conclusions and offers the raw data beneath it. 7. Business Analyst gives feedback.They repeat steps 5-8 until its good enough for Business Analyst to use. 8. Perhaps, they both agree, this insight is useful to more people. They begin prototyping for a larger audience. Insight Design
  • Insight Design IS ABOUT Effective partnerships Needs getting met Data informing action
  • IS UX + BI INSIGHT DESIGN
  • THANKS. THIS WAS FUN. Whatd you think? ! ! @robsaenz