Many SAFe transformations stall or fail to deliver the promised benefit of business agility. One prominent reason for these failures is SAFe’s insistence on using the Feature Factory approach. Let’s reinvigorate your SAFe transformation with a Product Operating Model concept.
The Dreaded Feature Factory
A Feature Factory is where someone other than the Agile development team defines what to do. For example, SAFe describes the Product Manager as responsible for writing Features and handing them off to the Agile team. That’s a Feature Factory. In SAFe, the “discovery” end game is all about writing more Features (just read the articles). These Features are then handed off to the Agile development teams.
This approach doesn’t pass the smell test. It reeks of waterfall.
A Feature Factory is undesirable for many reasons: it sends a message to the Developers that we don’t trust them to actually solve problems. It relegates them to order takers (go build this Feature). The Feature Factory stifles innovation. It makes Agile teams accountable for outputs, not outcomes.
Operating in this model we often hear statements such as:
“We need written instructions before we can build anything.”
“We need to figure out what needs to be done, then tell the Developers so they won’t get it wrong. Again.”
“We can’t trust the Developers, so we need to proxy the discovery activity to some other role or organization.”
It’s almost like a young Kevin Bacon in the Animal House movie screaming, “Thank you sir! May I have another?” as the Feature paddles hammer his backside.
The Feature Factory is a fundamentally flawed model, worthy of your attention!
Moving to an Empowered Team Model
Here’s my point: you can shift your Feature Factory model over to an Empowered Team model as described in the Product Operating Model (great article from Silicon Valley Product Group).
In an Empowered Team model, the Agile team is responsible for BOTH discovery and delivery. It asks the Agile team to receive a problem-to-solve (not a Feature). STOP right there – re-read the last two sentences! It’s the essence of an Empowered Team.
The Empowered Team works collaboratively with the customer to discover a potential solution for the given problem-to-solve. The developers are bringing their innovative ideas for solutions. They are working up quick low-cost prototypes (think vibe coding and throw-away prototypes), and establishing a fast feedback loop with the customer. No telephone game, just direct feedback with zero waste.
Once consensus is obtained, the Agile team builds the agreed-upon solution using their quality testing practices.
During the build phase, Agile teams can (if truly needed) define Features for release of incremental value. Notice how Features become a RELEASE consideration, not an up-front tell-us-what-to-go-do requirement. STOP right here and re-read this paragraph!
Call to Action
You will likely need some level of scaling structures (lightweight), so just pick & choose from SAFe or use commonly known scaling practices. Feel free to pare down your existing SAFe events, roles, and artifacts.
Courage statement: Replace the fundamentally flawed Feature Factory model with the Empowered Teams model to reinvigorate your SAFe transformation. There is much evidence that this will result in solution clarity, faster development, shorter Feature cycle times, and increased innovation.
Hesitant? Give it a try. Run an experiment with 1 – 2 teams while measuring discovery/delivery times and employee satisfaction.
Wrapping Up
Thanks, I hope this helps someone out there disappointed in their SAFe transformation.
Explore these resources for more insights: