Article · · By Innam Dustgir

How to Lead Digital Transformation

Three founders talk at laptops around a glass table in a modern office at night, beneath glowing floating panels showing a paper document turning into a digital workflow, with the title 'How to Lead Digital Transformation' and the name Innam Dustgir.

Ask most founders and they will agree that AI and new tools will change how their business runs. Far fewer can tell you what the route looks like. I can't fully either, and I don't think anyone honestly can right now.

That uncertainty changes the question. If you want to know how to lead digital transformation in a company where nobody has the map, start by looking at who is already exploring the territory. In most teams, those people exist. They are rarely the ones with the biggest titles.

Digital transformation leadership starts with people, not tools

When a business decides to "go digital," the usual first step is a tool. A new system, a new subscription, a plan built around software. Then the founder wonders why six months later the work looks almost the same.

Tools do not change a business. People changing how they work changes a business. The tool only makes that possible.

So my first job as a leader is not to choose the technology. It is to understand where the work is slow, repetitive or fragile, and who on the team is already trying to fix it.

I have written before about why you should fix the process before you automate it. The same rule applies here. Digital transformation leadership is mostly about the work and the people doing it.

Find the curious people who are already experimenting

In almost every team there are a few people who test new tools before anyone asks them to. They build a small automation for their own tasks. They try an AI assistant on a report. They find a faster way and quietly use it.

These people are often junior. Sometimes they are the newest hires. What sets them apart is not age or seniority. It is the habit of exploring.

They are also easy to miss, and sometimes easy to dislike. They experiment without permission. They question the way things have always been done, and they say it plainly. A founder who values order can read that as a problem.

I try to read it as information. The person who already built a workaround knows exactly where the current process breaks. That is more useful than any consultant's slide.

So the practical step is simple. Ask your managers, and ask the team directly: who here is already using new tools to do their work differently? Then go and see what they built.

Build honest, two-way conversations

Curious people bring energy, but they can also send a good initiative in the wrong direction. Senior people bring context, but they can also defend habits that no longer make sense. You need both, and they need to hear each other.

That means creating space where a junior person can tell a senior manager, "this step is not needed anymore," and be taken seriously. It also means the junior person hears, clearly and early, why some things cannot change: a client commitment, a legal requirement, a risk they did not see.

I find this works best when the conversation is regular and specific. Not a one-off brainstorm, but a short, recurring look at what people tried, what worked, and what should stop.

Cut the bureaucracy, keep the guardrails

If every experiment needs three approvals, the curious people will either stop or carry on in secret. Neither helps you.

At the same time, freedom without limits creates real risk. Customer data in the wrong tool. A prototype that becomes a critical system without anyone checking it. A quick build can become something the business depends on surprisingly fast, which is why I wrote about turning vibe-coded prototypes into tools a business can actually use.

My approach is to make the rules short and clear:

  • What the experiment is meant to improve, in one line.
  • What data and systems are off limits.
  • Who needs to know before anything touches a customer.
  • When we review it and decide to keep, change or stop.

Everything outside those lines should be fast. Guardrails are what let you say yes more often.

Give them air cover, and stay accountable yourself

An experiment that a junior person runs alone is easy to ignore or kill. The same experiment with visible support from the founder is treated differently.

Air cover means a few concrete things. Say publicly that this work matters. Give the person access to the decisions their work affects, not just a thank you. When something fails within the guardrails, make sure they are not punished for it.

What it does not mean is handing over the direction. The curious people can show you new routes. Deciding where the business is going is still your job. Transformation fails when leaders either control every step or disappear entirely. The useful place is in between: close enough to steer, far enough back to let people explore.

How to lead digital transformation in a small company

If I were starting this in a business tomorrow, I would keep the first month small:

  1. Name two or three problems in the work that cost real time or money.
  2. Find the people who are already experimenting and ask them what they have tried.
  3. Pair each of them with someone senior who owns that area of the business.
  4. Agree the guardrails in writing, on one page.
  5. Review results every two weeks, and decide openly what to keep and what to stop.
  6. Share what worked with the whole team, and credit the people who did it.

None of this needs a large budget. It needs attention from the founder and a willingness to learn from people below you in the structure. That is a big part of how AI is changing the rules of entrepreneurship: the advantage goes to companies that learn fastest, not the ones that buy the most tools.

This piece was prompted by a Harvard Business Review article on empowering your most curious employees to drive digital transformation, which argues that the employees already experimenting with new technology can speed up change if leaders know how to support them.

After 12 years of building businesses from Pakistan, I agree. Leading digital transformation is less about knowing the destination and more about noticing who is already finding the way, and giving them the room and the limits to do it well.

Frequently asked questions

How do you lead digital transformation in a small business?

Start with two or three real problems in the work, not with a tool. Find the people already experimenting, pair them with someone who owns that area, set short written guardrails, and review results every two weeks.

Who should lead digital transformation?

The founder or CEO owns the direction and stays accountable. Day to day, the work moves faster when the curious people who already use new tools are given visible support and a real say in decisions.

Why do digital transformations fail?

Often because they start with technology instead of the work, or because leaders either control every step or step away entirely. Too much bureaucracy stops experiments, and having no guardrails creates risk.

How do you engage employees in digital transformation?

Hold regular, honest conversations where junior and senior people both speak openly, remove unnecessary approvals, and publicly credit the people whose experiments work.

Originally published on LinkedIn