Ep 24 Methodologies: How to make agile methodologies work with your design process

Show notes

Welcome & Housekeeping

Host Introduction:

• Stephen Gates welcomes listeners to episode 24 of The Crazy One podcast.

• The show explores creativity, leadership, design, and challenges that matter to creative professionals.

 

Why There Was No Episode Last Week:

• Stephen spent Thanksgiving in Europe and was too jetlagged to produce a quality episode upon returning.

• He apologizes for the unexpected break.

 

Community Announcement:

• A new Facebook page has been created for The Crazy One Podcast to foster open discussion.

• Listeners are encouraged to like the page, ask questions, and participate in building a community.

 

Milestone Update:

• The episode following Stephen’s Adobe MAX talk received tremendous support.

• The podcast hit 15,000 downloads and entered the Top 5 Design Podcasts on iTunes.

• Stephen expresses deep gratitude to the community for their support and contributions.

 

---

 

Main Topic: Making Design and Creativity Work with Agile

1.  What Is Agile?

 

Definition:

• Agile is a methodology for software development that emphasizes iterative progress through collaboration.

• Stephen quotes Wikipedia: Agile involves collaborative, cross-functional teams that work in short, focused periods called “sprints.”

 

Agile vs. Waterfall:

• Traditional (“waterfall”) development flows linearly from strategy to design to development.

• Agile favors breaking work into smaller chunks with fast feedback loops.

 

Benefits:

• Agile encourages collaboration, adaptability, and continuous improvement.

• It aligns with the core principles of creativity and design thinking.

 

Core Challenge:

• Agile was designed for software development, not creative processes.

• Creative work often gets squeezed by Agile’s fast, iterative delivery focus.

 

---

 

2.  The Most Common Problems Creatives Face with Agile

 

Problem 1: Too Delivery-Focused

• Creatives feel overwhelmed in short sprints, leaving little time for deep ideation.

• Conceptual design often takes a back seat to fast-paced production demands.

 

Problem 2: Misalignment in Resourcing

• Agile requires fully dedicated team members, unlike waterfall, where people float across projects.

• This shift strains creative teams who aren’t staffed to embed designers per team.

 

Problem 3: Leadership Mismatch

• Leaders often want Agile implementation but retain waterfall approval processes.

• Creatives are caught between sprint demands and executive reviews.

 

Problem 4: No Shared Blueprint

• Agile promotes completing one feature before starting another.

• Without a comprehensive vision or “blueprint,” teams risk creating disjointed, inconsistent user experiences.

 

Problem 5: Sprint Synchronization Challenges

• Designers must work 2–3 sprints ahead of development to avoid delays.

• If stakeholders don’t review early design work carefully, issues go unnoticed until it’s too late.

 

Problem 6: Research Doesn’t Fit Sprint Timelines

• Research and testing often don’t return results fast enough for sprint cycles.

• Designers risk going “data blind” or overreacting to delayed insights.

 

Problem 7: Resistance to Change Among Stakeholders

• Agile requires buy-in from everyone, including product and business leaders.

• Many resist Agile’s ambiguity and relinquishing control, stalling collaboration.

 

Problem 8: Iteration Works Best Post-Launch

• Iteration is ideal for improving live products.

• For net-new products, Agile can feel incompatible without space for upfront invention and big thinking.

 

Notable Insight:

• Even companies like Facebook shifted from “Move fast and break things” to “Slow down and fix your shit,” reflecting the evolving reality of maturing processes.

 

---

 

3.  How to Make Agile Work for Creatives

 

Solution 1: Introduce a Sprint Zero or Design Sprint

• Dedicate time before Agile work begins to create the concept, blueprint, or Northstar vision.

• Ensures creative clarity and provides something tangible for stakeholders.

• Helps bridge the gap between Agile’s speed and design’s need for conceptual depth.

 

Solution 2: Sell the Vision First, Then Build Realistically

• Don’t just design what tech can build—dream bigger.

• Show the ideal, then scale it back for implementation.

• This elevates the perception of the design team and aligns long-term goals.

 

Solution 3: Communication is Everything

• Hold daily standups to share progress, blockers, and maintain alignment.

• Replace scattered meetings with a weekly multi-team design review.

  • Invite all decision-makers.

  • Focus on progress and unblock teams with quick decisions.

   

 

Solution 4: Preserve the Big Picture

• Assign someone (or a few) to oversee the full experience across all teams.

• Use app maps or master blueprints to guide individual scrums.

• Allow scrum teams to “decorate their room” but dictate where each room fits.

 

Solution 5: Establish a Common Design Language

• Build atomic design systems and pattern libraries.

• Ensure consistency in interaction and design across the entire product.

 

Tease: The next episode will dive deeper into atomic design systems.

---

 

Final Thoughts

 

Evolve Your Process:

• Agile, waterfall, or hybrid—every team must evolve its process.

• Process should never be so rigid that it stifles growth, creativity, or collaboration.

• Leadership and teams must regularly evaluate and adapt workflows.

 

Closing Message:

• Stephen reminds listeners that process is a living thing—it should grow with your team, not restrict it.

• Encourage open conversation about what works and what needs to change.

 

---

 

Outro

• If you enjoyed the episode, leave a review on iTunes. It’s the only currency Stephen asks for.

• Show notes, articles, and additional resources are available at podcast.stephengates.com.

• Join the new Crazy One Podcast Facebook page to ask questions and share insights.

• A quick legal reminder: All views are Stephen’s own and do not represent any employer.

• As always, Stephen thanks listeners for their time, calling it the most valuable luxury we have.

 

Until next time: Stay crazy.

Tagged as:
agile integration agile methodologies agile practices creative teams design challenges design process design workflows fostering creativity iterative design overcoming obstacles software methodology Stephen Gates teamwor The Crazy One podcast