We stand with Ukraine and our team members from Ukraine.

The Community Of Over 578,000

Home ›› Business Value and ROI ›› 6 Key Questions to Guide International UX Research ›› small_16 ›› So Agile Together: How designers and programmers can join forces to create great experiences

So Agile Together: How designers and programmers can join forces to create great experiences

by Andrew Wagner
Share this post on
Share on twitter
Tweet
Share on linkedin
Share
Share on facebook
Post
Share on reddit
Share
Share on email
Email
Share on print
Print

Save

By finding common ground and learning from one another, UX designers and programmers can forge better environments for agile software development.

Earlier this year, I attended a UX meetup that featured a panel discussing whether or not integrating UX designers into the agile software practice works.

I noticed during the discussion that the panelists made strong distinctions between “developers” and UX designers.

While this is commonplace, it stood out to me because I’m primarily working on the development side as a programmer, but I have an interest and background in user experience. I realize the need in larger organizations to hire for specific positions, but I think that as long as we maintain these distinctions, UX designers will not be able to effectively work within the agile software process. I also think the skill sets and aptitude for programmers and UX designers have significant overlap.

Common Ground

One of the principles listed on agilemanifesto.org is that, “Continuous attention to technical excellence and good design enhances agility.” This means that programmers must work on a daily basis with designers. If designers simply hand over designs for the programmers to implement, design considerations are more likely to be left by the wayside as technical challenges arise.

People work much better together when they can find common ground. By recognizing that the similarities between designers and programmers greatly outweigh their differences, we can all learn to work more effectively together on a daily basis.

Attention to Detail

Both developers and designers must be very detailed oriented and thorough. UX designers must consider all edge cases and possible motivations in order to shape a user’s experience. Programmers have to predict all of the little things that can go wrong and account for them to prevent bugs.

Empathetic by Nature

Both must be able to place themselves into the shoes of others. UX designers must be able to empathize with various personas to analyze the experience they will have. Programmers always have to empathize with one another in order to make sure that the code they write is understandable and maintainable by others.

Creative

Both must be very creative. UX designers have to find new and innovative ways to combine, update, and tweak existing UX paradigms to fit new use cases. Programmers must always devise new architectures and patterns to get tasks completed faster and make better, more efficient, and more stable programs.

Techies

One stereotypical difference between UX designers and programmers is that UX designers are more people-oriented and programmers are more technically oriented. However, UX designers in tech companies are technical. They are surrounded by technology all the time. They use technology to get their jobs done and they are often creating technology themselves—some even learn to program.

Similarly, programmers look at technology from a user-centered position. Many are constantly helping friends and family use technology and learn to appreciate UX design. Programmers are extremely proficient at recognizing patterns and they can spot UX that works and UX that doesn’t.

Come Together

By recognizing these similarities, UX design can move from being a precursor to programming to an integrated part of the development process allowing for better iteration on both the technical aspects and the design.

UX designers will still be the experts on user experience and will be the ones innovating the interface, but they will do it alongside the programmers instead of in their own world. Programmers can be evaluating the interfaces based on the patterns they see every day and technical issues can be addressed earlier. UX designers will still lead the research but programmers will greatly benefit from seeing some of the research first-hand.

Everyone can be on the same page about the importance of each change. Most importantly, by better integrating our prototyping and development processes, programmers can help designers iterate early on in the development cycle and designers can continue to iterate the UX until the end of development because programmers will be more invested in it.

Conclusion

I hope that one day we can all be considered “developers” and the difference between a UX person and a front-end programmer is no greater than a front-end programmer and a back-end programmer. As a programmer, I would love to learn more from UX designers and I would love to teach them more about programing.

We can all benefit from a more fluid and agile UX development process. UX cannot be developed completely before the developers see it because UX is never a static thing. Users, environments, and use cases are all constantly changing. We need to be able to iterate the usability of the application throughout the entire development process and it cannot stop at the 1.0 release. The usability iteration must continue as long as the product is being maintained. If we do all of the UX first, it will be much more challenging to iterate on it later.

I think that the best way we can move toward a more cohesive, agile development process that includes both UX designers and programmers is to stop seeing our roles as so different. UX designers and programmers can each learn skills from one another and support an overall product iteration that includes UX at its core.

 

Image of peas and carrots courtesy Shutterstock

post authorAndrew Wagner

Andrew Wagner, Andrew Wagner tries to bridge the gap between programmer and UX designer. He has worked primarily in programming roles but has always contributed to the UX conversation. He currently works as a developer and consultant for Chronos Interactive, a development shop focusing on both websites and mobile apps. He also developes his own apps as Learn Brigade, LLC His current apps include:

  • Notecards - Study using virtual note cards, anywhere, anytime
  • Busy Bee Cafe - Contract app for a Cafe / Restaurant / Bar in Raleigh, North Carolina. It allows patrons to look up the current menus, events, articles, and updates.
Before starting Chronos Interacttve, Andrew worked as an independent developer as Drewag, LLC and at a startup called ShowMobile located in Denver, CO as the lead iOS developer. He also worked at Garmin developing Speech Recognition. There he brainstormed and implemented new types of speech interaction with Garmin's navigation devices.

Share on twitter
Tweet
Share on linkedin
Share
Share on facebook
Post
Share on reddit
Share
Share on email
Email
Share on print
Print

Related Articles

Artificial intelligence (AI) could soon surpass human intelligence. Having both advantages and disadvantages, it still creates powerful opportunities and produces more accurate customer-behavior models.

Time to reflect on my future in the age of AI
  • Since AI-driven processes can create powerful opportunities to improve producing more accurate customer-behavior models, many traditional businesses will soon transform their core processes and business models to take advantage of ML.
  • Sonia P., People-Centric Design Enthusiast, brigs up such questions related to the role of AI in the future:
    • What’s exciting about AI?
    • What’s worrying?
    • How will we work with machines?
  • In order to make machines that behave better for humans is for UX designers to take all factors into considerations, bridge the gap and merge the knowledge from all sides to define the best solution.
Share:Time to reflect on my future in the age of AI
Time-to-reflect-my-future-in-the-age-of-AI.-article-image.png

There are numerous qualitative methods with students as users. Finding the right AAC system and implementing it effectively is essential to give every student access to communication.

How I Use UX Research in Speech Therapy
  • Kate Paolini, UX Researcher, and Speech-Language Pathologist digs deeper into how her students using augmentative and alternative communication (AAC) can benefit from a UX research approach.
  • Communication is much more than speech; therefore, finding the right AAC system and implementing it effectively is essential to give every student access to communication.
  • Kate Paolini conducted the research with the help of the following methods:
    • Buy-In & Initial Methods
    • Designing the AAC System for the User
    • Access & Education
    • Observations & Data Tracking
    • Heuristic Evaluation
    • Assess, Adapt, Repeat
Share:How I Use UX Research in Speech Therapy

This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and