
Operating Cadence
Part of Scaling startup operations
Standardising a repeated process before adding staff
Trace a repeated task, agree its handoffs and exceptions, then identify the staffing need that remains.
Before adding staff to handle recurring work, agree how its common case should move from request to result.
Set the inputs, handoffs, checks and stop points a new colleague would need.
Then assess the work that still exceeds available capacity. A written procedure alone establishes neither that the process works nor that another person is needed.
Trace the repeated work
Choose one type of work that has occurred in several recent cases. Review its records with the people who handled it.
Identify the trigger, information needed, points of waiting and work that had to be corrected.
Keep legitimate variation, such as different customer requirements, separate from repeated confusion or duplicate effort.
Ask what each existing check protects before changing it. An approval may catch a material error or protect a customer promise. If nobody can explain what it decides, examine whether the decision can be made earlier or by a defined owner.
Set a route for the common case
A compact route should answer:
- Trigger:What starts this type of work?
- Input:What must be known, and where is the source record?
- Owner and handoff:Who does each stage, and what shows the next person it is ready?
- Check:How is the result compared with the agreed need?
- Stop point:Which missing detail or exception needs another decision?
Use a checklist, template or procedure that fits the task.
Australian Government business guidance suggests reviewing bottlenecks, errors, unnecessary approvals and responsibility gaps, then standardising suitable routine tasks.
Place the current route where the task begins and name the person who can correct it when the offer, system or approval boundary changes.
For cases outside the common route, state who decides the exception.
Standardising a Repeated Process Before Adding Staff
- TriggerWhat starts this type of work?
- InputWhat must be known, and where is the source record?
- Owner and handoffWho does each stage, and what shows the next person it is ready?
- CheckHow is the result compared with the agreed need?
- Stop pointWhich missing detail or exception needs another decision?
See whether another person can use it
Ask a suitable colleague to attempt a real or safe practice case with the route. Note where information remains in someone's head, access is missing or the colleague cannot tell whether to stop.
Check whether the receiver gets what they need without asking the sender to repeat work. Revise the route before relying on it to train a new starter.
One successful case shows that the route was usable for that case. Continue watching materially different cases and preserve training or supervision needed for the task.
Define the staffing need that remains
Identify which necessary stage still needs time or a skill the team lacks, when the need occurs and whether it is continuing or temporary.
Include the existing colleague's time to train and review a new person's work.
If routine cases still return for missing information, repair that handoff before defining a role around it.
If the route works but necessary work repeatedly exceeds confirmed availability, use the remaining tasks and skills to inform the staffing decision.
Key Considerations for Staffing Decisions
- Routine cases exceeding capacity
- Identify if ongoing tasks exceed available time/skill
- Training and review time required
- Include existing staff time to onboard new hire
- Recurring missing information
- Fix handoff issues before defining role
- Exception handling responsibility
- Define who approves deviations from common route



