Before booking another technology course, check why staff are having difficulty with the work they already do. A repeated mistake may reflect missing instruction, but it could also come from an unclear approval rule, unsuitable access or two systems showing different information. Training cannot reliably fix a process the business has not agreed on.
This checklist helps Albany employers find gaps in an existing digital workflow. Use it with the employees who perform the task, then decide whether the next action is instruction, a process change or technical assistance. Keep the exercise practical and focused on improvement.
Check the task has a defined finish
- Name one task, such as recording a customer cancellation.
- Identify where the request arrives and where the result belongs.
- Write down what a correctly completed record contains.
- Confirm who has authority to make the change.
Compare these expectations with what staff have actually been told. If one person considers a task finished after sending an email and another expects a status change in the booking system, the business needs a shared rule. Do not describe that disagreement as a lack of digital confidence.
Check the instructions match the current system
- Open the procedure on the device employees normally use.
- Compare screen names and options with the live version.
- Look for undocumented steps known only to experienced staff.
- Record who will maintain the instructions after changes.
Old screenshots or unexplained abbreviations can make an otherwise simple task difficult. A long document is not necessarily a usable guide during a busy shift. Ask an employee unfamiliar with the procedure to explain where they would start, without turning the exercise into an assessment of their worth or intelligence.
Check what staff can do independently
- Observe a routine example using suitable sample information.
- Note where help is requested and what question is asked.
- Distinguish uncertainty from an actual error.
- Include a common exception, such as an incomplete request.
Explain the purpose beforehand and avoid collecting unnecessary personal performance data. The Digital Transformation Agency’s research guidance describes observing tasks and understanding staff workarounds. Its public service design principles can inform this exercise; they are not a mandatory private-sector training framework.
Check permissions before labelling a skills gap
- Confirm each role has the access necessary for its tasks.
- Check whether approval is required from another person.
- Identify missing access, rather than sharing somebody else’s login.
- Ask technical support about unexplained permission errors.
An employee may know the correct action and still be unable to perform it. Giving everyone administrator access is a poor shortcut. Separate a legitimate role requirement from a configuration fault and have the authorised person arrange the appropriate change. Make sure training explains when to stop and ask, especially around payments or sensitive records.
Check the underlying knowledge
- Ask what important statuses and fields mean.
- Confirm staff know which record is authoritative.
- Check whether they understand the effect of saving or sending.
- Identify the safe route for correcting a mistake.
Knowing which button to press is different from understanding the outcome. For example, changing an enquiry to accepted may trigger a message or commit staff time. Teach the business meaning alongside the screen action. Where a rule is unclear, resolve it with the responsible manager before building a lesson around it.
Check security knowledge in the same workflow
- Confirm staff recognise unexpected login or payment requests.
- Make reporting contacts easy to find.
- Practise checking a suspicious request through a trusted route.
- Ensure sample exercises do not expose real credentials.
The Australian Signals Directorate recommends ongoing cyber security education and clear reporting arrangements. Relate the instruction to ordinary work, such as a message requesting changed customer details. Attendance at a session does not prove that the behaviour is understood or that the system is secure.
Keep a gap log with the task, observed difficulty and next action. Write descriptions such as unable to identify the latest attachment rather than careless or bad with computers. This makes it easier to test whether clearer version labels, instruction or a different interface resolves the difficulty, without assuming the cause in advance.
Check the action plan is specific and achievable
- Group gaps into instruction, process and technical issues.
- Choose a small number of important learning outcomes.
- Allocate practice time and a person who can answer questions.
- Arrange a later task check to see what improved.
Business.gov.au’s staff development guidance supports identifying skills and planning suitable training. Match the format to the gap: a short task demonstration, coached practice or specialist instruction may each suit different needs. Confirm the trainer understands your version of the product and the actual staff roles.
For an Albany team working with remote support, agree on WA session times and how employees can ask follow-up questions. Keep a short record of the agreed process and unresolved issues. The useful result is a clearer task that staff can perform appropriately, with the remaining technical or management work assigned to someone who can resolve it.