Top

Process: Design Process

UXmatters has published 102 articles on the topic Design Process.

Top 3 Trending Articles on Design Process

  1. Creating a UX Design Style Guide

    November 18, 2019

    “A style guide is an artifact of design process. A design system is a living, funded product with a roadmap [and] backlog, serving an ecosystem.”—Nathan Curtis on Twitter

    As Nathan Curtis described on Twitter, a style guide is a document that a UX designer creates to document a growing and ever-evolving set of design guidelines that arise from the design process. In creating a style guide, UX designers are basically documenting their own thought process as they design a Web site, application, or system. Thus, the essence of creating a style guide is documenting your own design decisions. Who is the audience for this document? In this article, I’ll answer many important such questions about style guides to help UX designers create effective documentation. Read More

  2. Reviewing User Interfaces

    February 23, 2009

    Has your boss or a client ever asked you to review a user interface for a Web or desktop application? Perhaps the request went something like this: Can you just look over these new screens for us? Oh, and can you check the error messages, too? It won’t take long! And, by the way, we ship next month. Whether you are an interaction designer, usability professional, technical communicator, quality assurance engineer, or developer, reviewing a user interface typically means identifying

    • usability problems related to the layout, logical flow, and structure of the interface and inconsistencies in the design
    • non-compliance with standards
    • ambiguous wording in labels, dialog boxes, error messages, and onscreen user assistance
    • functional errors

    Read More

  3. Choosing the Right UX Process for Your Software-Development Model

    June 17, 2019

    “It’s very easy to be different, but very difficult to be better.”—Jonathan Ive, Chief Design Officer, Apple

    Deciding on the right product-development process for your team can often be a paradox. Maintaining balance amidst a proliferation of inconsistencies in product requirements and development outcomes is challenging for both large and mid-sized organizations —especially when teams lack any metrics to measure their impact on a release.

    Friction arises when there is a mismatch between the user’s mental model and product features. When a development team finds itself in an untenable situation, the blame game begins. But as Mad Men’s Don Draper often said, “Move forward.” Read More

Champion Advertisement
Continue Reading…

Columns on Design Process

New on UXmatters