Each week in SAFe Connect, we share one practical tip from a member of the community to help you apply SAFe in more meaningful ways.
This week, Raul Barth shares a principle that has shaped the way I approach transformations: understand the real problem before committing to a solution.
💡 Tip of the Week: Fall in Love With the Problem, Not the Solution
“Fall in love with the problem, not the solution” is one of the best pieces of advice I’ve ever received, and it has shaped the way I approach transformations.
In a complex environment, I start by clearly understanding the problems we are trying to solve. It can be easy to fall in love with a solution too early, but I’ve found it more valuable to first challenge assumptions and explore what the organization actually needs.
I think of SAFe as a toolbox rather than a rigid set of rules. I use and adapt the tools to fit the context and needs while keeping the underlying principles in mind. Those principles are the foundation upon which everything else is built.
For me, that means asking a few important questions before deciding what to apply:
- What problem are we actually trying to solve?
- What business or systemic challenge is getting in the way?
- What outcome are we trying to achieve?
- Which tools or practices can help us move toward that outcome?
I also keep learning by combining practice, community, and curiosity. Working with different organizations allows me to see what works—and what doesn’t—in real-world situations. I stay connected with the Agile and SAFe communities, exchange experiences with peers, and read beyond Agile to explore topics such as product, flow, leadership, and organizational change.
One resource I recommend is Project to Product by Mik Kersten because it helps shift the conversation from projects toward products, value streams, flow, and business outcomes. I also find the VSAI toolkit useful for bringing a practical, data-driven perspective to Value Stream Management.
The lesson I keep coming back to is simple: understand the real problem first. SAFe, Agile, or any other approach should be a means to an end—not the goal itself.
