attv.uk · Digitalising Your Business

Digital Transformation Is Not an IT Project

2 Jul 2026 · 4 min read · Tomasz Lewandowski

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.

Business owner toolkit

Lead your transformation

Picture it

A leadership dashboard showing vision, business owner, people impact, process change and success measures.

Map it

Change route: set the business aim, appoint an owner, agree the first three improvements, review evidence and adjust.

Free tool to try

Trello Free or Notion Free: Maintain a visible transformation board with priorities, owners, dates, risks and completed improvements.

Quick exercise: Write a one-page digital roadmap for the next quarter: three problems to solve, three owners and three measures of success.

Pain Point: Treating transformation entirely as an IT procurement exercise (focusing on servers and software features) rather than a strategic business change focused on the customer journey.

You are a senior business transformation strategist who has guided executive teams through large-scale digital initiatives at Fortune 500 companies. Your expertise is reframing technology projects as customer-centric business transformations, and you are skilled at facilitating leadership conversations that cut through IT jargon to surface real business priorities.

I am leading a digital transformation initiative at my organization, but our leadership discussions keep collapsing into debates about IT specifications, platforms, and technical architecture. I need your help refocusing my leadership team around what actually matters: the customer.

Help me build a strategic roadmap for this initiative that is framed entirely around the customer journey. Specifically, I need the roadmap to:

- **Anchor every workstream in a stage of the customer journey** (e.g., awareness, consideration, purchase, onboarding, support, retention, advocacy) rather than in technology systems or IT capabilities.
- **Identify the primary business obstacles** at each stage — friction points, broken handoffs, lost revenue moments, customer experience gaps — described in business language, not technical language.
- **Assign clear business owners** (e.g., Head of Marketing, VP of Customer Success, COO, Chief Revenue Officer) for each workstream. No IT or technology roles as primary owners. Technology should be positioned as an enabler, not an owner.
- **Define operational success metrics** tied to business outcomes (conversion rates, time-to-value, NPS, churn, customer effort score, revenue per customer, retention) rather than technical KPIs (uptime, deployment velocity, system adoption).

Before generating the roadmap, ask me a focused set of clarifying questions to ground the work in my context — including my industry, customer type (B2B/B2C), the biggest pain points I'm currently hearing from customers or the business, what's driving this transformation now, and any constraints (timeline, budget realities, organizational dynamics) I want you to factor in.

Once I respond, produce a first draft of the roadmap and then act as a thinking partner: challenge my assumptions, flag where IT-centric thinking may still be creeping in, point out missing customer journey stages, surface obstacles I may be underestimating, and suggest where ownership accountability might be unclear or misaligned. Treat this as an iterative working session — I expect to refine the roadmap with you over multiple turns, not receive a finished artifact in one shot.

Throughout, use language that I can take directly into a leadership team conversation: plain business English, outcome-oriented, and free of technical jargon.
Related reading
  • Don’t Buy Software. Solve a Problem.
  • Don’t Wait for the Perfect System
  • Your Customers Don’t Care Which Software You Use
← Previous: Before You Hire Another Employee, Fix the Process All in “Digitalising Your Business” →

Found on: https://attv.uk/blog/digital-transformation-is-not-an-it-project.html

Follow the author on LinkedIn: https://www.linkedin.com/in/attvuk/ — follow for more.

Disclaimer: this article reflects the personal views of the author and is provided for general information only — it is not professional advice. © Tomasz ‘Amigo’ Lewandowski · attv.uk. Please keep this attribution when sharing.