When the business sits with the team, a Product Owner still has to own the outcome

One Business Analyst (BA) and one developer, embedded with a business team for twelve weeks, turned work that previously took months to specify and build into days. The business team answered requirements questions in real time. The developer iterated without a change request. The team completed the pilot on time. The proposal is to run three more of these arrangements across the agency.

In Brief


  • A Business Analyst and developer embedded with the business speed up answers but leave the funded outcome and the order of work with no owner.
  • As scope grows, the business team’s most recent request sets the order of the Product Backlog unless one Product Owner holds the Product Goal.
  • Ron Jeffries attributed Chrysler’s C3 shutdown to its funder and goal-setter not talking; Fowler had seen no analysis of the cancellation based on much knowledge of the facts.
  • Appointing a Product Owner before the pilot scales gives the Executive Board one person who answers for whether the product delivered what the agency funded.

The business team was satisfied with what the BA specified and the developer built. Nobody in the arrangement held Product Owner accountability for whether the work, in the order it was done, delivered what the agency funded it to deliver. The on-time result measured how fast the team worked; the pilot never tested who answers for product value.

Proximity changes communication, not accountability

Co-location gets requirements answered on the same day. The feedback loop from request to delivery collapses from weeks to hours. The cost of a miscommunication falls when the people who ask for work and the people who build it share a room.

What co-location does not change is who answers for the product. The BA translates business need into development tasks, and the developer builds to that specification. Neither role holds the Product Goal, the specific outcome the agency funded the work to deliver, or controls the order in which the Product Backlog is built. The Scrum Guide is precise on this: the Product Owner is one person, not a committee, accountable for maximising the value of the product and for the order of the Product Backlog. The whole organisation must respect those decisions (Schwaber & Sutherland, 2020).

In a small pilot with a defined scope, the team operates without designating who owns the Product Goal. The sponsor who funded the work is accessible. The team’s output is close enough to the original intent that nobody has to appoint an owner for the alignment between what is being built and why the agency funded it. The missing owner becomes a structural problem when the work expands: more features, competing requests from multiple teams, a roadmap extending beyond the original use case. Without one person accountable for the Product Goal and the order of the work, the Product Backlog builds to operational demand rather than the funded product outcome.

When no one person owns the Product Goal and the order of the Product Backlog, the latest business request decides what is built next.

Chrysler’s C3 payroll project went live in 1997, paying around ten thousand people, but new development stopped in 1999. Ron Jeffries, one of its practitioners, later attributed the shutdown to the Goal Donor and the Gold Owner not talking with each other on a timely or productive basis (Jeffries, as cited in y-kamite, 2002). Fowler, writing about C3 more than five years after the shutdown, notes he had seen no analysis of the cancellation based on much knowledge of the facts (Fowler, 2004). In Jeffries’ account, the person paying for the system and the person setting its goals did not talk, so a project that produced working software left nobody to answer for whether it delivered the value Chrysler paid for.

The pilot proposal has no Product Owner

The Chief Digital Officer (CDO) who approves a BA-plus-developer pilot decides who sits with the business. The proposal leaves blank who has the authority to hold the Product Goal and is accountable for the order of the work.

As the scope extends without a designated Product Owner, the business team makes product decisions based on operational need. They are the most accessible voice, and nobody holds the Product Goal. The developer builds to the most recent request, because that is what the BA translates and there is no ordered Product Backlog to defer to. When the Executive Board asks whether the investment delivered what the agency funded it for, no single person can explain why the items were built in the order they were. The arrangement treats coordination as accountability: a distinction Evolve examines in tracing how product teams lose the connection between what they build and what the organisation funded them to deliver (Hodgson, 2026, Chapters 4 and 15).

Each cycle built to the most recent request adds work that nobody ordered against the outcome the agency funded. The people who requested each item judge whether it was right, and nobody is accountable for whether the funded outcome arrives. By the time that pattern is visible, the agency has already spent the investment building to the wrong order.

One question before the pilot scales

Making a BA-plus-developer arrangement accountable for product value requires one element: a single, accountable person with the authority and information to answer for the Product Goal and control the order of the work. That person may already exist in the pilot: the sponsor who funded the work, or a product manager who currently sits outside the team. The order-taker and the order-maker are distinct roles, and the accountability for product value sits with the order-maker (Hodgson, 2026, Chapter 15).

Before approving the expansion, put this question to the pilot’s sponsor: who in this arrangement owns the Product Goal and the order of the work, and answers to the Executive Board for whether the product delivers what the agency funded? Appointing that person before the pilot scales is the decision that separates a pilot that communicates faster from one that delivers what the agency funded it for.

What this means for senior leaders

  • Co-location and product ownership solve different operating model problems: improving communication between business and developers is a different question from deciding who answers for whether the product delivers its funded purpose.
  • The Product Owner is the one person who can tell the Executive Board whether the product delivered what the agency funded, and why the work ran in that order.
  • When a pilot appoints its Product Owner before scaling, the product operating model conversation with ZXM begins.

References

About the author

Receive insights on strategy, leadership, and transformation.
By subscribing you agree to our Privacy Policy
© 2026 Zen Ex Machina (ZXM) Pty Ltd. All rights reserved. ABN 93 153 194 220
search previous next tag category expand menu location phone mail time cart zoom edit close