Digital operations gaps often appear between tasks rather than inside a single application. An Albany business may receive an enquiry successfully but lose track of who should answer it. A system may store a completed document while the next person still does not know it is ready.
The problems and solutions below help find those gaps in an existing process. Start with how work actually moves today. A new purchase can be considered later if the evidence shows a need for it.
Problem: The process exists only in someone’s memory
A capable staff member may know the ordinary sequence without having written it down. When they are away, others discover missing instructions and informal exceptions. The problem becomes visible during absence, even though the gap existed before it.
The solution is to follow one ordinary task with the person doing it. Ask what starts the work, which information is needed, who decides and how completion is known. Record the sequence in plain language rather than trying to document every possible feature of the software.
Problem: A handover has no clear signal
Sending a file does not necessarily tell the next person what to do. A message may lack the required action, current version or expected review point. Work then waits while both people assume the other owns it.
Define the handover: what is ready, who receives it and what they need to do. Keep the relevant record in an authorised shared location with an identifiable current version. Avoid solving the problem by sending additional uncontrolled copies to everyone.
Problem: Status labels mean different things
One person’s complete may mean the draft is ready; another may interpret it as approved and sent. List the statuses used and the event each represents. Test the wording with people on both sides of a handover.
If a customer sees a status, check that it matches the service’s actual commitment. A request received is different from a confirmed booking. The gap may be in language and responsibility rather than the application itself.
Problem: Information is copied without a clear source
Trace where an important detail originates and which record should remain current. If staff copy it into several systems, ask how corrections reach each location. The aim is not to centralise everything blindly, but to understand the purpose of each copy.
The ASD’s ACSC business and customer data guidance recommends understanding what information is held, where it is stored and how it is used. It also calls for appropriate access and retention decisions. These principles help examine a process without creating another unnecessary data collection.
Problem: The ordinary path hides exceptions
A workflow can look complete until a request lacks information, a customer changes their mind or a system is unavailable. Ask staff for the types of exceptions they actually encounter. Avoid inventing an elaborate rare case before addressing repeated everyday difficulty.
- How is an exception identified?
- Who decides what happens next?
- What information does that person need?
- How is the customer or colleague informed?
- Where is the decision recorded?
- How does the work return to the ordinary process?
Keep uncertain transaction outcomes separate from confirmed failures. A repeat action may have consequences, so ask how staff verify what happened before trying again. Obtain technical help when the underlying behaviour is unclear.
Problem: Staff rely on workarounds nobody reviews
A personal spreadsheet or repeated message can become a way to make a difficult system usable. Ask why the workaround exists before instructing staff to stop. It may reveal a missing field, inaccessible function or unclear responsibility.
Assess the workaround’s information and security implications. A useful temporary fix still needs appropriate access and retention. Decide who will replace it or maintain it so temporary does not become unowned and permanent.
Problem: The gap is blamed on a lack of training
Training may help, but it cannot fix an undefined decision or a tool that lacks a necessary capability. Ask a staff member to explain the difficult step. Distinguish not knowing the method from a method that does not support the task.
For an Albany operation working with remote suppliers, clarify who can answer operating questions and who handles technical faults. Confirm support arrangements in relevant hours instead of assuming one person can resolve everything.
Solution: Prioritise one gap and check the result
Choose a gap that affects a meaningful task and define a limited correction. It might be clearer wording, a named owner, a different handover or a technical change. Record why the correction should address the observed problem.
Test it appropriately and check whether staff can complete the work and understand the outcome. Include any new effort or unresolved limitation. Do not infer that every business result improved because one step became simpler.
Keep the process reviewable
Save the short workflow, important decisions and open questions together. Update it when systems or responsibilities change. Finding gaps in digital operations helps an Albany business make a specific improvement, rather than repeatedly purchasing tools for a problem it has not yet described.