FLOW Classifications

FLOW Classifications — Overview

The FLOW classifications introduce the basic categories of how work behaves based on complexity and scale. At this stage, they are descriptive—not prescriptive. Correct classification depends on understanding how work is structured, connected, and approached in practice.

​

FLOW classifies work based on complexity (how hard it is to execute) and scale (how large its impact or reach is).
Each Unit of Effort receives one FLOW classification to ensure it is handled, governed, and optimized appropriately.

FLOW classifications do not describe importance, value, or who performs the work.
They describe how the work behaves in execution.

​

FLOW A — Simple, Small-Scale Work

What it is
FLOW A covers work that is low in complexity and low in scale. These Units of Effort are repeatable, well-defined, and require little judgment or coordination.

​

How it behaves

• Clear steps

• Minimal risk

• Little or no coordination

• Best handled through standard procedures

​​

Typical handling
Automation, checklists, templates, and routine execution.

​

FLOW B — Simple Work at Moderate Scale

What it is
FLOW B includes work that is still relatively simple, but larger in volume, reach, or impact. The work itself is not hard, but managing it at scale introduces coordination needs.

​

How it behaves

• Repetition across people, time, or locations

• Increased scheduling or tracking requirements

• Limited judgment, but more oversight than FLOW A

​​

Typical handling
Batching, coordination roles, light governance, and throughput management.

​

FLOW C — Complex, Judgment-Driven Work at Small to Moderate Scale

What it is
FLOW C applies to work that requires significant judgment, coordination, or problem-solving, even if the scale is not large. These Units of Effort cannot be fully standardized.

​

How it behaves

• Multiple stakeholders or systems

• Non-routine decisions

• Higher risk if handled incorrectly

• Outcomes depend on experience and context

 

Typical handling
Experienced ownership, escalation paths, collaboration, and tailored approaches.

​

FLOW D — Large-Scale System or Design Work

What it is
FLOW D represents work that is large in scale, regardless of whether it is simple or complex. The defining factor is the need for system-level design, coordination, or change.

​

How it behaves

• Broad organizational impact

• Requires upfront planning and structure

• Small failures cascade widely

• Often involves redesign, rollout, or transformation

 

Typical handling
Formal governance, system design, program management, and layered control.

​

FLOW S — Special or Exceptional Cases

What it is
FLOW S captures work that does not fit normal execution patterns due to sensitivity, urgency, risk, or uniqueness. These Units of Effort require deliberate exception handling.

​

How it behaves

• High visibility or consequence

• Irregular or one-off

• Often time-critical or politically sensitive

• Cannot be routed through standard FLOW paths

​

Typical handling
Direct oversight, bespoke handling, and explicit escalation.

​

How to read FLOW classifications

• FLOW levels are descriptive, not hierarchical

• Higher FLOW does not mean more important

• A single Unit of Effort may change FLOW only if context, scale, or intent changes

• FLOW classifications enable clarity before applying principles, structure, or optimization

 

Why FLOW classification comes first

Before applying any FLOW principle, you must understand what kind of work you are dealing with.
Classification provides the foundation for:

• Ownership and assignment

• Governance and control

• Learning and training depth

• Optimization and system design

​​

​The FLOW classifications describe common patterns in how work behaves. The principles that follow explain how to recognize and apply these patterns in real work.