In this fictional example, Nina runs a small Albany service business and Callum helps coordinate its administration. Their proposed week includes customer appointments, unanswered questions, record keeping and a longer-term improvement that keeps being postponed.
They want a clearer way to separate urgent tasks from important work. The example describes a planning method they could try, not an account of actual staff, customers or measured productivity results.
Nina and Callum put the work in one view
Nina would begin with the work already promised, while Callum would collect requests from the places where they currently arrive. They would avoid assuming that the loudest notification represents the most consequential task.
Each item would become a concrete action. An unclear note about a customer would be replaced with a description of what needs deciding or answering. They would retain the relevant context without copying unnecessary personal information into a widely shared planning tool.
They ask what makes an item urgent
For each apparent deadline, the pair would identify its source and the consequence of delay. A confirmed appointment, an agreed response and an internal preference would remain distinguishable.
Callum would check ambiguous dates before moving other work around them. A message marked urgent would receive attention, but the label alone would not establish its authority or priority. They would also keep safety concerns and suspected account misuse outside an ordinary weekly queue, following the appropriate response rather than waiting for a planning review.
They explain why the important work matters
Nina would identify the recurring problem behind the postponed improvement. In this example, the proposed project is to make service information clearer so staff need not repeatedly explain the same basic details.
Business.gov.au’s goal-setting guidance recommends defining a specific, relevant goal and considering the resources and timeframe. Nina and Callum would use that approach to explain the purpose of the project without promising it will automatically increase revenue or remove every customer question.
They separate consequences from convenience
The fictional pair would compare an easily completed cosmetic task with a less visible task that supports a real commitment. They would ask what happens if each waits, rather than treating quick completion as proof of importance.
A useful priority note would contain:
- the task and the outcome it supports;
- the genuine time constraint, if one exists;
- the consequence of postponing it;
- the person able to make the necessary decision.
This note would support judgement. It would not become an automatic score that overrides new information.
They protect a realistic piece of improvement work
Instead of reserving an unrealistic block for rewriting everything, Nina would choose a small approved service description as the first piece. Callum would gather the existing questions that indicate where clarification may help.
They would allow time for review and agreement, not only typing. Their schedule would also account for actual appointments and travel between commitments. The improvement would have a realistic place in the week while remaining adjustable if a genuine urgent matter arose.
They make responsibility and waiting visible
Nina would approve the service information; Callum would prepare the draft and record unresolved questions. A request awaiting Nina’s decision would be marked as waiting rather than repeatedly reassigned to Callum as unfinished writing.
They would identify dependencies before assuming a task can be completed in a spare moment. If an external answer is needed, they would note who is following it up and when it is useful to check again. Clear ownership would avoid everyone watching the same reminder while nobody takes the next action.
They choose technology after clarifying the method
The pair could begin with a simple shared list suited to their existing arrangements. Business.gov.au’s digital-tools guidance identifies task-allocation tools and recommends choosing features around actual needs.
Nina and Callum would not buy a more complex tool merely to label items urgent or important. They would first check whether their method is understandable. If testing software later, they would use appropriate sample information and retain access controls, rather than treating broad account access or constant notifications as necessary for coordination.
They decide what can move when the week changes
If a new request arrives, the fictional team would examine what it displaces. They would distinguish accepting a new commitment from simply adding another item to an already full day.
Where a promised time cannot be met, Nina would consider the actual agreement and communicate through the appropriate route. Silently changing an internal date would not change a commitment to someone else. A lower-priority task could be deferred explicitly so that the plan continues to describe a possible week.
They review the decisions rather than the number of ticks
After a future trial, Nina and Callum could examine which deadlines were genuine, which tasks repeatedly interrupted important work and which decisions caused unnecessary waiting. Those would be observations to collect, not results already established here.
They would adjust the method using that evidence. The purpose is a clearer relationship between promises, priorities and available time, so the work that matters has a place alongside the work that cannot reasonably wait.