Process: Design Process

In my previous columns, I’ve framed my discussions around the practice of information architecture. To recap, the DSIA Research Initiative—of which I am the curator—defines the practice of information architecture as “the effort of organizing and relating information in a way that simplifies how people navigate and use content on the Web.” While the practice of information architecture can surely extend beyond the Web and its content, this IA practice definition eschews theoretical language to resonate with businesses looking for concrete Web solutions and practitioners who want to make a living off something tangible.

In the end, business clients don’t pay practitioners to practice information architecture; they pay professionals to produce IA work products that help them to meet their business objectives. So, of the many professional interests that come together to create a digital experience, what work products make the practice of information architecture unique? Read More

We’re embarking on an increasingly automated future. By 2029, computers are likely to be more intelligent than humans, according to Ray Kurzweil, Director of Engineering at Google. Recent technologies such as artificial intelligence (AI) and machine learning can now support nonlinear, complex tasks that require logic—and, historically, human involvement as well. These innovations are transforming everything from the way financial technology, or fintech, startups offer financial advice to self-driving cars—and even smarter recommendations for the shows we stream on Netflix.

As automation increasingly plays an integral role in the complex products we create and use, we’re seeing great opportunities for automation to play a role in the future of UX design as well. Automation may be the next big thing to impact the entire industry of UX design—from optimizing the process of providing design feedback to transforming and streamlining the way product teams operate and increasing our ability to create compelling products. Read More

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