Showing posts with label change management. Show all posts
Showing posts with label change management. Show all posts

Friday, October 10, 2014

The Future of UX Leadership: Radical Transformation


Published: October 6, 2014
“Insights on how to help companies progress from delivering mediocre user experiences, as is all too common, to producing truly great experiences that differentiate their products and services in the marketplace.”
This column is the first in a series that will offer insights on how to help companies progress from delivering mediocre user experiences, as is all too common, to producing truly great experiences that differentiate their products and services in the marketplace. Doing so requires a radical transformation in the way business executives and UX teams engage in creating user experiences.
This series is not about making incremental improvements to the way UX teams work. It is about taking a different approach and driving radical transformation within organizations. No major changes in history have ever come about by playing it safe. Having said this, all of the ideas that we’ll share in this series have proven effective in one business context or another.
In this first installment of our series, we’ll focus on three main points:
  • the problem that UX teams currently confront
  • the role that design-driven differentiation plays in business success
  • positioning User Experience for success within your organization

The Problem That UX Teams Confront

“The way we’ve done things in the past just isn’t enough any longer. The field of user experience is at an inflection point in its evolution. We have to up our game….”
Far too often, highly qualified UX teams that have budgets in the tens of millions of dollars per year produce overly complex, dreary designs. This is especially true in companies that develop enterprise software. Why does this happen so often?
Creating great user experiences requires more than just hiring highly skilled designers and design leaders who employ typical UX research and design practices. The way we’ve done things in the past just isn’t enough any longer. The field of user experience is at an inflection point in its evolution. We have to up our game because it’s just a matter of time until the executives in these companies start realizing that their UX teams are delivering less-than-stellar, undifferentiated designs. Customers now have higher expectations for the quality of product user experiences—and they’re not shy about complaining loudly when we disappoint them. So, because it’s inevitable that business executives will soon start recognizing that their UX teams are not delivering the desired results, let’s consider what might happen next?
  • Executives may think that it’s just not worth paying the premium that they currently do for their in-house UX teams and decide that they can replace them with people who are not a highly trained UX professionals—and are not adept in design thinking. Many executives already tend to engage more with Customer Experience teams than with UX teams. Perhaps they’ll decide that UX teams are redundant. We’re seeing some evidence of this already.
  • Executives might decide to fire their in-house UX team and work with a renowned UX consultancy instead.
  • Executives might decide to fire their current UX team in the hope that they can hire a new UX leader who is capable of building a UX team that can transform their company by creating user experiences that truly differentiate their company’s product offerings.
  • Self-aware executives may recognize that they have created a corporate culture that presents insurmountable obstacles to delivering great user experiences and take responsibility for transforming it. Unfortunately, this is probably not the most likely scenario. But courageous UX leaders might be able to raise C-level awareness of these cultural barriers and persuade executives to work with them in transforming their organization.

The Role of Design-Driven Differentiation in Business Success

“Great UX design differentiates companies’ products from their competition and enhances their brand.”
Great UX design differentiates companies’ products from their competition and enhances their brand. As UX leaders, we must communicate this fact to our companies’ executives. If you cannot convince your company’s leaders of the value that User Experience can provide in differentiating their products in the marketplace and driving business success, you should walk away. There’s no way to succeed within such an organization. We should no longer be willing to work for companies that do not recognize that, in reality, user experience can differentiate their products. As a UX leader, what should you do to make a difference within your organization?

Apply Design Thinking at an Organizational Level

Design is fundamentally a problem-solving exercise. Sometimes, the problems that we solve are purely UX design problems. Typically, we need to optimize discoverability, learnability, ease of use, efficiency, or delight—to varying degrees in different contexts. For example, we may need to engage customers by creating an emotional connection to our products or ensure that experienced users can accomplish their work as efficiently as possible. The design problems that we solve differ depending on many factors, including whether we’re working on
  • products or services and in what domain
  • consumer or enterprise products
  • desktop, mobile, cross-device, or cross-channel experiences
  • products for users in a particular country or region
  • projects supporting a startup or a large enterprise
  • projects within an organization and with stakeholders whose maturity around user experience and design does or does not enable us to do our best work
As UX professionals, our approach to solving a design problem depends on the context. There is no one-size-fits-all approach to UX research or design. We must first identify the right challenge to solve, then choose the right approach to solving that particular problem. As we progress in our careers, our design challenges tend to become more complex and our scope of responsibility increases.
“As we progress in our careers, our design challenges tend to become more complex and our scope of responsibility increases.”
As UX leaders, whatever the problem that we need to solve, we can apply design thinking to solve it. Often, senior UX leaders design not just individual products or services or even software systems, but instead design—and run—UX organizations and more. When we design organizations or devise processes, the solutions that we provide can transform organizations. For example, when designing a UX team, the solution is an organizational structure and a team with which it is easy to engage and work, that fits well into the overall organizational structure, and that delivers stellar results, making the CEO and other executives delighted to work with the team. Whatever the problem we’re solving, we must engage in design thinking, strive to understand our users or stakeholders, and provide a solution that produces value.
Building a UX practice that can truly transform an organization and differentiate its products from those of its competitors requires having a number of elements in place—elements that are necessary to ensure our success. (We’ll discuss what those elements are shortly.)
If your organization doesn’t provide those elements—and if, after attempting to foster the necessary organizational changes, it seems unlikely that you can achieve them—you should leave and find work in an organization that affords many of those elements. Yes, walk away from your current role. That’s right. If you’re a UX leader who cannot be successful in a particular situation, bail. If you don’t, you’ll be judged for the quality of the team’s work and its lack of impact—regardless of the organizational reasons behind it.
Plus, if you’re a person who really values quality, but you’re working in a context that prevents your delivering it, you’ll be perpetually frustrated—locked in a vicious cycle in which nobody is happy. Instead, find an environment in which you can do great design and create a virtuous cycle that makes everybody happy. Leave the uninteresting problems and the mediocre jobs to average leaders and design teams.
All of the work that we do becomes a part of our legacy as UX professionals. Is producing anything other than stellar user experiences worth our time and energy? We should not settle for anything less than creating truly spectacular user experiences.

Deliver on the Value That User Experiences Promises

“As UX leaders, it’s our job to build UX teams that help our companies to differentiate on the basis of their products’ user experiences. … Design-led companies outperform their competitors financially by 228%.
As UX leaders, it’s our job to build UX teams that help our companies to differentiate on the basis of their products’ user experiences. We call on all UX professionals to subscribe to this manifesto:
Our goal is to deliver game-changing designs. We must deliver truly differentiated user experiences that provide maximal value to our customers and the organizations for whom we work. Nothing less will do.
We can move beyond debates about the value of user experience. Thanks to the Design Management Institute (DMI) and leaders who have conducted research over the past 20 years, we know for a fact that design-led companies outperform their competitors financially by 228%. Great design increases profit margins.
Fostering great design is important—not only for you as a UX leader, but also for the people who work for you, the customers who use the products your team designs, the company that employs you, and ultimately, the UX industry as a whole. As we said earlier, user experience is at an inflection point. While, as a discipline, we may talk the good talk, if we don’t consistently walk the walk, we’ll fail. Now, more than ever, we must deliver on the promise of user experience. If we don’t, perhaps we deserve to be marginalized.
As UX leaders, we must create corporate UX teams that can compete with the best design agencies—and even design better experiences than an agency could. The success of our industry depends on this. When we create inspiring designs that differentiate our products, our value to the organizations for which we work is clear. Differentiation creates competitive advantage, increases profit margins, drives brand value, and increases the value of our companies’ stock. Average design is a commodity. If we don’t deliver the value that user experience promises, executives might be justified in questioning whether they want to pay a premium for our skills.

Create Competitive Advantage

Differentiation creates competitive advantage, increases profit margins, drives brand value, and increases the value of our companies’ stock.
What are executives looking for when they hire UX teams? Every company wants to create disruptive innovations that will elevate them financially above their competition. Competitive differentiation drives higher profit margins and increases a company’s competitive advantage period (CAP)—that is, the period of time over which a company’s offerings provide sufficient differentiation that the company has a competitive advantage in the marketplace—as well as sustains higher profit margins. The basis of a company’s stock price is not only its current earnings and profit margins, but also its expected future earnings, which depend on its perceived CAP.
We know that design-led companies produce greater competitive advantage. Our challenge, as UX leaders, is to deliver competitive differentiation—or even disruptive innovation. If we cannot facilitate our teams’ producing user experiences that differentiate our organizations’ products and services, we’ve failed. Again, if there’s nothing we can do to succeed within a particular organization, we should find a company where we can make the difference that we know that we can make.

Embrace Purpose—for Yourself and Your Employees

“We shouldn’t be willing to work in companies whose cultures and ways of conducting business are antithetical to our teams’ delivering excellent work.”
As UX leaders, our goal should never be to produce average or minimally acceptable designs. So we shouldn’t be willing to work in companies whose cultures and ways of conducting business are antithetical to our teams’ delivering excellent work. As UX professionals, we all want to feel that the work we’re doing will make a difference for our users and customers, be successful in the marketplace, and help our company to thrive.
As UX leaders, we want to lead people who are passionate about their work and have a burning need to deliver work that they’re proud of. As Daniel Pink suggests in “Drive: The Surprising Truth About What Really Motivates Us,” purpose is what motivates human beings—knowing that we are contributing to something that matters to people—something that is bigger than ourselves. We also seek mastery, which enables us to do the best job possible. We all want to have a boss whose vision and plan will enable us to achieve great results and who gives us the autonomy to take ownership of our work, enabling us to do our very best work.
So, as UX leaders, if we want the best people in the world on our team, we need to be great bosses with the right leadership qualities, who give our team purpose, provide autonomy, and facilitate mastery. We must provide a strong vision and clear goals and set up both an organizational structure and processes that enable our team to deliver differentiated product user experiences. UX leaders need to have the right support system to accomplish great work—both from the top-down, our company’s executives, and the bottom-up, our employees. Accomplishing great things takes a team. If you want to achieve greatness, you must believe there’s a path to success, even if it’s circuitous.
Of course, we must be willing to work hard to push the UX rock uphill to attain relevance and value. Whenever we’re able to do that successfully, we’ll end up feeling that our effort was worthwhile—though we may have numerous scars to show for our efforts! It’s okay to start at the bottom of the hill—if you have the support you need to succeed. There are certain foundational factors that you should always evaluate when considering a new job.

Positioning User Experience for Success Within Your Organization

“One factor that is universally present in companies where design is a strong differentiator: the leader of the UX Design organization has a strong partnership with the CEO of the company.”
As a UX leader, you need to position yourself and your team appropriately in your organization—or report to a senior UX leader who has positioned User Experience for success.
As Jeneanne Rae points out in her article “What Is the Real Value of Design? there are a few key factors that ensure design-led companies outperform their competition. Let’s look at the most important of those now.

A Partnership Between the CEO and UX Design Leader

One factor that is universally present in companies where design is a strong differentiator: the leader of the UX Design organization has a strong partnership with the CEO of the company. This makes perfect sense, for several reasons.
First, having a CEO who recognizes the value of and supports User Experience and, more importantly, advocates for you as a UX leader affords you a level of power that enables you get things done. No matter how good a collaborator you are, how good your leadership skills are, or how much emotional intelligence you have, if you don’t have sufficient power in your organization, it’s hard to effect change.
Apple is everyone’s favorite example of a design-led organization, and we’ve heard much about the relationship between Steve Jobs and Jonathan Ive, but there are many other examples of partnerships between a company’s CEO and UX leader—IBM for one. Ginni Rommety, CEO of IBM, and Phil Gilbert, VP and General Manager of UX at IBM, have a strong relationship. Rommety endorses and supports UX Design across the organization. When IBM built a new Design Lab, Rommety said, “I believe … that the [design] work done here will change the world. This is a recommitment to a heritage of innovation that has transcended IBM.” At IBM, any member of a product team would ignore User Experience at their own peril.
Of course, UX professionals must also be great collaborators and address high-priority goals to deliver maximal value. But without the foundation of executive support and the power of influence that affords, trying to push that UX rock up the mountain just isn’t a worthwhile endeavor.
Does it have to be the CEO who recognizes the value of UX design? Would it be enough to report to—say—an Executive VP of an independent business unit who supports you and your UX team unequivocally, with the same level of enthusiasm that Ginni Rommety does? Maybe. The answer to this question depends on what organizational structure makes the most sense within a given company.
Most companies start out with a centralized UX team that needs the CEO’s support. Then, as the business grows, it splits into multiple business units, each with its own Executive VP and UX team. Later on, the UX team may become centralized again. Between 2007 and 2014, Yahoo did this twice, and they’re not the only company whose UX teams have gone through such cycles of change.
In theory, in a distributed UX model, individual UX teams should consistently be able to design differentiated user experiences. But—except in rare circumstances—they don’t. In reality, very few UX teams consistently deliver stellar, differentiated experiences. The few who do typically work for a VP or Senior VP of UX or a Chief Experience Officer (CXO) who has a strong partnership with the CEO.
“Having a CEO who recognizes the value of and supports User Experience and, more importantly, advocates for you as a UX leader affords you a level of power that enables you get things done.”
Does this mean that we shouldn’t work for companies with distributed UX teams? No, but it does mean that there needs to be a VP of UX in each division. It’s essential that the UX leader sit at the same level in an organization as the leaders of other disciplines such as Product Management and Engineering. Back in 2007, Pabini wrote an article about this titled “Sharing Ownership of UX.” While what she wrote then still holds true, software development has evolved considerably since then. So, we’ll take a fresh look at this topic in a later column in this series.
Another reason that User Experience needs to have visibility and support at the highest level in an organization: you want senior leaders to feel genuinely excited about your being on their team. They’ll share their excitement with the entire organization and build enthusiasm and support across the company. You should never join a company unless there’s significant buzz and genuine excitement about your joining—enthusiasm that executives share broadly throughout the organization. You’ll need this level of enthusiasm and broad-based support when you take the helm. As a new leader with executive support, you’ll have a brief honeymoon period during which you can set expectations, drive process changes, build alliances, and get teams excited about User Experience—in ways that you could not if you were just another hire. At a minimum, you need to be either a VP of UX or report to a VP of UX to effectively lead User Experience in an organization.
Finally, you need regular exposure to and the mindshare of the head of the organization for which you work. This leader must recognize the value that UX design can deliver. If you do not have this level of visibility and support, you must everything possible to create it. If you are unable to achieve this yourself, either encourage the company to hire someone at a higher level to whom you can report—who will have high visibility on the executive team—or move to another company. The leader of your business unit must recognize that great design can help their organization to differentiate its products from those of competitors and that this is just as important as technology innovations and their product roadmap.
As a new UX leader in an organization, you need to make sure that you have your boss’s mindshare, that the two of you see eye to eye, and that your boss is excited about the vision of what you can accomplish together. Of course, your boss also needs to believe that you can execute and deliver results, but you want your boss to be emotionally invested in your success. When an executive hires you and speaks highly of you, he or she will become emotionally invested in your success and even come to your defense, if necessary. Executives’ credibility depends on other people seeing them make good decisions. Since one of the decisions was to hire you, it’s in your boss’s best interests for you to succeed. That’s the dynamic that you should be looking for when joining a new company.
The leader of your business unit must recognize that great design can help their organization to differentiate its products from those of competitors and that this is just as important as technology innovations and their product roadmap.
If you don’t feel that shared excitement or you’re questioning whether a company truly intends to differentiate on the basis of stellar UX design, you need to establish enough of a relationship with the leader who wants to hire you to enable you to delve deeply into the inner workings of the company, as well as the leader’s plans. Only then can you judge whether you can believe what you’re being told or it’s just talk. Often, the leaders of companies who are trying to hire a UX leader tell candidates that User Experience is an essential part of their business strategy—after all, that’s what their customers want to hear, so they often talk about the importance of User Experience. In reality, many of them are just giving lip service to it. Perhaps this is not deception so much as it is a lack of understanding on their part about what inculcating User Experience into a culture really means—and the degree of change that entails—as well as ignorance of what it takes to produce great user experiences. They may not realize the investment of time and resources that it takes.
Far too many companies think that, if they hire just one great designer, they’ll get great UX design. Or, they may think that, if they hire one solid UX leader and a couple of designers, they’ll transform their products’ user experience—even if they have 500 developers and 50 product managers. It’s not that easy. To transform a company into a design-led organization, the company has to evolve—with the help of a UX leader who understands the goal and what it takes to drive that change. Such a leader knows how to set up an organizational structure that will enable the UX team to succeed. And that leader can inspire a culture that attracts the best UX talent, lets researchers and designers do what they do best, and fosters strategic design thinking within the organization.
We’ve both become tired of the back-and-forth dialogue about what it will take to make User Experience more relevant, so we can consistently deliver truly great user experiences. We need to lead! UX leaders need to learn the art of leadership to increase their scope of influence and transform User Experience. Step up and take the opportunity to help drive the transformation!

What’s Next?

“Attract the best talent in the industry, step into the boardroom, and gain recognition as a senior leader who can drive an organization’s transformation from mediocrity to excellence.”
What does it mean to be a great leader and, in particular, a great UX leader? Our next column will focus on the art of leadership and the specific qualities and skills that UX leaders must have to attract the best talent in the industry, step into the boardroom, and gain recognition as a senior leader who can drive an organization’s transformation from mediocrity to excellence. We’ll also describe the unique factors that make leading a UX team so very different from leading, say, an Engineering team.
Throughout this series, we’ll discuss the things that UX leaders need to do to transform an average UX team into one that consistently delivers user experiences that stand apart from their competition. In subsequent columns, we’ll discuss topics such as the following to illuminate the future path of UX leadership as radical transformation:
  • defining an optimal UX organizational structure by leveraging insights from design agencies and the most successful UX design organizations in product companies
  • working with multidisciplinary product teams
  • devising an effective UX design process—focusing less on agile or Lean UX and more on outcomes
  • making the case for what functions User Experience must own to drive radical transformation
  • measuring success for User Experience by looking at metrics from an executive’s perspective
  • meeting users’ rational needs by producing usable and useful products, as well as connecting with their hearts and driving emotional engagement
  • ensuring relevance and high-level visibility for User Experience
  • driving innovation
  • instilling design thinking throughout your organization’s culture to scale your UX organization
  • leveraging external design agencies to stimulate fresh thinking, expose your team to new approaches, drive quality, and scale your team
- See more at: http://www.uxmatters.com/mt/archives/2014/10/the-future-of-ux-leadership-radical-transformation.php#sthash.qK7i85qT.dpuf

A Pattern for User-Centric Organizational Change

go to article

Published: October 6, 2014
“During internal UX design presentations, many UX designers find themselves faced with well-meaning stakeholders who believe that their needs are highly representative of the needs of users, or customers.”
During internal UX design presentations, many UX designers find themselves faced with well-meaning stakeholders who believe that their needs are highly representative of the needs of users, or customers. For example, in recent months, stakeholders have told designers on my team:
  • “I prefer using a house icon instead of the word Home in the navigation, and I am sure that our users would feel the same way.”
  • “I used to be in the same field as our users five years ago, so I am sure that I know what they want.”
  • “If this is too difficult, we’ll just put more information in the training manual. That is what our users would expect.”
Rather than seeing this type of response to design decisions as an obstacle, I encourage my team to see this as an opportunity to help stakeholders understand that they are not representative of users. In all of the cases that I mentioned, my team already had direct user feedback that indicated the stakeholders’ assumptions were in fact incorrect. However, even this type of data may not be enough to change such deeply held beliefs.
On projects, for example, I have seen limited success when using tactics like providing access to usability test–session videos as a means of helping internal stakeholders to understand current user needs. While such an approach is helpful in building stakeholder understanding of specific user needs relating to a particular project, this type of learning is not necessarily portable across an entire organization.
After closely observing this organizational dance for several years, I conducted some research on how to help non-UX employees to develop a deeper understanding of user needs. The research that resulted from my curiosity about this issue eventually evolved into my doctoral research topic.
During that research, a pattern emerged that revealed a gap in UX professionals’ typical list of truisms. While “Know your users, because they are not you” is already on that list, we should add “Know your internal stakeholders, because they are not you” to the list. UX professionals are notrepresentative of the average employee in an organization.

The Listen, Learn, Act Framework

“I have been working with my team to develop the Listen, Learn, Act framework into a UX pattern for customer-centric organizational change.”
Employing this new point of view, I began to research a more systemic way of communicating current user needs to stakeholders—that is, non-UX employees. I created an initial, three-step framework—Listen, Learn, Act—to support more systematic user connectedness. During my research, I found that many non-UX employees feel frustrated when
  • they want to listen, but do not have access to voice-of-the-customer (VOC) data
  • they want to learn about, but do not have a clear sense of their firm’s customer-centric vision
  • they want to act, but first need to engage in training so they can learn how to apply customer-centric behaviors in their daily work 
Conversely, UX professionals—who are often more directly connected to user needs—become frustrated when internal stakeholders cannot understand how a design fulfills known user needs and, thus, their rationale for design decisions.
More recently, I have been working with my team to develop the Listen, Learn, Act framework into a UX pattern for customer-centric organizational change.  Communicating this framework using the familiar construct of a UX pattern has helped the designers on my team to tackle the problem of the stakeholder-user disconnect as a design problem instead of an issue relating to organizational politics. By applying this type of design thinking, we have reconceived our typical UX artifacts for the purpose of communicating with an internal audience and bridging the stakeholder-user gap.

Listening

“We start by listening and applying qualitative analysis practices to UX artifacts….”
In applying this pattern for customer-centric organizational behavior change, we start by listening and applying qualitative analysis practices to UX artifacts such as
  • Usability Reports
  • Ethnography Studies
  • Usage Metrics
During our analysis, we apply qualitative thematic coding across various customer-feedback listening posts.

Learning

“During learning, we take our coded themes and translate them into a customer journey map.”
Once we have a strong coding pattern in place, we can move on to the next phase in our pattern for customer-centric organizational behavior change, whose goal is to discover insights and learn from our data.
During learning, we take our coded themes and translate them into acustomer journey map. During this mapping process, we first create a simplified story about the customer’s journey when using our product. We then leverage this storytelling framework by inserting our coding from the listening phase so we can generate a data-driven storyboard. To increase the perceived validity of our journey map, we very carefully map our insights back to specific data sources. This approach has the added benefit of showing when it’s possible to triangulate a customer need across multiple listening posts.
Our goal during this learning phase is to create a journey map that both
  • conveys what our data shows is most important to customers
  • is comprehensible by a typical internal stakeholder in under ten minutes
The process of achieving this ten-minutes goal usually involves some pretty ruthless editing to ensure very succinct communication.
With this journey map in hand, our next step during the learning phase is to communicate the map broadly across the organization. By presenting this conceptual framework to our stakeholders, we build a common understanding of user needs—long before we present any design concepts. Because we have taken the additional step of tracking our data sources, stakeholders who remain skeptical can go back to the original data to review our analysis.

Acting

“We map our design rationale directly back to specific elements of the journey map.”
Having achieved an enhanced level of organizational understanding, we can then move on to the next stage of our pattern for customer-centric organizational behavior change and act.
During this stage, our primary action is to communicate a design solution and provide its accompanying design rationale. What makes this different from the way others might leverage journey maps is that we map our design rationale directly back to specific elements of the journey map. By delivering design documents that cross-reference our journey maps, we fully realize our pattern for customer-centric organizational behavior change. This approach lets us
  • build a common understanding of customer needs through easy-to-understand customer-insights education—using our journey map
  • deliver our design rationale within the framework of this common understanding of customer needs
By tying our design decisions back to the journey map—our common organizational knowledge base—we make our decisions less mysterious to our stakeholders. This can reduce the friction that is often associated with the socialization of a design.
Prior to the introduction of this pattern for customer-centric organizational behavior change, UX designers had tried to accomplish too much during a single design presentation meeting. They attempted to get stakeholders up to speed on user needs, while at the same time defending their design solutions. During those meetings, many stakeholders had seemed overwhelmed by the amount of information the designers were communicating to them, causing them to fall into the familiar pattern of assuming they were representative of the user.
Although this may seem counterintuitive, we actually gained greater efficiency by having two meetings instead of one. Separating user-needs education—our journey map presentation—from the communication of our design rationale—our design presentation—helped our stakeholders to more effectively digest the information.

Becoming Customer Centric

“To become customer centric, an organization must derive its goals from VOC data.”
To become customer centric, an organization must
  • derive its goals from VOC data—listen
  • communicate these goals broadly throughout the organization—learn
  • help employees to achieve these goals—act
By using this pattern for customer-centric organizational behavior change, UX professionals can position themselves as customer-centric change agents and create broader-based organizational support for their design solutions.
- See more at: http://www.uxmatters.com/mt/archives/2014/10/a-pattern-for-user-centric-organizational-change.php#sthash.e3Ykzsny.dpuf

Wednesday, September 24, 2014

Five Things They Didn’t Teach Me in School About Being a User Researcher

go to article

Graduate school taught me the basics of conducting user research, but it taught me little about what it’s like working as a user researcher in the wild. I don’t blame my school for this. There’s little publicly-available career information for user researchers, in large part because companies are still experimenting with how to best make use of our talents.
That said, in the midst of companies experimenting with how to maximize user researchers, there are a few things I’ve learned specific to the role of user researcher that have held true across the diverse companies I’ve worked for. Some of these learnings were a bit of a surprise early on my my career, and I hope in sharing them I’ll save a few from making career mistakes I made in the past for lack of knowing better.

There’s a ton of variation in what user researchers do.

In my career, I’ve encountered user researchers with drastically varying roles and skillsets: many who focus solely on usability, a few who act as hybrid designers and researchers, some that are specialists in ethnography, and yet others who are experts in quantitative research. I’ve also spoken with a few who are hybrid market/user researchers, and I know of one tech company that is training user researchers to own certain product management responsibilities.
If you take a moment to write down all of the titles you’ve encountered for people who do user research work, my guess is that it will be a long one. My list includes user experience researcher, product researcher, design researcher, consumer insights analyst, qualitative researcher, quantitative researcher, usability analyst, ethnographer, data scientist, and customer experience researcher. Sometimes companies choose one title over another for specific reasons, but most of the time they’ll use a title simply because of tradition, politics, or lack of knowing the difference.
At one company I once worked for, my title was user researcher, but I was really a usability analyst, spending 80% of my time conducting rapid iterative testing and evaluation (RITE) studies. When I accepted the job at that company, I assumed–based on my title–that I’d be involved in iterative research and more strategic, exploratory work. I quickly learned that the title was misleading and should have been usability analyst.

What does this all mean for your career?

For starters, it means you should do a ton of experimentation while in school or early on in your career to understand what type of user research you enjoy and excel at most. It also means that it’s incredibly important to ask questions about the job description during an interview to make sure you’re not making faulty assumptions, based on a title, about the work you’d be doing.

Decisions influence data as much as data influences decisions.

I used to think the more data the better applied to most situations, something I’ve recently heard referred to as “metrics fetishism.” I’ve now observed many situations in which people use data as a crutch, end up making mistakes by interpreting “objective” data incorrectly, or become paralyzed by too much data.
The truth is that there are limitations to every type of data, qualitative and quantitative. Even data lauded by some as completely objective–for example, data from website logs or surveys–oftentimes includes a layer of subjectiveness.
At the beginning and end of any research project there are decisions to be made. What method should I use? What questions should I ask and how exactly should they be asked? Which metrics do we want to focus on? What data should we exclude? Is it OK to aggregate some data? What baselines should we compare to? These decisions should themselves be grounded in data and experience as much as possible, but they will almost always involve some subjectivity and intuition.
I’ll never forget one situation in which a team I worked with refused to address obvious issues and explore solutions without first surveying users for feedback (in large part because of politics). In this situation, the issues were so obvious that we should have felt comfortable using our expertise to address them. Because we didn’t trust making decisions without data in this case, we delayed fixing the issues, and our competitors gained a huge advantage. There’s obviously a lot more detail to this story, but you get the point: In this circumstance, I learned that relying on data as a crutch can be harmful.

What does this mean for your career?

Our job as user researchers is not only to deliver insights via data, but also to make sure people understand the limitations of data and when it should and shouldn’t be used. For this reason, a successful user researcher is one who’s comfortable saying “no” when research requests aren’t appropriate, in addition to explaining the limitations of research conducted. This is easier said than done, especially as a new user researcher, but I promise it becomes easier with practice.

You’re not a DVR.

Coming out of school, I thought my job as a user researcher was solely to report the facts: 5 out of 8 users failed this task, 50% gave the experience a score of satisfactory, and the like. I was to remain completely objective at all times and to deliver massive reports with as much supporting evidence as I could find.
I now think it’s old-school for user researchers to not have an opinion informed by research findings. Little is accomplished when a user researcher simply summarizes data; that’s what video recordings and log data are for. Instead, what’s impactful is when researchers help their teams prioritize findings and translate them into actionable terms. This process requires having an opinion, oftentimes filling in holes where data isn’t available or is ambiguous.
One project I supported early in my career involved a large ethnography. Six user researchers conducted over 60 hours of interviews with target users throughout the United States. Once all of the interviews were completed, we composed a report with over 100 PowerPoint slides and hours of video footage, summarizing all that was learned without making any concrete recommendations or prioritizing findings. Ultimately we received feedback that our report was mostly ignored because no one had time to read through it and it wasn’t clear how to respond to it. Not feedback you want to receive as a user researcher!

What does this mean for your career?

The most impactful user researchers I’ve encountered in my career take research insights one step further by connecting the dots between learnings and design and product requirements. You might never be at the same depth of product understanding as your fellow product managers and designers, but it’s important to know enough about their domains to translate your work into actionable terms.
Having an opinion is a scary thought for a lot of user researchers because it’s not always possible to remain 100% objective in bridging the gap between research insights and design and product decisions. But remember that there’s often always limitations and a subjective layer to data, so always remaining 100% objective just isn’t realistic to begin with.
Little is accomplished when data is simply regurgitated; our biggest impact is contributing to the conversation by providing actionable insights and recommendations that helps decision makers question their assumptions and biases.

Relationships aren’t optional, they’re essential.

As a student, my success was often measured by how hard I worked relative to others, resulting in a competitive environment. I continued the competitive behavior I learned in school when I first started working as a user researcher; I put my nose to the grindstone and gave little thought to relationships with my colleagues. What I quickly learned, however, is that taking time to establish coworker relationships is just as important as conducting sound research.
Work shouldn’t be a popularity contest, right? Right–but solid coworker relationships make it easier to include colleagues in the research process, transforming user research into the shared process it should be. And trust me, work is way more fun and meaningful if you enjoy your coworkers!

What does this mean for your career?

Take the time to get to know your coworkers on a personal level, offer unsolicited help, share a laugh, and take interest in the work that your colleagues do. I could share a personal example here, but instead let me refer you to Dale Carnegie’s book How to Win Friends and Influence People. Also check out Tomer Sharon’s book It’s Our Research.

Expect change–and make your own happiness within it.

Change is a constant for UX’ers. I’m on my eighth manager as a user researcher, and in my career I’ve been managed by user researchers, designers, product managers, and even someone with the title of VP of Strategic Planning. I’ve also been through four reorganizations and a layoff.

What does this mean for your career?

Change can be stressful, but when embraced and expected, you’ll find that there are benefits to change. For example, change can provide needed refreshment and new challenges after a period of stagnation. Change can also save you from a difficult project or a bad manager.
I remember a conversation with a UX leader in which he shared he once quit a job because he couldn’t get along with a peer who just didn’t get the user experience process. A few months after he quit, the peer was fired. If only he had stuck around for a while.
The U.S. Navy SEALs have a saying: “Get comfortable being uncomfortable,” which refers to the importance of remaining focused on the objective at hand in the middle of ongoing change. Our objective as user researchers is to conduct research for the purpose of improving products and experiences for people. Everything else is secondary–don’t get distracted.
For more detailed recommendations on how to deal with change as a user research, I highly recommend watching Andrea Lindman’s talk “Adapting to Change: UX Research in an Ever-Changing Business Environment.”

Concluding thoughts

I’ve been happy to see in the past two years that the user experience community has stepped up in making career advice more readily available (we could do even better, though). For user researchers wanting advice beyond what I’ve shared in this article, here are four of my favorite resources:
  • Judd Antin’s talk in which he covers many opportunities and challenges of doing user research:http://vimeo.com/77110204.
  • You in UX, an online career conference for user experience professionals.
  • Tomer Sharon’s book It’s Our Research.
  • special issue of UXPA’s UX Magazine, with the theme of UX careers.