How to Build and Lead User Experience (UX) Teams

This article presents 9 guidelines for building and leading UX teams. They are based on what I learned from the people who led me as well as my own experience: recruit diverse talent; set up a process (and iterate); involve other teams from the start; be fair; have regular ceremonies; pass on knowledge; have a vision; ask questions (a lot); and make UX visible.

More Design, More UX … And More Books

I know I was a little negligent of my blog in 2018 and 2019, and I didn't write nearly as much as I would have liked to. But I'm very determined to improve on this again. (As you might have noticed based on the last three articles I published in pretty quick succession before they… Continue reading More Design, More UX … And More Books

Jobs To Be Done in a Nutshell

The theory of Jobs To Be Done explains that too much focus on socio-demographic data and correlations hurts companies. Rather, you have to gain a deeper understanding of your customers, who "hire" your product to help them do certain jobs under certain circumstances. For instance, you don't buy a video game console because you're male and over 30. You hire it to, e.g., do the job "connect with friends".

5 Design Methods I’ve Successfully Applied as a UX Manager at C&A

Depending on the environment you have to navigate, it's not always easy to try and apply all of the awesome design methods that are out there, be it due to daily business or a lack of management buy-in. In this article, I describe 5 methods that I have successfully and effectively applied in C&A's eCommerce department: Design Jams, Storyboards, Crazy 8s, 4×4×4, and Buy a Feature.

What’s a Design System, Design Language, and Design Language System? And what’s the Difference?

Depending on who you ask, a design system and a design language might be the same thing or not. Regardless, the important point here is that both a system and a language go beyond a simple pattern library. They have to include a set of rules and guidelines to give the included components structure and meaning.

An Introduction to Agile Development, Part 2: Getting Started with Scrum

To get started with Scrum, grab one of the popular tools (e.g., Jira), implement all the Scrum artifacts and fill your gaps with some experienced people. It is not all too important to have the right task estimates, sprint lengths, etc. from the beginning or to follow the methodology dogmatically. The crucial part is to have a team that commits to the process, reflects critically, is eager to learn, and improves incrementally.

An Introduction to Agile Development, Part 1: Scrum vs. Kanban

TL;DR: Two of the most popular agile methodologies are Scrum and Kanban. They mainly differ in the handling of prioritization (once per sprint vs. continuous) and deadlines (yes vs. no). Yet, independent of the approach, the key to success is to ensure focus and continuous delivery by: 1) creating small enough, manageable tasks, 2) prioritizing… Continue reading An Introduction to Agile Development, Part 1: Scrum vs. Kanban