Ask The UXer

In Part 1 I laid out how this effort to get away from the confusion and cruft on your site has to start with empowering someone / team to create and maintain a coherent website, or if that person already exists, like a CPO, to remind them this is part of…

Eighteen months ago I told you We will need to know our users better than we ever have before we even start to design something, or we will flood the zone with so many bad ideas our users will run away from our product or brand at the speed of light.

Medium for some reason thinks I continue to want to read about the demise of Agile project management methodologies for making software.

Why software dev is so hard, Part 1, Part 2 Testing in production is really expensive As discussed before, decades of experience teaches us we have to show users what they say they want so we can find out what will actually work for them, and we have to do

The Limits of Prototyping in Agile Development Central thesis of why software development is hard, and Part 1 So pretty soon in the late 90s it became common to find out what humans wanted out of computing systems by giving them a simulation of the system…

“Where have all the task decompositions gone?”

Scrum has been having a bad time for the last ten years, and thus so has Agile.

Six hundred years ago, in the early 2010s, I was working a contract—a heritage company that needed their website to be responsive—where I met my first digital transformation consultant.

I left London after ten years, and moved to Berlin, for various reasons.

The first time I actually worked on something we could term User Experience, I was changing the default positions of my icons on a UNIX workstation running some version of SunOS (in other words, it was a long effing time ago) and part of that was designing