Assess a use case

02 /Solution class

These three answers route the use case to the class of solution that fits. They do not reject it.

Rule expressibility

The logic can be written as fixed rules — same input, same outputRules cover most cases, but exceptions need judgementThe input varies too much for fixed rules

Reasoning depth

Single step — retrieve, extract or classifyA few dependent steps within one systemMulti-step across several systems, with decision points

Expected output

A prediction or a categoryAn answer grounded in existing documentsNew text or contentAn executed action in a system

04 /Business impact

05 /Technical feasibility

EU AI Act risk

Prohibited practiceSocial scoring, manipulative techniques, untargeted scraping for facial recognition.High riskDecisions about people: hiring, credit, access to services, safety components.Limited riskInteracts with people or generates content, so disclosure is required.Minimal riskNone of the above.

Risk categories follow Regulation (EU) 2024/1689 (EU AI Act). Self-classification for orientation, not legal advice.

Available tools

Select everything already in place.

Data availability

Not availableScattered and unstructuredStructured and accessibleCentralized and maintained

Budget band (EUR)

Time capacity

06 /User desirability

User pain

Users do not experience this as a problemUsers find it annoyingUsers actively ask for a solution

Change resistance

Expect open resistanceExpect hesitationUsers are motivated