Amr Selim – The Internet Guy | Why Technology Alone Will Never Save Your Business

In my early consulting days, I watched a pattern repeat itself in client after client.

A company would invest a small fortune in new software. CRM, ERP, e-commerce platform, training system — whatever the latest must-have was that year. Six months later, I would walk into the same company and find the new system half-implemented, half-ignored, and quietly resented by the team that was supposed to use it.

The technology was not the problem. The technology usually worked exactly as advertised. The problem was that the company had bought a tool to fix a people problem, or a process problem, or both — and tools cannot fix those.

That pattern eventually crystallised into a simple framework I have used ever since: People, Process, Technology. In that exact order.

The Order Matters More Than the Components

Most leaders know the three words. Very few get the sequence right.

They start with technology because it feels concrete. You can compare features. You can negotiate a contract. You can demo it. It feels like progress.

People and process are the opposite. They are messy, political, and resistant to change. So they get postponed. The tool gets installed first, and then everyone hopes the tool will somehow drag people and process into alignment behind it.

It does not work that way. Ever.

I learned this the hard way running operations at a fast-growing tech company in Dubai. We had the right tools — CRM, learning platforms, automation, the works. What we did not have was structured documentation, clear accountability, or aligned roles. The technology made our chaos more efficient. It did not make us less chaotic.

The 21,000-user transformation, the Dubai chaos, and the consulting calls that taught me this framework — all in Restart.

Get it on Amazon

🇨🇦 Get it on Amazon Canada

What Each Layer Actually Means

People First: Who Is Doing the Work?

Before any system, you have to be honest about who is on the team, what they are good at, where they are stretched, and what they actually need to succeed. You also need clarity on roles. If two people think they own the same decision, no tool will fix that. If nobody owns it, even the best tool will sit unused.

People also includes culture. A team that does not trust each other will not adopt a transparency tool. A team that fears the manager will not log honest data into a tracking system. Culture eats software for breakfast.

Process Second: How Does the Work Actually Flow?

Once you know who is doing what, you map how work actually moves through the organisation. Not how the org chart says it moves — how it actually moves. Where does it slow down? Where do things fall through the cracks? Where do people work around the official process because the official process does not work?

You cannot automate chaos. If your process is broken, automation will just make the broken process happen faster. The work of clarifying process — even on a whiteboard, even in a Google Doc — has to happen before the technology layer.

Technology Third: What Tool Best Supports the Above?

Now, and only now, you choose technology. The right question is not “what is the best CRM?” The right question is “given how our team works and how our process flows, what tool fits the way we already need to operate?”

When you start at this layer, you ask much better questions, you spend less, and the implementation actually sticks.

Why Most Digital Transformations Fail

There is a reason the failure rate of large digital transformation projects is consistently reported above 70%. It is not because the technology was bad. It is because companies tried to use technology to skip the harder conversations about people and process.

Working on Bahrain’s Labour Market Regulatory Authority transformation — where we trained more than 21,000 users on a new digital system — taught me this at scale. The system itself was modern and capable. But the project would have failed completely if we had not invested heavily in people (training, change management, support) and process (clarifying how work would actually flow once the system was in place) before and during the rollout.

The technology was maybe 30% of the work. The other 70% was people and process. That ratio is roughly true for every transformation I have ever seen.

How to Use This Framework Right Now

If you are about to invest in a new tool — for your business, your team, or yourself — pause and ask three questions in order:

People: Are the right humans in place, with clear roles, the right skills, and the trust needed to work together? If not, fix that first.

Process: Is the workflow you want to support actually documented and working — even manually? If not, clarify it before you automate it.

Technology: Given the answers above, what tool best fits how you already operate? Choose the tool that adapts to your reality, not the one that demands you reshape your reality around it.

Get this order right and your investment in technology will compound. Get it wrong and you will have a very expensive shelf decoration.


Restart goes deeper into the consulting and leadership lessons that shaped how I think about business systems today. It is available now on Amazon and free on Kindle Unlimited.

Have you ever watched a tool fail because the people or process was not ready? Tell me about it in the comments.