Design better experiences Get started free
InVision Enterprise Learn more
The world's smartest companies use InVision

The world's smartest companies use InVision Enterprise Edition

UI/UX

The lifecycle approach to UX design

by

on

View all posts

Much has been said of the agile lifecycle. We all know it: discover, design, develop, test, iterate, repeat.

Some project managers even repeat the process in their sleep. There are tons of well-known reasons to run an agile lifecycle on a project.

Image: Wikimedia Commons.

Image: Wikimedia Commons.

The most obvious reason: efficiency. Every leg of the journey is clearly defined, and each member of the team knows their role. The caveat? User experience bleeds into every part of the process, unbeknownst to many patrons of the profession.

User experience is a part of everything

For the skeptics who think that development is independent of UX, here’s the thing: the work of a UX designer is almost never complete—especially once the project enters the development phase.

Visual designers, developers, and QA specialists exist solely to realize the vision of the UX designer. So it’s imperative that UX designers maintain an active role in every forthcoming leg of the project lifecycle.

“User experience is a part of everything.”

If you’re asking yourself why it’s the UX designer’s responsibility to ensure that everyone else does their job, you’re asking the right question. Let me explain why.

Development choices have an effect on user experience

There are a number of choices that a developer can make as they work on a project that may adversely affect the usability of a website. These choices can relate to performance, programming language preference, and accessibility, to name a few.

If, for example, the developers have opted to use a front-end framework with a number of default grids, such as Foundation by Zurb, then it’s imperative that they match the the usability requirements determined by the UX designer.

Zurb Foundation Grid.

Zurb Foundation Grid.

In the above image, the sidebar has been allocated columns 9-12. It seems like a natural choice for the developer, but it could pose a number of usability challenges that only a UX designer would catch.

Other decisions, like ones that affect performance, also affect usability. So it’s up to the UX designer to ensure that any decisions that affect performance stay within the realm of their vision.

If a page fails to load within the time deemed acceptable by the UX designer, then it’s not usable. Deeper still, if particular assets, such as images and dynamic animations don’t function/load smoothly, they can also be a detriment to usability.

On the other hand, an implementation such as lazy loading, which aims to help pages load more quickly, can also negatively impact the usability of a page. Whether it does can only be determined by the visionary UX designer.

Agency website with lazy loading.

Agency website with lazy loading.

In the above example of an agency website with lazy loading, check out how the elements under “We Do Digital + Brand” haven’t loaded yet, even though the user has scrolled a good deal below it.

If this is consistent with the vision of the UX designer, then lazy loading would be an example of a development choice being beneficial.

But if the UX designer is less than excited about the fact that it takes an additional second for every new element to load as you scroll, then the implementation can be deemed detrimental to the usability of the page.

Collaboration among teams is vital

How does the UX designer ensure that the finished product is as close to their vision as possible? The key is collaboration. Effective collaboration is not only mission-critical, but also well within reach—even for the busiest of UX designers.

There are 3 ways to achieve effective collaboration:

1. Set up communication waypoints
Waypoints are predetermined times at which the primary UX designer ought to meet with the development team to make sure that the choices they have made are within the scope of the UX vision.

How to do it
First, determine the length of each sprint, and the amount of time it’ll take for the development team to build out each module. This information can usually be acquired from the project manager, who is used to working with timelines and feature build-outs.

Next, establish a review calendar of sorts, and set specific meeting times so that you can examine the work that’s been done on the project so far. Every time you meet with the development team, find out what features they’ve built out and the potential limitations of their work.

2. Define any benchmarks
Benchmarks are descriptors, both quantitative and qualitative, which aid in the implementation of a particular vision. Because benchmarks can be met in a variety of ways, UX designers should review benchmarks at each waypoint meeting.

How to do it
Before you can present the development team with usability benchmarks, you have to first determine what needs to be benchmarked. This can be done as you go through the process of crafting the user experience.

Next, you have to determine how each benchmark will be measured. If there are image-heavy elements above the fold that are essential to the experience, define an acceptable load time for the page, and take note of it for yourself.

3. Use something like Google Drive
Collaborative workspaces like Google Drive are extremely effective in keeping everybody up-to-date with everyone else’s work. Because of the way they work, collaborative tools can eliminate miscommunication and reduce the amount of “catching up” that needs to be done during the waypoint meetings.

lifecycle-03

How to do it
Create a master document for all relevant information, then share it with everyone. I mean everyone—the developers, the UX team, the project manager, even the client(s). The result is total transparency for everyone involved in the project.

Take charge

UX designers: don’t be afraid to be decisive and tell the developers when they aren’t adhering to the usability guidelines made available to them. Involve yourself in every leg of the software development lifecycle, and remain vigilant—you never know when a developer will do something without documenting it.

Author

Yona Gidalevitz
Yona is Codal’s technical researcher. At Codal, he is responsible for content strategy, documentation, blogging, and editing. He works closely with Codal’s UX, development, marketing, and administrative teams to produce all manner of written content. You can check out his work on Codal’s blog, Medgadget’s blog, and Usability Geek. In his free time, Yona is an avid guitarist, cook, and traveler.

Join over 1 million designers

Who get our content first.

No sales pitches, no games, and one-click unsubscribe.

Over 1 million designers
get our newsletter
every week

Find out why

Get awesome design content in your inbox every week

Just like over 1 million of your fellow designers do.

Plus get 3 free downloads, just for signing up.

Give it a try—it only takes a click to unsubscribe.

Thanks for signing up!

You should have a thank you gift in your inbox now—and you'll hear from us again soon!

Prototype better experiences with InVision

Just like over 1 million of your fellow designers do.

I agree to InVision's Terms of Service.

Want a free t-shirt?

Join the 1 million+ designers who get our newsletter weekly for your chance to win!

We hate spam as much as you do, and you can unsubscribe anytime.

Double your chances to win!

Tweet and automatically get a second entry

Tweet Now

No Thanks

Stay in touch!

We share news, freebies, and more on Twitter.