UI/UX Articles and Interesting Tidbits of the Week
July//12//2024
Here are some interesting finds on UI/UX of the week!
1.
The Need for Qualitative Research. Interesting article from dScout’s blog, “People Nerds”, hailing from author Charles Perry on the topic of proving to executives why Qualitative Research is important. The author provides some recommendations on how to make this process a reality, including running a research initiative, attaching these research endeavors to projects that are already endeared to executives, to name but a few. This type of article still baffles me, not for its intention, but for the fact that we’re in 2024, and yet it feels like Design and Research professionals are always toiling and advocating for data insights that should be something that any executive should be clamoring as well. And this is something that seems to be a never ending toil for Design and Research professionals. Highlight of the article includes:
“Execs have a way of fast-tracking pet projects they think are particularly important, and are more receptive to greenlighting work that focuses on topics they personally find exciting. (They’re human, too.) Volunteering to run an unexpected project proposed (or demanded) by leadership can be richly rewarding — though harrowing at times. Pitching a project on an issue an exec champions or returns to again and again can also be effective at jump-starting stalled work. The trick is to first get aligned and rigorously set expectations — regarding motivations behind this research, best-case scenario data output, timeline, and responsibilities. Then design a research plan so it’s likely to capture what senior decision-makers need to hear — not just what they want to hear. Be ready to propose a new battle plan if results actually end up proving executive expectations wrong. Having their assumptions called into question will be an uncomfortable, destabilizing moment for leadership. Offer some solid ground and a way forward.”
2.
The Potential of System Thinking in Modern Design. This article hailing from the Adobe Design Blog and author Bushra Mahmood is an insightful look at how System Thinking can and should permeate how Designers think about problems (and their solutions). An interesting quote on System Thinking states “system thinking is a nonlinear way of working that requires mapping all product dependencies you know to be true. System thinking has nothing to do with immediate user success; it focuses on understanding all the root causes of a problem, to plan for several possible solutions.” The article goes about explaining how System Thinking can in fact be implemented, detailing aspects such as Central Platforms, Frameworks and Patterns, UI Libraries, and Systems Processes and Checks. Well worth reading through this article, which features some very pertinent examples. Highlight of the article includes:
“A great example of natural collaboration between a system designer and product designer is when designing for a native platform like iOS. Apple has created a platform and basic set of interface elements that are reliable and have system thinking inherently built in, which means that any designer building with iOS guidelines is doing so with an understanding that their work will evolve along with the evolution of the system. That way, if new hardware or technological capability is unlocked, its integration will be far more natural than if it had been built independently of the system.”
3.
How UX Strengthens Businesses. Another article from the series that Dovetail had from their Insight Out conference, this one documents a presentation from Claudia Natasia, Co-Founder of Riley AI, who goes through some very interesting examples each demonstrating how data, research and ultimately UX played a fundamental role in molding the future of those business endeavors. The examples that are showcased illustrate user behaviors that have changed, how they impact adoption, acquisition, and ultimately inform product perception and shape relationships for clients. Very pertinent and relevant read. Highlight of the article includes:
“You’d want to collect data on relevant insights, like recurring usage. If you see people using certain areas of your product a little bit more, that’s a signal that there is a lot of interest in that particular area. And I challenge you not to take that insight at face value. If someone’s using the tablet a bit more, it doesn’t necessarily mean that the in-store tablet at Fivestars was the end game. We find other things that are essentially root causes or drivers of that behavior.”
