Technology is often presented as the answer to organisational inefficiency. If the process is slow, introduce automation. If information is difficult to find, implement a new system. If decisions take too long, create a dashboard. If people are overwhelmed, add AI.<\/p>\n\n\n\n
There is logic in this. Technology can reduce manual effort, improve visibility, speed up communication and support better decisions. But there is also a serious risk. When technology is applied to a poorly designed process, it rarely fixes the underlying problem. More often, it makes the poor process move faster, scale wider and become harder to challenge.<\/p>\n\n\n\n
A bad process with new technology is still a bad process.<\/p>\n\n\n\n
In fact, it may become a more expensive, more complex and more deeply embedded bad process.<\/p>\n\n\n\n
Many organisations fall into the same trap. They assume the problem is the absence of technology when the real problem is poor process design.<\/p>\n\n\n\n
A process may be slow because responsibilities are unclear. It may produce errors because data is entered multiple times. It may frustrate staff because approvals are excessive. It may create delays because decisions are pushed too far up the organisation. It may generate rework because requirements are vague at the start.<\/p>\n\n\n\n
None of these issues are solved automatically by buying software.<\/p>\n\n\n\n
Technology can route an approval more quickly, but it cannot decide whether the approval is necessary. It can move data from one system to another, but it cannot guarantee that the data is meaningful, accurate or used properly. It can generate a dashboard, but it cannot ensure that anyone acts on the information. It can automate a task, but it cannot confirm that the task should exist in the first place.<\/p>\n\n\n\n
This is why many digital transformation programmes disappoint. They focus on the system before understanding the work.<\/p>\n\n\n\n
McKinsey has long argued that digital transformation requires more than technology deployment; successful transformation depends heavily on adoption, change management, iterative improvement and organisational alignment rather than a simple linear \u201cinstall and train\u201d approach.<\/p>\n\n\n\n
One of the core lessons from Lean thinking is that organisations must first understand value. What matters to the customer? What activities create that value? What activities add delay, confusion, cost or risk?<\/p>\n\n\n\n
If that question is not answered, technology can easily automate waste.<\/p>\n\n\n\n
For example, an organisation may introduce a digital form to replace a paper form. On the surface, this looks like progress. The form is now online. It can be submitted instantly. It can be tracked. It may even have automated reminders.<\/p>\n\n\n\n
But if the form still asks for unnecessary information, goes to the wrong people, requires duplicate approvals and feeds into a report nobody uses, the organisation has not improved the process. It has simply digitised the waste.<\/p>\n\n\n\n
The same applies to workflows, dashboards, robotic process automation and AI. If the process is poorly designed, automation may reduce the time taken to complete a step while leaving the overall problem untouched.<\/p>\n\n\n\n
A common observation in recent digital transformation commentary is that organisations often automate broken processes and then wonder why performance does not improve. The issue is not that the technology is weak; it is that the underlying workflow was never properly understood or redesigned.<\/p>\n\n\n\n
Poor manual processes are often visible. People complain. Paper piles up. Spreadsheets multiply. Managers chase updates. Customers wait. Errors are obvious.<\/p>\n\n\n\n
Once technology is introduced, the same problems can become less visible.<\/p>\n\n\n\n
A delay may now sit inside a workflow queue. A poor decision may be hidden inside a system rule. A workaround may become a shadow spreadsheet outside the official process. A quality issue may be buried in data that is collected but not reviewed. A bottleneck may be masked by a dashboard that shows activity rather than effectiveness.<\/p>\n\n\n\n
This creates a dangerous illusion of control.<\/p>\n\n\n\n
The organisation appears more modern because it has digital tools. However, the actual experience of staff, customers or patients may not have improved. In some cases, it may become worse because people now have to work around the system as well as the process.<\/p>\n\n\n\n
This is especially common when technology is implemented without frontline input. The system reflects what senior teams believe the process is, not how the process actually works.<\/p>\n\n\n\n
The arrival of AI makes this issue even more important.<\/p>\n\n\n\n
AI can summarise information, generate documents, classify data, identify patterns, support decisions and automate knowledge work. These capabilities are powerful. But AI also amplifies whatever system it is placed into.<\/p>\n\n\n\n
If the process has poor data, AI will use poor data. If the workflow has unclear accountability, AI may make accountability even more blurred. If staff do not understand the purpose of a process, AI-generated outputs may be accepted without proper challenge. If controls are weak, AI may introduce new risks around accuracy, bias, compliance, data protection and decision quality.<\/p>\n\n\n\n
In other words, AI does not remove the need for process improvement. It increases it.<\/p>\n\n\n\n
Emerging research on AI-enhanced business process automation shows that AI can improve operational capacity, but it can also introduce new process dynamics that require monitoring, refinement and redesign.<\/p>\n\n\n\n
This matters greatly in regulated sectors such as pharmaceuticals, medical devices, food manufacturing, healthcare and financial services. In these environments, the goal is not simply to make work faster. Processes must remain controlled, validated, traceable, compliant and capable of producing reliable outcomes.<\/p>\n\n\n\n
An AI-enabled poor process may not just be inefficient. It may become a compliance risk.<\/p>\n\n\n\n
Before selecting technology, organisations should ask basic process questions.<\/p>\n\n\n\n
What problem are we trying to solve?
What value should this process create?
Who is the customer or end user?
Where does the process start and end?
Where are the delays, errors, handovers and rework loops?
Which steps are genuinely necessary?
Which decisions require human judgement?
Which controls are required for quality, compliance or safety?
What data is needed, who owns it, and how is it maintained?<\/p>\n\n\n\n
These questions may seem obvious, but they are often skipped. Organisations move straight from frustration to solution. The conversation becomes: \u201cWhat system should we buy?\u201d rather than \u201cWhy does the process fail?\u201d<\/p>\n\n\n\n
That is the wrong starting point.<\/p>\n\n\n\n
The right sequence is:<\/p>\n\n\n\n
Understand the process. Simplify the process. Standardise where appropriate. Then digitise, automate or apply AI.<\/strong><\/p>\n\n\n\n Technology should enable a better process, not compensate for the absence of one.<\/p>\n\n\n\n Consider an approval process that takes too long. The obvious technology solution is to create an automated approval workflow.<\/p>\n\n\n\n That may help. But first, the organisation should examine why approvals take too long.<\/p>\n\n\n\n Are there too many approval levels? If these questions are ignored, the new system will simply move the same poor logic into a digital format. The approval will still take too long, but now the delay will be system-generated and more difficult to challenge.<\/p>\n\n\n\n A better approach would be to redesign the approval process first. Low-risk decisions might be delegated. Approval criteria might be clarified. Duplicate reviews might be removed. Required information might be built into the initial request. Only then should a digital workflow be introduced.<\/p>\n\n\n\n The technology then supports a better process rather than preserving a bad one.<\/p>\n\n\n\n When technology projects fail, organisations often blame users. They say people are resistant to change, reluctant to adopt new tools or unwilling to move away from old habits.<\/p>\n\n\n\n Sometimes that is true. But often users resist because the new technology makes their work harder.<\/p>\n\n\n\n Staff quickly recognise when a system does not match the reality of the job. They know when the workflow is unrealistic, when data fields are unnecessary, when reports are not used, when approvals are performative, and when a digital process creates more work than the manual version.<\/p>\n\n\n\n In these situations, resistance is not always a cultural problem. It may be useful feedback.<\/p>\n\n\n\n If people create workarounds, duplicate trackers or unofficial templates, the organisation should ask why. Workarounds are often symptoms of poor process design. They show that the formal process does not support the work effectively.<\/p>\n\n\n\n This does not mean every workaround is acceptable. In regulated environments, informal workarounds can create serious compliance and data integrity risks. But they should still be studied because they reveal the gap between process design and operational reality.<\/p>\n\n\n\n Organisations should stop treating digital transformation as a technology programme. It is better understood as process transformation enabled by technology.<\/p>\n\n\n\n This changes the emphasis.<\/p>\n\n\n\n The objective is not to implement a platform. The objective is to improve how work gets done.<\/p>\n\n\n\n The objective is not to automate activity. The objective is to improve flow, quality, reliability, decision-making and customer experience.<\/p>\n\n\n\n The objective is not to create more dashboards. The objective is to make better decisions faster.<\/p>\n\n\n\n The objective is not to use AI because it is available. The objective is to apply AI where it improves value, reduces risk or strengthens capability.<\/p>\n\n\n\n Process mining, workflow analytics and AI-supported business process management are all developing rapidly, but the evidence points toward the same conclusion: technology is most valuable when it is connected to process understanding, governance and continuous refinement. Research on AI-augmented business process management describes future systems as more adaptive, proactive, explainable and context-sensitive, but this still depends on well-understood business processes and clear management of process lifecycles.<\/p>\n\n\n\n Before implementing new technology, organisations should complete a process readiness review.<\/p>\n\n\n\n This should include five practical steps.<\/p>\n\n\n\n First, map the current process as it actually operates, not as it is supposed to operate. Include informal workarounds, emails, spreadsheets, duplicate systems and approval delays.<\/p>\n\n\n\n Second, identify the root causes of poor performance. Do not assume that slowness means a lack of automation. The real cause may be unclear ownership, poor input quality, excessive variation or unnecessary complexity.<\/p>\n\n\n\n Third, remove obvious waste before digitising. If a step does not add value, meet a compliance need or reduce risk, challenge whether it should exist.<\/p>\n\n\n\n Fourth, define the future-state process. Technology should be selected to support this improved design, not to preserve the current-state problem.<\/p>\n\n\n\n Finally, build governance around the new workflow. Decide who owns the process, who owns the data, how performance will be measured, how exceptions will be managed and how the process will continue to improve.<\/p>\n\n\n\n Technology is not the enemy of process improvement. It is one of its most powerful enablers.<\/p>\n\n\n\n But technology is an amplifier. It amplifies clarity or confusion. It amplifies good data or poor data. It amplifies effective decisions or weak governance. It amplifies well-designed workflows or broken ones.<\/p>\n\n\n\n That is why the future of operational excellence will not be defined by technology alone. It will be defined by the ability to combine process thinking, systems thinking, data, digital tools, AI and human judgement.<\/p>\n\n\n\n The organisations that succeed will not be the ones that simply buy the newest systems. They will be the ones that understand their processes deeply, simplify them intelligently and then use technology to make good work flow better.<\/p>\n\n\n\n Technology will not fix a poorly designed process.<\/p>\n\n\n\n But a well-designed process, supported by the right technology, can transform how an organisation performs.<\/p>\n","protected":false},"excerpt":{"rendered":" Technology is often presented as the answer to organisational inefficiency. If the process is slow, introduce automation. If information is difficult to find, implement a new system. If decisions take too long, create a dashboard. If people are overwhelmed, add AI. There is logic in this. Technology can reduce manual effort, improve visibility, speed up […]<\/p>\n","protected":false},"author":1,"featured_media":1930,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1929","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/leansigma.ie\/index.php?rest_route=\/wp\/v2\/posts\/1929","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/leansigma.ie\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/leansigma.ie\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/leansigma.ie\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/leansigma.ie\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1929"}],"version-history":[{"count":1,"href":"https:\/\/leansigma.ie\/index.php?rest_route=\/wp\/v2\/posts\/1929\/revisions"}],"predecessor-version":[{"id":1931,"href":"https:\/\/leansigma.ie\/index.php?rest_route=\/wp\/v2\/posts\/1929\/revisions\/1931"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/leansigma.ie\/index.php?rest_route=\/wp\/v2\/media\/1930"}],"wp:attachment":[{"href":"https:\/\/leansigma.ie\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1929"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/leansigma.ie\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1929"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/leansigma.ie\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1929"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}A simple example: the approval process<\/h3>\n\n\n\n
Are approvers unclear about what they are approving?
Are low-risk decisions treated the same as high-risk decisions?
Are requests often incomplete when submitted?
Are approval criteria defined?
Are people approving because they add value, or because they have always been included?<\/p>\n\n\n\nPoor process design creates digital resistance<\/h3>\n\n\n\n
From digital transformation to process transformation<\/h3>\n\n\n\n
What organisations should do before investing in technology<\/h3>\n\n\n\n
Conclusion: technology is an amplifier<\/h3>\n\n\n\n