As the websites and digital products we build become more and more complex, it is more important than ever to ensure that we are not excluding people from being able to experience them. It is therefore imperative that we understand how all users interact with our products, particularly screen reader users. I'm not saying we all need to be experts at using them, even though that's not a bad goal, ...

As product people, we're used to being bombarded with feature requests from different stakeholders like the sales team, partners, other teams within the organisation, or even our customers and users.

It can be difficult to ignore the niggling thought that the career path you chose as a teenager might not be the most suitable direction for the person you have become. After having so much time for reflection over the last few years, many people are experiencing this same worry. In 2021, there was a 24% rise in applications from mature students for full-time undergraduate degrees, raising the bar for ...

As a product person, I know there’s always an infinite number of requests and problems that my teams could be working on. These can come from users, or different stakeholders within the business and they’re usually mostly linked to something they want to unlock or move forward relating to their goals. But that doesn’t necessarily mean that we should action them, or that we will entertain them at all.

tl;dr I'd like to see services like GitHub and GitLab give users the option to hide their contribution activity to help foster a healthier environment.

Making websites has become easy. As creatures of habit, we use the same tools we love to get our job done. As the world is slowly but surely facing irreversible changes because of human activities, what can we do to help as developers?

In my career as a product designer so far, I've learnt that creating a strong relationship with the engineers in the team is one of the most important elements for success. I’ve really enjoyed working closely alongside, and learning from, the developers and engineers on the teams I’ve been a part of, and it’s great to be able to work directly with the people building what I’m designing. From conversations ...

We often talk about user-centered design and development, however the process rarely includes accessibility and UX research with users with disabilities or impairments. (Web) accessibility is the practice of making your websites usable by as many people as possible, thus providing equal access to information and communications technologies, including the Web, to people with disabilities or impairments. Simply put, accessibility is a basic human right.

It’s a term that you can’t seem to get away from in product development since Frank Robinson introduced the methodology in 2001, and then Eric Ries popularised its meaning in 2009 as part of his larger thinking around Lean Startups.

As a developer, you want to ensure your work is accessible, but it can be hard to know where or how to start. You’ve been trained to write semantic HTML & add alt tags, but is that enough? What about a Lighthouse score of 100 — does that cover everything? (Hint: It doesn’t!)