Linknote — — 200 words

Business — User experience — User research

Undemocratising user research — Saswati Saha Mitra — UX Collective

A magic triangle: "Choose two between sustainability, scale and quality"

This piece really challenged my thinking.

In my job I am currently trying to figure out ways to make quality user research scale across the organisation in a sustainable manner. It’s like one of those triangular diagrams outlining three goals: “you can have two of these things”.

Working in such a large organisation, central resources inevitably have their limits. My desire is to empower others to carry out their own user research. Our role becomes an education role. How we do that remains an unsolved problem. Various attempts have yielded variable results.

But Saswati Saha Mitra, reflecting on her experiences of trying to democratise user research, suggests that it is a bad idea.

A researcher is a dynamic thinker who has to adapt their methods and questions based on who is in front of them, how much they have already learnt and what new areas could be probed on. This did not happen. We got a lot of verbatim and videos which after a point became repetitive and did not add more to the analysis. This then led to analysis paralysis.

I’m inclined to continue trying to empower others to conduct user research. But this article is food for thought.

Linknote — — 55 words

Content design — Human-centred approaches — User experience — Web

Work:

We’re hiring a Senior Content Designer — Website and Communications Blog

View of Edinburgh Castle from our office

The University of Edinburgh Website and Communications team is hiring a Senior Content Designer. Come and join my team!

If you’re passionate about using evidence-based approaches to create great content that meets users’ needs, we want to hear from you.

Read the blog post to learn more about the position and how to apply.

Linknote — — 206 words

Human-centred approaches — Technology — User experience

Principles and priorities — Jeremy Keith — Adactio

What makes a good principle? How do you avoid principles that are mere motherhood and apple pie? According to Jeremy Keith, it’s all about establishing priorities.

He goes on to outline the danger of prioritising the experience of developers or designers above the user experience. He makes an interesting observation about a perceived difference in the way developers, er, develop and the way designers do.

Developer efficiency is prized above all else. Like I said, that would be absolutely fine if we’re talking about technologies that only developers are exposed to, but as soon as we’re talking about shipping those technologies over the network to end users, it’s negligent to continue to prioritise the developer experience…

I’ve been talking about developers here, but this is something that applies just as much to designers. But I feel like designers go through that priority shift fairly early in their career. At the outset, they’re eager to make their mark and prove themselves. As they grow and realise that it’s not about them, they understand that the most appropriate solution for the user is what matters, even if that’s a “boring” tried-and-tested pattern that isn’t going to wow any fellow designers.

Linknote — — 96 words

User experience — User research

Meeting the challenges of conducting user research remotely — Website and Communications Blog

A laptop displaying a user interface

The coronavirus outbreak has posed massive challenges for everyone in society. For practitioners of human-centred approaches to design, where face-to-face interaction is often so important to enhancing our understanding, our current requirement to maintain social distancing creates obvious barriers.

However, this doesn’t mean our work to ensure we’re meeting people’s needs has to stop. In fact, there are some perhaps surprising advantages to working remotely as a user experience practitioner.

Over on my team’s blog, I have outlined some of what I’ve learned about remote user research over the past month or so.

Article — — 100 words

Service design — User experience — User research

Work:

Screenshot of the remotely-held UX Glasgow meetup

This week I presented to the UX Glasgow community about our user research into the needs of students and staff working with course materials digitally at the University of Edinburgh. It was my first real experience of presenting to a live audience remotely.

Linknote — — 84 words

Accessibility — Web

HTML: The Inaccessible Parts — Dave Rupert

Following on from Gov.UK’s revelation about <input type="number">, Dave Rupert has compiled a list of other bits of HTML that can cause inadvertent accessibility issues.

There are some cases where even using plain ol’ HTML causes accessibility problems. I get frustrated and want to quit web development whenever I read about these types of issues. Because if browsers can’t get this right, what hope is there for the rest of us.

Not that we should give up, of course.

Linknote — — 79 words

Business — Human-centred approaches

McKinsey: CEOs have no clue what chief design officers do — Mark Wilson — Fast Company

Picture of a hipster drinking coffee with headphones hanging of a massive Mac screen. I guess that's what a designer is.

Talk about designers “having a seat at the table” generally leaves me cold. But this useful article explains why it can matter — but why designers have a duty to do more than simply be at the table.

Evidence has long suggested that companies with a strong design focus are more successful. The example of Logitech outlined here bears that out.

But if some CEOs don’t understand the value of design, it’s up to designers to articulate it properly.

Linknote — — 83 words

Accessibility — Human-centred approaches — Web

Why the Gov.UK Design System team changed the input type for numbers — Hanna Laakso — Technology in government

Numeric keypad interface

The Gov.UK Design System team have discovered that using the HTML element <input type="number"> creates some surprising problems in certain environments.

Some of the limitations in assistive technologies such as Dragon Naturally Speaking are disappointing but unsurprising.

But Chrome deciding to convert large numbers to exponential notation is rather more eyebrow-raising. Then there is Safari adding commas to long numbers that are in fact credit card numbers. You have to wonder about some of the decision-making among browser vendors.