Reviewing cycle one and refining the plan

What "review" means in this standard

• The standard defines it exactly: comparing the outcome of the business activity with the original planned business activity.
• So a review is not a description of what happened, and it is not a reflection on how the group felt. It is a comparison, item by item, between plan and outcome.

How to structure the review

Take each part of the plan in turn and compare:

Planned	Actual	Difference	Why
Produce 80 units	Produced 80	0	—
Sell 80 units	Sold 63	−17	Ran out of time at the Thursday session; 6 turned away Tuesday
Unit cost $4.71	$5.02	+$0.31	Ingredient price rose; extra packaging bought late
Revenue $400	$315	−$85	Fewer units sold
Surplus $23	−$62	−$85	Unsold stock carried full cost
Deliver to 3 sessions	Delivered to 3	0	—
30 residents attending	41 attended	+11	Coordinator promoted it in the newsletter

• The "why" column is the review. Everything before it is bookkeeping.
• Review the community well-being goal with the same discipline. If the goal was that 30 residents attend and 41 did, say so and say why. If you have no evidence either way, say that too — it is an honest finding and it becomes a refinement about collecting evidence.

Explaining the differences

• Every difference has a cause, and the causes fall into a small number of types:
  • The plan was wrong — the estimate was optimistic, the price was too high, the schedule did not allow enough time.
  • The execution differed from the plan — someone was absent, a step was skipped, the promotion did not happen.
  • Something external changed — an ingredient price rose, the weather closed the session, another event clashed.
• Naming which type it was matters, because each needs a different refinement. An optimistic estimate is fixed by changing the plan; a skipped step is fixed by changing the process or the roster.

Refining the plan

• Refine is defined by the standard as making the changes arising from the review, with the aim of making improvements.
• Two rules:
  • Every refinement must come from something in the review. A change nobody has evidence for is a guess.
  • Every refinement needs a reason. Merit requires reasoned explanations to refine the activity — the reason is the mark.

A weak refinement: "We will promote it more next time."

A strong refinement: "In cycle one, six customers were turned away on Tuesday and stock ran out 20 minutes into the Thursday session, while sales on Wednesday were slow. This suggests demand is concentrated on Tuesday and Thursday rather than being insufficient overall. In cycle two we will produce the same total quantity but split it 35/10/35 across the three sessions instead of evenly, so supply matches when customers actually come. We expect this to raise units sold without increasing production costs."

Notice what makes it strong: the evidence, the interpretation, the specific change, and the expected effect — which is what makes it testable in cycle two.

How many refinements?

• Enough to address the significant differences, and few enough that you can tell which one worked.
• Three or four well-reasoned changes are far more useful than ten, because cycle two must be reviewed against the refined plan — and if everything changed at once, no difference can be attributed to anything.
• Prioritise: fix what cost the most, or what most affected the community outcome.