“It requires a very unusual mind to undertake the analysis of the obvious.” — Alfred North Whitehead, Science and the Modern World, 1925
A founder I worked with some years ago had just finished rolling out a significant technology investment. The project included a new CRM system, an integrated reporting dashboard, and automated workflows across the customer-facing parts of the business. It had taken six months to complete, had consumed a fair amount of management attention, and had not been inexpensive. By most measures it was successful: the systems worked, people were using them, and information was easier to access than it had ever been before.
Six months later, though, he told me the business felt exactly the same. Decisions were still landing on his desk. Managers were still escalating issues that should probably have been resolved elsewhere. The same conversations seemed to recur every few weeks, albeit now accompanied by better data and more sophisticated reports. He had more information arriving more quickly, but he remained the person everyone was waiting for. Nothing had fundamentally changed in how the business operated or who was responsible for what.
He assumed the technology had underperformed. It hadn’t. The technology had done precisely what it was designed to do. The problem was something else entirely, and it had been there long before the system was installed.
Over the years, I have seen versions of that conversation many times. The technology changes. Sometimes it’s a CRM system. Sometimes it’s workflow automation. More recently it’s often AI. The pattern, however, is remarkably consistent. Businesses invest in technology expecting change, only to discover that some things become easier while other things remain stubbornly the same.
That pattern feels particularly relevant today. Hardly a day passes without another AI tool being launched, another business automation platform being promoted, or another prediction about how dramatically business is about to change. Much of the discussion focuses on technology itself. The more interesting conversations often begin when you start looking at what the technology reveals about the business installing it.
The Noise Before the Decision
The technology landscape facing most SME founders today is genuinely overwhelming: the volume of platforms, AI tools, automation options, workflow systems, and integration layers available to a business of almost any size has expanded beyond any individual’s ability to evaluate thoroughly. As a result, technology has become one of those subjects that almost every business owner feels they need to think about, and try to keep up with, whether they want to or not. Even leaders who are not naturally interested in technology can find themselves wondering whether they are paying sufficient attention to it.
Vendors are capable and persuasive. Demonstrations are compelling. Every conference, webinar, industry publication and LinkedIn feed seems to contain another example of a business achieving remarkable results through some new platform, system or capability. Individually, these stories are easy enough to evaluate. Collectively, they create a persistent sense that something important may be happening elsewhere that the business might be missing out on.
Over time, that feeling can begin to influence the conversation. The question becomes which technology to invest in, which platform to select, or which capability to prioritise. Those are entirely reasonable questions, but they often arrive before a more fundamental one has been explored properly.
What exactly is the business trying to gain?
The answer is not always as obvious as it first appears. A business may believe it needs better reporting when the real frustration is slow decision-making. It may believe it needs greater visibility when the underlying issue is uncertainty about who owns a particular outcome. It may believe it needs automation when what it is really experiencing is the accumulated weight of processes that nobody has properly examined for years, coupled with a structure that has not grown with the business.
Technology tends to become the focus because it is tangible. Systems can be demonstrated. Features can be compared. Vendors can explain precisely what their products will do. The underlying organisational questions are often less clear and considerably harder to discuss.
That may be one reason why some technology investments create lasting change while others deliver benefits that feel smaller than expected. By the time many leaders reach a technology decision, they have already spent months surrounded by competing claims, competing priorities and competing possibilities. The pressure to choose something can become almost as strong as the need to choose well.
When that happens, the technology decision itself can begin to feel like progress. Whether it was addressing the most important issues in the business is a different question altogether.
Deployment Is Not Impact
One of the reasons business technology strategy discussions can become confusing is that two very different things are often treated as though they are the same.
The first is deployment. A system is selected, purchased, configured, and introduced into the business. People learn how to use it, processes are adjusted, data is migrated. Eventually the technology becomes part of the way the organisation operates. Most businesses are perfectly capable of doing this, although some do it more smoothly than others.
The second is impact.
The distinction sounds subtle, but in practice it is significant. A technology project can be successfully deployed without creating much impact at all. In fact, many of the conversations that leave founders feeling slightly disappointed a year or two after a major technology investment begin with systems that worked exactly as intended.
The founder I mentioned earlier was a good example. The CRM system worked. The reporting worked. Information was easier to access and considerably more reliable than before. Nobody would have described the project as a failure. Yet when he reflected on the previous six months, what struck him was how little had changed in the day-to-day experience of running the business. The same decisions were still finding their way back to him. The same people were still waiting for guidance before moving forward. The same conversations continued to reappear in different forms.
What had improved was his ability to process information. What had not changed was the organisation’s dependence on him.
That pattern appears more often than many people realise. AI for business provides a particularly interesting example. A founder can use AI to analyse information, prepare reports, draft communications, summarise meetings, and accelerate dozens of small activities that previously consumed valuable time. The individual becomes more productive, sometimes dramatically so. Yet the business itself may remain largely unchanged if authority, accountability, and decision-making continue to operate exactly as they did before.
The technology has increased personal capability. It has not necessarily increased organisational capacity.
The same pattern can appear in CRM systems, workflow platforms, reporting dashboards, and countless other technologies. Information becomes easier to access. Activities become easier to track. Work becomes easier to organise. Yet if the same decisions continue to depend on the same individuals, the organisation may simply have acquired a more efficient version of an existing bottleneck.
This is not a criticism of the technology. Most technology does precisely what it was designed to do. The more appropriate question is whether the business was positioned to convert those improvements into something larger than individual productivity.
That, in my experience, is where the distinction between deployment and impact begins to matter. One is largely about introducing a tool. The other is about whether the organisation changes in response to having it.
What Technology Tends to Amplify
There is an observation that experienced business technology leaders tend to arrive at independently, often after watching several cycles of investment and disappointment: technology amplifies what is already present in an organisation. It does not correct what is unclear. It makes what is clear faster and what is confused more visible.
Where decision authority is well-defined, roles are understood, and accountability sits clearly with the right people, technology adds genuine speed and capacity. Information flows to the people who can act on it. Decisions are made at the right level. Handovers work because the underlying ownership was never in doubt. In these organisations, a new reporting platform produces action. A CRM system produces consistency. An AI-assisted process produces output that the organisation can absorb and direct.
Where those conditions are absent – where decision rights are assumed rather than defined, where the founder remains the implicit resolution point for most things, where accountability is understood in general terms but not in specific ones – technology tends to make those conditions more visible and more rapid rather than resolving them. A CRM system in a business with unclear customer ownership produces better-organised confusion, and it produces it faster. A reporting platform in a business without clear accountability produces a faster circulation of numbers that nobody quite knows what to do with. Workflow automation in a business with unresolved role boundaries tends to automate the points of friction rather than remove them.
Looking back, I am not sure technology changes organisations as often as we like to think. More frequently, it seems to expose strengths and weaknesses that were already present. It reveals where authority genuinely sits, where accountability is unclear, and whether information is actually the thing holding the business back. The structural conditions that allow a business to operate with speed and clarity are usually the same conditions that allow technology to create meaningful impact. Without them, the investment tends to produce a more sophisticated version of the same situation.
Sometimes the most valuable thing a technology investment produces is not efficiency, but clarity.
The Question Beneath Every Technology Investment
Most technology conversations in SMEs begin in the wrong place. They begin with products, features, vendors, and capabilities. They compare options, evaluate integrations, assess costs, and consider technology implementation timelines. These are all legitimate and necessary considerations, yet many of the businesses that seem to gain the greatest benefit from technology appear to have done something else first.
Somewhere before the technology arrived, there was already a reasonable degree of clarity about the structure of the growing business: how decisions were made, where responsibility sat, and what people were expected to own. Nobody would have described the business as perfect. Growing businesses never are. Yet there was enough clarity for the technology to reinforce something useful rather than compensate for something missing.
I have seen the opposite happen too: a founder invests in new systems hoping they will improve accountability. Six months later, the reports are better, the dashboards are more sophisticated, and the visibility is greater, yet accountability feels much the same as before because the technology never had the authority to create it in the first place. The question is not whether the technology is good. Most modern business technology is good. The question is whether people are sufficiently clear about who decides what, what they are responsible for, how work moves through the business, and how information reaches the people who need it.
This is not an argument for waiting until conditions are perfect. In a growing business, perfect conditions for anything rarely arrive. It is an argument for sequencing – for recognising that certain structural conditions need to be sufficiently present before technology investment converts reliably from cost to impact. Interestingly, and as the MIT Sloan Management Review has also noted in its research on digital transformation, the organisations that extract the greatest value from technology tend to be distinguished less by the technology itself than by the clarity of their operating models before the technology arrives.
The sequencing question gets skipped for understandable reasons. Organisational structure and governance feel slower and less tangible than a technology project. A new platform has a launch date, a demonstration, a visible outcome. Clarifying decision authority and governance has none of those features. It is less compelling to present to a leadership team, and harder to explain to a board. But the businesses that tend to gain genuine impact from technology investment have usually done the less visible work first, even if they did not frame it in those terms at the time.
What Technology Impact Actually Looks Like
When technology impact is working in an SME, it tends to be visible not in the technology itself but in what the organisation is able to do without the founder’s direct involvement.
Fewer decisions return to the founder without resolution, because the information needed to make those decisions is available to the people responsible for making them. Information appears before it needs to be requested, because the systems are configured around the organisation’s actual decision structure rather than around an individual’s need to stay informed. Handovers between people and between teams work without the founder as the live connection, because the underlying clarity of ownership makes the technology’s role straightforward rather than compensatory.
Customer experiences become consistent regardless of who is handling them, because the processes supported by the technology reflect agreed standards rather than individual judgement. The business can operate, at least partially, in the founder’s absence – not because the founder is no longer important, but because the organisation has been designed to carry its own weight and the technology supports that design.
These are organisational outcomes, not business technology outcomes. The technology enables them, but it does not create them. What creates them is the prior work of designing an organisation with sufficient clarity, authority, and accountability to use what the technology offers. In a well-structured business, a capable CRM application becomes a system of record that the whole organisation trusts and acts from. In a less structured one, it becomes an expensive contact database that the founder checks when they want to know what is happening.
The difference between those two outcomes is rarely the technology. It is almost always the organisation beneath it. The execution gap that opens between decision and action in growing SMEs is the same gap that technology investment tends to widen when the structural conditions are not yet in place.
This is what meaningful impact looks like. Not better technology for its own sake, but a business that becomes increasingly capable of making good use of the technology it has.
A Question Worth Thinking About
The pace of digital transformation shows little sign of slowing. Artificial intelligence will continue to evolve. Business automation will become more sophisticated. New tools will emerge, each promising greater efficiency, insight and productivity than the last. Many businesses will invest, and many will see real benefits – faster processes, cleaner data, more capable individuals.
The more interesting question sits underneath all of that. If the same decisions keep returning to the same desk, if the same dependencies remain in place, if the organisation is no less reliant on the founder’s presence and judgement than it was before the investment was made – then what has actually changed?
Technology that makes a founder more productive while leaving the organisation structurally unchanged may make the business appear faster without actually increasing organisational capacity. And the question worth asking, perhaps before the next investment decision rather than after it, is whether your business is gaining genuine capacity from the technology it already has – or whether it is simply running the same structure, and encountering the same bottlenecks, at a higher speed.
If you enjoyed this article you can subscribe here to receive future articles.
—
0 Comments