The Workflow Friction Hiding Inside a Busy Team

A busy team is not always an efficient team.

People can spend the entire week replying to messages, searching for files, rebuilding reports, chasing approvals and forwarding information between departments without actually moving work forward quickly.

For many Nigerian businesses, the problem is not a lack of effort.

It is workflow friction.

The warning signs are usually familiar:

A purchase request is waiting inside someone’s WhatsApp chat.
A manager cannot approve a request because the spreadsheet has not been resent.
Customer information exists across email, WhatsApp, Excel and individual devices.
A salesperson does not know whether another team member has already followed up.
A weekly report is rebuilt manually because nobody trusts the underlying data.
Employees spend time asking, “Has this been approved?” instead of being able to see the status themselves.

This is where conversations about business workflow automation in Nigeria often begin.

But the first step should not be buying another platform.

It should be identifying the exact point where work stops moving.

What Is Workflow Friction?

Workflow friction is any avoidable delay, duplication, uncertainty or manual dependency that makes a business process harder to complete.

It can appear in almost any department.

In finance, it may be an invoice waiting for approval.

In HR, it may be a leave request moving through email and WhatsApp.

In sales, it may be an enquiry that has no clear owner.

In operations, it may be a purchase request that requires somebody to manually chase three managers.

In management reporting, it may be employees spending hours combining multiple spreadsheets every Friday.

Individually, these delays may look small.

Across a business, they can consume significant time and make it difficult for management to see what is actually happening.

The goal of automation is not simply to remove manual work.

It is to create a clearer and more reliable path from request to action to completion.

Start With One Real Request

A useful workflow review begins with something real.

Choose one recurring process such as:

A quotation request
Purchase approval
Leave request
Expense approval
Customer complaint
Sales enquiry
Vendor onboarding
Management report
Contract review

Then map what actually happens today.

Ask:

What triggers the process?

Does someone complete a form, send an email, make a WhatsApp request or call a staff member?

Who receives it first?

Is there a named person, a department or simply whoever notices the request?

What information is required?

Does the next person already have what they need, or must they ask for documents again?

Who approves it?

Is the approval authority clearly defined?

What happens after approval?

Does another person receive a task automatically, or does somebody need to remember to forward the request?

How is completion recorded?

Can anyone see that the process has finished?

This simple exercise often reveals the friction before any software discussion begins.

Mark the Waiting Points

Once the process is visible, mark every place where work waits.

Look particularly for questions such as:

Is the next owner obvious?
Does the process rely on somebody remembering to follow up?
Is information copied manually between systems?
Does somebody need to resend a file before work can continue?
Can the requester see the current status?
Does approval depend entirely on one unavailable person?
Are decisions stored in private WhatsApp conversations?
Is the same information entered more than once?

These waiting points are often better automation candidates than entire departments.

A business does not necessarily need to “automate operations.”

It may simply need to fix three specific transitions that repeatedly slow operations down.

That is a much more useful starting point.

Separate a People Problem From a Process Problem

When work is delayed, the easiest conclusion is often:

“Someone did not do their job.”

Sometimes that is true.

Sometimes the process itself made failure very likely.

Imagine a purchase request with:

No assigned owner
No required completion date
No reminder
No escalation rule
No central status record

If the request is forgotten, the problem may not simply be carelessness.

The workflow provided very little structure.

The reverse is also true.

Automation cannot repair an unclear business rule.

If three managers disagree about who is authorised to approve a particular expense, digitising the form does not solve the disagreement.

It simply moves the confusion online.

Before automating a process, define:

Who owns each stage
Who has approval authority
What information is required
What can happen automatically
What requires human judgement
What happens when somebody does not respond
What evidence needs to be retained

Define the rule first. Automate the rule second.

Manual Approval Processes Are Often a Good Place to Look

Manual approvals are a common source of workflow friction.

A request may begin in email, move to WhatsApp, return as a spreadsheet and eventually reach the person who can approve it.

By that point, nobody is entirely certain which version is current.

Microsoft Power Automate supports approval workflows where requests can be routed to designated approvers and a flow can wait for an approval decision before continuing. Microsoft also supports different approval patterns, including first-response, all-approver and sequential approval scenarios.

That makes approval processes a potentially useful area for Microsoft 365 workflow automation.

But the technology is only part of the answer.

The organisation still needs to decide:

Who should approve
What happens if the approver is unavailable
Whether multiple approvals are required
What information approvers should see
Who can view sensitive records
When escalation should occur
How the final decision should be recorded

Automation can route and record the decision.

It cannot decide your governance structure for you

Look Beyond Approvals

Workflow friction also appears in everyday operational work.

Consider customer enquiries.

A customer fills in a website form.

Marketing receives the notification.

Someone copies the information into a spreadsheet.

Another employee sends it to sales on WhatsApp.

Sales replies to the customer but does not update the spreadsheet.

Two days later, management asks for the status.

Someone begins searching through messages.

This is not primarily a productivity problem.

It is a process-design problem.

A better workflow might create a single record, assign an owner, set the next action and make status visible without requiring another round of messages.

The same principle applies to:

Procurement
Finance requests
Internal approvals
HR processes
Customer service
Project reporting
Sales operations
Document management

Scattered Files Are a Workflow Problem Too

Businesses often discuss workflow automation as though it only concerns forms and approvals.

File access can create just as much friction.

A team may have documents spread across:

Personal laptops
Email attachments
WhatsApp
Google Drive
OneDrive
Shared folders
Multiple versions of the same spreadsheet

The question is not merely where files are stored.

Ask instead:

Can the right person find the correct information when the workflow requires it?

If an employee spends fifteen minutes searching for the latest quotation before every approval request, that search time is part of the workflow.

If staff regularly use outdated files because version ownership is unclear, that is also workflow friction.

Reporting Is Another Common Warning Sign

Manual reporting often reveals deeper process problems.

Imagine a manager asking for a weekly report every Friday.

Five departments submit different Excel sheets.

Someone manually combines them.

Numbers do not match.

The team spends another hour confirming which figure is correct.

By Monday, management is reviewing information that may already be outdated.

Automating the final report may help.

But the more important question is:

Why is the source information inconsistent in the first place?

Good automation should improve the path through which reliable information is created.

It should not simply make an unreliable report arrive faster.

Measure Movement, Not Activity

Before changing the workflow, establish a simple baseline.

You do not need an elaborate transformation dashboard.

Start with a few practical measures.

Average completion time

How long does the process take from request to completion?

Number of handoffs

How many people or systems does the request pass through?

Waiting time

Where does the process spend the most time doing nothing?

Avoidable rework

How often does somebody repeat work because information was missing, incorrect or unavailable?

Open exceptions

How many requests are stalled because they do not fit the normal process?

These measurements make it easier to judge whether a proposed improvement actually helped.

Change One Thing, Then Test Again

Avoid changing the entire workflow at once.

Choose one important friction point.

For example:

Before:
Purchase requests are submitted through WhatsApp and manually forwarded to managers.

Change:
Introduce a structured request form with assigned approval routing.

Then compare the next similar group of requests.

Did completion time improve?

Were fewer requests lost?

Did managers receive better information?

Was less manual follow-up required?

Did the process still maintain the right controls?

This is a much stronger way to evaluate operational efficiency in Nigeria than relying on broad claims about “digital transformation.”

Faster Is Not Automatically Better

Speed matters.

But speed is only valuable when the outcome remains accurate, secure, and governed.

An approval completed in five minutes is not an improvement if the wrong person approved it.

A customer response sent instantly is not useful if it contains incorrect information.

A report generated automatically is not valuable if nobody trusts the data.

A good automation project should improve several things together:

Speed.

Clarity.

Ownership.

Accuracy.

Visibility.

Governance.

That combination is more useful than automation for its own sake.

What Should You Automate First?

A practical first automation project usually has four characteristics.

It is:

Frequent
The workflow happens regularly enough for improvement to matter.

Rules-based
The next step can be determined from reasonably clear business rules.

Painful
There is a visible delay, repeated manual effort or avoidable error.

Owned
Someone is accountable for the process and can define what successful improvement means.

This is why starting with the organisation’s biggest process is often unnecessary.

A smaller, high-friction workflow can provide a better pilot.

Where Microsoft 365 Workflow Automation Can Fit

For organisations already using Microsoft 365, workflow automation can sometimes be built around tools such as Power Automate, SharePoint, Microsoft Lists, Teams and related business systems.

Power Automate, for example, can coordinate approval requests and continue a workflow based on the approver’s response.

But the correct implementation depends on factors such as:

Existing licences
Current applications
Data sensitivity
Security requirements
Integration needs
User roles
Approval policies
Reporting requirements

The goal should not be to use every available Microsoft tool.

It should be to create the simplest reliable workflow that solves the identified problem.

Use the Workflow Friction Canvas Before Discussing Software

Before asking:

“Which automation platform should we buy?”

Map one process.

Use the Workflow Friction Canvas to capture:

Trigger: What starts the process?
Input: What information is required?
Owner: Who is responsible now?
Approval: Who has authority to decide?
Handoff: Who receives the next action?
Waiting point: Where does work usually stop?
System: Where is the information stored?
Status: Can the requester see progress?
Exception: What happens when the normal process fails?
Completion: How is the final outcome recorded?

Once those answers are visible, the automation discussion becomes much more concrete.

Instead of asking for “digital transformation,” you can ask:

“Can we reduce the time between request submission and manager approval while keeping the right audit trail?”

That is a project somebody can actually design, test and measure.

Business Workflow Automation Should Begin With the Work

Automation works best when it is applied to a process the organisation understands.

Start with the work.

Find the friction.

Clarify the rules.

Assign ownership.

Establish the baseline.

Then decide where technology can reduce waiting, repetition and uncertainty.

Because the goal is not to make a busy team even busier with more software.

The goal is to make work move.

Get the Workflow Friction Canvas

TechBots Experts helps businesses review manual processes, identify practical automation opportunities and connect the right technology to the right operational problem.

Use our Workflow Friction Canvas to map one process before discussing software.

DM “FIX” to TechBots Experts or contact 09169337821.

Human support: Monday–Friday, 9:00 a.m.–6:00 p.m. WAT.
Sunday messages can be logged for the next staffed period.

Frequently Asked Questions

What should we automate first?

Start with a frequent, rules-based workflow that has a visible delay, repeated manual effort and a clearly accountable owner.

Examples may include purchase approvals, leave requests, customer-enquiry routing, recurring reporting or document approvals.

Avoid starting with the largest process in the organisation simply because it is the largest.

Do we need Microsoft 365 for workflow automation?

No.

The appropriate implementation depends on the systems your organisation already uses, available licences, security requirements, integrations and the process being automated.

For businesses already operating within Microsoft 365, tools such as Power Automate may provide useful workflow and approval capabilities.

Can automation remove every approval?

No.

Automation can route requests, notify approvers, record responses and continue workflows after decisions are made.

The business still needs to decide where human authority and judgement remain necessary.

How do we know whether a workflow is worth automating?

Look for repeated delays, duplicate data entry, unclear ownership, manual reminders, avoidable rework or frequent requests for status updates.

The stronger the combination of frequency and friction, the more useful the workflow may be as an automation candidate.

Will automation automatically improve operational efficiency?

Not necessarily.

If the underlying policy is unclear or the process is poorly designed, automation may simply make the same confusion move faster.

Clarify the process first, then automate the parts where technology can create measurable improvement.