Domain 4 · lesson
Workflow Integration and Solution Design
Learning goal: design a workflow around a real problem, measurable requirements, human responsibilities, and safe integration. S09 S24
Objective 4.1
Analyze requirements and use cases
Core content
Identify users, current process, desired outcome, inputs, outputs, constraints, risks, approvals, and success criteria. Preserve open questions instead of silently converting them into requirements. S08 S10
Applied example
Discovery notes may contain decisions, suggestions, and unresolved issues. Tie requirements to evidence, label open questions, and validate them with responsible stakeholders before treating them as commitments.
Exam decision rule
Do not invent deadlines, scope, or approval from incomplete discovery material.
Objective 4.2
Use Claude for research, planning, and process optimization
Core content
Start with a defined objective and baseline. Use Claude to collect, structure, compare, or propose improvements; evaluate against representative cases; then decide whether to scale. Claims of productivity should include review and correction time, not just generation time. S09 S16
Applied example
A summary pilot should measure the current process, run a controlled sample, compare quality and total effort, and document failure modes before rollout.
Exam decision rule
Treat a pilot as a test of a hypothesis, not a ceremony performed after the rollout decision has already been made.
Objective 4.3
Support solution design, development, and iteration
Core content
Claude can help create designs, drafts, code, tests, and alternatives, but generated work remains subject to requirements, source control, testing, review, and deployment controls. S09 S24
Applied example
A generated script that parses financial files should be tested on known fixtures, malformed input, missing columns, and permission boundaries before being used in production.
Exam decision rule
Generated implementation does not bypass the normal evidence required to approve the solution.
Objective 4.4
Integrate Claude to augment or redesign work
Core content
Decide what Claude drafts, what tools or connectors it may use, what stays human-owned, and where approval gates belong. Prefer the simplest workflow that satisfies requirements. More agent autonomy increases the need for clear permissions, observability, and failure handling. S21 S24
Applied example
An assistant may draft an email from approved CRM data, while a human confirms recipient and content before sending. If the connector can send directly, that capability does not automatically mean automatic sending is authorized.
Exam decision rule
Distinguish capable of acting from authorized to act.
Objective 4.5
Communicate value and limitations to stakeholders
Core content
Report measured benefits, scope, known failure modes, residual risks, human responsibilities, and the evidence behind the claim. Avoid universal claims from narrow pilots. S09
Applied example
"Reduced drafting time 35% on 50 low-complexity support cases with trained review" is more defensible than "Claude makes support 35% faster." The second statement erases population and process constraints.
Exam decision rule
Communicate what was measured, for whom, under what conditions, and what remains untested.