### Overview SAFe is a framework that enables large organizations to apply agile practices across multiple teams and departments. It emphasizes alignment, collaboration, and delivery at scale, particularly in complex product environments. For UX professionals, SAFe introduces opportunities and challenges in integrating design into cross-functional, sprint-based workflows. ### Description / Learning Log #### 2025-03-30 • Thought: In SAFe, UX tends to struggle with cadence—designers are expected to contribute to PI Planning, but their work often spans multiple increments. I wonder how “dual-track agile” can complement this. #### 2025-03-27 • Insight: Post-PI Planning can be a key opportunity for UX teams to re-evaluate design assumptions before the next sprint begins. Connected note: [[Post PI Planning]] **Use Cases / Examples** • Enterprise software teams using SAFe to manage 100+ developers across domains • UX teams creating design artifacts ahead of PI Planning to inform backlog prioritization • Case study: IBM’s Design Thinking approach within SAFe (link) **Questions / To Explore** • How can design research be better integrated into SAFe timelines? • What does a successful “Design PI Planning” look like? • Is there an effective model for UX metrics within SAFe?