“They’re not using it the way it’s designed to work.”– clients’ response to your UX design concepts..
“This is a training issue.”
“We just have to train the users to do it that way, not this way.”
“We don’t want to design things that enforce behaviors we don’t like.”
I have heard these comments many times in the enterprise UX world. Sometimes we have this idea of how things should work in our head. We have ways in which we wish users would do things. Or we’re attached to the way we designed a system to work. And even when we find out users aren’t using it how we’d expect, how we might prefer, we turn it into a training issue rather than a design exercise.
Sometimes, “the customer is always right.” Design should be in service of a users’ process, not a deterrent. Products should be designed to be intuitive, not require weeks of training. Instead of the above mindsets, I encourage team members to reframe the problem and riff on some “how might we’s..
How might we design it to work the way people want to use it?– reframing the “training issue..”
How might we learn why people are not using it as trained?
How might we let users’ natural behaviors guide our design decisions?
How might we respond to users’ workarounds?
Elon Musk says, “Any product that needs a manual to work is broken.”
— For the most part, I kinda agree! How about you?
TᕼE IᑎᗪIE ᑕOᑎᔕᑌᒪTᗩᑎT
𝗣𝗿𝗼𝗱𝘂𝗰𝘁 »𝗖𝗫« 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 𝗗𝗲𝘀𝗶𝗴𝗻
I’m Heatherlee. An independent research and design consultant with a background in UX, a passion for service design, an interest in biomimicry and a stake in your strategy. I’m passionate about helping you bridge the gap between your product teams and the people you design for.
Contact info & more about me here.