How Far Along Is Your Project-to-Product Shift?
An AI coaching prompt from my "Product Orientation Through LPM" talk: pressure-test one real initiative, find the real gap, and get one experiment to run.
Insights Topic
SAFe Done Right
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 Criticism, Deconstructed: The SPC Role
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 articleSAFe Flow
How do you measure flow and value in SAFe?
A 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.
SPC Role & Criticism
How do you deconstruct SAFe criticism and keep SPCs effective?
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.
FAQ
Frequently asked questions
Is SAFe too bureaucratic for agile teams?
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.
How do you align OKRs with SAFe?
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
All SAFe Done Right Articles
Browse the complete archive of articles and case studies related to safe done right.
-
-
How ARAS Software Is Agile About Scaling Agile
How ARAS Software scaled from startup to 60+ engineers with SAFe, then moved past it when rigid PI Planning started dragging on throughput and innovation.
-
SAFe Strengths, Weaknesses, and Controversies
Is SAFe good? Is SAFe agile? As a SAFe Fellow and Professional Scrum Trainer, I argue both sides — why SAFe is popular and where the criticism lands.
-
Tackling Strategy Theater - Fractals to the Rescue
Strategic themes gathering dust like New Year's resolutions? Use the same outcome-oriented, empirical patterns from team level to break strategy theater.
-
SAFe-ly Scaling an Agile Product Operating Model
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 vs. the Product Operating Model (Podcast)
SAFe and the Product Operating Model are not in conflict. A podcast on empowered product teams, outcome-oriented PI Planning, and why incentives matter most.
-
How To Organize Agile Release Trains (ARTs)
Practical criteria for designing Agile Release Trains: group teams around value streams, localize dependencies, and avoid ARTs that mirror your org chart.
-
Product Operating Model for Shared Services Teams
How to apply product operating model principles to shared services and business operations teams to improve handoffs, flow, and business readiness.
-
Breaking the SAFe: Reclaiming Professional Scrum
Season 1 of Breaking the SAFe: where SAFe helps, where it goes sideways, and how to course-correct before the framework becomes theater.
-
Lean Portfolio Management and OKRs (Podcast)
Lean Portfolio Management and OKRs together: how strategic objectives connect to portfolio investment decisions, and what makes OKRs useful at that level.
-
Should SAFe Strategic Themes Have Key Results?
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.
-
SAFe Criticism, Deconstructed: The SPC Role
A SAFe Fellow's honest take on the most common SAFe criticisms — what's fair, what's FUD, and where the SPC certification model makes it worse.
-
SAFe Product Owner vs Product Manager
SAFe splits product ownership between Product Manager and Product Owner. The tradeoffs, common failure modes, and practical ways to make it work.
-
· KanbanSustainable Pace in Scrum, SAFe and Kanban
Sustainable pace is a core agile principle that often gets sacrificed in enterprise implementations. How Scrum, SAFe, and Kanban each approach the problem.
-
Connecting OKRs, KPIs, OVSs, and DVSs in SAFe
OKRs, KPIs, Operational Value Streams, and Development Value Streams in SAFe — how they connect, where people confuse them, and how to align them effectively.
-
· AgilityIterating faster with SAFe
How SAFe organizations can iterate faster — moving from quarterly PI cadences toward more frequent delivery with shorter iterations and faster feedback.
-
How B2B Vendors Organize Around Customer Value
B2B tech vendors struggle to map SAFe's Operational Value Streams to their context. How to organize around customer value without distorting product delivery.
-
INVEST in effective SAFe PI Objectives
Applying the INVEST criteria to SAFe PI Objectives — how Independent, Negotiable, Valuable, Estimable, Small, and Testable goals make PI Planning honest.
-
· FlowDrunk Agile Podcast SAFe, Kanban and Scrum
A podcast conversation on how SAFe, Kanban, and Scrum complement each other — and where the friction points are when teams try to combine them.
-
· AgileHandling Scope Change During a SAFe PI
How to handle scope changes mid-PI — switching features, updating PI Objectives, and managing the hit to predictability score without gaming it.
-
From Pain to Flow: SAFe Dependency Boards
SAFe dependency boards can be pain-tracking tools or learning engines. How to use dependency retrospectives to actually reduce dependencies over time.
-
Please don’t come to my Implementing SAFe workshop
The wrong reasons people sign up for SAFe SPC certification — and what you should actually expect to get out of an Implementing SAFe workshop.
-
Improving SAFe thru Professional Scrum
SAFe implementations often under-develop team-level Scrum discipline. How Professional Scrum training and coaching strengthens the foundation SAFe sits on.
-
· KanbanAdding Flow Metrics to Your SAFe Implementation
SAFe implementations often focus on ceremonies and roles while ignoring the underlying flow. Adding Kanban-style flow metrics makes the system evidence-based.
-
Forecasting in SAFe Without Story Point Theater
Forecast in SAFe with smaller slices, throughput, and cycle time instead of story-point-heavy PI planning. A lighter way to size features and plan.
-
· AgilityPlanned vs Actual vs Actual Actual Business Value
Planned, Actual, and 'Actual Actual' Business Value in SAFe PI Objectives: why the gap between them signals broken goal-setting, and what to do about it.
-
SAFe Is a Framework, Not a Methodology
The difference between a framework and a methodology matters. SAFe gives you structure and choices, not a prescriptive path, and that changes how you use it.
-
Building Great Release Train Engineers
The Release Train Engineer role is one of the toughest in SAFe: part coach, part facilitator, part servant leader. What makes a great RTE and how to grow them.
- · Agility
Musings about “Hard-coded” Frameworks
Why SAFe gets called prescriptive — and why the real problem is practitioners treating a configurable framework as hard-coded rules.
-
SAFe Configurations
SAFe is not one-size-fits-all. How large programs, rapid enhancement pipelines, and fixed-scope regulatory projects need different SAFe configurations.
-
Invitation-Based SAFe Implementation Guidance
The official SAFe guidance article on Invitation-Based SAFe Implementation — why pull-based change beats mandate-driven rollouts.