( Insights ) — Blog
Blog & insights.
Practical writing on SAFe implementation, AI-Native operating models, innovation culture, and the lessons from 21 years inside Fortune 500 transformations.
-
AI as a Teammate: The Fourth Capability of an AI-Native Team
AI-Native SAFe names AI as one of the four capabilities of an AI-Native Team. It provides automation and continuous analysis — under human supervision and inside clear guidelines. What that means.
-
The Domain Expert Capability — and Where the Scrum Master Went
The Domain Expert capability brings the context that makes a general AI proposal fit your situation. It’s also where Scrum Masters and Team Coaches belong in an AI-Native Team.
-
The Builder Capability: Less Typing, More Thinking
The Builder capability turns intent into working systems using AI. It’s where most team members spend most of their time — and AI changes what that time is spent on.
-
The Product Capability: Why It Matters More When Building Is Cheap
The Product capability defines why the work matters and keeps an AI-Native Team connected to customer needs. Why it matters more when building gets cheap.
-
AI-Native Teams: Four Capabilities, Not Four Roles
AI-Native Teams organize around four capabilities — Product, Builder, Domain Expert and AI — not four job titles. People move between them, which is why the team owns the outcome together.
-
Business Owners in an AI-Native ART: Steering on Live Evidence
In AI-Native SAFe, Business Owners move from steering investment at planning events to steering it continuously, on evidence coming in from real work. What changes, and why.
-
RTEs in an AI-Native ART: Same Job, Faster Pace
In AI-Native SAFe, the Release Train Engineer keeps doing what they do best — flow, obstacles, risk and dependencies. What changes is how often, and the tools they use to keep up.
-
System Architects in an AI-Native ART: Guardrails, Not Documents
In AI-Native SAFe, System Architects move from designing architecture up front to building guardrails directly into the workflows people and agents use every day. What changes, and why.
-
Product Management in an AI-Native ART: From Backlog to Evidence
In AI-Native SAFe, Product Management stops being the keeper of the backlog and becomes the curator of evidence and hypotheses that shape what the ART pursues. What changes, and why.
-
How AI Reshapes ART Leadership — Not Just Its Workload
In an AI-Native ART, teams learn faster and decisions arrive more often. That changes the job of the four ART leadership roles — not just their workload. What changes for each, and the balance they hold together.
-
The AI Innovation Pipeline: How ARTs Move at AI Speed, Safely
What the AI Innovation Pipeline is in AI-Native SAFe — its five stages, learning versus value outputs, four components — and the one reason it matters: agents can’t bridge undocumented processes.
-
A PI Outcome Is Not a Renamed PI Objective. It Is the Result an ART Commits to for the Next PI — Drafted From Evidence, Tested Against Every Team’s Plan, and Traceable All the Way Up.
What a PI Outcome is in AI-Native SAFe, where it comes from, how teams turn it into commitments, and why not every hour of capacity has to map to one — straight from the framework guidance.
