Delivery

Workflow Automation: Where to Start and What to Automate First

A practical guide to choosing your first workflow automation: how to map a process, use BPMN terms to describe it, and pick work that is worth automating.

By Devacon LtdPublished 5 min read

Most organizations have more manual work than anyone has time to fix. Approvals bounce around email, the same data is typed into three systems, and a spreadsheet tracks the status of everything. Workflow automation promises relief, but the hard part is not the software. It is choosing what to automate first, understanding how that work really happens, and avoiding the trap of automating a broken process.

This guide offers a practical starting method. It borrows a small amount of vocabulary from BPMN, an open standard notation for drawing business processes, because a shared language makes the conversations between business owners and developers much easier.

Start with the problem, not the tool

Before looking at any platform, write one sentence about what is wrong. Good problem statements are specific:

  • “Purchase requests wait days for approval because nobody knows whose turn it is.”
  • “New employee accounts are created by hand in four systems, and one is often missed.”
  • “Customer refunds are re-keyed from email into the finance system.”

A vague goal such as “be more efficient” makes every option look equally good. A specific problem tells you what success looks like and how you will know you achieved it.

Map the process as it really runs

Next, map the current process with the people who actually do the work, not only the people who designed it. Ask them to walk through a recent real example from start to finish.

A shared vocabulary: BPMN basics

Business Process Model and Notation (BPMN) is a standard published by the Object Management Group (OMG). Version 2.0.2 is OMG document formal/2013-12-09. The specification states that its primary goal is a notation that all business users can readily understand, from the analysts who draft processes, to the developers who implement them, to the people who manage and monitor them.

You do not need to learn the full specification to benefit from it. The spec organizes its graphical elements into five basic categories:

Category What it contains
Flow Objects Events, Activities and Gateways
Data Data Objects, Data Inputs, Data Outputs and Data Stores
Connecting Objects Sequence Flows, Message Flows, Associations and Data Associations
Swimlanes Pools and Lanes
Artifacts Group and Text Annotation

For a first map, four ideas carry most of the value:

  • Events: what starts or ends the process, such as “request submitted” or “invoice paid”.
  • Activities: the work itself, such as “check budget” or “create account”.
  • Gateways: decisions and branches, such as “amount above approval limit?”
  • Lanes: who or which system does each activity.

Drawing the process this way quickly shows where work waits, where it loops back and where it changes hands. Those handoffs are usually where delay and errors live.

Score candidates before you automate

Once you have a few processes mapped, compare them. A simple scoring table keeps the choice honest:

Factor Ask
Volume How often does this run?
Rules Are the decisions clear rules, or judgment calls?
Stability Has the process been stable, or does it change often?
Inputs Is the data structured and available, or buried in free text and attachments?
Systems Do the systems involved have APIs, or only screens?
Pain What does delay or error cost: customers, money, compliance, morale?
Ownership Is there one person who can make decisions about the process?

Strong first candidates are frequent, rule-based, stable processes with structured inputs, systems that can be integrated, clear pain, and a single owner. They deliver visible results and teach the team how automation will work in your environment.

Leave for later the processes that depend heavily on judgment, change every quarter, or have no clear owner. Those may still be worth improving, but usually through redesign first.

Fix, then automate

Mapping often reveals steps that exist only for historical reasons: a signature nobody reads, a copy sent to a mailbox nobody checks, a check duplicated by two teams. Remove those before automating. Automating a wasteful step just makes waste faster, and it makes the step harder to remove later because it is now embedded in software.

Choose the right kind of automation

Different problems call for different tools. In broad terms:

  • Workflow and approval routing: moving a request through people and decisions, with reminders, escalations and a clear status.
  • System integration: moving data between systems through their APIs, so nobody re-keys it.
  • Document and data capture: turning forms and attachments into structured data.
  • Scheduled jobs and notifications: reports, reconciliations and alerts that run without anyone remembering to start them.
  • Custom applications: when the process is core to the business and off-the-shelf tools would force awkward compromises.

Many real solutions combine several of these. A purchase approval, for example, might combine a form, a routing workflow and an integration that creates the purchase order once approved.

A first-project checklist

  • Problem statement in one sentence, agreed with the process owner.
  • Current process map drawn with the people who do the work.
  • Target process map with unnecessary steps removed.
  • Success measures chosen before building, such as cycle time or error count, and a baseline recorded.
  • Exceptions listed: what happens when data is missing, a system is down or someone is on leave.
  • Integration points confirmed, including authentication and access for each system.
  • Audit trail designed in, so every automated decision can be traced.
  • Rollout plan, starting with a small group and a manual fallback.
  • Owner for ongoing changes, because processes keep evolving after launch.

Signs you are ready to scale

After the first automation has run for a while, look for these signals before expanding:

  • The process owner trusts the automated path and no longer double-checks it by hand.
  • Exceptions are handled in the workflow, not in side emails.
  • The team has a repeatable way to map, build, test and release changes.
  • Monitoring shows when something stalls, before a user complains.

When those are in place, the next process will be faster to deliver than the first.

How Devacon can help

We help organizations map their processes, choose automation candidates and build the workflows, integrations and custom applications to run them. A typical engagement starts with one well-scoped process, from mapping to a working automation with monitoring and an audit trail. Learn more about our process automation services.

Sources

  1. Object Management Group: About the Business Process Model and Notation specification, version 2.0.2
  2. Business Process Model and Notation (BPMN) Version 2.0.2, specification document

Facts in this article were checked against the sources above on November 17, 2026. Standards and products change, so check the source before relying on a detail. Related service: Process Automation.

More insights

Let's build something great together

Ready to talk about custom software? Tell us about your project requirements and we will get back to you.