Practical perspectives on the choices behind better digital operations. No crystal balls, just useful questions for people running real businesses.
Automation is most useful when it removes a genuine obstacle—not when it simply makes a confusing process happen faster.
Pick one handover that happens repeatedly. Write down what information needs to move, who needs it next and where mistakes or waiting tend to occur. Then ask whether the process can be simplified before anything is automated.
A small, well-understood change is easier to test and easier for the team to trust. Start with one case, agree what better looks like and keep a route for a person to step in when the unusual happens.
Talk through an idea ↗Security is not switched on by buying a new platform. For a smaller business, a handful of consistent habits can make the everyday environment more dependable.
Begin with the basics: make sure every person has their own account, use multi-factor authentication where available, remove access promptly when roles change, and understand how files are backed up and restored.
Review who can access what, keep devices and software current, and make sure someone knows what to do if an account looks compromised. Write these steps down so they do not live in one person’s memory.
Talk through an idea ↗You do not need a twenty-page specification to start a productive software conversation. A clear description of the problem is more useful than a premature list of features.
Describe the people involved, the task they are trying to complete, what makes it difficult today and how you will recognise an improvement. Include examples of common and unusual cases.
Then note the tools and information already in play, any constraints, and what you do not yet know. A good discovery conversation can turn that first draft into a sensible scope without pretending every answer is already settled.
Talk through an idea ↗A technology plan should help a business make decisions, not become another shelf document. Keep it connected to the priorities that matter this year.
List the operational goals first: perhaps faster service, fewer errors, a new location or more reliable reporting. Map the systems those goals depend on and note where manual work or risk is concentrated.
Prioritise the smallest useful changes, give each a clear owner and revisit the plan regularly. The right next step may be a process improvement, training or removing a tool—not always buying something new.
Talk through an idea ↗