Two researchers could write very different test plans when an objective is unclear or misaligned. You can start the conversation at a high level by determining what features or processes they want test participants to review, like a navigation menu or website messaging.Īnd before you put a stamp of approval on a research objective, ask for feedback from your team. For further inspiration, collaborate with the product’s stakeholders. FAQ concept test: Is the design approach we’re considering for the proposed redesign understandable? What can we do to optimize it?Īs you can see, the above objective can be branched out to address content, usability, and design.FAQ accessibility: Can customers easily find the FAQ section? What access points should we consider?.Content quality: Learn whether the FAQ questions anticipate users’ needs and if the answers are sufficiently detailed and directive.For instance, take this research objective, “I want to understand and resolve the barriers customers face when looking for answers about products and services on our website.”įrom this one objective, potential study angles could be: In addition, your objective doesn’t have to spark one angle alone it could have the potential to inspire multiple test directions.

Subsequently, it’ll also be easier to extract answers later on in the analysis. Many UX researchers agree that the more specific the objectives, the easier it is to write tasks and questions. From there, your objective might look like, “Do people find value in this new product idea?” or “How do our competitors describe their offerings compared to us?” Before you write your objective, you need a problem statement, which you can source from your support team and the frequent customer issues they encounter, negative customer reviews, or feedback from social media.

What does it mean to be objective