No matter your status or situation, whether director or loner, you are in a position to lead, to raise the bar in a place where it consistently sits lower than you think it should.
As an in-house UX professional, I’ve formed and run UX teams for multiple companies. As a consultant, I’ve worked with dozens of clients on hundreds of projects. Here’s what I’ve learned about how to get what you want. Most of these things can be applied whether you’re inside of a company or consulting for one, whether you’re a fledgling designer or a veteran leader.
Note: This article will be leaving out the stuff about how to be a good UX’er in the first place, such as how to do good research, define strategy, track and analyze data and so on. If you don’t know that part by now, there is a handy UX eBook Bundle available on these subjects.
Do What You Ask
There are a few things in common amongst the leaders I’ve encountered (in the web industry or otherwise) who are able to gain the respect of everyone around them. This is one of those things:
They never ask people to do things they wouldn’t do themselves.
Whether it’s taking out the garbage, making coffee or staying late to sweat out six screens for an app because of new requirements, UX leaders do what all UX’ers do: they design.
Even if you’re at the top of your corporate ladder and should therefore be respected by default, there’s no other way to demonstrate your chops than to put your own expertise to work.
Design something. Put up or shut up.
This is some pretty basic pop psychology here, but it’s relevant:
We teach others how to treat us. When we jump out of our seats at the slightest jostling, we teach people to yell “Boo!” When we get and stay anxious, we teach people to avoid us. When we push things off, we teach people they can’t trust us.
When the CEO postpones everyone’s favorite project for three weeks to deal with legacy issues on a product you’re phasing out anyway and you sigh and roll your eyes, you teach the CEO to treat you like a nuisance rather than a leader.
No matter what happens, remember that the way you act and react affects the way everyone else will see you the next time they need you to act or react. Stay calm in all situations and you will have all the respect you’ll ever need to get things done when the chance comes.
Never Mind The Bollocks
There are a million distractions in every office, in every company, every day, that can keep you from finally getting that new product launched, finally fixing those old bugs or finally leaving work at a reasonable hour. They might be managers who treat whims like emergencies. They might be a CTO’s sudden urge to put in for an award. A design tweak at the request of the CEO’s best friend. They can even be the guy down the hall who uses his daily breaks as a reason to wander around and make sure everyone else is having a break, too.
Distractions come in all shapes and sizes. Not one of them matters.
Product design and management is a marathon. Relax. Panic and frustration will not make it happen any sooner. It certainly will not make it any more enjoyable. See past this stuff. Keep your eyes on the long term.
Someone hired you. In theory, they did this because you know some things. Yet, for some reason, the second you got hired, you stopped knowing things. You stopped asserting your knowledge, your passion, your care. You started being afraid. You started worrying about your job instead of your work.
Well, guess what. It’s your job to know when something is bad, and to be able to say so. Assuming you are able to back up your arguments — assuming you can demonstrate that you know what you’re doing — your job is to do exactly that.
Refuse to play along with bad ideas. Refuse to stop voicing your concerns, your ambitions, your evidence, your knowledge. Your passion for UX got you here. If they don’t want it now that they’re paying for it, get out. Refuse to work in a place that refuses to consider sound arguments formed by someone who cares deeply for them. If something is bad, and you can back up your opinion with insight, you need to be able to speak up. If you can’t, find someplace you can.
However, if you’re new to the profession, backing up your arguments will be tougher for you. You’re also less likely to be able to see the complete picture (it’s always a much bigger picture than you think). Stick around long enough to get some valuable experience before you start asserting yourself much. Trying to claim a leadership role before you’re ready can damage your reputation before you even get going.
Take Criticism Well
When you critique others, you don’t want a lot of resistance. You want people to keep their heart rates in check long enough to think through what you’re telling them and to consider that you might have a point.
Just as you need to be able to criticize, others need to be able to criticize you. Don’t be the person who shoots down any feedback that doesn’t go your way. You need people to see the problems in your work. Other people need to trust that you can handle objection.
Take criticism well. Because you expect others to do the same.
Invite, Include, Consider
When you take on an effort to define the vision and strategy for a project — and you should do this for every project, regardless of its size or significance — include other people. Don’t do this because you’re trying to be cool and inclusive. Do it because you can’t define a project well without talking to stakeholders, users as well as team members.
You may be a genius, but that doesn’t negate the fact that people produce better results in well-run groups than they can alone. (Numerous studies have proven this.)
A “well-run” group, by the way, is one with a clear leader, whose job is to make the final decision, and at least one devil’s advocate, whose job is to poke holes in ideas and force people to back them up and think through them completely.
Well-run groups are also limited to as few voices as possible — only those most crucial to the key decisions. Your job is to collect and listen to and consider opinions, but also to remember that there’s a gigantic difference between opinion and insight, and that the time it takes to consider too many opinions will keep you from putting any of your insights to work.
No company comprises UX experts alone. They comprise marketers and accountants and salespeople and product managers and executives and programmers. A single UX professional may not be found, in fact. But you need a bunch of people to be able to make good design decisions, because you can’t make them all on your own, and because you don’t have time to undo the bad ones other people will make in the absence of UX knowledge.
So arm them. Arm them with insight, knowledge, technique, considerations, best practices, design standards and anything else you can use to help them make good design decisions. Explain every recommendation you make. Put out design standards that other people can apply. Explain how to think through UX decisions so that other people at least make the attempt to do it on their own. Do this all the time, every day.
If you’re starting from zero, it will be a long time before this pays off. But you’ll enjoy it; people will develop respect for your knowledge along the way; and one day, it will indeed pay off. People with bad ideas will become people with good ideas. They’ll become people who help you produce great work.
Teach Them To Teach
Most of your job as a UX professional is not about designing, but about selling your ideas. It’s about convincing people that your recommendations are merited and considered and probably right (based on your experience and your research, which you will be able to show as part of your pitch).
This is also true of everyone else on your UX team.
If you are part of one, make it an absolute priority to teach the other people on the team how to sell their ideas. Make sure they know how to make their case, and that they need to in the first place.
If you can’t convince, you can’t succeed. Neither can they.
This one is for the managers:
There are a lot of perspectives on the difference between management and leadership. The debate isn’t all that useful. What is useful, however, is to understand the difference between what should be managed and what gets managed. They are usually very different things.
What usually gets managed are people. Managers think they are being paid to organize and to delegate and to track. This is a myth. Believing it is a detriment to productivity.
People want to do good work. It’s human nature. They want to feel proud of their effort. If it seems like they don’t, it’s usually either because they think their current situation prevents them from doing so and have resigned to that idea; because your version of “good” and theirs have different definitions; or because you are at different points on the spectrum with regard to your ability to evaluate what “good” means. (In either case, addressing the underlying problem is the only effective way to deal with it.)
Besides this, you have a distinct advantage that some other industries might not have: You work in the web industry. People who join the web industry do it with their whole selves. They become absolute freaks for this work. They love it. They eat it for breakfast.
You don’t need to manage people in the web industry. You need to manage things away from people in the web industry. Your job, in other words, is not to tell them what to do, but to keep things out of their way so that they can do what they already want to do.
If you’re doing everything you can to give a person what they need to do their job well, and they’re still not doing it, then you have a problem.
Odds are, that won’t happen.
Let Them Improve
Another one for the managers:
I once had a junior designer on my team who desperately wanted to do more strategy work. He told me so at least three times while we were in the midst of a Herculean effort to rid ourselves of technical debt. He was at his least challenged. He wanted to push himself.
Soon after, a project I’d been pushing for came to fruition. The first step was to define a strategy (as it always should be). I wanted to do it myself. Badly. I gave it to him instead. I told him I’d be there for guidance and to answer questions if he needed but that the project was all his. (Secretly, I also committed to asking him loads of questions along the way that would allude to the kinds of things he should be thinking about.)
He kicked ass on that project. He proved himself to a bunch of people in a bunch of ways. And he learned some things in the process that enabled me to go to him later as a strategic thinker.
Again, people in the web industry already want to do great work. They want to learn more, take on more, build more, design more, ship more. They’re hungry. So feed them.
When someone wants the chance to improve at something, find ways to let them. The next time a project comes up that appeals to that person, hand it off, even if you really want to do it yourself. Nine times out of ten, that person will step up. And both of you will be better off for it.
Influence At Every Turn
Every UX professional’s job has an internal part and an external part. To lead on the UX front, you must lead outside of the team as well inside of it.
Every interaction you have with non-UX people in your company is an opportunity to espouse how you make decisions, to talk about how users view things and will view things and how you, as a company, should want them to view things.
Remember, we teach people how to treat us. Every last UX person on the planet should act in a reasoned, deliberate, intelligent, dedicated manner, so that others in their organizations will treat them as such.
This is the last one specifically for managers:
A few months ago, I was sitting on a stool at the front of a room in the Capitol Factory in Austin, Texas. Next to me was Harry Max, VP of Design for Rackspace and the man who will be forever known for designing the web’s first shopping cart. We’d given our respective talks, and the floor was open for questions. A few dozen sets of eyes were staring at us, and neither of us had any idea what question would come next. The third or fourth one was a nerve-shaker.
“How do you know who to hire?”
As in, when you bring in a gaggle of UX candidates to meet people, shake hands and answer questions, how do you know which one is good and which one is terrible when you don’t know the first thing about UX or how to evaluate its success?
It was one of the best questions I’ve ever been asked by an audience member.
It’s not an easy thing to answer. Volumes could be (and have been) written on what “UX” really means, and why, and how far it reaches into the business and what skills you actually need for your business or for this project. And the people who claim UX in their title have a huge range of backgrounds. Some have a degree in cognitive psychology and are experts in usability. Some just walked out of graphic design school yesterday. Even someone who’s been doing it for years may have just come from an organization that thinks the UX person is nothing more than a glorified wireframer. You need to be able to discern one from the other.
There’s exactly one way to pick a great UX professional — or one with the potential to be great — out of a lineup.
Look for the person asking all the best questions.
There are two parts to this: all and best. A UX person asks questions — about the users, the business, the concerns, the needs, the prior decisions, the team, the goals. A great UX person wants to see the whole picture.
They don’t pick colors; they ask questions to sort out how and when and why to use which color. They don’t devise layouts; they ask questions to determine relevance, priority, meaning. They don’t wait to be told what to do. They lead.
If you are interviewing a UX person and you are the one asking all of the questions, call it off. This is not the UX person you’re looking for.
Always Talk Psychology
The root of design is psychology. Anything else is art or decoration or something else. We all know this much. A design is a plan, and a plan requires an intended outcome. For design to succeed, human psychology has to be at the center of it. No user can ever have the kind of feeling you hope they will have about your product unless you consider how they will approach it, get through it and talk about it later. Some elements will be used to convince them of the value of the product. Others will encourage them to take specific actions. Others will surprise them, placate them, make them laugh, piss them off. Whatever the intent, the approach should be applied to all design decisions that get made. This much is a given.
It’s easy to forget, though, that other people don’t think about this like you do. They don’t realize that the root of design is psychology.
A client of mine recently said as much:
“There’s so much psychology involved!”
To which I replied:
“You’re in sales. Design is just like that.”
Talk about the psychology. (And when you do, cite your sources.) Show people that there’s a lot more to UX than checkboxes and radio buttons. UX is psychology applied to design.
Give Credit Away
People love it when you give them credit. People also love people who freely give credit where credit is due. So give credit away. All the time. People will love you for it.
But far beyond that, it will help you get things done. It’s counter-intuitive, for sure, but when you give credit away, people credit you for all kinds of things in return. Focus on building a team full of people who are respected and revered. Focus on building a reputation for your team rather than yourself. Care more about getting it right than putting your name on it.
Don’t worry. You’ll get your credit.
“The reasonable man adapts himself to the world,” said George Bernard Shaw. “The unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.”
This sounds like an ego trip. It’s not. It doesn’t mean you should try to get everyone to be like you. It means you should try to hold the world to your standard of excellence. It means you should try to design the world to that standard. You are a designer, after all. This is your special power. Use it.
If something is crap, call it out. If something has a flaw, point at it (and then propose an improvement, because complaints alone are useless). If something doesn’t exist that should, say why, and, if it’s important enough, go after it with all your might. If you’re the only person who cares and you don’t care enough to make it happen, then it will not happen.
Progress is made when people push hard for it. They stand for things. They forge good arguments. They convince, they challenge, they prove. It’s how the seatbelt was invented. It’s how America won its independence. It’s how “user experience” became a common notion and a ubiquitous demand. (Fifteen years ago, a lot fewer of us were fighting this fight. It was hard then. But it was a worthy war.)
Don’t be reasonable. Be successful.
Further Reading on SmashingMag:
- What Is User Experience Design? Overview, Tools And Resources
- Icons As Part Of A Great User Experience
- The Real-Life UX Design Process
- Why User Experience Cannot Be Designed