When we do early-phase UX analysis, we dream of getting clear-cut outcomes from the information we gather. That the whole lot will come collectively neatly. But, typically, our analysis findings find yourself being much less apparent than we’d like them to be. This ambiguity makes deciphering our analysis findings and defining a product technique difficult. As UX researchers, which ends up and suggestions ought to we current to stakeholders? Will they miss out on one thing vital if we don’t share all of our findings with them? Which outcomes ought to we deemphasize? How can we navigate the anomaly that may outcome from formative UX analysis?
In this column, I’ll present some key methods for find out how to deal with the anomaly that comes with analyzing qualitative knowledge from formative UX analysis. As a lot as we attempt to stay unbiased and depend on the precise proof that we’ve gathered throughout our analysis periods, we might generally speak ourselves into taking a facet when presenting our findings and suggestions. How can we double-check our motives and make sure that we do proper by our product stakeholders—even when that may imply delivering unhealthy information to our product crew? Read More
This article sources data from UXmatters