4.1 · Lesson 1 of 5
Requirements and Use Cases
What you need to know
Domain 4 is Workflow Integration and Solution Design (16%). Lesson 4.1 starts before the first prompt: define the deliverable, the audience, the sources, and what success looks like. A clear requirement turns a fuzzy idea like “use AI for reports” into something Claude and your team can execute and measure.
Define before you prompt
- Deliverable — what is produced, in what format, for whom, and by when
- Sources — the policy, dataset, or style guide that owns the truth
- Success — observable terms, not “better”
- Reviewer and owner — who checks and who is accountable
Scope what belongs in claude.ai
Tasks built on provided text and judgement fit well. Tasks needing automatic data feeds or system access should be escalated to the technical team instead of forced into a chat. Separating fit early keeps Domain 4 solutions honest.
Worked example
Weekly customer-feedback summary: deliverable is a one-page themes brief for the product manager; sources are the week’s survey export and the product taxonomy; constraints include no customer names; success is “PM can prioritise without asking follow-ups.” That brief becomes the first prompt — and the yardstick for whether the result worked.
Exam traps
Start prompting before defining the result
Define deliverable, audience, sources, and success first.
Call success "better" without a measure
Success must be observable: time saved, error rate, reviewer approval, or “a manager can act without follow-ups.”
Leave reviewer and owner unnamed
A workflow with no named reviewer will eventually publish an unchecked error.
Force system integrations into a chat when they need technical design
Tasks needing automatic data feeds or system access belong with the technical team, not forced into claude.ai alone.
Practice scenario
A team wants to “use AI for reports” but cannot say who the reader is, what sources are allowed, or how they will judge success. What should they do first?
Build exercise
Write a One-Page Use-Case Brief Before Prompting
4.1 · Beginner · ~25 min · claude.ai
What you will practise
- Why the deliverable, audience, sources, and success measure come before the prompt.
- How a clear brief shortens iteration.
- How to spot a requirement you do not yet know.
- How to turn a brief into a first prompt.
Fill all five headings on the Domain 4 exercise, then judge the result against the success line.
Open Domain 4 exercisesPath: /learn/claude-associate/exercises/4-workflow-integration-design
Sources
- CCAO-F Exam Guide v1.0 — Domain 4 task statement 4.1 — Requirements and Use Cases
- preporato/claude-certification-guide — CCAO-F Ch.2 — requirements pedagogy (rewritten)
- evggzzz/ccao-f-guide — task 4.1 Knowledge/Skills
- docs/ccao-f-implementation-plan.md — Domain 4 lesson map