The system is running. The team is not using it. The explanation is not the one most leaders reach for first.
The Adoption Illusion
The platform is live. The training sessions ran. The team lead sent the message about using the new system. And three weeks later, the approval requests are back in the email inbox, the documents are back on the shared drive, and the workflow tool is logging in at 20 percent of the team and zero percent of the senior approvers.
The first diagnosis is usually attitude. The team is resistant. They are comfortable with old habits. They need to be pushed harder. This diagnosis is almost always wrong.
As eLearning Industry’s analysis of why employees resist new software makes clear, software adoption is not primarily a technology problem. It is a people problem and a design problem. Employees do not adopt software because it is technically better. They adopt it because it genuinely makes their jobs easier. The biggest mistake organisations make is assuming that better technology automatically creates better user behaviour.
The data from enterprise software rollouts supports this. Studies cited by Sparkout Tech’s 2026 technology adoption analysis show that 50 to 63 percent of CRM adoption initiatives fail, mainly due to process misalignment, not technology failure. When teams continue using spreadsheets and email after a new tool is deployed, it is because the new tool is harder to use for their actual daily tasks than the old informal method.
The Real Reason Teams Return to Email
Email is frictionless for the person sending an approval request. Open a new email, attach the document, type the approver’s name, hit send. The whole action takes less than a minute. The workflow system, if it is not designed well, requires logging in, navigating to the right section, creating a new workflow instance, attaching the document, selecting the approver, configuring any options, and submitting. That sequence might take five minutes.
For a team processing approvals dozens of times per day, the five-minute version loses to the one-minute version every single time, regardless of the governance advantages the five-minute version provides. The team is not being irrational. They are optimising for the job as they experience it, not for the governance properties that matter to the compliance officer.
As Information Week’s 2026 analysis of enterprise change resistance reports, when users stop raising issues with a system, they have often stopped believing anyone is listening. That is when workarounds multiply and adoption numbers become fiction. Adoption without value-add is just compliance, and compliance is fragile.
| When employees bypass an approved workflow and use email instead, they are sending a clear signal about the system’s usability. The question is whether the organisation treats that signal as a data point for improving the system or as evidence of employee resistance to be managed. |
Five Design Fixes That Actually Improve Adoption
1. Make the submission faster than email
If submitting an approval request through the system takes longer than an email, the system will lose. Design the submission experience so that a document can be routed for approval in fewer steps than sending an email. Pre-configured routing, one-click approval templates for recurring document types, and inbox integration all reduce friction at the submission point.
2. Make the approval faster, not just the request
The approver’s experience determines whether the workflow becomes the default. If approving a request inside the system requires more clicks than replying to an email, the approver will reply to the email. Mobile approval interfaces, one-tap decision recording, and in-notification approval actions all reduce the approver’s friction below the email equivalent.
3. Show the team what email cannot give them
Adoption improves when the team can see what they are giving up by staying in email: no visibility into where approvals stand, no automatic escalation when an approver is unresponsive, no audit record that survives the approver’s email deletion, no version control on the document. The system’s advantages need to be visible to the people using it, not just to the compliance team.
4. Start with the highest-frequency workflow
The team member who uses the system for the workflow they run twenty times a week will become comfortable with it faster and more durably than the one who uses it for the workflow they run once a month. Identify the highest-frequency approval workflow in the organisation and make it the mandatory starting point for system adoption.
5. Make the workaround harder, not the system easier
This is the step most organisations skip. When email remains an equally available alternative, some percentage of the team will always choose it. Removing the email option for defined approval categories, rather than making it policy to not use email, forces the workflow system into the daily habit. Once the habit forms, the system wins on its own merits.
Flowmono is designed to be faster than email for the submission, approval, and recording steps that most teams currently run through their inboxes. See what frictionless workflow adoption looks like on Flowmono. Start here. For a view of how scaling organisations have made this transition, see our article on how Flowmono helps African businesses scale with workflow automation.
