attv.uk · Digitalising Your Business

You Don’t Have to Digitise Everything

25 Jun 2026 · 5 min read · Tomasz Lewandowski

You Don’t Have to Digitise Everything
Digitalising Your Business — Prioritisation

One of the biggest misconceptions about digital transformation is that it has to happen all at once. Business owners imagine months of disruption, expensive consultants, new software in every department and a complete overhaul of the way people work. It is hardly surprising that many decide to postpone the project. Fortunately, that approach is rarely necessary. In fact, the most successful digital transformations often begin with a single process, a single spreadsheet or even a single recurring frustration. The goal is not to digitise everything. The goal is to digitise the right things.

Not Every Problem Is Worth Solving

Every organisation has inefficiencies. Some cost a few minutes each month. Others waste hours every day. Learning to distinguish between the two is one of the most valuable management skills. If your team spends five minutes each year updating a rarely used document, automation is unlikely to provide much return. If they spend two hours every morning manually processing orders, the opportunity is very different. Focus on problems that occur frequently and affect multiple people.

Apply the 80/20 Principle

The Pareto Principle suggests that roughly 80 per cent of outcomes often come from 20 per cent of causes. While the exact numbers vary, the lesson is useful. A handful of processes usually generate most of the delays, errors and administrative effort within a business. Rather than trying to improve everything simultaneously, identify the activities that consume disproportionate amounts of time. Start there. Small, targeted improvements often deliver surprisingly large results.

Look for Repetition

The best candidates for digitalisation tend to share certain characteristics. They happen every day. They follow predictable rules. They involve repetitive manual work. They require information to be copied between systems. They rarely depend on complex human judgement. Examples include:

  • creating invoices,
  • processing routine enquiries,
  • updating customer records,
  • sending appointment confirmations,
  • generating standard reports,
  • tracking stock movements.

These are precisely the kinds of activities where technology can provide immediate value.

Keep People Focused on People

One mistake organisations sometimes make is trying to automate tasks that genuinely require human understanding. Negotiating with a difficult customer. Handling an unusual complaint. Designing a bespoke solution. Mentoring a new colleague. These activities benefit from empathy, experience and creativity. By contrast, renaming files, copying addresses and sending identical reminder emails do not. The objective should be to remove repetitive administration so that employees have more time for meaningful work.

Start With Your Biggest Frustration

If you are unsure where to begin, ask your team one simple question:

What is the most annoying task you repeat every week?

The answers often reveal opportunities that managers have overlooked. Sometimes the problem is not even technological. A poorly designed form. An unnecessary approval. A report that nobody reads. Removing unnecessary work can be just as valuable as automating it.

Practical Tips You Can Implement This Week

  • Keep a frustration log. For one week, ask employees to note every repetitive or unnecessarily manual task they perform. Patterns will quickly emerge.
  • Measure before changing. Estimate how many times each task occurs and how long it takes. This helps prioritise the changes with the greatest impact.
  • Eliminate before automating. If a process serves no useful purpose, remove it instead of investing in technology to speed it up.
  • Standardise inputs. Use consistent templates, forms and naming conventions. Clean inputs make future automation significantly easier.
  • Review recurring reports. If nobody acts on a report, question whether it needs to exist at all.
  • Start with one success. Choose a single improvement that can be implemented quickly. Visible wins build confidence and encourage further change.
  • Score opportunities. Give each improvement a simple score for impact, frequency, risk and effort. Start with high-impact, low-effort work.
  • Create a three-month roadmap. Do not plan the next five years in detail. Choose a small number of improvements you can realistically deliver this quarter.

Beware of Perfection

Many businesses delay progress because they want the ideal solution. They wait until they have the budget for a complete transformation or until every requirement has been defined. Meanwhile, avoidable inefficiencies continue month after month.

A modest improvement implemented today often delivers more value than a perfect plan postponed for another year.

Progress is usually incremental.

Digital Transformation Is a Habit

The organisations that adapt most successfully rarely experience one dramatic moment of change. Instead, they make dozens of small decisions. They simplify a form. They merge duplicate databases. They document a process. They remove an unnecessary approval. They automate a recurring email.

Individually, these actions may seem insignificant. Collectively, they transform the way the business operates.

Start With One Thing

If you remember only one idea from this article, let it be this:

Do not ask, “How can we digitise the entire business?” Ask instead: What is the one repetitive task that wastes the most time, and how can we improve it this month?

Solve that problem. Then solve the next. Digital transformation is not a single project with a fixed finish line. It is the ongoing practice of making work simpler, information more accessible and people more productive. And more often than not, it begins with one small improvement that nobody thought was worth fixing.

Business owner toolkit

Score your quick wins

Picture it

An impact-and-effort matrix separating quick wins, strategic projects, low-value work and ideas to park.

Map it

Opportunity scoring: list frustrations, score impact/frequency/risk/effort, then build a three-month roadmap.

Free tool to try

Trello Free: Track improvement ideas in columns for Capture, Score, This Month, Later and Done.

Quick exercise: Run a 30-minute team session and collect ten repetitive tasks, then score each for impact and effort.

Pain Point: Paralyzed by the scale of "digital transformation," causing the business to delay making small, highly impactful improvements right now.

You are an experienced operations and digital transformation consultant who specializes in helping small and mid-sized teams find practical, high-leverage improvements without large-scale overhauls. You are pragmatic, Pareto-minded, and skeptical of over-engineered solutions. Your job is to act as my thinking partner — not to hand me a finished plan, but to help me make sharper decisions.

**Context**
I am feeling overwhelmed by the idea of a full digital overhaul of how my team works. Instead of trying to fix everything, I want to apply the 80/20 rule and identify the small set of quick wins that will eliminate most of my team's daily friction. I will share a list of my team's top daily frustrations.

**What I need from you**

1. **Clarify before scoring.** Once I share the frustrations list, ask me any clarifying questions you need (team size, tools currently used, budget/authority constraints, technical skill level, anything ambiguous in my list). Do not assume — surface what you need to score accurately.

2. **Build a prioritisation matrix.** Score each frustration on these four dimensions using a 1–5 scale, and explain your reasoning briefly for each score so I can challenge it:
   - **Impact** — how much pain it removes or value it creates if solved
   - **Frequency** — how often the issue hits the team
   - **Risk** — risk of the current state continuing AND risk of the proposed fix
   - **Effort** — realistic effort to implement (time, money, change management)
   
   Calculate a composite "quick win score" that explicitly favors high-impact, low-effort items (e.g., (Impact × Frequency) ÷ Effort, with Risk as a modifier). Show the formula you use and why.

3. **Separate the quick wins from the rest.** Clearly identify which items qualify as 80/20 quick wins versus items that should be deferred, ignored, or escalated to a larger initiative later. Be honest if something I listed is actually a symptom of a deeper problem.

4. **Output a realistic 90-day roadmap** focused purely on high-impact, low-effort improvements. Sequence the work into 30/60/90-day horizons, account for dependencies and team bandwidth, and flag any item that looks like a quick win but is likely to expand in scope.

5. **Stay collaborative.** Treat this as a dialogue. Push back where my framing seems off, offer alternatives I may not have considered, and check in before producing the final roadmap so I can adjust scoring or priorities.

**How to start**
Begin by asking me to paste my team's list of daily frustrations, along with any clarifying questions about my context that will help you score accurately. Do not start scoring or planning until I have shared the list.
Related reading
  • Don’t Buy Software. Solve a Problem.
← Previous: If You Can’t Describe the Process, You Can’t Improve It All in “Digitalising Your Business” →

Found on: https://attv.uk/blog/you-dont-have-to-digitise-everything.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.