Workflow systems—such as xFLOWer—can significantly improve a company's operations. They organize processes, provide visibility into tasks, and ensure an audit trail. But it is important to acknowledge that implementing a workflow system is not worthwhile in every situation.
When is implementing a workflow system NOT worthwhile?
1. When the rules have not yet been defined
We had a client whose management team was very enthusiastic: they wanted to digitalize their project handover and acceptance processes. The only problem was that every manager worked in a completely different way. There were no standardized documents or consistent sequences of steps. After the system was implemented, everyone tried to impose their own methods on the workflow—the result was chaos. After six months, they returned to a combination of email and Excel.
2. When flexibility is the greatest asset
An advertising agency comes to mind. Its projects constantly changed based on clients' ideas. Implementing a workflow system only slowed the team down: every minor change required administrative work, which stifled creativity. After three months, they abandoned the initiative, explaining that their ad hoc approach was precisely what gave them a competitive advantage.
3. When no one takes ownership
A workflow system cannot simply be dropped into a company. It needs an internal owner to monitor, update, and maintain it. At one medium-sized trading company, for example, no one took on this role after the initial enthusiasm faded. Over time, the automations began sending incorrect data, and users started bypassing the system.
4. When management does not support it
This may be the most important lesson. At a manufacturing company, after a year-long project, when the system was almost ready to go live, the CEO declared: “I want to approve everything on paper.” This immediately split the process in two: paper and the system running in parallel. People soon reverted to paper, and the system went to waste.
5. When the organization is too small
A three-person consultancy tried a simple workflow system for contract management. They quickly realized that opening a shared folder and discussing things directly was easier. The system took more time than it saved.
When DOES implementing a workflow system and automating make sense?
- When more than ten people work together across multiple departments or locations.
- When there are recurring processes that can be standardized (invoice approvals, quotations, contracts).
- When transparency is required for regulatory compliance or ISO certification.
- When there is automation potential: integration with other systems, email-based triggers, document generation.
- When there is a risk that “everything is in one person's head”—the system helps preserve that knowledge.
Workflow systems—such as xFLOWer—can completely transform a company's operations. They automate tasks, provide process visibility, and ensure auditability.
But there are situations where implementation or automation is not only unnecessary but can even be harmful.
1. When the organization does not yet know what it wants to standardize
Example:
The management of a 25-person construction company decided to digitalize its project handover and acceptance processes.
The problem was that every site supervisor worked differently, with no consistency in document formats or the sequence of steps.
The system was implemented in six months, but because there had been no standardized process beforehand, employees tried to force their own familiar methods into the system.
The result: chaos, unnecessary frustration, and ultimately the decision to stop using the system and return to a combination of email and Excel.
2. When operations are entirely ad hoc—and that is a competitive advantage
Example:
A creative advertising agency thought a workflow system would bring greater visibility to its project management.
The problems began because campaign plans had to change constantly in response to the client's creative ideas.
The system burdened every change with administrative steps instead of supporting flexibility.
After three months, management acknowledged that, in this industry, a structured workflow tended to hold back the implementation of ideas.
3. When there are no resources for implementation and maintenance
Example:
A 40-person trading company began implementing a workflow system with just two IT support staff.
During the project, it became clear that there was no dedicated internal owner to administer the system and fine-tune the processes.
After the initial enthusiasm faded, processes became outdated, automations started sending incorrect data, and users increasingly bypassed the system.
4. When management is not committed
Example:
A manufacturing company had been running a year-long implementation project, and the system was almost ready to go live.
At that point, the CEO—who had not actively participated in the project—declared:
“I still want to approve everything on paper.”
This immediately split the process in two: middle managers had to maintain records both in the system and on paper.
Because of the extra work, employees began reverting to paper-based operations, and the system eventually became redundant.
5. When the organization is too small
Example:
A three-person consultancy implemented a simple workflow system for contract management.
In practice, however, all documents were created in a shared folder through direct coordination.
Using the system took more time than the improved visibility saved, so they eventually removed it.
When does implementation and automation make sense?
Growing headcount and broader collaboration (10+ people, multiple departments or locations).
Recurring processes that can be standardized (invoice approvals, contract management, quotations).
A critical need for transparency and an audit trail (regulatory compliance, ISO certification).
Automation potential (integration with other systems, email-based triggers, document generation).
Key-person dependency risk—the system standardizes processes and preserves knowledge.
