Technology delivers more value when built on strong foundations
Seven in ten digital transformations fall short of their objectives, according to research by Boston Consulting Group (BCG)1. The same research suggests that while technology matters, the factors that often determine success lie elsewhere, including an organisation’s operating model, processes, people and culture.
That raises a practical question for anyone planning a technology investment.
If your underlying processes are inefficient, fragmented or overly complex, will new technology solve the problem or simply digitise it?
Automation and AI are understandably appealing. Before choosing a tool, however, it is worth looking carefully at how the work actually gets done. Where are the bottlenecks? Which steps add value? Where is work duplicated? And does the process still make sense for the organisation today?
This groundwork does not mean putting technology investment on hold. Process review and technology planning can run side by side. What matters is that requirements come from a clear understanding of the process, so that technology is applied to the right process, designed in the right way and used to solve the right problem.
Start with the process, not the product
Before evaluating technology, map how the work happens today.
A process that looks simple on paper may rely on spreadsheets, emails, manual approvals, duplicate data entry and workarounds that have accumulated over several years. Processes are often designed one way, assumed to operate another and, in practice, carried out differently again.
Introduce technology without understanding this and there is a risk of digitising the workaround rather than addressing the underlying problem.
A practical starting point is to ask:
- What outcome are you trying to achieve?
- How does the process work today in practice?
- Which activities add value and which do not?
- What information do you capture, where is it stored and who owns it?
- Which steps should be simplified or removed before automation?
- What should the future process look like?
The answers become the basis for your requirements. Technology choices made against clearly defined requirements are easier to justify and less likely to require costly rework later.
Do not automate a bad process
Automation can deliver significant efficiencies, but an inefficient process does not become efficient simply because it is automated.
Consider an organisation where every expenditure request follows the same six-step approval process, whether it relates to a €200 software licence or a €50,000 investment.
Workflow technology could certainly help. It could route each request automatically, send reminders and maintain a record of every approval.
Yet the underlying process would barely change.
Further analysis might show that most requests are low value and routine, that several approvals duplicate existing checks, and that others are only required when particular risk, value or compliance criteria apply.
Rather than automating six approvals for every request, the organisation could redesign the workflow around appropriate risk and value thresholds. Routine requests could follow a shorter path, while only those requiring additional scrutiny would be escalated.
The technology then does more than digitise the existing process. It supports a process that has first been deliberately simplified and improved.
Look at the wider systems landscape
Processes rarely sit within a single application or department.
Consider client onboarding. Contact details might be entered into a Customer Relationship Management system, re-entered into the finance system for billing and tracked again in a spreadsheet for compliance checks, while supporting documents are stored in a separate repository.
When a client’s address changes, someone may then need to update it in several places, with uncertainty over which record should be treated as authoritative.
Adding a new onboarding tool on top of this simply creates another place where information needs to be maintained.
System decisions should therefore not be made in isolation.
Organisations need to determine how information will move between systems, where master data will sit and which integrations are required. Processes, data, reporting, governance and technology architecture should be considered together rather than expecting a single implementation to resolve wider operational issues.
Bring your people with you
The people who manage a process every day often know where it breaks.
Involving them early can help identify workarounds that may never appear in a procedure manual. Employees are also more likely to adopt a solution when they have had an opportunity to contribute to how it is designed.
Ownership matters too. Every process step, dataset and system should have clear accountability so that decisions do not stall and issues do not fall between teams.
Adoption should also be considered from the beginning.
Training, clear guidance and support following implementation can determine whether a new system becomes part of how people work or simply another tool they find ways around.
Check the four foundations
Before introducing new technology, organisations should consider four foundations:
- Process: Is the process clear, efficient and appropriately controlled?
- People: Do teams understand who owns what, and are they prepared for the change?
- Data: Is the information accurate, structured and consistently defined?
- Systems: How will the new solution fit within the existing technology environment?
Getting these foundations right does not slow transformation down. It can reduce the risk of expensive rework, unnecessary customisation and technology that employees struggle to use effectively.
How RSM Malta can help
The most successful technology projects start with a business problem, not a product demonstration.
RSM Malta’s Digital Advisory team helps organisations understand their requirements, distinguish critical needs from desirable features, improve underlying processes and assess the wider systems landscape before selecting or implementing technology.
Whether an organisation is reviewing existing processes, considering automation or preparing to implement a new business system, the starting point remains the same: understand the business first and let technology support it.
To discuss how your organisation can strengthen its processes and systems before making its next technology investment, contact RSM Malta’s Digital Advisory team.
Flipping the Odds of Digital Transformation Success