Because it clarifies the problem: In the design-and-build phase, why is defining the business context and use

Defining the use case sets the problem, users and outcomes that anchor all later design, data and risk decisions.

The question

Preparing for AIGP? Take the free 5-min readiness quiz →

1. Because it fixes the exact model architecture and hyperparameters the engineering team must use throughout the entire build.

   Plausible but wrong: architecture and hyperparameters are downstream engineering choices, not the purpose of defining the use case.
2. Because it satisfies the post-market monitoring obligation that applies once the system has already been released into production.

   Plausible but wrong: post-market monitoring is a release-phase duty, not the reason to define the use case during design.
3. Because it clarifies the problem, users and intended outcomes that guide later data, model, risk and oversight decisions. ✓

   Correct: a defined business context and use case gives every later governance and design decision its anchor, which is why it comes first.
4. Because it produces the translated user documentation needed before the system is offered in new markets.

   Plausible but wrong: preparing localized documentation is a late-stage task unrelated to scoping the system's purpose up front.

How to remember it

Defining the use case sets the problem, users and outcomes that anchor all later design, data and risk decisions.

More Understanding How to Govern AI Development questions

• To describe the system's design: What is the primary purpose of this technical documentation? →
• During design and build: At what point is performing an impact assessment on the system most appropriate? →
• Stakeholder engagement and feedback: Which best practice does this activity represent? →
• All 426 Understanding How to Govern AI Development questions →