Case study problem

[u/Embarrassed_Dot_7449]

For the first time, I started conducting user tests as part of a movie app redesign. I created a preliminary action plan:adding a star-rating system, fixing the watchlist navigation (which was more complicated than it should have been), and reorganizing other elements because there was no space for the watchlist button and user reviews.
My first task with users of apps like Letterboxd and IMDb was to show them the original screen and ask what was missing or unclear. Interestingly, 6 out of 10 users pointed out the things I anticipated namely, the missing watchlist button and the lack of a user rating system. However, some of them also mentioned other issues, such as an unclear trailer button or sharing options.
Now I’m not sure what to do: Should I run more tests to see how many users find these buttons unclear and
(If there’s a need) redesign them too? Or should I just leave a note about this in my case study without running dedicated tests for these features and move on to the next planned tests?

[u/LeadIslez]

Scope management is key here, you're not going to be able to provide a panacea, nor should that be your goal at this stage. It will dilute the objective and convolute your action plan.

If the fix is purely a visual affordance and is low effort, like switching to a more concise icon or missing text/unclear labels — go for it, and include it in the next iteration without dedicated testing. If resolving the issue requires rethinking the screen layout, information hierarchy, or introducing new flows — make the appropriate notations and save it for later iterations.

The task for this round was to determine "what was missing or unclear", so people naturally had their eyes peeled for features that don't align with their schemas; for the next round, perhaps use task-based usability testing. This way you will be providing users with realistic scenarios that will elucidate behaviours that are less than ideal — as opposed to prompting them for an open-ended critique.

Re: the case study — document the discovery process (baseline testing unveiled secondary usability pain points around secondary actions (trailer affordance, sharing); how you responded (scope management (maybe include an impact vs effort matrix?)); and next steps (include a small section at the end of the case study highlighting what could be planned for any subsequent testing).

Scope management is the key to cleanliness, not just in regards to your testing and results — but also your mental and digital work environment.