# Experiential Design Published articles for Experiential Design. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Design Process and Agile Development: Part 1 -- Design Is Collaborative DevFeed: [The Design Process and Agile Development: Part 1 -- Design Is Collaborative]() Original publisher: [Read original article]() Author: Daisy Mølving Published: 2026-02-05T06:00:00Z Content type: opinion Language: en Sources: [8th Light Insights]() Topics: [Agile](), [User experience (UX)](), [Development](), [Self-organizing Team]() Tags: [agile](), [delivery-and-practice](), [design-thinking](), [development](), [development-process](), [experiential-design](), [product-strategy-innovation](), [research](), [teams](), [user-experience](), [ux-design]() ### AI overview Part 1 of a series examines how design thinking and UX research can work alongside Agile development. It argues that iterative design and Agile delivery are compatible, while noting the tension between research needs, rapid timelines, client goals, and incremental development. ### Source excerpt This is Part 1 in our blog series on how the design process works alongside Agile methodology to produce results within an integrated team. Updated 2/5/2026. Originally published 2/2/2024 When it comes to developing new software, not every designer approaches the task the same way. While some use a design thinking approach, looking at the tasks from a user perspective, others use Agile methods, approaching it from an iterative project management standpoint. However, the two approaches are not mutually exclusive. The most successful designers approach their tasks using design thinking which helps inform prioritization within the Agile methodology. High performing teams delivering outcomes through the agile methodology do so with confidence when they know solutions are informed by the voice of the user. Working with Design Thinking and Agile Timelines Designers who've worked alongside Agile methodologies have likely felt the pressure of Agile timelines conflicting with the need for comprehensive design. While the approaches may feel conflicting at first, it's important to remember that both design and Agile methodologies emphasize the importance of working in small iterations to develop products that constantly evolve-- focusing on the smallest modifications that lead to making valuable products and building upon them. However, with its need for preliminary research, I've observed that user experience (UX) design can give Agile practitioners the impression of a waterfall process. Agile teams want to deliver quickly and continue iterating on the project after receiving feedback. As a UX designer, it is my responsibility to establish and fulfil the human need by talking to some users and conducting competitor research before we dive blindly into development. Working as a UX designer in this environment can feel like you're stuck between a rock and a hard place. You have a client who cares about the bottom line and wants to get to market quickly and a development team of ## The Design Process and Agile Development: Part 2 -- Collaborative Activities DevFeed: [The Design Process and Agile Development: Part 2 -- Collaborative Activities]() Original publisher: [Read original article]() Author: Daisy Mølving Published: 2026-01-16T06:00:00Z Content type: tutorial Language: en Sources: [8th Light Insights]() Topics: [Agile](), [User experience (UX)](), [Development](), [Software Engineering](), [Testing]() Tags: [agile](), [continuous-integration](), [design](), [development](), [experiential-design](), [teams](), [testing](), [user-experience]() ### AI overview This article explains how UX designers, product owners, and software developers can collaborate during an agile design process. It focuses on continuous discovery through stakeholder interviews, competitive and analogous research, user interviews, testing, and collaboration with developers on codebase, infrastructure, feasibility, and timelines. ### Source excerpt Updated 1/16/2026. Originally published 12/10/2024 As we talked about in Part 1 of this blog series, The Design Process and Agile Development: Part 1 -- Design Is Collaborative, the design process provides teams with the opportunity to join forces, paving the way for an integrated team of user experience (UX) designers, product owners, and agile software development to create a successful product. So where do you begin? You have a new project and an integrated team. You know that success can be achieved in close collaboration between your team members, each representing deep expertise in desirability, viability, and feasibility. But you need to determine which activities are most profitable for the team to put their heads together on and what their responsibilities should be. Find Out Together Finding Out is where it all starts, but it most certainly doesn't only happen at the start! We 'find out' in continuous cycles throughout the project, not just from our users, but also from our stakeholders and product and development teammates. After all, though the end product is ultimately for our end users, design is also influenced by viability, or the business, and feasibility, or the developers. So it makes sense to 'find out' collaboratively. You can do this through stakeholder interviews, competitive analysis and analogous research, user interviews and testing, and continuous integration (CI) tools. Stakeholder Interviews Stakeholder interviews are an early, integral step for determining what your stakeholders care about -- their hopes and fears, past project experiences that might drive their decision-making, key metrics they need to hit, and any assumptions they may have. Not only will you build rapport, you'll also learn how to engage your stakeholders through the design process. I've experienced that not all stakeholders have immediate faith in design, so understanding how they measure success and engaging with their success criteria throughout your work can be cruc ## Using Viability and Feasibility to Guide Ambiguous Design Projects DevFeed: [Using Viability and Feasibility to Guide Ambiguous Design Projects]() Original publisher: [Read original article]() Author: Agustin Sanchez Published: 2025-07-25T05:00:00Z Content type: article Language: en Sources: [8th Light Insights]() Topics: [iteration](), [Testing](), [Users]() Tags: [experiential-design](), [experiment](), [human-centered-design](), [iteration](), [onboarding](), [value]() ### AI overview This article presents human-centered design as a way to navigate ambiguous projects. It explains how defining business objectives and measurable outcomes establishes viability, while testing ideas early and iterating helps assess feasibility and reduce risk. ### Source excerpt Updated 7/25/2025. Originally published 12/10/2024 Ambiguity in design isn't a roadblock -- it's an opportunity. Design ingenuity thrives in the gray area where rules haven't been written, and solutions are waiting to be discovered. So how do you turn "I have no idea where to start" into breakthrough ideas that actually work? At 8th Light, our approach is anchored in the three pillars of human-centered design: viability, feasibility, and desirability. These are the tools that transform chaos into clarity and make ambiguity your ally, not your enemy. Viability: Define Your Destination Before Picking the Route The truth is, you don't need to know the "how" right away. However, you absolutely need to know the "why." Viability ensures your team stays aligned with business objectives, reducing costly detours and keeping your efforts focused on delivering measurable value. Picture this: You're tasked with fixing an outdated customer onboarding process. The details are vague, but the goal is crystal clear -- reduce the time it takes for new users to find value. Once you've mastered the "why," the rest becomes an experiment. Early setbacks are simply data points, guiding you toward smarter decisions. Viability keeps you aligned with business objectives, ensuring that every test and rapid iteration thereafter, serves a purpose. Pro tip: Start every ambiguous project with these two questions: What are we trying to achieve? Why does this matter? -> Takeaway: Before starting a project, define clear business objectives and measurable outcomes. Use these as your north star to guide every decision. Feasibility: Stop Guessing, Start Testing With your goals in place, it's time to embrace the unknown and start experimenting. Feasibility minimizes risk by validating ideas early, reducing the chance of expensive missteps, and accelerating your path to market-ready solutions, encouraging you to iterate effectively to reach the solution. It answers the question: Can we actually build this?