21. HiPPO Tips Identifying the HiPPO Tracking the HiPPO Neutralizing the HiPPO Helping HiPPOs help you
22. Identifying the HiPPO Photo courtesy of Stephan Castillo & Christy Sky of Disney Worldhttp://www.flickr.com/photos/scottkinmartin/489538824
23. Identifying the HiPPO Know organizational structure Understand strategic objectives Watch out for HiPPOs in disguise Listen more than you speak Watch more than you present
30. Tracking the HiPPO Know company’s decision making model Know company’s bonus & performance review structure Lay pipe (the art of the pre-sell) Find the HiPPOs breeding ground
34. Find the HiPPOs breeding ground http://www.flickr.com/photos/cottonm/71972163
35. Neutralizing the HiPPO Don’t pen them in Communicate collaboratively Pick your battles Use strategy and tactics Teach a HiPPO about IA and UX Use data and analytics
36. Don’t pen HiPPOs in Matthew Falk http://www.flickr.com/photos/mfalk/2764309498
I’m in innie, but I’ve hired a lot of UX consultants and have successfully increased UX budget by 300%, gotten big customer focused projects approved, and added new headcount just two months ago right after one of the worst retail holiday seasons in history.
I’ve had a bit of series of titles in my current job as we try to figure out what it is that I actually do, but at the moment my title is Manager of Online Information Strategy and Architecture.
It is critical that you listen, as early and often as possible. This one is particularly difficult for me because I get so excited about things. In one role I was pretty new and had called a meeting with some peers and our upper management to start evangelizing the need for an IA function at the company. I noted that we didn’t do wireframes, and started to talk about how valuable they would be. Had I been listening more carefully over the previous couple of months, I would have realized that in this organization, the term ‘wireframe’ was used to mean ‘high fidelity design mockup’. So when I spoke about the lack of wireframes, I offended the person in charge of design and greatly confused everyone else. This misstep caused at least a year of slow down in my efforts to bring an IA discipline to the work.
Similarly, watch more than you present. There is no way you can know what to present or how to present without carefully watching everything around you. You can learn so much by watching people’s faces, body language and level of engagement in meetings or when someone is presenting. Are people having side conversations? With whom? A couple of years ago I learned this one the hard way when I was in a meeting where an agency I hired was presenting their UX solution to the executive ultimately in charge of the website. The agency was watching their notes, I was watching the agency and no one was watching the executive. He got sidetracked on one piece of the presentation and completely missed a foundational point the agency was making that was key to understanding their whole approach. I saw him get sidetracked, but I wasn’t truly watching. I was mentally prepping for my part in the presentation. This mistake cost that agency later work, their reputation to anyone who talked to the executive and I had to hole up for 3 weeks to redo their work according to his opinion.
Know how people are evaluated and how they get bonuses. Similar to understanding the business objectives for various teams, having a sense of what goals people are evaluated on will enable you to understand their motivations. Maybe their goals are aligned in ways you would have never guessed with your work. Maybe their goals are in opposition to yours. Even if you can’t change their goals, it is helpful to know so as not to not take it personally if someone is always unresponsive to your ideas. I have recently started working with someone in a completely different department that I normally never work with because I eventually discovered that her goals are all around putting the customer first.
Know how people are evaluated and how they get bonuses. Similar to understanding the business objectives for various teams, having a sense of what goals people are evaluated on will enable you to understand their motivations. Maybe their goals are aligned in ways you would have never guessed with your work. Maybe their goals are in opposition to yours. Even if you can’t change their goals, it is helpful to know so as not to not take it personally if someone is always unresponsive to your ideas. I have recently started working with someone in a completely different department that I normally never work with because I eventually discovered that her goals are all around putting the customer first.
Lay pipe. This is a favorite of my current VP, passed down to me by my manager who has been a brilliant mentor Begin setting the stage for what you want to happen months or even years in advance. I have positive momentum just starting to happen now on work that I started a year and a half ago. Pre-sell your ideas as much as you can up, down and sideways. If what you are proposing could be controversial work to make the conversations ‘barely uncomfortable’. This was great feedback my manager gave me in my last review. True change will probably require some slightly tense conversations rather than just going with the flow all of the time, but if you make people too uncomfortable too early they might shut off completely.
Play nice. This is a good general rule for any part of business, but sometimes it can be hard if you feel like others are not including you and your work or valuing it appropriately. Try to let all of that go and find everyway possible to collaborate. Ask people for their thoughts and perspectives on user experience. You will always learn something, at the very least you will learn more about how that person thinks.
Pick your battles. Be okay with not getting your way all of the time. There are times when it will be much better for the long haul to just let some stuff go, even you disagree, even if it contrary to your entire vision. Here is an admission I almost hate to make: I’ve let whole projects launch without pushing for a UX component because I knew that harping on it at that time and circumstance would probably turn people off longer term and I knew that I needed all the support I could get later on for more critical work. The key is knowing which battles to let go, and it’s something I still spend everyday thinking about.
Strategy and tactics. We have been talking a lot about strategy over the last number of years, and how to get a ‘seat at the strategy table’, but we can’t forget the tactics as well. A lot of Hippos prize results above all else, and you could have the most brilliant strategy in the world, but if you can’t walk the walk they could lose interest. Pride yourself on finding ways to just get something done. Even if it is on something small, it will start to get you noticed as a do-er, and in a world where everyone wants a piece of the strategy pie, sometimes playing the tactics is different enough to get you noticed.
Educate but don’t be pendantic. You may have to teach some Hippos about UX and why it is important. More challenging, you may have to re-teach them.
Use data and analytics. I have to admit; I am not a numbers person and have yet to discover any latent talent for analyzing data. However, in many many organizations, the higher up you get the more you have to care about KPIs and ROI and TCO and all of those financial acronyms. Get comfortable with measuring, analyzing and being accountable!