mLearnCon Session: Pretotyping: Design, Iterate, and Test Apps Before You Write a Line of Code

Wednesday June 16, 2010 02:30 PMMain Pointsto get good ideas, you need a lot of ideasshorten the failure cycleincreases innovationGoogle – no processes, diverse work (start-up) culture90 second pitchescomes before wire frames and prototypingaccelerates conversations and concept developmentRaw Dump:Expends…

Wednesday June 16, 2010 02:30 PM

Main Points

  • to get good ideas, you need a lot of ideas
  • shorten the failure cycle
  • increases innovation
  • Google – no processes, diverse work (start-up) culture
  • 90 second pitches
  • comes before wire frames and prototyping
  • accelerates conversations and concept development

Raw Dump:

Expends includes money, time, mind shift, etc.
Paper
Paper and video
Not a wireframe, something that has some thought behind it, a next step

Full or partial mockup
Investment of min/hours/days
Implies rather than achieves a design
Democratized innovation ?
Lo-fi aesthetics reflect transitory nature, intentionally

Goals
Increase innovation
Increasae ideas in the pipeline
Accellerate fail velocity
Good ideas from lots of ideas

Think napkins, keeps it in his pocket
Is there a use case
Are there extrinsic rerwards?
Google bike app is the example
You want to taet your idea

What do you want to accomplish simply really well

As little program management as possible, high iterations

He mentioned agile in reference to project managment?

Think creative commons, two hours to create the video
The value is in the conversations between the evaluators, 30-60 min of time from the evaluators

Why use video? Rapid growth of conversation
How has the culture adopted this approach?