Lesson 4.1 · D4 Workflow Integration & Solution Design · 6 min
Analyse requirements and use cases
Start from the real process and a measurable problem, then find the steps where Claude genuinely helps.
What the exam tests
Choosing the right first step when someone asks to “use AI” for something, and telling good use cases from poor ones.
Key ideas
- Clarify the problem
- Turn “use AI for onboarding” into specific pain points, measures (time, error rate, backlog) and the people who will act on the output.
- Map the workflow
- Walk through the current steps and find text-heavy, repetitive, judgment-light work: drafting from approved material, summarising, triaging, reformatting.
- Good candidates
- First drafts for review, summaries for a decision-maker, categorising enquiries, pre-call briefs, FAQ drafts from policy.
- Poor candidates
- Final decisions about people, money or safety; approvals; anything where nobody would check the output.
- Check data and risk early
- What data the step involves and whether policy allows it in an approved Claude workspace.
Worked example
A director says, “We should use AI to fix our referral backlog.”
Weaker
Ask Claude to work through the backlog and prioritise each referral.
Stronger
Map the referral process, find where delays occur, identify the administrative steps Claude could help with, and agree how success will be measured.
Why: Requirements come before tools, and prioritising referrals is a decision people must own.
Common traps
- Buying licences for everyone as the first step.
- Letting Claude design the strategy or policy on its own.
- Telling stakeholders AI can't help without looking at the process.
Remember
Problem → process map → suitable steps → success measures.