Image
Top
Menu
July 25, 2014

Agile & UX: it’s a mindset, not a process

Agile is one of these magical words in our days. It’s like a promise that by using an “agile method” everything will be faster, cheaper and definitely more innovative. The project managers that I heard talking about Agile made it always sound like paradise: everybody is working together, the process is very flexible, the client is involved and part of the game, it’s like a big game show and everybody is invited to play. The result will be an amazing product that everybody loves – because of the very flexible and dynamic process.

And I share parts of that vision. Having iterations, coming together regularly to share work in progress, give and get feedback – that’s great!

But I am still trying to figure out what an agile process means for a UX person. How does it affect my working style? In order to answer that question for myself I need to get a better understanding about

 


What does Agile mean to me?

To me there are three main characteristics about the agile approach:

 

1. Agile is an alternative to traditional project management

The agile approach offers a new way of planning a project by splitting it into smaller pieces.

 

2. Agile is about collaboration, everything happens in parallel

The agile approach to me is first and foremost about collaboration instead of working in silos, which also allows more flexibility instead of following fixed phases.

 

3. Agile is a mindset

All in all agile to me is a mindset rather than a methodology. A lot of methods and “tools” are not really new to the development process – but it helps to start a new way of thinking. Even though we all like to be proud of our “work results”, we want to feel some kind of “ownership” of our deliverables – which could be wireframes, design comps or code – in a project team we should start to get a more holistic view and understand that it is all about the final product that we are all contributing to – and not about a single deliverable.

I really like Anders Ramsay’s thoughts on the Agile Attitude: Why Agile UX is Meaningless without an Agile Attitude

 


What does Agile mean for UX?

A different way of organizing projects, a collaborative working style and a specific mindset – what impact does it have on my way of working? How does it effect my role as a UX designer?

I was having an interesting conversation with my colleague, Harjot, and we were coming up with 4 different “visions” of how we as UX people could see our role in an agile development process.

 

Agile as a Mini Waterfall
Mini Waterfall

Agile as a Mini Waterfall

That approach is something that I witnessed a lot: we are talking about agile – but it’s not really a big change to a waterfall method other than splitting a bigger goal into different sections – and keep passing them on from one silo to the other.

Pro:

  • The work is done in small slices with quick turnaround so that the client has a quick access to what could potentially turn into the final product.

Con:

  • It doesn’t foster collaboration very well.
  • There is a risk of not seeing the bigger picture.

Conclusion: This version of an “agile process” is more or less a fake and doesn’t change we work together in a team that much.

 

Agile with UX Strategists
UX Strategist

UX Strategist

Another approach could focus on reducing deliverables. Instead of focusing on creating detailed wireframes the UX Designer observes, listens and verbalizes concepts with the visual designer and the developer.

Pro:

  • Time is not invested in detailed wireframes. Working on “the real thing” starts sooner.
  • It fosters collaboration

Con:

  • There is a risk of missing out details or running in the wrong direction
  • Developing takes more time than creating a wireframe – so it will be cost more money and time before feedback can be received

Conclusion:

This version would change the role of an UX Designer and would ask for different or additional skillsets: a UX Designer becomes more of a strategist and lead person, focuses on the big picture but not on details and micro-interactions.

 

The Utopian Version of Agile
Utopian Agile

Utopian Agile

This is the version that I hear people talk about often. It’s the paradise version, the dreamland, the “let’s do it all together”: People with different skills and knowledge would come together, brainstorm, sketch out, ideate and iterate together. The product is being creating based on a team effort with people sitting next to each other to communicate easily. Deliverables are reduced to the minimum, developing starts right away.

Pro:

  • Focus on collaboration, no silos
  • Everybody is in the loop and constantly involved

Con:

  • Risk of not seeing the big picture because there is no detailed “plan” (=wireframes)
  • Needs lots of resources – inefficiency?

Conclusion: Is this what the ideal version of agile should look like? Is this even feasable?

 

Agile as a Collaborative Waterfall
Collaborative Waterfall

Agile as a Collaborative Waterfall

The last approach is my currently preferred working style. It follows the traditional approach – but uses the “agile attitude” with a very collaborative mindset. A UX Designer still does wireframes – but instead of figuring everything out amongst their UX tribes they talk to a developer and designer to make sure, ideas are feasible.

Pro:

  • People are in the loop
  • Ideas are being reviewed by people with different skills

Con:

  • From a project management point of view it’s hard to plan resources

Conclusion: This approach is a version of having a collaborative work environment while letting people still focusing on their specific skill sets.

I am curious to experience different “agile” work environment to get a better idea of how it affects my work as a UX designer – but for now to me agile is mostly about the attitude than about a method or a process.