UXmatters has published 18 articles on the topic Design Strategy.
This month in Ask UXmatters, our expert panel discusses how objectives and key results (OKRs) can inform UX design. The panel explores how the use of OKRs differs from traditional requirements gathering. Our panelists then discuss the relationship between OKRs and product strategy and common pitfalls of using OKRs.
We also recommend a couple of books that could help you apply OKRs in your work. Finally, I discuss the importance of keeping business needs in mind. Read More
In the first part of my series on applied UX strategy, I outlined a UX maturity framework. Parts 2–4 of this series provided in-depth coverage of some operational and tactical aspects of implementing UX strategy, including requirements for product designers, employing platform thinking to ship quality products, setting up a design team, and creating a design culture. Now, I’ll begin my discussion of how to solve business problems through design.
In Part 5.1, I’ll discuss the use of a shared language between business and design, then solving business problems through design. Finally, I’ll consider the transformation of the product designer’s role in depth, which progresses through three stages:
When information architecture (IA) arrived on the scene in the late 1990s, it brought attention to an aspect of user-interface design that was then only marginally understood: structure. The need to focus on structure is still a significant concern—especially in environments of large scale and complexity.
Digital product and services organizations and large institutions regularly fall short of their desired goals because their user interfaces lack sufficient structure. With today’s complex landscape of human-digital experiences, it is necessary to be mindful of the importance of structure—and its relationship to the practice of information architecture. Read More