Skip to content

Change 3 of 6

Governance

Review outcomes weekly.

Agree the outcomes. Review the evidence. Decide what to do next.

The change

Govern through evidence and decisions.

A plan describes what a team intends to do. It cannot establish whether the work will improve the customer experience. When reviews concentrate on time and cost milestones, teams focus on delivering the outputs while the outcome may not improve at all.

ZeroBlockers makes outcomes the basis of the governance conversation. Leaders and teams agree the measures up front, review evidence regularly, and decide what to continue, adapt, or stop. Teams need authority over the decisions that influence those measures.

When AI makes it possible to test and ship more frequently, a monthly approval meeting can hold up the next useful decision.

What changes in practice

  1. Agree the measures together.

    Choose the customer or product outcome the team exists to improve. Make sure the team can influence it within its scope.

  2. Pair the target with a health measure.

    Keep an eye on what might deteriorate while the target improves. A better conversion rate is not enough if customers are being misled.

  3. Review the trajectory weekly.

    Use a short Weekly Product Review to show the outcome trend, the health measure, what was learned, and any decision needed. Use the review to resolve blockers and agree actions with owners. Teams keep making routine decisions within their guardrails between reviews.

A practical example

The checklist shipped. Did more customers sign up?

A team releases a checklist to help prospective customers complete signup. The old model considers the work done once the checklist is delivered.

In ZeroBlockers, the team stays responsible until the customer outcome improves. At the weekly review, it compares signup conversion with the baseline and target, alongside customer feedback and support requests per new customer. These guardrails help determine whether the objective has been achieved without creating new problems.

If signup conversion stays flat, or if support demand worsens, the team decides whether to adapt the checklist, try a different approach, or stop the work. The review makes the evidence and decisions visible to leaders without requiring them to approve every change.

Four layers of metrics

  1. InputHours worked
    Effort investedTime spent doing the work.
  2. OutputChecklist shipped
    Old model stops hereDelivery is treated as done, even if nothing changes for customers.
  3. OutcomeMore customers signed up
    ZeroBlockers: accountable hereThe work is done when the outcome is achieved.
  4. ImpactRevenue up
    What the business wantsWhat the business ultimately wants. It moves too slowly to steer day-to-day product decisions.

Governance in practice

Real case studies from UXDX conferences and other sources.

Amazon logo

Tracking Strategic Outcomes Through Weekly Business Reviews

How Amazon uses the Weekly Business Review (WBR) process to track and manage strategic outcomes effectively within a structure of empowered teams, ensuring alignment with long-term business goals.

E-commerce / Technology

American Marketing Association

Evaluating Product Success Across Ecosystems

How the American Marketing Association enhanced strategic decision-making and improved product outcomes by implementing a structured business review process.

Marketing / Professional Association

Browse 2 governance case studies ↗

Common objections

What stops teams from building crazy features?
Stream Teams don't work unsupervised. They report to Product Teams, and before they build something they share what they intend to build, the opportunity they think it addresses and what they learned from testing prototypes. We can trust teams to build the right thing, and we still have a responsibility to check that they are. That conversation is where the check happens.
Measuring outcomes is a nice fairy tale but it isn't feasible in the real world
You're right that most business metrics are too far removed from what a single Stream Team can influence. Revenue moves for many different parallel and competing reasons to hold one team accountable for it. That's why Product Teams act as a translation layer between the business metrics leadership cares about and the product metrics a Stream Team can move. Once a team is autonomous, it's reasonable to hold it accountable for those product metrics, because it controls the decisions that affect them.
We are regulated. Auditors need evidence that changes were approved
Auditors need evidence that changes are controlled, and an approval committee is one way to provide it. Traffic-light release governance is another. Instead of approving individual changes, you pre-approve patterns. Each class of change has published checks, anything that matches the pattern ships with those checks built in, and changes that need real judgment still escalate. Compliance tests run on every change, so the audit trail builds up in the pipeline as the work happens. DORA's research supports this. It found no evidence that formal external review is associated with lower change fail rates, and it recommends peer review captured in the development platform as a way to meet segregation of duties. Read DORA’s research on change approval.
Does outcome governance mean leaders lose oversight?
No. Leaders keep responsibility for direction, scope, funding and the agreed boundaries, and regular reviews make the results visible to them. Two things change. The evidence leaders use to govern moves from plans and status reports toward results, and teams can make more decisions without escalating.
All common objections ↗