Improving Everyday Business Processes in Albany: Measuring Results Before Spending More

An everyday process can be awkward without needing an expensive new system. For an Albany business, the first improvement might be clearer information, fewer unnecessary handovers or an agreed check before work leaves the premises. Measurement helps you understand whether the change is useful before spending more.

Use this checklist for a bounded process such as preparing an order for collection. It focuses on the work itself, whether the eventual solution is a revised instruction, an existing tool or paid specialist help. Keep safety, legal obligations and customer commitments in place throughout the exercise.

Check the task has a clear boundary

  • Name the event that starts the task.
  • Describe what counts as finished.
  • Identify the people handing work to one another.
  • Include waiting and clarification, not just visible actions.
  • Record where the customer or next team receives the result.

For an order prepared for collection, finished could mean the correct goods are labelled and the customer has been notified through the agreed channel. It does not necessarily mean payment is complete or the order has been collected. Separate those events so the measurement remains understandable.

Business Queensland’s process guidance explains the role of usable operational instructions. Its general planning principles can help frame this exercise without determining requirements that apply to a Western Australian business.

Check the baseline reflects ordinary work

  • Observe a suitable sample before changing the process.
  • Record the dates and number of cases examined.
  • Separate hands-on effort from time waiting for information.
  • Note unusual orders and other relevant conditions.
  • Ask staff which recurring difficulty the sample may miss.

Do not rely on memory alone. An owner may remember one particularly frustrating incident while overlooking a smaller issue that occurs frequently. Equally, a serious exception can matter even if it is uncommon; describe its significance separately.

Choose a recording method the team can maintain. A short tally or task sheet may be enough. The baseline should inform the decision without creating a second administrative burden larger than the problem.

Check the proposed change addresses a known cause

  • Identify why the delay or rework occurs.
  • Separate missing information from unclear responsibility.
  • Keep necessary verification and approval steps.
  • Choose one small change that can be explained.
  • State what will remain outside the test.

If staff repeatedly search for the collection name, a consistent field and labelling rule might help. If nobody is authorised to resolve a stock discrepancy, a faster label printer will not settle the decision. Match the response to the observed cause.

Ask the people doing the work to examine the proposal. They may identify a practical dependency that is absent from the owner’s view. This is consultation about the process, not an assumption that every suggestion must become a new feature.

Check success is defined before the test

  • Choose a measure connected to the original difficulty.
  • Define how each person will count it.
  • Include quality and unresolved exceptions.
  • Record additional preparation or maintenance work.
  • Set a review point and identify who decides next.

The government’s goal-setting guidance supports using a clear, measurable objective. For this exercise, success could involve fewer orders requiring staff to locate missing information, while still completing the required checks.

A faster average is not enough if errors increase or difficult cases are quietly excluded. Keep the quality of the result alongside the time measure so the team can explain the trade-off.

Check the test does not hide work elsewhere

  • Observe the task before and after the changed step.
  • Ask the person receiving the handover about the result.
  • Note new copying, correction or checking work.
  • Keep comparable cases separate from unusual ones.
  • Record changes in workload or staff availability.

A new intake rule might save preparation time while making customers repeat information they already supplied. A shared sheet might help the counter team but require another person to re-enter every order. These are part of the result.

Use actual counts and explain limitations. A small sample can reveal a useful operational lesson without proving an exact annual saving. Do not multiply a brief best-case result into a firm financial forecast.

Check that the trial instruction reached everyone who performs the task, including staff working different shifts. If half the team uses the old labelling rule and half uses the new one, the result will be difficult to interpret. Give the instruction a date, identify the current version and provide a simple place to record questions. This also helps distinguish a problem with the proposed process from a problem caused by inconsistent introduction.

Check the next spend follows the evidence

  • Summarise what improved and what remained difficult.
  • Identify whether a procedure change is sufficient.
  • Request a specific scope if specialist help is still needed.
  • Include staff time and continuing upkeep in the cost.
  • Keep the decision and supporting records together.

Retain the change only if it remains useful in ordinary work. If a new tool is justified, the observations now provide concrete requirements for a proposal. The business can spend on the unresolved need instead of buying a broad solution before understanding the task.