Skip to main content

Home/ ModCloth_IXD/ Group items matching "guidelines" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Megan Pearlman

http://www.bbc.co.uk/guidelines/gel/downloads/gvl3_styleguide_v1.pdf - 2 views

  •  
    BBC Global Visual Language (PDF)
Jonathan Hung

What people see before they buy: Design guidelines for e-commerce product pages with eyetracking data | cxpartners - 3 views

  •  
    Cool article; about a 50/50 mix of common sense v. unexpectedness... although some conjecture seems more opinion formed on observation than fact-based. I like guidelines 1, 2, and 4 a lot.
Andrea Nelson

Design Better And Faster With Rapid Prototyping - Smashing Magazine - 3 views

  • What Needs to Be Prototyped? Good candidates for prototyping include complex interactions, new functionality and changes in workflow, technology or design. For example, prototyping search results is useful when you want to depart significantly from the standard search experience; say, to introduce faceted search or the ability to preview a document without leaving the search results.
  • How Much Should Be Prototyped? A good rule of thumb is to focus on the 20% of the functionality that will be used 80% of the time; i.e. key functionality that will be used most often. Remember, the point of rapid prototyping is to showcase how something will work or, in later stages, what the design will look like, without prototyping the entire product.
  • In choosing the prototype fidelity, there is no one correct approach. Most designs of new products are best started with sketches, then moving to either medium- or high-fidelity prototypes, depending on the complexity of the system and the requirements of the dimensions of fidelity.
  • ...2 more annotations...
  • Avoid “prototype creep” by setting expectations for the process, including ones affecting the purpose, fidelity, scope and duration. Remind everyone, including yourself, that rapid prototyping is a means to an end, not an end in itself.
  • Don’t begin prototype review sessions without clear guidelines for feedback. Be very specific about the type of feedback you are looking for. (Are the steps logically arranged? Is the navigation clear and intuitive?) If not, be prepared for, “I don’t like the blue in the header,” or “Can’t we use this font instead?” or “Can you make this bigger, bolder, in red and flashing?” Don’t be a perfectionist. In most cases, rapid prototyping does not have to be 100% perfect, just good enough to give everyone a common understanding.
1 - 12 of 12
Showing 20 items per page