By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.

It Can Be Tough to Build Central UX Teams. Here’s How to Make It Work.

It Can Be Tough to Build Central UX Teams. Here’s How to Make It Work.

Not too long ago, you couldn’t stand on the shoulders of giants when building user-centered design capabilities within large organizations. The territory was uncharted, with no map to consult. 

That’s no longer the case. But even with the stepped-up recognition of human-centric design's value and the increased number of organizations making this journey, it’s still laden with pitfalls that can derail even the most well-intentioned efforts.

<svg width="1440" height="810" viewBox="0 0 1440 810" fill="none" xmlns="http://www.w3.org/2000/svg"> <g clip-path="url(#clip0_205_367)"> <path d="M583 540.514C673.696 711.841 1193.6 771.223 1440 474.217" stroke="#121AFF" stroke-width="16.1869" stroke-linecap="square"/> <path d="M531 337.257C523.692 318.805 473.154 282.513 464.647 379.795C444.707 607.825 352.132 574.446 337.5 528.5" stroke="#121AFF" stroke-width="16.1869" stroke-linecap="square"/> <path d="M315 442.703C303.239 423 289.028 448.123 273.836 499.843C232.573 640.327 115.515 702.483 0 636.749" stroke="#121AFF" stroke-width="16.1869" stroke-linecap="square"/> </g> <defs> <clipPath id="clip0_205_367"> <rect width="1440" height="810" fill="white"/> </clipPath> </defs> </svg>
<svg width="1440" height="810" viewBox="0 0 1440 810" fill="none" xmlns="http://www.w3.org/2000/svg"> <g clip-path="url(#clip0_205_367)"> <path d="M583 540.514C673.696 711.841 1193.6 771.223 1440 474.217" stroke="#121AFF" stroke-width="16.1869" stroke-linecap="square"/> <path d="M531 337.257C523.692 318.805 473.154 282.513 464.647 379.795C444.707 607.825 352.132 574.446 337.5 528.5" stroke="#121AFF" stroke-width="16.1869" stroke-linecap="square"/> <path d="M315 442.703C303.239 423 289.028 448.123 273.836 499.843C232.573 640.327 115.515 702.483 0 636.749" stroke="#121AFF" stroke-width="16.1869" stroke-linecap="square"/> </g> <defs> <clipPath id="clip0_205_367"> <rect width="1440" height="810" fill="white"/> </clipPath> </defs> </svg>

Not too long ago, you couldn’t stand on the shoulders of giants when building user-centered design capabilities within large organizations. The territory was uncharted, with no map to consult. 

That’s no longer the case. But even with the stepped-up recognition of human-centric design's value and the increased number of organizations making this journey, it’s still laden with pitfalls that can derail even the most well-intentioned efforts.

Project
Authors
Sabine Müllauer
Pascal Soboll
Illustration
Mara Weber

3 pervasive big challenges:

Proving success to senior leadership is difficult but essential.

Buy-in from the top is crucial. Without it, everything becomes much harder. To get the attention, support, and resources required to get a UX team off the ground and establish it sustainably, senior support is a must-have. Not having it secured should be a non-starter.

Change takes time, potentially exceeding the attention span of senior management and shareholders.

Having secured the support of at least one senior leader, managing their expectations will be key. Visionary leaders will be the wind beneath a UX team’s wings, as long as their attention is sufficiently focused on the topic. As executive leaders are juggling lots of important topics, you run the risk of dropping off the priority radar. It will be key to keep them engaged and interested, showing promise, progress,  and impact in quick succession. Proving value early on and building bridges into the breadth of the organization is mission-critical to outlast fickle management attention spans.

‘Enabling’ is much more work than anticipated.

Advocating for your team and teaching your approach can’t be resigned to a distant second place behind actually “doing the UX work”. The simple existence of information, insights, and tools themselves will not do anything for the organization. Planning for a two-tiered approach from the get-go is essential in order to connect to a wide range of teams within the organization.

8 guiding principles that help overcome those challenges:

Be realistic going in.

Change takes time and resistance may emerge in unanticipated places. What’s key is patience, not haste. Think in terms of years, not months, when it comes to building up the competency across all business units. Don’t focus solely on the end-state picture: Break the overall journey into many incremental steps and celebrate all small successes along the way.

Try this:

• Set achievable short-term goals. Small steps can start a long journey.

• Implement a tight learning loop; frequently review what has worked and what hasn’t so far.

• Make sure a runway funding of at least two years is ensured. If not, discuss with your senior champion how this could be achieved.

• Avoid the urge to reach everyone right away. Target small pockets of the organization and let the team and concept develop a certain robustness before involving the breadth of the organization.

Go deeper: Marta Lago Arenas on the Importance of a Having Thick Skin

Ensure top-down support and create a bottom-up movement.

Make sure senior leadership brings up the topic in board discussions regularly and give them a metric to judge progress by. Ideally let talent from across the organization self-select. Focus on finding and involving your champions rather than converting critics.

Try this:

• Know who your senior champions are, ideally on the board level and on the C-level. If you lack a proponent in either group, convince one to assume the role. Provide them with a vision to spread, and let them know what is needed from leadership for the UX team to succeed.

• Set realistic but detailed expectations with senior leadership to ensure accountability.

• Create opportunities for interested colleagues to get involved, e.g. set up an open-innovation challenge to identify them from across the organization.

Go deeper: Knut Mayser on Finding Engaged Stakeholders

Anticipate hopes and fears.

Many existing teams will benefit from joining forces under the umbrella of user-centeredness but not all of them will welcome the change at first. Some will inevitably be worried about their roles and their territory. Teams you thought were “on your side” might push back hard unexpectedly. Manage it proactively. Just because you assume they will be on board doesn’t mean that they will see the benefit right away.

Try this:

• Actively contact related teams, like product design, market research, business strategy, etc.

• Understand how they might benefit from a broader UX initiative - or which aspects might feel threatening.

• Bring them into projects, even if this creates inefficiencies. Avoid duplicating their structures.

• Come up with a key message and repeat it, to make everyone see that it is much better to collaborate to move this undervalued area ahead than to compete.

Hire for two 
key capabilities.

Driving innovation is the more obvious key capability to build up, but it’s not the only one. Driving transformation by enabling the broader organization is another. The two require different mindsets and different skill sets. While the former is all about team-based problem solving (i.e., committing to one innovation challenge at a time and continually digging to create new-to-the-world, valuable solutions), the other is all about incessant communication and inclusion (i.e., banging the drum for everyone to hear, inviting people in, and repeating basically the same set of messages over and over, but keeping them fresh and exciting). You essentially need core teams: One that shows everyone in the organization “what good looks like” and one that focuses on how to establish UX within the organization in terms of process, structure, and anchoring it within all business units. Sure, there will be team members who are equally good at both, but will they have time to truly focus while switching back and forth between the two mindsets?

Try this:

• Plan and account for both targets separately; clearly define which activity advances which one.

• Ensure that UX team members are empathic with the rest of the organization and conversant in the languages of science, technology, and business so their ideas can make it through the frameworks of the organization and beyond.

• Remain “permeable”: Learn constantly, engage in radical collaboration, adapt continuously.

• Early on, it might pay off to add a “storytelling layer” to projects to capture and convey relevant process knowledge to the wider organization.

• Build a roadmap that shows how business units can gradually move toward a UX-enabled state, with celebrate-able milestones along the way.

Build bridges into all business units.

Create “bridgehead” roles within business units and involve them frequently. This will allow you to focus on working with a small-ish group of ambassadors, rather than having to “boil the ocean” by having to reach all at once. The strength and effectiveness of your communications with this small group will directly impact the strength and effectiveness of what they convey to the business units.

Try this:

• Invite a few selected colleagues in each BU on defined levels of the org chart to join a pioneering group.

• Equip this group with knowledge of UX methodology, practicalities, differences, etc., so they can be effective ambassadors.

• Convene regularly to identify suitable project briefs from the BUs or to spread relevant information about activities and events in person.

Show what good 
looks like early.

Lighthouse projects are a good way to create excitement and momentum. They allow you to demonstrate early on that a human-centered approach leads to results that the organization would not typically achieve.

Try this:

• Gather potential briefs for lighthouse projects from across the organization.

• Rank them by suitability. Parameters should include their potential for visibility (internal and external), cross-BU applications, systemic solutions, and new-to-the organization results.

• Choose the ones that can best showcase the added value that UX approaches bring, e.g., a strong user experience element and involving questions that are sufficiently complex and whose answers are non-obvious.

• Aim high. Prioritize quality of results above all else, including showing off results in impressive formats. Use external design support if needed in order to create "Holy... I had no idea we could do this" moments.

Go deeper: Ivo Furrer on Cutting Through the Lehmschicht

Don’t restrict yourself to one type of innovation.

Avoid focusing on one flavor of innovation. Project briefs should be carefully chosen and ideally curated to represent a portfolio. A set of projects can, for example, be assembled to illustrate a spectrum from “evolutionary”, i.e., reasonably close to the core business, demonstrating relevance, to revolutionary, i.e., ”new-to-the organization” or even “new-to-the-world”, demonstrating disruptive potential.

Try this:

• Be conscious about the differences in potential briefs: Which ones are close to the core business, which ones are “blue sky”?

• Ideally assemble a portfolio of projects to work on, assigning a defined portion of the budget to incremental vs. disruptive innovation efforts, e.g. following the innovation matrix.

• Balance long- and short-term oriented projects, highlighting the individual benefits of each when communicating results.

Communicate, communicate, communicate.

We’ve said it before, but in so many ways, it all comes down to this. Invite, integrate, explain, demonstrate, learn. Stay on everyone’s radar with good stories, but don’t get self-absorbed and too enamored with your own human-centered, design-y view of the world in the process. In the end it’s about adding real business value to the organization. That is only possible if everyone pulls together, including engineers, accountants, and middle managers, and if everyone agrees to evolve their perspectives, approaches, and language to be compatible with each other.

Try this:

• Challenge your team to put out at least one piece of communication to the larger organization per week.

• Think about how the way you communicate (copy, imagery) reflects the nature of your approach and how it is different from the traditional way of doing things in your company.

• Offer people opportunities to learn more and get involved in small, low-barrier ways as well as in high-profile, visible ways.

• Create excitement and visibility by holding events, celebrating successes, and giving out awards.

Go deeper: Stefan Knoll on Why Incessant Communication Isn’t Too Much

Conclusion

In the ever-changing world of customer desire, there's still a big demand for products, services, and brands that truly cater to people's individual needs. And with AI becoming a bigger part of the picture, it's even more important for companies to keep a focus on being human-centered. We have no doubt that the overall value of user-centered innovation is only going to increase and strongly believe that to achieve true human-centeredness, the guiding principles outlined above will continue to apply. Any team adhering to these points will be planting all the right seeds for growing strong central UX capabilities and shifting their organization toward true user-centeredness. Where does your organization fit in? What has worked and what hasn’t? What have you learned so far, and what advice can you share?