I’d like to propose an alternative to typical, preliminary design exploration techniques such as wire-framing and interactive prototyping – when designing new Microsoft Surface experiences. In 5 years of brainstorming, visualizing, and creating Microsoft Surface experiences as a designer; I have definitely learned the limitations and advantages of various techniques due to the fact that showing interaction design on Microsoft Surface requires a lot more human interaction (touch, multi-touch, complex gestures, etc.) as well as other factors like physical objects, multi-directional experiences, etc.

What is Video Sketching?

Video Sketching is a technique that involves using a any simple video camera (i.e. Flip), any surface, everyday objects, some green construction paper, and some simple AfterEffects (or equivelant) compositing techniques any designer can easily pickup. Video Sketching is a technique optimized for:

• Quickly and efficiently exploring and visualizing key feature ideas, design solutions, scenarios
• Easily communicating a design concept to a wide audience (i.e. researchers, developers, management, etc) BEFORE a line of code is written
• Visualize solutions that involve interaction beyond the device itself
• Visualize your solution with real people!

Why Video Sketches?

• They are lightweight, low cost, efficient, and most importantly… disposable!
• FAR more cost-effective than building premature, functional software prototypes
• Provides more breadth to design possibilities and communicates the right information at the appropriate time
• Helps you think about how users realistically approach Surface (just by physically acting out your own scenarios)
• Forces designers and researchers to think ‘outside of the screen’ to ultimately design solutions that are seamless with their environment (as opposed to UI wireframes)
• Allows you to ‘mock-up’ scenarios that are outside of your current technical capabilities (i.e. integration with other devices, new technologies, even audio, etc.) - helping set a bar to work toward and even drive technical requirements.
• Allows you to consider other form factors for the product in a variety of settings