A workflow is a defined, repeatable sequence of tasks performed by people, systems, or both, in a particular order to complete a specific business outcome, an onboarding checklist, an expense approval, a leave request. A workflow specifies the steps, the sequence and dependencies between them, who or what is responsible for each step, and the conditions that move work from one step to the next.
Workflow vs process vs procedure
Process is the broadest term: an end-to-end set of activities that transforms inputs into an output for a stakeholder, talent acquisition as a whole, for example. A process is often described at a strategic level and can span multiple departments and systems.
Workflow is the operational layer within a process, the concrete, ordered sequence of tasks and handoffs that actually execute a piece of it. Within talent acquisition, the resume-screening workflow, the interview-scheduling workflow, and the offer-approval workflow are each distinct workflows sitting inside that broader process. Workflows are what get automated and run through workflow software; processes are what get modeled or redesigned at a higher level.
Procedure is narrower still, a documented, step-by-step instruction for how one person performs one task correctly, such as how to submit a purchase requisition in a given system. A procedure tells an individual how to do a step; a workflow defines the order and handoffs of many steps, often across several people, toward a shared outcome.
Where workflow thinking comes from
Frederick Winslow Taylor’s 1911 book The Principles of Scientific Management is a genuine early precursor, arguing that manual and managerial work could be broken into discrete, measurable, standardized steps rather than left to informal tradition. That decomposition logic, breaking a job into steps that can be sequenced and improved, is the intellectual ancestor of modern workflow modeling, even though Taylor was writing about physical, industrial labor nearly a century before computing.
Michael Hammer and James Champy’s 1993 book Reengineering the Corporation pushed the idea further, arguing organizations should redesign end-to-end processes around outcomes rather than siloed departmental handoffs, a direct bridge between Taylorist task decomposition and the business process management software common today.
What workflow automation adds
Workflow automation uses software to execute, route, and monitor the steps of a workflow with minimal manual intervention, automatically routing a leave request to a manager and then to payroll, without anyone forwarding an email by hand or chasing a signature. Organizations that have gone further and redesigned their actual workflows around AI, not just automated the existing steps, show a real performance gap. McKinsey’s 2026 State of AI survey found 72% of high-performing organizations had fundamentally redesigned their workflows around AI, up from 55% a year earlier, against only 25% of other organizations.
That gap between redesigning workflows and merely automating them shows up elsewhere too, and it is worth naming directly since it explains why AI investment and AI value so often diverge. SHRM’s State of AI in HR 2026 found 39% of organizations have implemented AI within HR functions, concentrated most heavily in recruiting workflows at 27%, but also found 56% of HR functions do not formally measure the return on those workflow-automation investments, suggesting adoption is running ahead of measurement.
Workflow vs process vs procedure at a glance
Scope
Example
Process
End-to-end, often cross-department
Talent acquisition as a whole
Workflow
One ordered sequence within a process
The interview-scheduling workflow
Procedure
One person’s steps for one task
How to log a candidate’s status in the ATS
A worked example
A new-hire onboarding process might include several distinct workflows running alongside each other: an IT-provisioning workflow that orders and configures a laptop, an HR-paperwork workflow that routes tax and benefits forms for signature, and a manager-introduction workflow that schedules a first-week check-in and assigns a buddy. Each workflow has its own steps and owners, but they all serve the single broader onboarding process. A procedure sits one level below any of these, for example the exact keystrokes an IT technician follows to image a new laptop correctly, or the specific script a manager uses during a first-week check-in.
Signs a workflow needs redesign, not just automation
The steps exist only because “that’s how it’s always been done.” Automating a bad sequence just makes the bad sequence faster.
Multiple handoffs require the same information re-entered. A sign the underlying process was never designed as one connected flow.
No one can explain why a step exists. If the reason has been lost, the step is a candidate for removal, not automation.
Exceptions outnumber the standard path. A workflow built for the common case that constantly needs manual override was designed around the wrong assumptions from the start.
Workflow FAQs
What is a workflow?
A workflow is a defined, repeatable sequence of tasks, performed by people or systems, that must occur in a particular order to complete a specific outcome, such as an approval or an onboarding process.
How is a workflow different from a process?
A process is the broader, end-to-end set of activities that produces value for a stakeholder, often spanning multiple departments. A workflow is the operational sequence of steps executing one piece of that larger process.
How is a workflow different from a procedure?
A procedure documents how one person performs a single task correctly. A workflow defines the order and handoffs of multiple tasks, often across several people, toward a shared outcome.
Does automating a workflow always improve it?
Not necessarily. Automating a poorly designed sequence of steps just executes the same flawed process faster. Organizations that see the biggest gains tend to redesign the workflow itself around new capabilities, rather than simply automating the existing steps as they are.
Performance
