Selecting digital features in Albany should end with a process staff can perform, rather than a long list of functions somebody has purchased. A useful handover connects each feature to a task, a person and a recognisable outcome. Follow these steps before committing to a new tool or adding functionality to an existing system.
Step 1: choose one task for the handover
Define the task in everyday language, such as receiving a service enquiry and giving it to the appropriate staff member. Avoid starting with a product category or a request for every available automation. Specify where the task begins and what counts as a completed handover, so the selection has a clear boundary.
Step 2: watch how the work happens now
Ask the people performing the task to explain the current sequence, including interruptions and work outside the main screen. Record what they need to know before moving the task forward. The UK Government’s user research planning guidance recommends turning assumptions into research questions. Use that as a practical research approach, rather than an Australian legal requirement or a fixed research timetable.
Step 3: identify the handover information
Separate information needed for the next action from details collected merely because a field exists. For the enquiry example, staff may need the request type, an appropriate contact method and the person responsible for following up. Decide which information belongs in the working record and which should not be copied into a general team message.
Step 4: translate needs into feature tests
Write a small test for each proposed feature. If the need is to find unassigned enquiries, the test should show whether a staff member can identify those records and take the permitted next step. A colourful overview screen is not enough if the relevant item remains difficult to locate.
Use the same tests when comparing options. That prevents an impressive demonstration from changing the selection criteria halfway through the decision.
Step 5: separate essential functions from additions
Mark the functions required to complete the chosen task, then list useful additions separately. An optional reporting chart should not delay resolving a missing assignment or an unclear status. Record why each essential feature matters, so staff can distinguish a necessary part of the process from a preference that could change later.
Step 6: test the ordinary path with invented records
Prepare clearly fictional enquiries and follow them from arrival to assignment and completion. Do not use live customer details simply to make a demonstration look realistic. Check what staff see at each point and whether the record’s status matches what has actually happened. A message being sent is different from the next person accepting the task.
Step 7: practise an exception
Add a case with missing information, an incorrect assignment or a staff member who is unavailable. Decide where the work waits and who can resolve it. The handover should explain how staff recognise an exception without inventing a completion or repeatedly sending the same customer request to different people.
Step 8: assign suitable access
Identify who needs to view, change or administer the system. ASD’s access-control guidance recommends permissions matched to duties and reviewing them as roles change. Give the handover role-specific instructions rather than teaching everyone through an administrator account with powers they will not have during ordinary work.
Step 9: write the shortest complete working instruction
Describe the starting point, action and result in the words staff use. Include enough context to choose the correct record, not just the instruction to press a button. Screenshots can help locate controls, but pair them with text explaining the decision. Otherwise a small layout change can make the entire guide difficult to follow.
Keep the working note structured around:
- What the staff member is trying to complete.
- Which information and permissions they need.
- How to recognise completion or an exception.
- Who receives a question that remains unresolved.
Step 10: ask another staff member to perform the task
Let someone who did not write the instructions try the fictional cases using the access intended for their role. Observe where they hesitate and ask what they expected to happen. Revise the explanation rather than treating a question as evidence that the person failed to learn. Check whether they can identify an unfinished task as well as complete an ordinary one.
Step 11: name the person who maintains the handover
Assign ownership of the guide, feature settings and escalation contacts. Record when instructions need review, such as after a changed workflow or interface. Remove obsolete copies from normal use while retaining any records the business needs. Staff should know which version to follow without comparing several conflicting screenshots.
Step 12: decide on the feature using the trial evidence
Review which tasks people could complete, what still needed explanation and what extra administration the feature created. Keep unresolved points visible before purchase or rollout. A successful digital handover gives Albany staff a repeatable way to do the work and recognise its limits, with features chosen to support that process.