Skip to content

Digital Transformation Is Not an IT Project

By Tomasz Lewandowski · 2 Jul 2026 · 4 min read

Digital Transformation Is Not an IT Project
Digitalising Your Business — Leadership and Change

Mention digital transformation in a meeting and watch what happens.

People start talking about software. Servers. Cloud platforms. Cybersecurity. Artificial intelligence. Someone asks for a budget. Someone else asks the IT department for recommendations.

And yet the most important people in the room may not be the technical specialists at all. They are the people who understand how the business actually works.

Because digital transformation is not fundamentally about technology. It is about improving the way a business operates.

Technology Is the Easy Part

Modern software is remarkably capable. There are excellent tools for managing customers, stock, projects, accounts, marketing and communication.

The challenge is rarely finding technology. The challenge is deciding what should change.

A CRM cannot tell you how your sales process ought to work. An AI assistant cannot decide which approvals are unnecessary. A database cannot resolve disagreements about responsibility between departments.

Those are business decisions. Technology merely supports them.

Start With the Customer Journey

Instead of asking: Which software should we buy? Ask: How does a customer experience our business from beginning to end?

Think through the journey.

  • How do they first contact you?
  • How long does it take to receive a response?
  • How is a quotation prepared?
  • How is an order confirmed?
  • What happens after payment?
  • How are problems resolved?

Every delay, duplication or misunderstanding is an opportunity for improvement. Many of those improvements require better processes rather than better software.

Every Department Owns Part of the Transformation

Sales collects information. Finance invoices customers. Operations fulfils orders. Customer service handles enquiries. Management reviews performance.

If each department optimises only its own activities without considering the wider business, inefficiencies emerge between them. The most valuable improvements often occur at these handover points. When information flows seamlessly from one team to another, everyone benefits.

Do Not Delegate the Entire Project to IT

Technical specialists play a vital role, but they cannot redesign your business in isolation. They may know how to implement a system. They cannot decide whether your approval process contains unnecessary steps. They cannot determine whether duplicate reports should exist. They cannot identify every frustration experienced by frontline staff.

Business leaders must remain actively involved. After all, they own the outcomes.

Practical Steps Before Any Technology Investment

  • Map one customer journey. Follow a real transaction from initial enquiry to final payment. Write down every step.
  • Identify bottlenecks. Where does work stop and wait? Where are delays introduced?
  • Count handovers. Every transfer between people or departments increases complexity. Challenge whether each one is necessary.
  • Ask employees where they lose time. The answers often reveal practical improvements that require little or no investment.
  • Define success in business terms. Instead of saying, “We want a new CRM,” say, “We want to reduce quotation times from two days to two hours.” That objective is measurable and technology-independent.
  • Involve users early. People who use the system every day should help shape its design. They often identify problems that senior management never sees.
  • Appoint a business owner. Every digital project needs someone responsible for the business outcome, not just the technical delivery.
  • Communicate the reason for change. People accept new systems more readily when they understand the problem being solved and the benefit to their daily work.

Better Processes Create Better Software Projects

Businesses sometimes believe a disappointing implementation means they selected the wrong technology. Frequently, the real issue is that they automated an unclear process.

Good software reflects good thinking. If responsibilities are clear, data is well organised and workflows make sense, implementation becomes far easier. If not, even the most advanced platform will struggle.

Remember Why You Started

Digital transformation is not about having modern software for its own sake. It is not about replacing paper with screens. It is not about following trends or impressing competitors. Its purpose is much simpler.

  • To help customers more effectively.
  • To enable employees to work more efficiently.
  • To reduce unnecessary effort.
  • To make better decisions using reliable information.

Everything else is secondary.

A Final Exercise

Before approving your next technology purchase, gather your leadership team and ask each person to answer one question:

What is the single biggest obstacle preventing us from serving customers better?

If everyone gives the same answer, you probably have a clear priority. If every answer is different, resist buying software just yet. Spend time understanding the business first.

Because digital transformation succeeds not when you install the newest technology, but when you solve the problems that matter most. And those problems are almost always business problems before they become technical ones.

How to prepare your business before any technology investment

  1. Map one customer journey. Follow a real transaction from initial enquiry to final payment and write down every single step the customer experiences.
  2. Identify bottlenecks. Pinpoint where work stops and waits, and where delays are introduced along that journey.
  3. Count handovers. Every transfer between people or departments increases complexity, so list each one and challenge whether it is necessary.
  4. Ask employees where they lose time. The answers often reveal practical improvements that require little or no investment.
  5. Define success in business terms. Set a measurable, technology-independent objective - for example 'reduce quotation times from two days to two hours' rather than 'we want a new CRM'.
  6. Involve users early. People who use the system every day should help shape its design, as they often identify problems senior management never sees.
  7. Appoint a business owner. Make one person responsible for the business outcome of the project, not just the technical delivery.
  8. Communicate the reason for change. Explain the problem being solved and the benefit to daily work, because people accept new systems more readily when they understand why.

Frequently asked questions

Is digital transformation an IT project?

No. Digital transformation is not fundamentally about technology - it is about improving the way a business operates. Technical specialists play a vital role and may know how to implement a system, but they cannot redesign your business in isolation. Business leaders must remain actively involved because they own the outcomes.

Should we decide which software to buy first?

No. Instead of asking which software to buy, ask how a customer experiences your business from beginning to end. Many improvements require better processes rather than better software, so map and understand the business before buying anything. As a final exercise, the article suggests resisting a purchase if your leadership team cannot agree on the single biggest obstacle to serving customers better.

Why did our last software implementation disappoint us even though we picked a capable tool?

Frequently the real issue is not the technology but that you automated an unclear process. Good software reflects good thinking: if responsibilities are clear, data is well organised and workflows make sense, implementation becomes far easier. If not, even the most advanced platform will struggle.

What should we do before investing in any new technology?

Map one real customer journey from initial enquiry to final payment and write down every step, then identify bottlenecks and count handovers, challenging whether each one is necessary. Ask employees where they lose time, define success in measurable business terms, involve users early, appoint a business owner for the outcome, and communicate the reason for change.

Why shouldn't we just hand the whole project to our IT department?

Technical specialists know how to implement a system, but they cannot decide whether your approval process contains unnecessary steps, whether duplicate reports should exist, or identify every frustration experienced by frontline staff. Those are business decisions that leaders must own. Delegating the entire project to IT removes the people best placed to decide what should actually change.

What is digital transformation actually for?

Its purpose is to help customers more effectively, enable employees to work more efficiently, reduce unnecessary effort, and make better decisions using reliable information. It is not about having modern software for its own sake, replacing paper with screens, following trends, or impressing competitors. Everything else is secondary.

Share Follow
Don’t Wait for the Perfect System
Digitalising Your Business

Don’t Wait for the Perfect System

Waiting for the perfect system before you start is the single biggest reason digital projects stall. Learn why starting small and iterating delivers more value than planning indefinitely.

26 Jun 2026 · 4 min read
You Don’t Have to Digitise Everything
Digitalising Your Business

You Don’t Have to Digitise Everything

Digital transformation rarely needs to happen all at once. Discover how to identify the right processes to tackle first — and why one small improvement beats a perfect plan every time.

25 Jun 2026 · 5 min read
The Most Valuable Database May Be Sitting Inside Someone’s Head
Digitalising Your Business

The Most Valuable Database May Be Sitting Inside Someone’s Head

One of your most valuable databases may never appear on a server — it lives in your employees' heads. Capturing that knowledge is the first step towards resilience and digital transformation.

17 Jun 2026 · 5 min read