John Doerr describes a healthy OKR environment as one that strikes a balance between alignment and autonomy. The PI Outcome is where AI-Native SAFe puts that balance to work.
What a PI Outcome is
An ART expresses its longer-term strategy as ART outcomes — typically the results it intends to achieve over the year ahead.
PI outcomes are the set of outcomes that will best advance those ART outcomes in the next Planning Interval.
They sit one level below ART outcomes in the AI-Native SAFe outcome tree. The tree runs from the portfolio’s longer-term strategic outcomes down to the outcomes that give AI-Native Teams their day-to-day focus. It communicates purpose down through the organization and commitment back up.
Where PI outcomes come from
They are not invented on planning day. In the weeks before the PI Outcome Planning event, ART Leadership and Business Owners review three things:
- The product vision and roadmap
- Current progress against ART outcomes
- Insights from recent Sense and Respond events
From those, they draft the PI outcomes they believe will best advance the ART outcomes. The drafts typically go to teams about a week before the event, so teams have time to work out how they can contribute.
The third input is the one worth noticing. What the ART learned in recent iterations is meant to shape what it commits to next.
How teams respond
Teams do not arrive with a blank slate. In the days before the event, each team drafts its own team outcomes, answering one question: given our capabilities and the part of the product we own, how can we best advance the PI outcomes — and solve the customer and business problems behind them?
The framework is explicit that this is where much of the ART’s innovation begins. Good ideas are not bound by hierarchy, and the teams closest to the product and the customer are often the first to see what is possible.
How drafts become commitments
PI Outcome Planning is a one-day event at the start of every PI, with the whole ART in attendance. There, draft team outcomes are tested against other teams’ plans. Teams make adjustments and trade-offs, then commit to a finalized set.
ART leadership and stakeholders validate three things: how each team intends to contribute, where its capacity is going, and whether the overall plan holds together. The event closes with a confidence vote.
Not every hour has to map to a PI outcome
This is the detail most planning boards get wrong. The framework states that a team’s capacity is not consumed entirely by PI-outcome work. A team may hold spare capacity for other outcomes that serve the ART’s longer-term goals, and for routine work that isn’t captured in any outcome at all.
A plan that claims 100% of capacity traces to PI outcomes is not more aligned. It is less honest.
When it happens
At the start of every PI. Drawing on Mik Kersten’s research into organizations that use AI effectively at scale, the guidance is to plan at the business cadence. If the business runs quarterly, PIs typically do too — one cadence across the organization.
Three questions for your next PI
1. Did our draft PI outcomes draw on Sense and Respond insights — or only the roadmap?
2. Did teams draft their own team outcomes before the event, or were outcomes handed to them?
3. Does our plan show the capacity held outside PI outcomes — honestly?
The world has changed. The leaders who notice will be the ones the next decade is built around. I write on Thursdays at agile-agilist.com.
Source
Scaled Agile, Inc. — AI-Native SAFe framework guidance: PI Outcome Planning.
