Insights Topic
SAFe is not a compliance checklist. Connect scaled structures to flow principles and actual business outcomes.
On this page:
SAFe implementations frequently devolve into heavy, top-down bureaucracy. Below, I outline how to keep the framework focused on systems thinking, flow economics, and actual business outcomes.
Start here · Cornerstone read
SAFe done right — connecting the framework's structure to product thinking, flow principles, and actual business outcomes rather than compliance and ceremony.
Read the full articleA successful SAFe implementation shifts the focus away from framework checkpoints and ceremony compliance. Instead, the emphasis must be on end-to-end flow metrics: velocity, load, time, efficiency, and distribution.
By exposing where work queues up across Agile Release Trains (ARTs), leaders can identify real bottlenecks. This visibility allows teams to solve actual systemic constraints rather than just optimizing local sprint velocities.
A significant portion of SAFe criticism is entirely valid—but it is usually directed at poor, bureaucratic implementations rather than the core principles. When SAFe becomes a rigid rulebook, it fails to deliver agility.
Keeping the framework effective requires shifting the role of the SAFe Practice Consultant (SPC). Rather than acting as framework administrators and certificate coordinators, SPCs need to operate as organizational design coaches and flow leaders.
It can be if implemented as a rigid compliance checklist. However, if you focus on the underlying principles—like decentralized decision rights and flow economics—SAFe provides a structured way to align scale with speed.
Use OKRs to define strategic themes and value stream objectives. Avoid writing OKRs as feature lists; keep KRs focused on business outcomes, and steer execution through lightweight portfolio Kanban systems.
Insights Database
Browse the complete archive of articles and case studies related to safe done right.
A follow-up AI coaching prompt for anyone who sat through my "Product Orientation Through LPM" talk — pressure-test one real initiative, find the real gap, and get one experiment to run in the next few weeks.
How ARAS Software scaled from startup to 60+ engineers — adopting SAFe for alignment at scale, then evolving beyond it when rigid PI Planning became a drag on the throughput and innovation they originally installed it to protect.
Is SAFe good? Is SAFe agile? As both a SAFe Fellow and a Professional Scrum Trainer, I get to argue both sides honestly. A balanced look at why SAFe is popular, where the criticism lands, and the controversies around the Scrum Master and product owner roles.
Strategic themes gathering dust like unused New Year's resolutions? How to apply the same outcome-oriented, empirical patterns used at the team and portfolio level to break strategy theater at the enterprise level.
SAFe evolving toward a product operating model: how the framework is adapting to empowered product teams, outcome focus, and the shift from project to product.
SAFe and the Product Operating Model are not in conflict — they can complement each other. A podcast interview exploring empowered product teams, outcome-oriented PI Planning, and why incentive alignment is the real lever.
Practical criteria for designing Agile Release Trains (ARTs): how to group teams around value streams, localize dependencies, and avoid the common mistake of creating ARTs that mirror your org chart.
How to apply product operating model principles to shared services and business operations teams to improve handoffs, flow, and business readiness.
Season 1 of Breaking the SAFe: an honest exploration of where SAFe implementations go wrong and what practitioners can do to course-correct before the transformation stalls.
Lean Portfolio Management and OKRs together: how strategic objectives connect to portfolio investment decisions, and what makes OKRs useful at the portfolio level.
SAFe Strategic Themes are not OKRs — and treating them like OKRs creates confusion. When to use gradable Key Results vs directional strategic themes in SAFe.
A SAFe Fellow's honest analysis of the most common SAFe criticisms — what's fair, what's FUD, and how the SPC certification model contributes to implementation theater.
SAFe splits product ownership between Product Manager and Product Owner. This guide explores the tradeoffs, common failure modes, and practical ways to make it work.
Sustainable pace is a core agile principle that often gets sacrificed in enterprise implementations. How Scrum, SAFe, and Kanban each approach the problem.
OKRs, KPIs, Operational Value Streams, and Development Value Streams in SAFe — how they connect, where people confuse them, and how to align them effectively.
How SAFe organizations can iterate faster — moving from quarterly PI cadences toward more frequent delivery using shorter iteration lengths, faster feedback loops, and flow optimization.
B2B tech vendors struggle to map SAFe's Operational Value Streams to their context. A practical guide to how vendors should organize around customer value without distorting their product development structure.
Applying the INVEST criteria to SAFe PI Objectives — how Independent, Negotiable, Valuable, Estimable, Small, and Testable goals make PI Planning outcomes more actionable and honest.
A podcast conversation on how SAFe, Kanban, and Scrum complement each other — and where the friction points are when teams try to combine them.
How to handle scope changes during a SAFe Program Increment — switching features mid-PI, updating PI Objectives, and managing the impact on predictability score without gaming the system.
SAFe dependency boards can be pain-tracking tools or double-loop learning engines. How to use dependency retrospectives to actually reduce inter-team dependencies over time.
The wrong reasons people sign up for SAFe SPC certification — and what you should actually expect to get out of an Implementing SAFe workshop if you attend with the right mindset.
SAFe implementations often under-develop team-level Scrum discipline. How Professional Scrum training and coaching strengthens the foundation that SAFe programs are built on.
SAFe implementations often focus on ceremonies and roles while ignoring the underlying flow. How adding Kanban-style flow metrics to your SAFe implementation makes the whole system more evidence-based.
How to forecast in SAFe using smaller slices, throughput, cycle time, and lighter feature sizing. A practical alternative to story-point-heavy PI planning, release forecasting, and roadmap conversations.
What's the difference between Planned, Actual, and 'Actual Actual' Business Value in SAFe PI Objectives? Why the gap between them is a sign of broken goal-setting, and what to do about it.
The difference between a framework and a methodology matters. SAFe provides structure and choices — not a prescriptive path. Understanding this distinction is key to implementing it well.
The Release Train Engineer role is one of the most challenging in SAFe: part coach, part facilitator, part servant leader. What makes a great RTE and how to develop them.
Why frameworks like SAFe get criticized as prescriptive — and why the real problem is practitioners who treat a configurable framework as hard-coded rules rather than a set of principles and choices.
SAFe is not one-size-fits-all. A look at how different enterprise scenarios (large programs, rapid enhancement pipelines, fixed-scope regulatory projects) require different SAFe configuration choices.
The official SAFe guidance article on Invitation-Based SAFe Implementation — how pull-based, invitation-style change management improves SAFe adoption outcomes vs mandate-driven rollouts.