Design Technology. Prototype vs SIM

I loved this presentation from the folks at frogDesign. They were most wonderful – creative, geeky, informative all rolled in.

“Users wont wear the glove, they will dance.”

Key Concepts

  • “Quantum inspiration” – if you have inspiration, there’s a likelhod others had the idea too. Because of rapid propagation one needs to move fast.
  • Generative gut check” – trust your gut.
  • Requirements fail/wireframe fail – esp. when Visionary, Innovative & Prescriptive.



  • Step 1: State the problem
  • Step 2: Whole bunch of ideation up front – many ideas to solve the problem
    • in your gut, what is your favorite/most viable. Trusting your gut on a disparate team
    • advance this
    • identify & solve
    • focus on: architecture, interaction
  • Step 3: Build
    • Expedient technology is used to stand up the model as rapidly as possibly. Very different than wireframing/prototyping.
    • Throw hardware on it, right poor code, get it in front of the customer asap
  • Step 4: Show
    • Put the simulation in front of customer and use it for storytelling
    • Generative Whiteboarding – then pick a single viable. (very similar to the 1up concept)
    • Flipping through a virtualizations is so much more relevant for stakeholders, esp. for hardware.
    • Index of the vision, but tell them it’s fake! Blue sky factor – maybe it will be 5 years in the future.


  • Making is designing.. no more design then make! So say the folks at Frog Design.
  • Fragmentation in technology also becomes a design issue. Designing for multiple devices, one learns just making & doing.
  • Have the engineering team do design concepts early on.
  • 4 integrities: perceptual, technical viability, logical, economic.
  • Never underestimate the smallest prototype in someones hands vs. vast volumes of paper.
  • Bring the engineers into the process, don’t have them siloed. If you can show them you got to the 10% of what you want to get to, then engineerings will trust the design more and they will work toward you.
  • Flip your engineering team from the guy who protects the requirement to the guy who enables the designer.


There was a quad chart here.. didn’t have time to re-do it.. but imagine it!









Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s