The little UX that could...

This is a simple fairy tale that talks to the experience of being a UX person. You are not going to be the King, you are not going to be the Princess, so you have to find room for UX.

Given a simple development process - Definition, Back end Development, Implementation - the Princess (sponsor) will be involved in the definition, and be partly involved in the other two steps. The Wizard - back end developer - will be involved in the back end development based on definition and throwing it to implementation. The Witches - implementation team - will only be involved in implementing. As UX you will be involved in all steps in the process. So we have to create success without ownership.


Frequently someone else owns the product definition, and you will not be the only one who sees issues with the definition, but you will likely be the first person to say that we need to get the user involved.

Frequently, someone else owns the requirements. In the fable the little UX had to work with an incomplete set of requirements and expand them out to include the user. Usually, the project sponsor will push forward with development, even though you are not done. Be ready to go back and rebuild consensus.


Someone else owns implementation. They are going to be focused on implementation, not on the end user. They will be measured on their ability to implement the system, not how well the system works. You need to be the one to bring the purpose of the system back into the process.

Acceptance is not buy in. People will all love the user, until something causes them pain. You will have to go back, again and again to align
consensus and to bring the user back into the process.


Managing UX in the real world requires techniques and tactics that work up and down the conceptual ladder. Don't wait for a mandate. Concentrate on the idea that "I can make things better".


Always offer solutions to every problem you raise. Don't think your solutions are the be all and end all, but use them as a starting point for discussion. If you just point out the problem you will generate resistance.


Be ready to work harder than anyone else involved in the product.

Enjoy the successes, but don't take them at face value.

Don't assume that a successful project will have a positive effect on the next.