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's tip comes from Louise Farrow and focuses on a lesson that can significantly improve the effectiveness of SAFe implementations: intentionally designing Agile Release Trains around value delivery rather than existing organizational structures.
đĄ Tip of the Week: Start with Value Streams, Not Org Charts
One of the biggest lessons I've learned is that not all Agile Release Trains are created equally. In many organizations, there's a temptation to take existing teams and structures and simply apply SAFe terminology to them. While this may seem like a faster path to adoption, it can limit the benefits that SAFe is designed to deliver.
When I'm working in a complex environment, I encourage people to think carefully about how ARTs are formed. Rather than starting with the current organizational chart, start by understanding how value actually flows through the organization.
A few things I keep in mind:
- Don't skip value stream mapping. It helps reveal how work truly moves through the system.
- Be intentional about ART design instead of defaulting to existing structures.
- Reassess whether ARTs are serving the flow of value, especially at PI boundaries.
- Stay pragmatic and focus on what works best in your specific context.
This perspective aligns with how I continue learning. I'm currently working my way through the SAFe reading list because it helps me deepen my understanding of the principles behind the framework, not just the mechanics. The better I understand the underlying concepts, the more effectively I can apply them in different situations.
The best advice I can offer is to avoid treating SAFe as a set of labels or ceremonies. Focus on understanding the system, how value is delivered, and what will help your organization work more effectively. When you start there, the framework becomes much more powerful.
