9. EXPLORE
WHEN DATA IS INVOLVED
• Have the attitude that “anything is possible (eventually)”
• Don’t focus too much on the details of the data or analysis
• Speak the language of the problem, not the solution
15. SKETCH
WHEN DATA IS INVOLVED
• Usually sketch many times before writing any code
• Make sure concept addresses one use case well
• Use finer tipped markers, pens, and pencils for more detail
• Build even more refined wireframes with inkscape/photoshop
• Keep using the language of the problem owners, not nerd speak.
21. PROTOTYPE
WHEN DATA IS INVOLVED
• This involves getting data, doing some analysis, and presenting results
• Short iteration cycle forces you to focus on essential parts
• Important thing is to start building trust with end users
• The details of feasibility come up here
• It’s OK to fail; you’ve got lots of good ideas on the backburner