Friday, May 22, 2015

Greylock Partners: Prototyping Research

Greylock Partners: Prototyping Research

An in-depth look at the tools and process design teams use for asset creation, prototype creation, design asset storage, prototype sharing, and challenges in the process.
Published in: Business, Design

 Transcript

  • 1. Greylock Partners Prototyping Process Survey Results ! Chris McCann
  • 2. Survey Background • 33 participants ! • 40% B2B | 84% B2C* ! • Designer Team Sizes:
 3% 1 design team member 31% 2-5 | 28% 5-10
 12% 10-25 | 13% 25-50
 13% 50+ *companies can list as both B2B and B2C
  • 3. Other Photoshop Sketch Illustrator Asset Creation Tools • 50% of designers use more than one tool, 34% sketch only. ! • 71% of B2B designers using Sketch ! • 72% of designers are designing for both web and mobile, 9% web only
  • 4. Other Keynote Invision Framer Flinto Prototype Creation Tools • 75% of designers use more than one prototyping tool ! • Framer/InVision is most popular combo. ! • No set prototyping tool, lots of designers using Pixate, HTML, Bootstrap, Avacado, etc.
  • 5. Other Google Drive Dropbox Box Prototype/Asset Storage • Dropbox is the clear leader for storing prototypes and asset files - 77%
 • More sensitive prototypes will host on internal servers.
 • 0% of B2B companies host on Box.
  • 6. Coding Involved in Prototypes • Responses are all over the place.
 • “Consensus” is very little programming and if so most of it is in the animations and interactions.
 • A few complex or data intensive apps needed more coding involved.
  • 7. Sharing prototypes • Responses are all over the place.
 • “Consensus” is in person or over company communication channels (Slack, WebEx). Typical is to share the Invision or Framer link. (Check out wake.io)
 • Hard part is collecting the feedback and making changes to the initial prototype. Much of that is taken in notes, person, docs, etc. (Check out Red Pen)
  • 8. Biggest frustrations with Prototyping process • Easily communicate prototype (flow + animations) without needing a lot of coding.
 • Very time consuming. Ex. Framer is great but steep learning curve.
 • Difficultly of moving from prototype to implementation, having spec for engineers. (Avocode)
 • Too many disparate tools makes process cumbersome. Asset creation, flow, and animation should be in one tool.
  • 9. Greylock Partners Prototyping Process Survey Results ! Chris McCann
at