Workflow evaluation and operational metrics
Test a workflow’s important failures, not just its average score.
Reviewed: 2026-10-03
Source-based teaching example · Fictional data
Narration: Microsoft Mark · locally synthesized

00:00:00.000 — What you will learn

Test a workflow’s important failures, not just its average score.

Visual description:
Test a workflow’s important failures, not just its average score.

00:00:07.208 — The idea

Decide what counts as success before testing. Include cases with missing evidence and blocked actions. Report those results separately from routine cases.

Visual description:
Decide what counts as success before testing. Include cases with missing evidence and blocked actions. Report those results separately from routine cases.

00:00:20.542 — One useful term

Release gate. A required check that must pass before a workflow is allowed to move forward.

Visual description:
A required check that must pass before a workflow is allowed to move forward.

00:00:29.333 — A worked example

The made-up workflow answers eight routine cases correctly. It guesses on two missing-evidence cases and tries to send on two prohibited-action cases. Faster drafting does not cancel those failures.

Visual description:
The made-up workflow answers eight routine cases correctly. It guesses on two missing-evidence cases and tries to send on two prohibited-action cases. Faster drafting does not cancel those failures.

00:00:45.125 — Your turn to think

Can many correct routine answers outweigh an unauthorized send? Pause and decide before continuing.

Visual description:
Can many correct routine answers outweigh an unauthorized send?
Pause the video if you need more time.

00:01:02.542 — Why this answer works

No. Apply the critical rule separately. Stop or revise the workflow rather than hiding the failure inside an average.

Visual description:
No. Apply the critical rule separately. Stop or revise the workflow rather than hiding the failure inside an average.

00:01:13.375 — Check 1

Set expected behavior before the test.

Visual description:
Set expected behavior before the test.

00:01:18.875 — Check 2

Report counts for each case type.

Visual description:
Report counts for each case type.

00:01:24.083 — Check 3

Include checking time in effort measurements.

Visual description:
Include checking time in effort measurements.

00:01:29.667 — Now try a different case

Open the lesson and try its different practice case. Use every check in the full task. Watching alone does not mark the lesson complete.

Visual description:
Open the lesson
Try the new case
Check and revise
The full task and its requirements are in the linked lesson.