UX Magazine

Defining and Informing the Complex Field of User Experience (UX)
Article No. 755 October 28, 2011

UX, It's Time to Define CXO

What is a Chief Experience Officer (CXO)? We’ve been singing its praises when the title started cropping up in boardrooms. “Thank the gods, UX has finally made C-level!” There were riots in the streets, free sharpies were given out on every city block, and colored pencils rained from the sky... Okay, obviously none of that happened. However, we were all elated to know that experience was finally being represented at an executive level.

But now that the CXO title has been around for a few years, I ask you: what does the CXO really do and how have things changed for us? How have we, as a profession, taken ownership of this role? What are you doing differently now that you have a CXO in your organization, and does that CXO even have a UX background? Furthermore, how do we ensure the CXO seat is filled by UX, and what skills does someone need to fill it?

I think that this role needs some serious examination. If we don’t investigate the definition of the CXO further and if we don’t answer the questions around what one does and why the position exists, then the UX field can never really own it. And we have to own it. We’ve waited so long for executive backing! But we need to present a united front and a solid definition of the role, else it will not be what we all have hoped for. If we don’t get there first, other parts of the organization will define it for us, and we will lose all hope of solidifying UX’s position at a higher level.

Let’s start by looking at how CXO is defined today. According to Wikipedia, a CXO is “an officer responsible of all user experience of an organization. This function is taking care of marketing communications, community relations, internal relations, HR relations, investor relations—and all other encounters an organization may have with its various audiences.” This kind of makes sense, but doesn’t seem like what we asked for. The definition on chiefexperienceofficer.com comes close, saying that the CXO is “the CEO’s strategic design resource” whose areas of concern include:

  • corporate leadership in UX strategy
  • software and hardware design management
  • creative reviews and concept development
  • intellectual property positioning and protection

Even this seems a little bit sketchy, but we’re progressing. There does seem to be a definition looming, but one can see how UX goals and experiences are not being fully represented.

So, let’s define it for ourselves!

First, let’s think about the intended output. What is the goal of having a CXO? Ideally, it’s to have someone responsible for curating and maintaining a holistic user-, business-, and technology-appropriate experience, thus backing up and advocating for the UX team. To do this, a CXO needs to:

  1. understand the users, business and technology
  2. figure out how the product should grow to support the intended experiences
  3. maintain an evolving plan of action to support and produce this output

Understand the users, business, and technology

In order to know our users, we need to institute a design research framework. A design research framework is a framework for conducting user research based on company and product needs and growth plans. This prevents the UX group from just conducting ad hoc research whenever there is a project; instead, they continually conduct research in order to keep the users participants in the product development. This research framework should aim to learn about user needs and find ways to use this information to enhance user experiences. Personas and related items should look at all user types and be created and maintained over time. In order to know our business and technology, the CXO needs to be a great listener as well as invite business and engineering team members into the experience work.

Figure out how the product should grow

Once the CXO and the experience team know the users, they need to define the experience strategy to meet and exceed user expectations. This means they also need to define the organization’s personality so that the experience can exude and tie to that personality. One way of doing this is to hold experience strategy meetings where the entire team (UX, business, marketing, brand and technology) looks at the current business model, users, branding and technology and brainstorms how they want the product to appeal and grow. During this time, they are basing the product’s appeal and growth on persona needs and goals, business goals, and tech goals.

After the entire team has brainstormed ideas around the growth of the product, they begin to get more specific by defining product features based on the ideas that have come up. No idea is a bad idea at this point, and each should be considered. Next, the features are aggregated and prioritized by everyone on the team. The output is an experience-based strategy and product roadmap. That roadmap shows the path of product growth and has taken into consideration each team member’s point of view, while focusing on the experience. This roadmap should be made public to the entire organization to ensure the organization’s focus is understood as well as to gain buy-in from employees.

Note: In bigger organizations, the CXO would partner heavily with product to ensure the roadmap “maps” to the number goals (revenue, reach, etc).

Maintain an evolving plan of action

The CXO needs to stay on top of the product roadmap and experience strategy, and continually update them in response to changes in each domain (users, business, brand, and tech). One stays informed about users through the design research framework. The business and tech concerns are the responsibility of other parts of the organization, but are things the CXO needs to be informed about to keep the experience strategy up to date. Thus, they should use their communication and listening skills to partner with leaders from these other teams in order to stay in the know, as well as include these partners in their own work.

By following these three steps, the CXO curates and maintains a holistic product experience that includes input from across the organization as well as from the customers the product is meant to serve. It is important to recognize that depending on the organization, the CXO may personally do this work or it may be someone within her organization, but the point is that the experience is being attended to, and the roles, purpose, and value of the CXO are being defined.

In order to take these three steps, the CXO and/or her team needs to be able to:

This is a C-level position, so “experience” in every sense of the word is a key component of the role. A successful CXO should consume all the information she can about UX, understand the business side of things, have empathy, and learn about the responsibilities of all roles in the organization. In large organizations, it will be the CXO who puts together the team to take on these roles. In order to put that team together, the CXO needs to understand what it takes to go through UX processes to create the outputs that UX professionals create each day. We all know what happens when non-UX folks try to put together a team of UX talent. Sometimes it works, but a lot of times it doesn’t.

Lastly, using this model, we can see that a CXO is responsible for understanding the user and organization domain, curating that into an experience, maintaining that experience, and communicating that throughout the organization. CXOs either do this themselves (in the case of small organizations and startups) or have the skills to hire the right people to take on these roles. That, in short, is the definition I’m proposing for CXO. There are probably other and better ways to define the role, which is why I wrote this: to start the conversation.

By defining CXO ourselves, UX can make it a point to create our leadership instead of being left out of it. If we do define this ourselves, it will mean UX-minded people will have to fill the CXO spot, because they will be the ones that really know what the role is. By nailing down this definition, proving its benefit to our business and executive personas, and following through on that benefit, UX will be empowered to step into the C-level world.


User Profile

Lis Hubert is a Strategy & UX Consultant based here in NYC. Her passion lies in helping people and companies of all types make their products and services easier and more enjoyable to use. Lis has worked with clients such as ESPN Mobile, NBA.com, Google, Weight Watchers, and MTV Networks and has recently signed on as Chief Experience Officer at 8coupons.com.

Add new comment



Great read! However, I am interesting in how you see the overlap with the Chief Marketing Officer. The CMO is responsible for the product development, market research, channel distribution, communications and pricing, in short everything around the product. These functions are quite distinctive in regards to those of the COO, CFO and CEO.

In contrast, the functions and responsibility you describe for a CXO position show major overlap in what the CMO does and can lead to conflicting situations?


This is one of those very, very few articles that I appreciate. It gets right to the point and leaves little (if any) grey areas to be questioned.
What I would like to reiterate would be the issues of "Experience" and "Business". To me, these items appear to be the biggest outstanding components that a a good CXO must offer. When I say "experience", I'm not talking about the user's experience, but rather the number of years a CXO has contributed to the field and to what degree he has grown within this capacity. More and more, I'm seeing people with 1, 2 and 3 years experience claiming the title of CXO; this blows my mind. Now mind you, the very few "real" CXOs that I know are all in the U.S. and work for big companies where a chief executive team has brought them on board after an extensive interrogation process.
The other group of CXOs are usually in smaller startups, but bring 10 experience to the position and rightfully deserve that title.
Then there are those who give themselves this coveted title with no experience whatsoever or they have a fellow co-worker who puts this title on them but have no idea what it means. (Even if they do know the definition of the title, they don't in anyway shape or form deserve it.

I've said this in several blogs before, but I wish there was a real way to qualify this title within our field. The whole #UX hashtag and "IA/ UX" job titles appears to be a big frenzy of an Experience Circus with just about anyone giving themselves these titles.

For those who know me, I often voice this a lot. In the last 2-3 years especially, every caricature from every motley crew has joined this field and has turned it into a circus. My question is, what is the qualifying factors that these people bring to the field and who's monitoring this?

I agree with Lis' closing statement which states "By defining CXO ourselves, UX can make it a point to create our leadership instead of being left out of it. If we do define this ourselves, it will mean UX-minded people will have to fill the CXO spot, because they will be the ones that really know what the role is. By nailing down this definition, proving its benefit to our business and executive personas, and following through on that benefit, UX will be empowered to step into the C-level world."

I'll stop here on this concern.

The 2nd outstanding factor I'd like to bring to the table is the issue of "Business". I believe that a fantastic CXO who's worth their salt will understand business. How to grow a business, and to endorse a product/ service. How to develop relationships with partners and competitors. How to approach a consumer on or off-line and know which part of the buyers life-cycle that consumer is in. What personas need to be catered too, and how to amalgamate design thinking for the betterment of business development.

Many UX professionals I know are either back or front end types that don't appear cool to A-type business personalities. They incorporate best practices by reading books and implementing information from blog articles and advice from Twitter friends. While all this is fine and dandy, I find that many UXers can not run a business meeting.

To me, the CXO must be more then just a UX type. While I believe that the UX value-add is the basis for such a position, I also believe that knowledge workers who are more social, business oriented and agile would serve greatly in a role such as this.

I luv the thought that was put into this article and would highly recommend it as a starting point for those wanting to get into this position or are asked to fill it.

In my 2nd last employment, I was hired as a Sr. IA, got promoted to Director of Usability and was asked to initiate this role of CXO. However at the time I was already planning on transitioning to a closer location at another company.

As I made this transition, one thought kept ringing through my mind. How could I fill this role of a CXO? I was already swamped as a Director. Did the company really understand what they were asking for by this request?

I was happy to move on from this, and although I currently hold the title CIA (Chief Information Architect) for my own consultancy, I can't help but think that someone else who wasn't qualified to hold this title nor run it's positon might of been hired for the job. What scares me most about this is that this job position is still young and there may be those who are holding these titles who are confusing the nobility of the craft so that in the long run, the title "CXO" will be common like "Web Designer".

Now I know the scenario I'm giving is a little extreme, but as guardians of the UX flame, it is up to us to initiate and define these positions that more and more companies are finally becoming aware of and are realizing the need for such a vital and specialized service.

Rock on.


More perspectives on the role, as well as some history: 1) Impact of the role of the Chief Customer Officer; http://riander.blogspot.com/2011/03/chief-customer-officer-and-ownership-of.html; 2) Hail to the Chief!: http://riander.blogspot.com/2007/06/hail-to-chief.html; 3) The Chief Experience Officer: http://riander.blogspot.com/2005/05/chief-experience-officer.html.


The emphasis is always on the the "T" in IT, even though the "I" that holds the intrinsic value.

I sat in on a conversation with a group of web pro's at a university. In a 20 minute conversation they worked out how they could streamline registration to include course schedules, financial aid and payment, housing applications and approvals. They could do it except that the registrar and admissions each have their own walled garden they protect. They could except that the housing group didn't want to. They could except that administration thought everything is/was as good as it could be.

An "I" person in administration is going to bring a far, far different perspective to any business. The opportunities for collaboration can be seen from the web's vantage point when it is beyond the view of those happy in their silo's.

Anyway, great article, congrats. Please succeed so we can use you as an example when advancing this idea in other organizations.


Great article Lis and congratulations on taking the CXO role at 8coupons. This is something I've been thinking a lot about lately and agree that we need to do a better job defining these roles (at all levels). I still see so much misunderstanding about what UX encompasses, often being equated to usability and HCI (even among practitioners) and tacked on as a bullet point for development and graphic design positions.