How To Apply UX In An Organisation New To User-centred Design

How To Apply UX In An Organisation New To User-centred Design

Summary:

When you’re the only UX Designer in a team, the hot and cold support for your role can be difficult.

Luke reflects on his experiences working within difficult corporate cultures, and explains how setting the right expectations, getting buy-in, and charting a course through it all can go a long way towards creating positive change.

I once was subcontracted by a large corporate as the sole user experience designer in a team of designers and developers. This isn’t an unusual situation for a UXer, but this role came with unique difficulties.

My mandate was to help the project team “create a well-designed product that met user needs.” While there was a lot of support for this, after a few weeks it became obvious that much of it was lip-service, and there were more than a few challenges in actually achieving this goal. It was easy for the organisation to say the right things and use the right buzzwords, but getting things actually moving in the right direction was hard.

As the sole user-centred designer with any experience in the team, I noticed that the support I received on applying user experience principles beyond basic usability and accessibility ran hot and cold. My attempts to encourage people to care about the fact that their web application was only part of the user’s larger experience of a situation were often falling on deaf ears.

Pushback like this is pretty normal when introducing UX to a new organisation—it’s natural to resist change. However, by applying some creativity and strategic thinking, these hurdles can be overcome. Setting the right expectations, getting buy-in and then charting a course through it all to demonstrate achievement goes a long way towards “earning your keep” and creating positive change in a difficult environment.

Principles Trump Process

The biggest challenge I encountered was the internal processes used by the team. These processes were in place for a number of reasons: the complicated technical infrastructure we were stuck with, the varied backgrounds and experiences of the team members’ and the dominant culture of the workplace. It was clear that I, as a lone user experience designer, wasn’t going to change any of that very quickly, and in the meantime I needed to be scoring clear goals.

What I learnt after several unsuccessful attempts to bang my head against the process wall is that well-applied UX principles trump process every time.

Here’s why:

  • Principles can be used to determine both the end product as well as the journey you use to get there.
  • Processes can adapt to change, but principles are a guiding light. They define the goal for what your user-centred approach should achieve—something that is sorely needed when processes aren’t working so well.
  • Process is often the first thing people blame when things don’t work, but too much energy goes into changing it that could instead be fed into developing the relationships and understandings that underpin your role.
  • The processes needed for UX are rarely in place for an organisation that is new to user-centred design.
  • Even if you do have the “right” processes, if people aren’t participating and don’t have the right attitude, they won’t work anyway.
RELATED:  Sketchnoting 101: How To Create Awesome Visual Notes

If you’re working as a sole user advocate in a team, it’s your attitude, not your job description, that will make the difference.

Here are four principles for going it alone in a business new to UX, based on my experiences:

  1. Listen up!

    As Grandma used to say: “You have two ears, but only one mouth”. People often describe UX practitioners as facilitators, and as the reconcilers of creative and technical tensions that deliver a satisfying experience for users. To fulfil this role, you need to understand the points of view of the people you’re talking with.

    This requires that you shut up and actively listen to others as they describe their understandings and ideas, their previous attempts to solve the design problem, to implement a technical solution, or the many pressures, perspectives and priorities you may be facing.

  2. Be the voice of honesty and open-mindedness.

    Always have time for talking with your team. Keeping your head down to achieve your tasks and to look like you’re busy and productive won’t end up convincing people that you’re worth your wage. It may disengage you from the team and make you seem stand-offish. UX is a collaborative discipline, so make sure you bring lots of team spirit with you to a project.

  3. Get practical and collaborative.

    When the stakes are high, discussions can become lively when people latch onto a pet subject or solid belief. Voicing opinions is fine, as long as people in your team all have the same goal in mind. It doesn’t matter if they have different ideas about how to get there—your job is to turn these opinions into tangible tasks that can be discussed, tested and refined. If you can quickly sketch or prototype an idea, you can save a lot of time arguing when you may already agree fundamentally. Plus you’ll get the benefits of iterating a design to boot.

  4. Make it good enough, but no better.

    As a UXer, your work is never really finished. Conversations about what is most important to get right will be more fruitful than an endless obsession with making things perfect. Knowing when you’re done—and when you can let others take over from what you’ve begun—is far more satisfying. Getting the foundations, attitudes and direction right will set the stage for the rest of the team to carry the vision through the rest of their work.

Keeping these principles in mind keeps me sane during the hustle of a new or difficult working environment. I hope you can apply these too, and would love to hear about your experiences. Let me know in the comments!

Written by
Luke Chambers
Join the discussion

12 comments
  • Likewise I am having the same issue with different stakeholders in my UX project.. Thanks a lot for sharing this..

    • You’re very welcome, Nitish. How are things going with the project? Can you share anything else you’ve learnt too?

  • This is really helpful. I’m currently facing the same issue. I’ve been hired to redesign a big web app and “make it look beautiful’. Yeah this is what my line manager asked for.
    I’m the only Designer in the company and people start to give me some weird tasks, like changing an image background or size. It’s been 3 month now that i didn’t get the opportunity to test my knowledge and run some usability testing or user interview. All i’m doing is Coding, because i’m a front end developer too.
    How can i change this situation to my favor and let the team and the company know what is really my tasks and my role as a new UXer???

  • this was really helpful.

    I’m a design student in Simon Fraser University which concentrating on interactive system and I’m doing my first Co-op as a UX designer. It is a big challenge and definitely having team work and interpersonal skills one of the major things that helps me to connect the team members together.

  • I am in the similar situation as you. They want UX but are not sure what it is and getting input from stakeholders is proving to be real hard, not to mention, my role itself is fluctuating so much I am not even sure what I am doing. Like right now I am suppose to purpose some designs to propose change in color pallet of the website they had developed before I joined on.

    Again, I am the sole User Experience designer, they have service design experts but not one for product design

  • I’m in a similar situation where the organization is very much interested in UX but the team pay lip-service to it. After a full UX cycle, architectural considerations and project timelines are given priority over user needs. And a s a result every proposed feature has been descoped out of the development. What is left is a product with limited usability. I have accommodated to technical considerations consideration to the point of being a doormat because I believe team success is important. It is however one-sided. When I insist a design consideration that we should not compromise on, it is blatantly ignored. I made the fatal mistake of losing my temper at the colleague following which they promptly bypassed me with the manager’s approval. The manager has placated me saying that the project must go-live. I have conceded. But basically UX in the project is just a paperweight. I admit I was in the wrong by getting emotional. But how can I convince the team that while technical challengers are valid, a user-centric product would be more successful than a technically feasible product?

  • I found this at the right time. Here I am exasperated trying to get things to work. This article is so perfect it exactly highlights my situation. I must change my strategy now after reading this. Thank you Luke.

  • My first company i worked in as a UX UI designer is exactly like this. No idea on what they are doing, they just want to make an app that does “this”. And the rest of you will have to conceptualize from scratch. I am the sole UX UI Designer they hired to do this, and they hired remote developer to build it. Its really hard.