Worked example: turn a late job into an operating decision

A late job is not a management action. Until someone identifies what must change, who owns that change and when it will be checked, the same issue can return to the next review unchanged.

The narrower job of a business operating system is to make priorities, measures, responsibilities, decisions and recurring work visible. This worked example follows one issue from observation to review without inventing a successful outcome.

Illustrative starting situation: booked jobs are waiting

This is an illustrative example, not a client case study or a result from my own business.

A service team notices that several booked jobs are waiting for customer information. The delay is visible, but the discussion keeps returning to individual jobs rather than the recurring gap in the process.

The first discipline is to separate the observation from the action. “Jobs waiting for information” describes the issue. It does not say what the business will do differently.

What would change in another business

The method stays the same, but the evidence, measure and responsible role will depend on the business. A different company might find that work is delayed by an unclear approval, a missing internal handover or information that has not been recorded. It should not copy the service team’s decision unless the same bottleneck is present.

The measure must also fit the decision. A broad label such as “sales” is not enough because it could mean enquiries, accepted proposals, invoices or money received. Define the measure, its source, who updates it and what change should trigger a question.

Before adopting any template, ask: what recurring issue are we trying to expose, what evidence would show it and who is able to make or carry out the relevant decision?

The decision: check readiness before booking

In the illustrative service team, the review identifies a missing handover step. The decision is to have one person check readiness before a job is booked, with exceptions escalated to the delivery lead.

The action can now be written plainly: “Confirm readiness before booking the next job.” The record should also contain the owner and the next review date.

This is more useful than continuing to list delayed jobs because it changes a recurring part of the work. It also makes the next check possible. The business can look for evidence that the readiness check was used and ask whether the same delay occurred.

Working steps: move from issue to reviewable action

1. Record the observation without disguising it as an action: jobs are waiting for customer information.
2. Identify the recurring step behind the delay: readiness is not being confirmed before booking.
3. Make the decision: readiness will be checked before a job is booked, and exceptions will go to the delivery lead.
4. Name the person responsible for carrying out the check. Do not leave ownership with “the team”.
5. Keep the action separate from the issue: confirm readiness before booking the next job.
6. Set the next review date so the change does not disappear after the meeting.
7. At the following review, check whether the readiness step was used and whether the same delay occurred.
8. If the action remains open, decide whether its scope must change, capacity must be provided or the action should be stopped explicitly. Do not treat a repeated label as progress.

Keep the weekly review focused on decisions

A short recurring review can work through numbers, priorities, customers, issues, actions and decisions. Its purpose is not to talk about everything. It is to see what changed, decide what matters and give the next actions owners.

Prepare the numbers before the meeting. Use the meeting for exceptions, trade-offs and decisions requiring more than one person. Detailed problem-solving belongs in a separate discussion with the people who can resolve it. Otherwise, the review becomes a status recital.

Keep the record visible afterwards. Carry open actions forward with their existing owners instead of producing a fresh list each week, and close an action only when the agreed result can be checked.

Common mistakes that weaken the method

• Recording “jobs waiting for information” as though it were an action.
• Discussing every delayed job without looking for the recurring handover failure.
• Assigning responsibility to a group rather than one person.
• Using a measure without defining what it means, where it comes from or who updates it.
• Filling the review with everything the business can count rather than the information needed for decisions.
• Letting detailed problem-solving consume the recurring review.
• Starting a new action list while older actions remain open and unexamined.
• Closing an action without checking evidence of the agreed change.

Where the working files help

You can apply the method without buying anything. Start with one recurring issue, separate the observation from the action, name an owner and set a review date. The free guide to a simple weekly business review provides the six-question rhythm at https://chrisgjones.co.uk/business-fix/guides/weekly-business-review-template.

I create and sell Build Your Business Operating System as a one-off digital Business Fix toolkit. No software or consultancy is included. The current product page is https://chrisgjones.co.uk/business-fix/business-operating-system.

The files support the administrative work around this method. They do not make the decision for you or carry out the change.

• The management rhythm starting guide helps bring recurring management work into a review routine built around priorities, ownership and the next decision.
• The management bottleneck scorecard and action register helps assess reviews, measures, responsibilities and decisions, then keeps evidence and next actions visible.
• The management decisions worksheet records what needs to change in reviews, KPIs, responsibilities and recurring work, including who will act.
• The business review drafting prompt can prepare a summary and draft actions from notes you supply, without allowing AI to invent figures or commitments.
• The management meeting preparation prompt uses approved management notes to prepare review material and identify unknowns that require a person’s decision.
• The management action check helps close the loop by checking ownership, completion evidence and the next review date.

These are selected files and are not necessarily the full pack inventory. I would not buy the toolkit if the business is unwilling to name owners, record decisions or revisit open actions. Files cannot compensate for avoiding those choices.

The check at the next review

The illustrative example does not assume that the new step worked. At the following review, the team should ask whether the readiness check was actually used and whether the same type of delay occurred.

That check determines the next decision. If the change was not used, examine ownership, scope or capacity. If the delay still occurred, look at whether the identified handover step was genuinely the bottleneck. If the evidence is unclear, improve the record rather than claiming progress.

The practical next action is simple: take one recurring issue from your latest management discussion and rewrite it as an observable change with one owner and a next review date. If you cannot do that, you have not yet made a management decision.