Review Workflow

A workflow is the operational path work follows through a system. It shows the sequence of steps, handoffs, decisions, people, tools, and information involved.

A workflow follows the work from one action to the next. It shows who does what, which system they use, what information moves, where decisions happen, and what must occur before the next step can begin.

A documented process describes the related activities intended to produce a result. Following the workflow helps us see how work actually moves through the larger system, including workarounds, delays, and hidden handoffs.

A customer emails a request, an office manager copies details into a spreadsheet, a dispatcher checks technician availability, and the customer receives a scheduling confirmation.

A workflow is not the same as a process or a system. A process describes related activities that transform inputs into a result. A system is the larger arrangement of interacting elements. A workflow follows the operational path work actually takes through both.

Follow the work to see what actually happens.

* [[process|Process]] * [[handoff|Handoff]] * [[actor|Actor]] * [[system|System]] * [[current-state|Current State]]

* [NISTIR 7316, *Assessment of Access Control Systems*](https://csrc.nist.gov/pubs/ir/7316/final) — workflow discussion and task dependencies, sequencing, performers, and data; see page 9. * [IBM, “About workflows”](https://www.ibm.com/docs/en/zos/3.2.0?topic=overview-about-workflows) — guided steps, dependencies, sequence, and performers.

* [Friction Mapping: Understanding Work Before Recommending Solutions](../../../../modules/friction-mapping-understanding-work-before-recommending-solutions/module.md)