UX Politics
We represent a population of users, but just how well?
For those responsible for user experience, giving up design details along the way to launch is a fact of life. Sometimes we argue for a nuanced interaction over here and win, only to let another over there slip through our fingers. A sobering fact of life. It can be a bit like politics, advocating for the user: you can’t always get everything you want, so you have to pick the details that matter most to your constituents. That you hope will matter most.
When it comes to delighting the users of our products, how do we know what will matter to them? What will get them to vote for our product and to love it?
We might just take a page from the political handbook — start to poll the voters a bit more, visit a few more diners, shake a few more hands. Not to kowtow to popular sentiment, but to learn where the pain is. Where the opportunity is. Visit the neighborhood where the potholes haven’t been fixed for years or the factory is dumping dangerous waste or the park is run down, overgrown and unsafe. As with voters, we designers need to learn what’s wrong in our users’ world and what could lift them up. We need to represent them.
As designers, we can either bristle at this comparison and the suggestion that we’d ever lower ourselves to the level of a politician, or we can change the way we think about the job they do. If we just think about the gig itself—forget the dubious individuals who make headlines—their core job is very similar to the designer’s. They work within a tangle of constraints to craft solutions that address the specific problems of the largest number of people in the community they serve. They negotiate with competing interests and argue on behalf of their constituents. They rarely get every little thing they fight for. And what they do get is a compromise. Sound familiar?
What politicians do that many designers don’t get the chance to do enough of —despite the long, uphill missionary work of human centered design practitioners—is spend lots of time meeting with the voters, listening to their concerns, engaging them to understand the complexities of the issues they care about. Most of those citizens aren’t in a position to write legislation or draft policies themselves. As Steve Jobs famously said about customers, it’s not their job to come up with the solution. But they are the ones for whom the solution is built.
Get Marty Vian’s stories in your inbox
Join Medium for free to get updates from this writer.
Why is this a useful analogy? Because politicians are voted in or out of office based on what they are able to bring into being—imperfect as it might be—it attempts to solve what the majority of people said was a problem. It moves the community toward something most of them said mattered, even if not all the way. It shows that the people who make the laws are listening.
Or it doesn’t and they’re put on notice or sent home. Accountable, yes, but to the right masters.
In this light, design can be seen as representing users’ problems instead of packaging a product that solves a problem we told them they had. If we can treat users like voters—get out there and learn about their issues—we can create things that matter to them.
A great solution can come—and will probably more likely come—in phases that get closer and closer to truly satisfying the need and delighting the user.
So why not just use the market as the barometer of what is or isn’t valuable? After all, if people don’t like a product, they don’t buy it. And if they do like it… well, everyone is happy. The trouble is, the market often only offers quantitative feedback—that the customer did or did not buy, with little or no insight into why they didn’t buy, which is the thing we really need to know. And it’s a lagging indicator, too often providing this feedback only after betting the farm on a product’s development and spending a fortune in marketing.
On the other hand in the political arena, the qualitative nature of feedback from personal conversations, town hall meetings, letters, petitions, editorials and yes, poll results addressing the issues provide nearly real time feedback channels.
This is just another way of looking at what we do as designers. It’s a different frame to put around our work. It gives us more of an imperative to get out there among the users. Listen harder. Ask more questions. If we’re advocating for the user’s experience and bringing them a solution to a real problem, then all of the frustrations of navigating the process, every little design compromise, every argument we make to do right by the user can be seen as fighting the good fight.
Somehow this mandate lets us push a little harder, shout a little louder, and lobby for more support from the organization. It really is for the greater good.
As a representative for the user, the picture I hold in my head is of Jimmy Stewart as Mr. Smith (who went to Washington) with the power of spirit only a righteous cause can bring, “I’ve got a piece to speak, and blow hot or cold, I’m going to speak it.”







