Equinix is a company you've probably never heard of, but if they disappeared tomorrow, the entire internet would collapse.
They own most of the facilities around the world that internet traffic goes through. Back in the day, companies would have their own servers and data centers. As the demands on big data grew, it no longer became sustainable to run it all yourself, so they offloaded it to an external provider.
All the companies you associate with cloud and data -- AWS, Google Cloud, Rackspace, Akamai -- they all host their data in Equinix facilities.
So how can a company this large be completely under the radar?
The big problem Equinix has is that they have trouble explaining what they do. Their online presence is becoming more and more important for communication and generating interest, but right now, it's not doing its job very well. The writing is convoluted and the content structures make no sense. It's a very classic enterprise problem: The company is mapping its internal structures and language onto an external site.
Create a Human Centered Design culture at Equinix. Hire on new team members, mentor the current designers, institute new methods and practices to shift the thinking away from internal wants and needs towards our customers.
Successes so far
This is a story that's still unfolding, but we've already had some early wins.
Better user tracking
A big part of shifting how an org thinks about design is by removing personal taste out of the equation. We don't want reviews of the designer's work to devolve into art critiques, where the loudest (or highest ranking) voice in the room gets what they want. To prevent this, you need accurate data about how customers are behaving. So we replaced the old user tracking software (CrazyEgg) with a better one (HotJar), that gives us much more in-depth information on how customers are behaving on the site. Armed with this information, it's much easier to guide conversations away from stakeholders' personal preference, towards what customers are trying to accomplish.
Closer collaboration with junior designers
I have two other designers I'm working with. One is a visual designer and relatively junior, the other is a design developer hybrid and definitely senior. With the way the office is laid out, we barely saw each other and every one of us was working on an island. So we instituted weekly design reviews every Wednesday and group design sessions every 2nd Monday, to review each other's work, push each other further, and sometimes just vent about what's frustrating at work this week.
A culture of testing
We instituted a policy of regularly A/B testing designs, especially when we discover two possible courses of action and can't tell which one will work better.
Major Mentoring Successes
Something I'm really proud of is when I first started out, I was tasked with a redesign of the homepage. The way this role is structured, I do almost no visual design (we have a visual designer for that), but the homepage, I wanted to demonstrate the value of design reviews and the type of feedback I was looking for. So I did a mockup of visual design for the homepage as well. Based on that guidance, I encouraged my designer to explore and refine more options, until we ended up with something that was entirely hers, and much better than what I set forth. I'll update this page with screenshots as soon as the new homepage launches.
Forming new culture-habits
A lot of this job is just saying the same things over and over again, until new habits form in the culture. So when stakeholders tell me something like "My director really wants this dropdown added", I'll politely remind people that we as a design team aren't working for the stakeholder, but instead the entire organization is working for the customers.
Being a true partner to stakeholders
Sometimes, when you are working with stakeholders, you need to listen past what they are asking you to do to understand what the real problem is and what's the best way to solve it. Very often, stakeholders will approach you with a solution they have in mind. Many designers will just start executing the solution the stakeholder presented to them. (I write more about this phenomenon in this blog post).
I encountered this during the design process for the cloud provider availability tool. My stakeholders just wanted an excel spreadsheet posted on the website, with all of the providers. At that point, I had been with the company for just three or so months, so no one had any context or understanding of what I'm doing. Almost against their will, I dragged them through the design process, and we ended up with a solution that's easy to navigate, contains all of the information needed -- and looks kind of like a spreadsheet.
The end result was that this tool got some of the highest engagement numbers from customers, it got recognized by the executive leadership as one of our best launches, and those stakeholders who were previously critical of my process, are now my biggest allies.