Before anything gets built, someone has to identify where Claude fits. That means examining business requirements and processes and finding tasks or steps Claude can genuinely support or improve — commonly falling into research, planning, content creation, analysis, or decision-support.
This is a judgment step, not a rubber stamp. Not every task is a good candidate. The discipline of use-case analysis is distinguishing where Claude genuinely helps from where the integration effort simply doesn't pay off — enthusiasm for the tool isn't a substitute for actually checking fit.
Use-case analysis sits upstream of two things covered earlier in this course: once a use case is confirmed, entry-point/feature/model selection (Module 1) follows from it, and evaluation criteria (Module 3) should be designed alongside the use case — not bolted on afterward once something's already shipping.