Glossary: Domain 4 — Workflow Integration and Solution Design

Use Case

A specific job where Claude is applied, defined by the deliverable, the audience, the sources, and what success looks like. Defining it first makes prompting and evaluation simpler.

See also: 4.1 Requirements and Use Cases

Requirements

What a solution must deliver: format, quality bar, constraints, and inputs. Unknown requirements are gaps to close before prompting.

Exam context: Define the deliverable, audience, and success measure before you design the prompt or workflow.

See also: 4.1 Requirements and Use Cases

Strong Fit / Weak Fit

A way to judge a task. Strong-fit work includes research synthesis, drafting, planning, and analyzing material you provide. Weak-fit work includes exact calculation, data Claude cannot see, and decisions requiring authority.

Exam context: For a weak-fit task, redesign the split of work rather than abandoning the use case.

Process Optimization

Using Claude to analyze a workflow, find delays and handoffs, and propose improvements that people then evaluate and pilot.

Pilot

A small, time-boxed trial of a Claude-assisted task with a baseline and measures. It shows whether the approach helps before you commit the wider team.

Exam context: Start small, measure against a baseline, then expand. Rolling out to everyone first is the trap answer.

Baseline

The current time, quality, and rework for a task before Claude is added. Without a baseline, you cannot tell whether a change helped.

Workflow Integration

Fitting Claude into how work already happens, either augmenting steps in the current process or redesigning the process around what Claude makes possible.

Exam context: Recurring work belongs in a Project. Escalate requests to connect other systems to the team that builds and secures integrations.

Augment vs Redesign

Augmenting adds Claude to an existing step. Redesigning changes the process because a constraint that shaped it no longer applies.

Division of Labor

A clear statement of what Claude does and what people do in a workflow, including the review step. It is the honest answer to "can Claude do X?".

Exam context: Good stakeholder answers state the value, the split of work, and the review step. Overpromising and flat refusals are both wrong.

See also: 4.5 Stakeholder Communication

Stakeholder Communication

Explaining Claude's value and limits to the people who rely on, approve, or are affected by a workflow, in terms they care about such as time, consistency, and risk.