UXmatters has published 22 articles on the topic Requirements Definition.
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 this installment of Ask UXmatters, our experts discuss how to write effective usability requirements and determine the right metrics for the redesign of a legacy, public-sector system.
Ask UXmatters exists to answer your questions about user experience matters. If you want to read our experts’ responses to your questions in an upcoming installment of Ask UXmatters, please send your questions to: [email protected]. Read More
So, you’ve wrapped up your customer research, completed your personas, and have even written a few scenarios that show how users would want to interact with your brand new product. What’s next? What happens to the personas and scenarios once you’re ready to start requirements definition and design. Are you sure you’ve adequately communicated the type of system your users need to the Business Analyst and Interaction Designer on your team?
If you’re like me, you’ve always felt something was missing once you finished creating your personas and scenarios. They communicate the heart and goals of the user, but miss out on a lot of details. And while it’s the intent of both documents to do just that, neither personas nor scenarios succinctly communicates to your business what features a product or service should have and why it should have them. Read More