A short introduction

The system works.
Is the change holding?

An investment depends on something becoming true in the work. Delivery and usage figures may leave that condition unexamined.

A business question can become a technology action.

A review ends with a request to investigate the workflow. The technology team has an action, but nobody has agreed how the investigation will answer the business question, or who will change the conditions when the answer comes back.

That is the problem OO addresses: a route from knowledge of the work to a decision someone has the authority to make.

Look beyond activity.

In the pricing illustration, the platform can be busy while approval arrives after a discounted price has been promised. The work may also be taking place through email or a spreadsheet. Those traces raise questions; they still need interpretation, including an account from the people doing the work.

A workaround can reveal a missing capability or an impractical process. Its existence does not, by itself, identify the right response.

Give the question somewhere to go.

Someone who knows the work prepares an account that can be challenged. A business executive and a technology counterpart examine it together. The business executive retains the commercial choice; the technology counterpart answers for the evidence and process. The result is checked against what the response was expected to achieve.

That commitment can expose a disappointing result or a weakness in a system that was delivered successfully. Its value has to justify the attention and effort it asks of the participants.

Work with the organisation you have.

OO can be used alongside existing delivery, operations and benefits management arrangements. A formal benefits management practice is not a prerequisite. The organisation still needs a clear business purpose and the authority, evidence and resources to act.

If existing arrangements already carry the concern through to a decision and a check on its effect, OO may add too little to justify another commitment.

The proposal still needs testing.

The discipline has not yet been formally deployed. Its examples explain the design; they do not demonstrate that it works.

The forthcoming book develops the commitments, boundaries and practical method. Experienced leaders are invited to review selected chapters.