Build a thirty-day operating system

A book becomes useful when it changes the next operating week. Do not begin by making a complex dashboard. Begin with a small number of accurate measures and a scheduled decision meeting.

The seven operating measures

1. Cash available: reconciled and net of reserved obligations.
2. Minimum thirteen-week projected cash: the lowest forecast position and its date.
3. Outstanding receivables: including overdue amounts and ageing.
4. Contribution performance: by product or service, consistently calculated.
5. Committed obligations: bills, payroll and taxes coming due.
6. Demand evidence: qualified enquiries, orders, repeat purchases and validation results.
7. Owner capacity: workload, recovery and critical single-person dependencies.

Each measure needs a source, an owner, update frequency and action threshold. A metric with no next action is decoration.

Thirty-day sequence

Week one — establish reality. Reconcile records, list customers and obligations, write the one-page business model and complete the owner workload map. Do not buy new systems yet.

Week two — make cash visible. Calculate core contribution and approximate break-even, build the thirteen-week forecast, document the next payment dates and identify any funding or compliance gap. Validate assumptions with actual records.

Week three — test and simplify. Choose one uncertain customer question for a low-cost seven-day experiment. Select one repeated administrative task for an AI-assisted pilot, using approved data only. Document a handoff procedure for a task previously dependent on the owner.

Week four — compare and decide. Review experiment evidence, the forecast-versus-actual cash variance, time saved after checking and owner capacity. Decide what to continue, change or stop. Assign no more than three major improvements for the following month.

Weekly 30-minute meeting

Minutes 0–5: owner capacity and urgent commitments. Minutes 5–15: receipts, outflows, forecast minimum and overdue invoices. Minutes 15–22: customer evidence and delivery constraints. Minutes 22–27: improvement tests and AI quality. Minutes 27–30: decisions, owners and due dates. Record actions as what | why | owner | due | evidence of completion.

Decision rights and escalation

Write who can approve routine purchases, customer discounts, public communications, payments, system access and non-standard commitments. Set limits proportionate to business size and risk. Schedule escalation when forecast cash falls below the reserve floor or when compliance deadlines may be missed.

One-page review template

What changed this week? Summarise facts. Which numbers moved? Show actual and plan. What may fail next? Name the assumption. What did we learn? Record customer evidence or trial results. What will we do? Assign the next action. How will we know? Define measurable evidence.

A considered improvement principle

Change the smallest process that removes a real constraint. Adding a customer channel, technology product or staff member without knowing what is constraining performance can add cost and cognitive load. Prefer documented, reversible trials until the evidence supports a larger commitment.

Workbook completion checklist

Maintain an owner capacity map, one-page offer brief, funding estimate, contribution and break-even worksheet, thirteen-week forecast, compliance calendar, AI policy and a 30-day decisions log. These are living records; review them, do not file them away.

KEVOS independently authored practical business learning material. This is general information, not personalised legal, tax or investment advice.

Extended study: professional practice

Build a management rhythm without bureaucracy

The purpose of a weekly review is to make fewer avoidable surprises, not create meetings. Keep one agenda with consistent sections: essential commitments, cash outlook, customers, delivery constraints, improvement work and decisions. Circulate simple evidence beforehand. Timebox discussion and record an owner for every agreed action. If a point cannot be resolved because information is absent, assign evidence gathering rather than debating assumptions. Review the effectiveness of the meeting quarterly. If decisions do not change, remove the measure or improve its interpretation.

Build a dashboard with provenance

Every metric needs a plain definition, source and update date. ‘Revenue’ might mean invoiced sales, recognised revenue or received cash; do not permit an unlabeled chart to mix them. The dashboard should show actual versus prior expectation, trend, meaningful threshold and next action. Cash, receivables, contribution, late delivery, qualified demand and owner capacity cover different risks. Do not summarise them into an invented single ‘business health’ score without validating weights. A short note explaining a material variance can be more valuable than a sophisticated chart.

Use decision records for irreversible commitments

Before hiring, purchasing significant equipment, adding an expensive subscription or entering a long contract, document the problem, options, expected benefit, cash commitment, assumptions, risks, exit costs, approval and review date. Identify a smaller reversible experiment if possible. After the decision, compare outcomes with the original assumptions rather than rewriting the business case. Keep decision records confidential where they contain commercial details. This discipline improves organisational memory and makes management less dependent on one person’s recollection.

Link owner capacity to financial decisions

Growth plans change more than revenue. A new contract may require production hours, working capital, more customer communication and special compliance obligations. Add a simple capacity review to every major sales or investment decision. Who will deliver? What existing work will be displaced? When will customer money arrive? Which person owns quality? If the owner must work nights indefinitely to fulfil the plan, the forecast is operationally incomplete. Consider an explicit cost of replacement labour and a realistic recovery buffer alongside projected profit.

Run one experiment at a time where evidence is weak

When a business launches multiple promotions, changes pricing, modifies its website and introduces AI concurrently, it becomes difficult to explain any performance change. Select one principal business hypothesis for each short test, with a clear baseline, outcome and decision rule. Related operational improvements may proceed separately if their measures are independent. Document confounding factors such as seasonality or unusual customers. A failed test may justify an altered experiment, but it should not be reported as a success simply because activity increased.

A practical 30-day handover

At the end of a month, assemble an operating packet: reconciled financial position, thirteen-week cash forecast, open customer and supplier commitments, unresolved risks, owner workload map, compliance schedule, AI pilot results and top three next actions. The packet should permit a trusted authorised manager to understand current priorities without a long oral briefing. Test it by asking someone unfamiliar with the details to locate the next due payment and the current delivery status. Repair missing explanations and access problems while the original owner is still available.

Review and reset the system

Ask which measure helped a real decision, which process saved actual time, which commitment was missed and which procedure created unnecessary work. Carry forward unresolved actions with owners and dates, but archive completed items rather than allowing the list to become a monument to past activity. Revisit compliance references whenever legislation or staffing circumstances change. A sustainable business system is lightweight, accurate and responsive; it does not depend on collecting more data than anyone can use.

Primary learning references

• Australian Government small-business guidance.
• ATO for current Australian tax and super requirements.
• Fair Work Ombudsman for employment requirements.

Study note: Worked numbers and scenarios are educational illustrations, not actual client records or promises of commercial results.

Implementation laboratory: management reviews and decision records

Define a realistic starting point

Before changing anything, create a baseline record dated at the beginning of the exercise. State what is currently happening, who owns the process, what happens when it fails, and what evidence is available. For this topic, give special attention to status meetings producing no changed decisions. A single recent incident is not necessarily a representative trend, so look for several examples where available. If the process is entirely new, say that there is no observed baseline and use a synthetic rehearsal rather than describing assumptions as history.

Write a one-sentence objective in the form: “Over the next four weeks we want to improve [measurable outcome] while maintaining [quality or safety requirement].” Avoid using a vague outcome such as working harder, being more professional or creating growth. A useful objective contains an observable difference and a control that prevents apparent efficiency from concealing new problems.

Identify the people and decision boundaries

Consider the different responsibilities of the owner, finance, delivery and customer lead. In a microbusiness one individual may hold several roles, but those roles should still be conceptually separated. Identify who prepares the information, who checks it, who approves a change, who carries it out and who records the result. If outside advice is required, identify the point at which the process must pause for that advice. Avoid giving software or an AI assistant implicit authority to make legal, financial or employment commitments.

Prepare a short responsibility table with the columns Input owner, Process owner, Independent check, Final approver and Backup contact. For a sole trader, the independent check may be a periodic external professional review instead of a second employee. The objective is accountability, not artificial complexity.

Build a small evidence package

An evidence package should contain the current procedure, one or more real or simulated examples, relevant figures, the expected output and a list of known exceptions. Remove confidential personal information from teaching materials. For a real business, store operational evidence in an approved private location with access limited to the people who need it. Link each figure to its source instead of copying it manually between documents without a reference.

Separate observed facts from forecasts and estimates. An observed payment date is a fact; a future customer’s payment is an assumption, even when it is a reasonable one. A change in accounting classification or business circumstances may alter which facts are comparable. Mark missing information explicitly and assign responsibility for collecting it.

Work through an exception rather than only the easy case

Normal scenarios are useful for learning the steps; exceptions test the quality of the process. Imagine that status meetings producing no changed decisions occurs just before an important customer or statutory deadline. Which facts would you need immediately? Which decisions can be made under the existing authority? Which tasks could be paused safely? How would the customer, supplier, employee or adviser be informed where appropriate? What written record would be necessary to explain the response later?

Run the situation twice. First follow the present procedure. Then follow the improved procedure and compare clarity, elapsed time, error risk and confidence in the information. Note where the new approach merely moves work to another person. An effective improvement should not reduce one person’s workload by hiding costs or risk elsewhere.

Choose a review metric and define it precisely

The principal indicator for this exercise is action closure, cash surprises and sustained workload. State the numerator, denominator, measurement period and data source where applicable. Decide what level of movement would be meaningful before seeing the results. Pair a speed or output measure with at least one quality indicator. For example, a process that closes actions more quickly but increases uncorrected mistakes has not clearly improved.

Review results using a small table: Period, Baseline or target, Actual, Difference, Reason, Corrective action and Owner. Do not infer causation from a single good week. Demand, seasonality, staff absence or unusual orders can affect outcomes independently of the process change.

Put an approval gate before an irreversible action

The major decision boundary is new hires, large contracts and major system investment. Before crossing it, prepare a concise decision note: the available options, evidence, total cash exposure, dependencies, legal or customer obligations, reversibility, downside risk and the person authorised to approve. If information is missing, a smaller pilot may be preferable to a permanent commitment. Refusing to invent an uncertain input is a sign of a trustworthy process.

Agree a review date and an exit rule. An exit rule might limit an experiment to a fixed amount of money, a defined sample size or a certain number of weeks. The rule should be proportionate to the risk rather than copied from another business. Keep written approval evidence for consequential commitments and use specialist advice where required.

Complete a four-week practice cycle

First week: Describe the present method and collect baseline evidence. Do not redesign everything at once. Check whether the records can support action closure, cash surprises and sustained workload and choose one narrow intervention.

Second week: Create the new procedure, checklist or template. Test it on a simple example and on a difficult exception. Document each correction and identify whether missing inputs or ambiguous responsibility caused the problem.

Third week: Conduct a limited live pilot where appropriate and authorised. An example of a suitably narrow outcome for this topic is a repeatable thirty-minute operating review. Measure time, quality and unintended consequences. Keep the ability to return to the prior process if the pilot fails.

Fourth week: Compare results, collect feedback from the people affected and write a decision: adopt, refine, retest or stop. Assign an owner and future review date. If no clear benefit appears, keep the evidence but do not claim success. The purpose of a pilot is to learn accurately, not to defend the original idea.

Reflection and transfer

Explain the principle to someone who has not read the chapter, without using jargon. Ask them to reproduce the calculation, review or process from your instructions. Any point requiring your verbal rescue is an opportunity to improve the documentation. Then consider where the same logic applies in another process: setting clear inputs, acknowledging uncertainty, naming decision rights, measuring outcomes and checking the effect on both money and people.

Completion evidence: a dated baseline, one-page procedure, exception test, recorded results and approved next action. These five records convert general business advice into a verifiable operating improvement.