A recent report, published here on the Econsultancy blog, revealed a staggering 45% of companies aren't performing any UX testing when developing a creative project.

Whether it's a website or an app, user experience (UX) is an important factor in both the success, and the scalability of a product.

Together with the flexibility of the Agile approach to development, it can help you to build a better, more satisfying product. 

The importance of UX testing

We've all come across a website or used an application where, despite the obvious production values invested in its aesthetic appearance, something isn't quite right.

It might be confusing navigation, or a flash of window dressing, as distracting as it is redundant. Poor accessibility, or any other of a myriad of reasons that make your experience one you've no desire to repeat.

What looks good on paper, doesn't necessarily work in practice.

What is UX testing?

UX testing places your product in the hands of the customer and end-user during the development process, so that feedback on its constituent elements can be harvested and acted upon. These might include layout, design, content, functionality and interaction.

By observing how it performs in the hands of a real user, you can fix errors, iron out the creases, and continually improve, until you have a product everybody is happy with.

This way, you can ensure you never lose sight of what the customer and end-user wants from their website or app, adapting to fit business and user goals.

Why Agile?

The Agile approach sees development of a creative project carried out in short (usually 2- 4 weeks) cycles known as iterations, or 'sprints'. This places an emphasis on:

  • Flexibility
  • Feedback
  • Improvement

Which creates a framework intended to be:

  • Iterative
  • Adaptive
  • Fast

If you are developing in an Agile environment, your aim is to get a functional product into the hands of the end user as quickly as possible. This is the bare bones, which you then flesh out incrementally – according to the feedback you receive – over the subsequent iterations.

Successive releases are adapted, tweaked and improved, until an end product exists that meets the needs of the customer, and matches the expectations of the user.

UX testing + Agile

Although there's no strict linearity in the development cycle of an Agile framework, the fact remains that an Agile iteration and the accepted UX prototype design and testing process, are very similar.

As with the Agile approach, UX design is a system in which you iterate, test, learn from user reactions, rinse and repeat.

Traditional UX Testing can often be a long, drawn out process, with multiple test subjects, and results sometimes taking weeks to be collated, analysed and readied for the next stage. With Agile iterations all about a customer-focused, faster turnaround (the development cycle, remember, is also known as a 'sprint'), the timeframes of the two disciplines may seem incompatible.

This ignores one of the core values of the Agile development methodology: Adaptability.

Integrating UX Testing with Agile

It is simply a case of adapting UX Testing to fit in with the development cycle.

Size. Whether testing remotely or in-house, keep the number of participants involved in the process low. UX Designer and Blogger, Jeff Gothelf, suggests as few as three  (we would argue that in many projects fewer still) users are suitable for validation, and putting your team on the right footing for the next iteration.

Design. Begin your conceptual design early, and execute as much UX work as possible prior to the onset of development. This will aid in maintaining a consistent UI, as well as user familiarity, as the product evolves. Consider keeping the UX design team one iteration ahead of the developers

Continual testing. Ensure that UX Testing is an intrinsic, preferably scheduled, component of your development cycle. Undertaking testing at regular, preordained intervals will give your teams the steady flow of feedback they require to adapt to user needs, and plan for the next iteration.

Jeff Gothelf, UX Designer:

"The goal of Agile usability testing is to clear the boulders from the road – not provide pixel-level design direction.

By using a combination of the user-centric methodology behind UX Testing, and the flexible, customer-focused approach of Agile, firm bedrock upon which to build more successful websites and apps.

Rita Auta

Published 16 May, 2013 by Rita Auta

Rita Auta is Marketing and Communications Manager at Activate Media and where she frequently writes about business web technologies. Connect with her on Linkedin or Google+. 

1 more post from this author

You might be interested in

Comments (4)


Jeremy Swinfen Green

It is certainly important to conduct UX testing within an agile development framework. But this doesn't need to be difficult or time consuming. Excluding time to recruit participants, a test project can take as little as 2 days.

At Amberlight we do a lot of "active testing". A day of preparation including a pilot test is followed by a set of 4 or 5 UX tests that take place over a single day. (I think 3 would be an absolute minimum and with the best recruitment in the world 1 or 2 would bring huge dangers of skewed results.) Our clients observe these "actively" during an extended workshop that we moderate. Themes are identified and ideas formulated. After the final test we spend a couple of hours reviewing the tests and arriving at design decisions. No waiting around for a report.

For this to work we need committed clients willing to field a team of design and development decision makers for a long and hard day. But done right it can work really well and free up the development process to include several rounds of UX testing.

about 5 years ago


Nichola Finan

Thank you Rita - points well made - I would love to see that stat at 95%, not 45%, and think agile + UX is a pragmatic path through. It is so inefficient trying to optimise web journeys using site analytics, in splendid isolation.

about 5 years ago

Rita Auta

Rita Auta, Marketing & Communications Manager at Activate Media

Thanks for your comments.

Richard: Yes, it can be fast- but if the testing troughs up any significant issues, it will take a whole cycle to get it changed, as significant changes need to be approved by the customer as well. But it's much better option than doing the full development and then figuring out people can't actually use it.

Nichola: agreed! Hopefully in time with awareness we'll be seeing the stats improve.

about 5 years ago


Deri Jones, CEO at SciVisum Ltd


> It is so inefficient trying to optimise web journeys using site analytics, in splendid isolation.

Yup, all too often that 'splended isolation' is the norm.

Marketers... UX guys... and under-pinning everything, Tech guys that control the technology and therefore ultimately the varying speed of each journey on the site too.

about 5 years ago

Save or Cancel

Enjoying this article?

Get more just like this, delivered to your inbox.

Keep up to date with the latest analysis, inspiration and learning from the Econsultancy blog with our free Digital Pulse newsletter. You will receive a hand-picked digest of the latest and greatest articles, as well as snippets of new market data, best practice guides and trends research.