Published July 12, 2024

Agile Design Drives Continuous Improvement and User Satisfaction

13 min read

Combining design thinking with agile drives efficiency, encourages innovation, and enhances team collaboration.

An agile design process is a powerful approach that blends the iterative nature of agile development with the user-centered focus of design thinking. This combination drives efficiency, encourages innovation, and enhances team collaboration. In this post, we’ll explore how to create an agile design process, ensuring your products meet user needs and adapt quickly to changes.

Jiri Mcc recently shared his experience combining design thinking with agile practices to improve product design and delivery. His method supports creative teams in effectively handling diverse product and service propositions. 

He argues:

→ Design Thinking integrates human desirability, technical feasibility, and economic viability. It empowers non-designers to solve various problems using design tools and principles.

→ Dual-Track Agile divides work into two tracks: discovery and delivery. The discovery track involves research and prototype creation without technical constraints, focusing on validating ideas. The delivery track efficiently turns these validated ideas into production-ready software.

Understanding Agile Design

Agile design is more than just a methodology; it’s a mindset that combines the iterative nature of agile development with the user-centered focus of design thinking. This fusion helps teams rapidly adapt to changes, continuously improve their designs, and deliver products that meet user needs. By prioritizing flexibility, collaboration, and user feedback, agile design ensures that every product development stage is innovative and viable.

Agile Design Principles

  1. Flexibility: At the heart of agile design is the ability to adapt. Flexibility means being open to changes in requirements, even late in the development process. This principle ensures that the final product can evolve based on user feedback and new insights, rather than sticking rigidly to an initial plan.
  2. Collaboration: Agile design thrives on teamwork. It encourages cross-functional collaboration, bringing together designers, developers, marketers, and other stakeholders to work harmoniously. This collaborative approach fosters creativity and ensures that all perspectives are considered, leading to more well-rounded and effective solutions.
  3. User-Centricity: Understanding and prioritizing the user’s needs is paramount in agile design. By creating solutions that address real user problems, teams can deliver functional and highly satisfying products to the end-user. This user-centric approach is achieved through constant engagement with users, gathering feedback, and iterating on designs.

Dual-Track Agile helps teams balance the need for discovery with the need for delivery, ensuring that products are both innovative and viable.

Avatar of the person that wrote the post

Dalyn Ward 

VP Product

Planoly

Agile Design Thinking

This thinking integrates three crucial elements: human desirability, technical feasibility, and economic viability. This holistic approach ensures that the products developed are desirable and useful for users, feasible to build, and viable from a business perspective.

  1. Human Desirability: This aspect focuses on understanding what users want and need. It involves empathizing with users, gathering insights through research, and ensuring that the product addresses these insights effectively. By keeping human desirability at the forefront, teams can create products that resonate with their target audience.
  2. Technical Feasibility: While it’s essential to design products that users want, ensuring they can be built with the available technology is equally crucial. Agile design thinking encourages teams to prototype and test ideas quickly, validating technical feasibility early in the agile design process to avoid costly mistakes later.
  3. Economic Viability: For a product to be successful, it must make sense from a business standpoint. This means considering the cost of development, potential market size, pricing strategies, and overall return on investment. Agile design thinking helps teams balance these factors, ensuring that the products they develop are desirable, feasible, and financially viable.

By integrating these principles and elements, agile design empowers teams to create flexible, collaborative, and user-centered products. This approach enhances the quality of the final product and improves the efficiency and effectiveness of the entire design process.

The Dual-Track Agile Methodology

Dual-track agile separates the design and development processes into two parallel tracks: discovery and delivery. This approach ensures a continuous focus on both user research and product development.

Benefits of Dual-Track Agile:

  1. Transparency: Enhances collaboration and reduces ambiguity.
  2. Scalability: Supports scaling design operations by separating tracks.
  3. Time to Market: Accelerates product release by maintaining parallel focus.
  4. Lower Operational Costs: Validates ideas before they reach the backlog.
  5. Better Products: Enhances team empowerment and accountability.

Resources

Agile Design Resources

Check out these links on Dual-Track Agile, as Dylan Ward, Kevin Albrecht, and Jeff Patton emphasize the importance of integrating customer feedback in product development. Paulo Caroli’s Lean Inception and Adriana Katrandzhieva’s video further highlight the approach’s focus on discovery and delivering customer value.


Key Stages in the Agile Design Process

The agile design process is structured to ensure continuous improvement and adaptability. It encompasses several key stages that help teams empathize with users, define problems clearly, generate innovative ideas, prototype solutions, and test them with real users. Each stage is crucial in creating products that meet user needs and adapt to changes efficiently.

1. Empathize

Understanding user needs is the foundation of the agile design process. During this stage, teams employ various techniques to gather insights directly from users. These techniques include user interviews, surveys, and observational studies, which help understand user behaviors, pain points, and desires.

  • User-Centered Design: This approach ensures the design process revolves around the user’s needs and experiences. By keeping the user at the center, teams can create more relevant and effective solutions.
  • User Stories are short descriptions of a feature from the end user’s perspective. They help capture users’ requirements and expectations, clearly focusing on the design process.

Helio: Helio significantly enhances the empathize stage by offering robust user research tools that streamline the process of gathering user insights. With Helio, teams can quickly deploy user surveys and observational studies, making collecting and analyzing data easier. We ran one of these surveys to learn about Usage & Attitudes (U&A) patterns in an audience of male formal wear consumers in the US who prefer to shop online.

The goal was to understand what consumers currently have the most difficulty with when shopping for formal wear, to identify opportunities for a theoretical clothing brand:

Consumers indicated that they are least comfortable with sizing and matching accessories. Their follow-up responses then provided clarity for what consumers are feeling when thinking of making a purchase:

“I am not good with choosing the size that is best for me. The ones I choose are normally to big or make me look bigger.”

  • Male Formal Wear Online Shopper (US)

This type of U&A survey is the bread and butter of Helio. The platform’s intuitive interface allows teams to design and distribute surveys, track responses, and visualize data, ensuring that user feedback is at the forefront of the design process.

View the Helio Data Report

2. Define

After empathizing with users, the next stage is to define the problem that needs to be solved clearly. This stage involves synthesizing the information gathered during the empathize stage to create a clear problem statement. Defining the problem accurately ensures that the team is addressing the right issues.

  • Design Collaboration: Collaboration among team members is essential to accurately defining problems. By working together, team members can share different perspectives and insights, leading to a more comprehensive understanding of the problem.
  • Agile Workflow: An agile workflow helps break down the problem into manageable tasks. It allows teams to prioritize and tackle the most critical aspects first, ensuring steady progress towards solving the problem.

Helio supports the define stage by facilitating seamless design collaboration across teams. Using the data collected in the Empathize stage, you can provide validation (or invalidation) for different opportunities the team brings.

Opportunity Index Method

Using an Opportunity Index method, you can combine these data signals with input from business and tech stakeholders on your team to produce a clearly defined and prioritized list of opportunities to pursue. We used this research method on the same data collected above on online formal wear consumers to provide a ranked index of ideas for a theoretical brand to execute on.

We started by gathering a list of feature ideas for a mobile clothing app, such as personal online style experts, push-to-store options to try on clothes in person, and outfit suggestions for events.  

These ideas were listed in the Opportunity Index framework, with areas for the team to expand on what problem each concept is solving, why it’s important, and how it can benefit the business.

The data collected from the user surveys in the Empathize phase is entered next to each feature idea, and the value of that idea is translated into a 1 – 5 rating based on how important it would be to a Getup user. For instance, sizing was revealed as the least comfortable aspect for suit purchasers the testing above, so an opportunity that speaks to helping consumers with sizing would be rated a 5/5.

The data observation supporting each user rating is listed to the right, and a link leads to the raw data.

Rating each Opportunity

Now, with a user rating for each opportunity, the Biz and Tech ratings could also be applied to each idea based on input from the Getup team. Engineering stakeholders on the team rated the technical feasibility of each idea on a 1 – 5 scale (5 being easiest), and the project’s key stakeholders gave input on the Business value on a 1 – 5 scale. 

The final total out of 15 is evaluated for each opportunity, with the highest-ranking opportunities representing a combination of importance to the business and users and simplicity to build from a technical standpoint.

With a fully fleshed-out and user-validated list of product opportunities ranked by priority, teams can now define exactly what ideas they should pursue that should produce the highest return on investment for their business.

View the Opportunity Index Case Study

3. Ideate

The ideate stage is where creativity flourishes. During this stage, teams brainstorm and generate various ideas to solve the defined problem. Encouraging diverse perspectives and collaborative brainstorming sessions leads to innovative and effective solutions.

  • Design Thinking: This methodology encourages creative problem-solving and innovation. It involves generating multiple ideas, exploring various possibilities, and selecting the most promising ones for further development.
  • Collaborative Design: Collaboration during ideation ensures that all team members contribute their unique perspectives. This collective effort results in more innovative and well-rounded solutions.

Helio helps produce a prioritized list of ideas to execute in the Define phase. Now, with ideation on the table, the team can move forward with their highest-ranked opportunities and quickly iterate on multiple versions.

For example, a highly ranked opportunity on Indiana University’s redesigned website was improving the experience of their degree index page, where visitors search for the degree they want to pursue.

One of the team’s ideas was prioritizing how features are displayed on the degree listing page rather than maintaining the current alphabetical order.

Encouraging Exploration

The Indiana University team’s goal was to encourage the exploration of different degrees on the index page and increase engagement with 10 of their key school programs. 

One hundred participants from IU’s audience of undergrad and grad students interacted with each version of the page, answering the same questions to compare their responses across variations. Once the data had been collected, the responses were copied into a data comparison framework for quick design evaluation.

Once the data had been collected and loaded into the comparison framework, the picture of how users reacted to each different version became more clear:

In the current page version, with the degrees in alphabetical order, only 7% of participants engaged with the list, instead opting to go directly to the filters and search bar. 

When the degrees list was reorganized to show featured degrees up top, engagement with the list jumped to 19-24%, showing a desire to interact with the page rather than resort to the search features.

The versions where we tried highlights in the degrees list both reduced satisfaction with the look of the page (V2) and reduced engagement when hidden under a dropdown (V3). The team moved forward by reordering the degree list without adding visual highlights.

Experimentation like this in the Ideate phase helps launch teams past typical collaboration woes. It addresses differing opinions and provides hard data and signals to inform the team’s decision-making.

View the Idea Validation Case Study

4. Prototype

Prototyping involves creating simple, tangible representations of the ideas generated during the ideate stage. These prototypes help teams explore potential solutions quickly and cost-effectively. Prototyping allows teams to visualize ideas and gather early feedback.

  • Design Prototyping: Prototyping tools and techniques enable teams to create functional models of their ideas. These models help explore different design options and test their feasibility.
  • Iterative Design: Iteration is a core principle of agile design. By continuously refining and improving prototypes based on feedback, teams can develop more effective and user-friendly solutions.

Helio provides powerful prototyping testing tools that allow teams to quickly test functional models of their ideas. The platform supports testing interactive Figma prototypes that can be shared with users for feedback. 

For example, Indiana University aimed to enhance the user experience on its homepage by determining which visual elements most positively influenced user impressions and satisfaction. To create this effective homepage, the Indiana University team hypothesized that animating their city’s skyline on the page would better align with their desired brand impressions.

Figma Prototyping

The team placed each version of the homepage into a Figma prototype to showcase its animated aspects, allowing participants to experience the animations in an interactive environment. After interacting with the Figma prototype, we asked participants a series of evaluative questions to compare satisfaction and brand impressions across the three versions.

Our team presented three homepage variations to users:

  • Simple, no skyline: Basic design without any background imagery.
  • Skyline V1: Features the city skyline during the day as a background.
  • Skyline V2: Incorporates a vibrant evening city skyline with prominent university branding.

We randomly assigned participants to review one of the three versions and they provided feedback on their satisfaction and overall impression of the page.

We quickly copied the data from the Indiana University skyline testing from each separate Helio test into the framework below:

Positive Participant Feedback

This side-by-side view quickly reveals which variations received the most positive participant feedback. Brand impressions such as Impact, Discovery, and Innovation increased compared to version 1. Skyline version 2’s net positive alignment (total positive impressions minus total negative impressions) was much greater than the other versions. Combined with the higher satisfaction, the IU team confidently moved forward with their plans for an animated skyline on the homepage.

Helio’s user testing capabilities enable teams to gather insights on their prototypes, ensuring that they can refine and improve their designs iteratively. This accelerates the prototyping process and helps teams develop more effective solutions.

View the Prototype Testing Case Study

5. Test

The testing stage is critical for validating the effectiveness of the prototypes. By testing prototypes with real users, teams can gather valuable feedback and identify areas for improvement. Continuous testing and refinement ensure that the final product meets user needs and expectations.

  • Agile Development: Agile development methodologies support the iterative testing process. By breaking down the development into small, manageable increments, teams can systematically test and refine each component.
  • Continuous Improvement: This principle emphasizes the importance of ongoing refinement and enhancement. By continuously testing and improving the design, teams can ensure that the final product is of the highest quality and meets user needs.

Helio provides user feedback throughout the agile process and excels in the testing stage with its comprehensive user testing tools. The prototyping tools we discussed above also provide detailed usability metrics about how users navigate the flow.

Prototype of an ad management platform

For example, we tested a prototype of a theoretical ad management platform called Advent, which allows users to adjust the audience targeting parameters of their ad campaigns.

This Advent prototype data revealed that up to 13% of participants were unsuccessful at editing their target audience. Most of these failures occurred on the very first step, indicating that the initial action of finding the specific audience demographic information on the page was complex for users.

This usability data can be combined with evaluative questions that paint how a participant navigates a product and feels about that experience.

“there was a lot of information on the page. It took me a second to find the right group as they were not in an order I recognized. I then needed to find the correct line to edit with income; this did not match up with a previous line with a different income level. So it took me a few seconds to find the correct line.”

  • Small Business Advertiser (US)

Our recommendation for future iterations of Advent’s audience page would be to emphasize top-level demographics on the page that users may gravitate towards more often, such as age and location, to improve the usability for those key actions.

Using Helio

Teams can easily set up user tests, gather real-time feedback, and analyze results within the platform. Helio’s advanced reporting helps identify critical areas for improvement, enabling continuous refinement of the prototypes. This ensures the final product is optimized to meet user needs and expectations, enhancing overall product quality and user satisfaction.

View the Advent Prototype Survey!

By following these key stages in the agile design process, teams can create innovative, user-centric, adaptable, and efficient products. This structured yet flexible approach ensures that every stage of product development is focused on delivering the best possible outcomes for users.

Best Practices for Implementing an Agile Design Process

Implementing an agile design process requires a strategic approach focusing on collaboration, continuous feedback, and adaptability. By following best practices and overcoming common challenges, teams can create innovative products aligned with user needs and business goals.

To ensure the success of your agile design process, consider these key tips:

  • Cross-Functional Teams: Foster collaboration across different disciplines. Bringing together designers, developers, marketers, and other stakeholders helps ensure that all perspectives are considered, leading to more holistic and effective solutions.
  • Regular Check-Ins: Maintain frequent touchpoints to review progress and adjust as needed. Regular check-ins help keep the team aligned, identify issues early, and ensure that the project stays on track.
  • User Feedback: Continuously incorporate user feedback to refine ideas. Engaging with users throughout the design process ensures that the product remains user-centered and meets their needs effectively.

Dual-Track Development emphasizes the importance of integrating customer feedback throughout the process, ensuring that the end product truly meets user needs.

Avatar of the person that wrote the post

Jeff Patton 

Chief Troublemaker

Jeff Patton Associates

Overcoming Common Challenges in Agile Design

While agile design offers many benefits, it also presents certain challenges. Common obstacles include managing dependencies and ensuring team alignment. Here are some strategies to overcome these challenges:

  • Dependency Management: Clearly define roles and responsibilities within the team. By establishing clear boundaries and expectations, teams can avoid confusion and ensure that everyone understands their contributions to the project.
  • Team Alignment: Communicate goals and progress regularly to keep everyone on the same page. Consistent communication helps align the team’s efforts with the project’s objectives and ensures that all members quickly share and understand any changes.

By integrating these best practices and addressing common challenges, teams can enhance their agile design process, resulting in innovative and user-focused products. Utilizing tools like Helio further strengthens this approach by providing robust user research and testing capabilities, streamlining collaboration, and ensuring continuous improvement throughout the design process.

Agile Design FAQ

What is agile design?
Caret signaling that you can click it to open the dropdown

Agile design is a methodology that combines the iterative nature of agile development with the user-centered focus of design thinking. This approach prioritizes flexibility, collaboration, and user feedback, allowing teams to adapt quickly to changes, continuously improve their designs, and effectively create products that meet user needs.


How does agile design differ from traditional design methodologies?
Caret signaling that you can click it to open the dropdown

Agile design differs from traditional design methodologies by emphasizing iterative development, continuous user feedback, and cross-functional collaboration. While traditional methods often follow a linear process, agile design allows for ongoing refinement and adaptation, ensuring that products evolve based on real-time user insights and changing requirements.


What are the core principles of agile design?
Caret signaling that you can click it to open the dropdown

The core principles of agile design include flexibility, collaboration, and user-centricity. Flexibility ensures the ability to adapt to changes, collaboration fosters teamwork across different disciplines, and user-centricity focuses on creating solutions that address real user problems, enhancing the overall user experience.


What is the dual-track agile methodology?
Caret signaling that you can click it to open the dropdown

The dual-track agile methodology separates the design and development processes into two parallel tracks: discovery and delivery. The discovery track focuses on user research and prototype creation, while the delivery track turns validated ideas into production-ready software. This approach enhances transparency, scalability, time to market, and product quality.


How can Helio enhance the agile design process?
Caret signaling that you can click it to open the dropdown

Helio.app enhances the agile design process by providing robust tools for user research, collaboration, and testing. It streamlines the gathering of user insights, facilitates real-time collaboration among team members, and supports iterative prototyping and testing. This ensures continuous improvement and alignment with user needs throughout the design process.


What are some best practices for implementing agile design?
Caret signaling that you can click it to open the dropdown

Best practices for implementing agile design include fostering cross-functional teams, maintaining regular check-ins, and continuously incorporating user feedback. Cross-functional teams ensure diverse perspectives and holistic solutions, regular check-ins keep the team aligned and identify issues early, and ongoing user feedback helps refine ideas to meet user needs effectively.


How can teams overcome common challenges in agile design?
Caret signaling that you can click it to open the dropdown

Teams can overcome common challenges in agile design by clearly defining roles and responsibilities to manage dependencies and regularly communicating goals and progress to ensure team alignment. Establishing clear boundaries and expectations prevents confusion, and consistent communication keeps everyone on the same page, facilitating a smooth and efficient design process.


Build something your users truly want