Every Feature Can Be Broken Down into Separate Releases

I'm sure you've seen the picture from Henrik kniberg depicting the iterative development showing a skateboard, bicycle and then a car. The theory made sense to me but whenever I was faced with a project I couldn't figure out how to apply it. The solution only worked when all of the pieces were in place - half the solution just wouldn't work at all.

The problem twofold. First, I didn't really understand the customer needs. I was just reading the requirements and everything was mandatory. Second, I was so used to breaking down software into components that was the only way I knew.

As I learned more, new objections would arise - it cost's more to do multiple releases, it's less efficient for developers, that might work for tech startups but we have a brand to protect and we're regulated. It just seemed like it wasn't possible to break down solutions in the places I worked.

But, it just takes a new way of looking at the problem. From a customer's perspective it is easy to see how smaller subsets of scope can deliver value sooner. I dive into much more detail on this topic in my article this week.

This Week’s Updates

Enabling the Team

Conversation Quality And Scale by John Cutler
The quality of conversations within teams directly shapes alignment, trust, and decision-making. Leaders who focus on improving dialogue create healthier, more effective environments.

Empathy Is A Non-negotiable Leadership Skill. Here’s How To Practice It. By Palena Neale
Empathy is essential for building trust, reducing conflict, and guiding teams through uncertainty. Practicing it well means listening without fixing, staying curious, and making space for other perspectives.

Product Direction

Team Autonomy And AI by Marty Cagan
As AI reshapes product work, the need for true team autonomy becomes even more urgent. When teams are trusted to solve problems rather than deliver requirements, they’re better equipped to integrate AI in meaningful and responsible ways.

What Successful Product Organizations Have In Common by Petra Wille
Strong product organisations share clear expectations, consistent coaching, and a commitment to continuous improvement. Success comes from aligning individual growth with company goals and reinforcing product craft at every level.

Continuous Research

Why Qualitative Data Belongs In Your Key Results by Christina Wodtke
Key results often rely too heavily on quantitative metrics, overlooking the nuance that qualitative data provides. Integrating stories and observations helps teams stay connected to real user impact, not just the numbers.

How To Use AI For Product And Market Research by GoPractice
AI tools can speed up early-stage product discovery by summarising trends, analysing competitor moves, and surfacing customer needs. The key is combining automation with human judgement to guide strategy, not replace it.

Continuous Design

Thinking Like AI: A New Approach To AI UX Design by Michael O’Sullivan
A 'jobs-to-be-done' framework for AI UX design, encouraging designers to empathize with AI's tasks and challenges.Enhancing the synergy between human users and AI systems, leading to more intuitive and efficient interactions.

Explaining UX Design Through The Lens Of Construction by Saranya Gunasekaran
UX design can be likened to constructing a building: both require solid planning, foundational structures, and user-centric approaches to ensure long-term functionality and stability.

Continuous Development

Every Feature Can Be Broken Down Into Separate Releases by Rory Madden
By understanding customer needs, targeting specific segments, delivering end-to-end slices, and testing assumptions early, teams can overcome resistance and unlock the potential of iterative development.

This Is Why You're Not Shipping by Andy Vandervell
Slow shipping often stems from overcomplication, unclear ownership, or fear of failure—not just bad tooling. Cutting scope, simplifying decisions, and building momentum through small wins can help teams ship faster and more often.

Master Product Vision & Strategy in Barcelona

Develop your skills to lead & align impactful strategies.

Take your product strategy to the next level at our one-day Product Vision & Strategy training on July 10, 2025, in Barcelona. This immersive workshop is designed for product professionals looking to sharpen their strategic skills and align teams around a compelling vision. Whether you’re leading a product team, managing cross-functional collaboration, or starting a new venture, this course will help you create actionable product strategies that deliver results.

Don’t miss out on this unique opportunity to gain practical insights and connect with peers. Limited spots available, and UXDX subscribers get 20% off with code UXDXMEMBER25. Register now and transform your product strategy!

Click here to book your tickets today!

FREE COMMUNITY EVENTS 

Check out more upcoming community events 

Video of the Week
Right-First-Time Code: Early Defect Detection for Product Teams

In this week's video, join Fabrice, CTO of Theodo and author of The Lean Tech Manifesto, as he delves into the world of right-first-time software delivery. Discover how to incorporate early defect detection into your process with his “Dantotsu” approach, designed to catch issues early and streamline delivery.

Fabrice will explore how this innovative methodology combines lean strategy with the agility and speed needed for modern product teams to scale effectively. Don’t miss out and watch below for actionable strategies!

The Results of Last Week’s Poll

The question: What tool or method does your team use to map out dependencies before starting a project?

This week’s poll results reveal that the majority of teams (57%) use Wardley Mapping to map out dependencies before starting a project. This method is clearly popular for its strategic value in visualizing the competitive landscape and the evolution of key components.

Interestingly, 24% rely on informal discussions to identify dependencies, while 5% use Architecture Decision Records (ADRs) to formalize decisions. 9% of teams use other frameworks, and 5% reported they don't have a specific method for mapping dependencies. These results highlight that while formal methods like Wardley Mapping are widely used, some teams still rely on informal approaches to address project dependencies.

If you’re looking to improve how you map out dependencies or explore effective frameworks for your team, check out strategies for better project alignment in our Continuous Development course!

Seen an interesting article online? Share it with us and we might feature it in our next issue!
Click here to share an article