Learning path · Level 9 · Tutorial 1

Prioritizing AI Use Cases for a Team

Create an evidence-backed shortlist of AI opportunities for a team or small business, balancing user needs and potential value against feasibility, data readiness, and unacceptable risks.

  • Level: Intermediate
  • Duration: 18 min
  • 8 steps
Start tutorial Back to the path
Prioritizing AI Use Cases for a Team

What you will go through

  1. Start with the user problem Turn a technology-first suggestion into a bounded use case with a specific user and observable desired improvement. 2 min
  2. Apply non-negotiable gates Use essential consequence, authorization, review, and fallback requirements to decide whether a candidate can proceed to later assessment. 2 min
  3. Estimate potential value Rate potential value from evidence about recurring work and user improvement, without treating current workload as guaranteed savings. 3 min
  4. Check practical feasibility Rate practical implementation feasibility using consistent anchors while keeping essential blockers and data readiness separate. 2 min
  5. Inspect data readiness Assess whether candidate use cases have accessible, permitted, relevant, current, and sufficiently representative sources before assigning Data readiness (D). 2 min
  6. Build an evidence-aware scorecard Use gates, ratings, and criterion-specific evidence labels together so a numerical score does not hide uncertainty or blockers. 2 min
  7. Turn the scorecard into a shortlist Turn a completed scorecard into a transparent, evidence-aware use-case shortlist. 2 min
  8. Make and defend the recommendation Integrate evidence, gates, ratings, uncertainty, and next actions into a defensible use-case shortlist for Harbor Office Supplies. 3 min

What you will learn

  • Frame candidate use cases as specific user problems with observable desired improvements.
  • Rate each candidate's potential value, feasibility, and data readiness using consistent criteria and supporting evidence.
  • Exclude or defer candidates that fail essential safety, authorization, or operational requirements rather than allowing a high value score to outweigh those failures.
  • Produce a ranked shortlist with a recommended next step and unresolved questions for each candidate.

Before you start

  • Practical experience with AI-assisted workplace tasks and bounded no-code workflows
  • Building an Evidence-Based Answer Test Set
  • Responsible-use assessment of privacy, security, bias, rights, and regulatory risks

Step 1 of 8

Start with the user problem

Turn a technology-first suggestion into a bounded use case with a specific user and observable desired improvement.

Describe the work problem

A problem-first frame

Begin with the work, not the tool

A candidate use case is a specific work problem that may be improved—not a request to “add AI” or a choice of product.

Frame each candidate by answering four questions:

  1. Who is affected?
  2. What recurring task do they perform?
  3. What difficulty occurs now?
  4. What observable improvement do they need?

This keeps the decision focused on people and outcomes before discussing technology.

The four parts of a use case

A four-part visual flow: user, recurring task, current difficulty, and desired improvement.

A useful use-case statement connects the affected user, their repeated task, the present friction, and an improvement that could later be observed.

Make the scope specific

Use the case facts carefully

At Harbor Office Supplies, use the shared candidates as problem frames—not as assumed solutions. All case evidence needed for the exercises appears in this tutorial.

For example, FAQ reply drafts concerns customer-support work. Agents handle 100 requests/week at 6 min/request today. Those figures describe current work; they do not prove that any future approach will save time.

Example

Reframe the suggestion

Technology-first suggestion:

“Add AI to answer FAQ questions.”

Problem-first use case:

“Customer-support agents handle recurring FAQ requests. Writing replies from approved FAQ material takes repeated effort; they need a reviewable, consistent first draft.”

The second statement identifies a user, task, difficulty, and desired improvement. It does not select a product or promise a result.

Set a clear boundary

Bound the proposal

A useful scope says where assistance starts and stops. For FAQ reply drafts, assistance could begin when an agent opens a recurring FAQ request and end with a first draft based on approved FAQ material.

The agent’s final review, correction, and sending of the customer-facing reply remain outside the assistance proposal. Non-FAQ cases are also outside this scope.

Boundaries make later assessment more realistic: you can ask whether a defined task improves without quietly expanding the proposal.

Practice the problem-first frame

Build the problem frame

For FAQ reply drafts, arrange the parts into one problem-first use-case statement. Do not add a technology choice.

Your sentence

Available words

Step 2 of 8

Apply non-negotiable gates

Use essential consequence, authorization, review, and fallback requirements to decide whether a candidate can proceed to later assessment.

Screen eligibility before attractiveness

Gate check first

Gates come before scoring

A gate check is an eligibility screen, not a comparison of benefits. Before assessing a candidate further, use existing findings to ask:

  • Could an error cause unacceptable consequences for people affected by the task?
  • Is the necessary authorization in place for the proposed processing?
  • Can the team provide required review before a customer-facing output, detect and correct errors, and use a workable manual fallback?

Assign one status:

  • Pass: essential requirements are sufficiently supported for further assessment.
  • Hold: an essential requirement is unresolved or temporarily unmet.
  • Stop: the proposal as framed conflicts with a requirement or has unacceptable consequences.

A promising benefit cannot compensate for a missing authorization or an essential safeguard.

The gate sequence

A flow diagram showing a candidate passing through consequence, authorization, and review-and-fallback checks before receiving one of three outcomes.

Check essential conditions first. The outcome is Pass, Hold, or Stop—not a numerical trade-off.

Tip

Keep the boundary clear

A Pass only permits further assessment; it is not approval to deploy. Revisit the status if evidence changes. In particular, missing authorization remains a gate issue rather than something a later rating can offset.

Record why a candidate is blocked

Apply the findings to the shared case

Use the responsible-use and authorization findings already available. Record the specific requirement and evidence that produce the gate status, rather than making a broad claim that a candidate is simply “safe” or “unsafe.”

Blocked candidates

These candidates do not proceed as currently framed.

Gate review for two Harbor Office Supplies candidates.
CandidateExisting evidenceGate statusDecision basis
Order-status reply draftsAuthorization to process order records is pending.HoldNecessary authorization is unresolved.
Unreviewed refund denialsThe proposal removes review and appeal before customer-facing denials.StopIt conflicts with required review and leaves no adequate correction path.

Warning

Do not hide a blocker

Do not turn either result into a low implementation rating. A pending authorization is a Hold. Removing the required review from refund denials is a Stop for this proposal as framed. Neither result declares every possible order-status or refund-support approach unacceptable.

Practice: assign the gate status

Gate the candidates

Match each evidence-backed case to its gate status and the requirement that supports or blocks it.

Tap an item and then its matching pair.

Step 3 of 8

Estimate potential value

Rate potential value from evidence about recurring work and user improvement, without treating current workload as guaranteed savings.

Recognize potential value

Potential value is about meaningful improvement

What Potential value (V) asks

For an eligible candidate, Potential value (V) asks how much improvement could matter—not whether an AI tool is exciting.

Consider four signals together:

  • Task frequency: How often does the recurring task occur?
  • Avoidable effort: Which parts of the current work might assistance reduce?
  • Service quality: Could users receive a more useful, consistent, or timely result?
  • Importance to users: How much does the outcome matter to the people affected?

High volume can support value, but it is not the only source. A lower-volume task may still matter greatly if it improves an important user outcome.

Current work is not automatic savings

A support-request workflow shows a large amount of current work, followed by AI drafting, human review, and remaining manual tasks.

Current workload shows work that could be affected. Review, correction, and remaining manual tasks mean that only part of it may become avoidable effort.

Value anchors

Use the same anchors for every candidate.

Potential value (V) rating anchors
RatingAnchor
1Limited benefit
2Meaningful recurring improvement
3Substantial avoidable effort or a major improvement to a user-important outcome

Use evidence without overstating it

Read workload evidence carefully

Workload records provide concrete evidence about the scale of current work. They do not demonstrate what an AI-assisted process will save.

For Harbor Office Supplies, multiply requests per week by current handling time to describe the workload potentially affected. Keep the result separate from any future claim about time released or savings.

Harbor Office Supplies workload records

These calculations describe the current process only.

Recorded current work for two candidates
CandidateCurrent-work calculationWhat the record supportsWhat it does not show
FAQ reply drafts100 requests/week × 6 min/request = 10.0 hours/weekA substantial amount of recurring work may be affectedThat 10.0 hours/week will be saved
Product-spec lookup60 requests/week × 3 min/request = 3.0 hours/weekA meaningful recurring workload may be affectedHow much review, correction, or remaining work is needed

Apply the value anchor

Choose a defensible value rating

For FAQ reply drafts, which assessment of Potential value (V) is best supported by the case evidence?

Step 4 of 8

Check practical feasibility

Rate practical implementation feasibility using consistent anchors while keeping essential blockers and data readiness separate.

Assess the practical fit

What feasibility measures

Feasibility asks a practical question: can this team realistically support this task as proposed? Look for the capabilities, staff skills, system connections, and changes to everyday work that the proposal needs.

A familiar drafting or lookup task may fit existing ways of working. A task that needs unavailable system access, an unsupported action, or a major workflow change may not.

Keep this distinct from source quality. Whether records are current or sufficiently complete is assessed separately as data readiness; do not subtract for the same weakness twice.

Implementation fit, dependencies, and gates

A diagram separates a supported implementation fit, an identified dependency, a missing required approval checkpoint, and a separate source-data assessment.

Feasibility considers implementation fit and dependencies. A missing essential requirement goes back to gate review; source readiness is a separate assessment.

Tip

Apply the question to the case

For example, FAQ reply drafts and Product-spec lookup resemble work the support team already performs. If existing capabilities and reviewers can support the assistance with limited change, that is evidence toward a high feasibility rating. It does not by itself prove that the sources have sufficient coverage for every task.

Choose a rating or return to gates

Feasibility anchors

Use the same anchors for every candidate. Rate the realistic implementation path, not enthusiasm for the idea.

Rate the implementation, not a blocker

A numerical rating is appropriate only when essential requirements remain satisfied. If an essential requirement fails, return to gate review instead of treating it as a low score.

Common anchors for Potential value (V), Feasibility (F), and Data readiness (D) use different evidence. This table defines only Feasibility (F).
Feasibility (F)Implementation evidenceInterpretation
3Available capabilities and skills support the task; limited process changeA supported fit
2Manageable gap or dependency with an identifiable path to address itProceed only with that dependency visible
1Substantial unresolved capability, integration, skill, or process gapImplementation is currently difficult
Not a ratingRequired review, workable manual fallback, or necessary authorization cannot be satisfiedReturn to gate review

Warning

Do not score around essential requirements

At Harbor Office Supplies, order-record processing authorization is pending for Order-status reply drafts. That is a gate finding: its status remains Hold, rather than becoming a low feasibility rating.

Likewise, a proposal that removes review and appeal for Unreviewed refund denials conflicts with the team’s requirements. Its Stop status cannot be outweighed by an attractive score.

Practice the distinction

Classify the implementation evidence

Match each implementation evidence pattern to the appropriate feasibility anchor or decision route.

Tap an item and then its matching pair.

Step 5 of 8

Inspect data readiness

Assess whether candidate use cases have accessible, permitted, relevant, current, and sufficiently representative sources before assigning Data readiness (D).

Check the evidence, not the collection size

What data readiness checks

Data readiness asks a narrower question than feasibility: do we have usable evidence sources for this task? Check five things before rating: source availability, permitted use, relevance, currency, and coverage of typical cases.

A source can be large and approved yet still be a weak fit if it does not cover the cases the proposed task must handle. Record what is known; do not fill gaps with optimism.

A visual flow from five source-evidence checks to a data-readiness rating or an unknown result.

Check the source evidence before assigning Data readiness (D).

Rate what the evidence supports

Data readiness (D) anchors

Use the same anchors for every candidate. A rating is defensible only when its supporting evidence matches the anchor.

If a required fact is not known, do not guess a low or high rating. Mark the affected criterion as Unknown, use U as its numerical rating, and leave any incomplete total as Not calculated.

Rating guide

Use evidence that can be checked within the candidate’s stated scope.

Data readiness (D) is about source fitness for the proposed task.
D ratingEvidence pattern
3Accessible, permitted, current, task-relevant sources with sufficient demonstrated coverage
2Usable sources with bounded gaps
1Known major source gaps
UA required readiness fact is Unknown; do not infer a numerical rating

Tip

Evidence is criterion-specific

An approval record supports permitted use, but it does not by itself prove coverage. A source inventory can show availability; update information can show currency; representative examples can show whether typical cases are covered.

Separate gaps, unknowns, and gates

Read the case evidence precisely

Apply the checks to the Harbor Office Supplies candidates. The FAQ evidence supports a complete rating because the sources are current, approved for this proposed use, and matched to typical FAQ requests. The issue-category records are approved, but their coverage of typical issues is uncertain. That is an unknown fact, not proof of a major gap.

Compact evidence view

This compact view keeps gate status separate from Data readiness (D).

Known source gaps and unknown coverage lead to different records.
CandidateGate statusDEvidence and uncertainty
FAQ reply draftsPass3Data readiness (D): Supported — current, approved FAQ sources match typical requests
Product-spec lookupPass3Data readiness (D): Supported — current, approved product-catalog sources match typical lookups
Weekly issue summariesPassUData readiness (D): Unknown — issue-category records are approved; typical-case coverage is uncertain

Warning

Keep authorization in the gate review

A pending authorization to process order records is a gate finding. Record Hold rather than trying to compensate with a lower Data readiness (D) score. Gate status answers whether assessment may proceed; the rating describes source readiness.

Apply the rating and gate rules

Choose the scorecard entry

Use this concise evidence brief to select the most defensible scorecard records.

  • FAQ reply drafts: Current FAQ sources are approved for this proposed use. A representative check shows they cover typical FAQ requests.
  • Order-status reply drafts: Processing authorization for order records is pending. No complete source-readiness assessment is available yet.

Which pair of records follows the evidence and scoring rules?

Step 6 of 8

Build an evidence-aware scorecard

Use gates, ratings, and criterion-specific evidence labels together so a numerical score does not hide uncertainty or blockers.

Separate eligibility, ratings, and evidence

Keep the layers separate

A scorecard makes the reasoning behind a use-case shortlist visible. Keep three layers separate:

  • Gate status: Is the candidate eligible for scoring now?
  • Ratings: Potential value (V), Feasibility (F), and Data readiness (D), each from 1 to 3.
  • Evidence status: How well each individual rating is supported.

Calculate only when Gate status is Pass and all three ratings are integers:

Priority score = V + F + D

The possible range is 3–9. This equally weighted score is a discussion aid—not a probability of success or an objective measure of worth. Do not calculate a score for a Hold or Stop candidate.

How a scorecard is structured

A Pass gate flows into three separate ratings and then a total, while Hold and Stop routes bypass the total. Each rating has its own evidence note.

Calculate a total only after a Pass gate and complete numerical ratings. Record evidence beside each criterion, not inside the total.

Tip

Label the strength of each rating

Use one evidence-status label for each criterion:

  • Supported: identifiable evidence supports the rating within its stated scope.
  • Estimated: the rating relies partly on a reasoned estimate or untested assumption.
  • Unknown: evidence is not sufficient to assign a numerical rating.

Supported does not guarantee future results. It means the team can point to evidence for the rating it recorded. If a required rating is Unknown, record U and use Not calculated for the incomplete total.

Record uncertainty without hiding it

Read the current scorecard

The compact scorecard keeps the gate result, the three ratings, and the total visible as separate records. Weekly issue summaries has a complete feasibility rating: the support lead can use an available summarization capability on the existing issue-category records, with no new system integration and limited change to the weekly review routine. Its data coverage remains a separate unknown.

Scorecard snapshot

A compact view of the working evidence for the use-case shortlist.

Only Pass candidates with complete numerical ratings receive a Priority score.
CandidateGate statusVFDPriority score
FAQ reply draftsPass3339
Product-spec lookupPass2338
Weekly issue summariesPass23UNot calculated
Order-status reply draftsHoldUUUNot calculated
Unreviewed refund denialsStopUUUNot calculated

Criterion-specific evidence

Keep the evidence attached to the specific criterion it supports.

Feasibility evidence describes the implementation path; it is not a substitute for gate evidence.
CandidateEvidence and uncertainty
FAQ reply draftsV: Supported—100 requests/week at 6 min/request, or 10.0 hours/week of current work. F: Supported—drafting fits the team’s existing support-reply workflow and available capabilities, with limited process change. D: Supported—current, approved FAQ sources cover typical requests.
Product-spec lookupV: Supported—60 requests/week at 3 min/request, or 3.0 hours/week of current work. F: Supported—lookup fits agents’ existing work and available capabilities, with limited process change. D: Supported—current, approved product-catalog sources match typical lookups.
Weekly issue summariesV: Estimated—the benefit of recurring summaries is an estimate. F: Supported—available summarization capability can support the support lead’s existing weekly review routine without a new integration. D: Unknown—approved issue-category records have uncertain coverage of typical issues.

Example

Equal totals can mean different things

A hypothetical Pass record can have V = 3 Estimated, F = 3 Supported, and D = 3 Supported. Its Priority score is 9, but the total is provisional because one rating relies on an estimate.

FAQ reply drafts also has a score of 9, with all three ratings Supported in the stated scope. Equal totals do not mean equal evidence strength. Inspect the rating profile, evidence labels, and assumptions before using a score to discuss the order of the use-case shortlist.

Practice an evidence-aware scorecard

Complete and inspect the records

Complete and interpret two independent scorecard records in your own words.

Record A has Gate status Pass. A reasoned forecast supports V = 3. Documented implementation evidence supports F = 3, and documented source evidence supports D = 3.

Record B has Gate status Pass. Documented task evidence supports V = 2 and documented implementation evidence supports F = 3. The source coverage has not been sampled, so D cannot receive a numerical rating.

For each record, state the evidence status for V, F, and D; then give the Priority score or Not calculated. State whether Record A’s total is provisional. Finally, explain why its attractive total is not stronger evidence than the supported score for FAQ reply drafts.

Write at least 180 characters (0/180).

Step 7 of 8

Turn the scorecard into a shortlist

Turn a completed scorecard into a transparent, evidence-aware use-case shortlist.

Rank only the eligible candidates

From scorecard to recommendation

Rank after gates, not instead of them

Start with eligibility. Rank candidates only when their gate status is Pass and their ratings are complete enough to calculate a Priority score. Then inspect the user problem, rating profile, evidence strength, and dependencies—not just the total.

A close score is a provisional order, not a tie-breaker by itself. Stronger evidence or a less important dependency can justify an order; an unresolved tie can remain visible.

Use dispositions precisely:

  • Pursue now: move to solution-option comparison, not purchase, build, or deployment.
  • Investigate further: resolve non-gate uncertainty before a firm recommendation.
  • Defer: a binding dependency prevents progress; state what must change and when to revisit.
  • Avoid: reject the proposal as framed because of a Stop condition.
A flow diagram showing gate screening before ranking, with Pass candidates moving toward a ranked list and Hold or Stop candidates kept in a decision record.

Gate status determines eligibility first. A numerical score sequences eligible, sufficiently supported candidates; it does not override a Hold or Stop.

Record the reason as well as the result

Harbor Office Supplies decision record

The compact scorecard below separates the ranked, complete-rating candidates from entries that need investigation or cannot progress. U means the numerical rating is unknown, so the total is Not calculated.

The first two candidates form the current ranked eligible set: FAQ reply drafts before Product-spec lookup. Weekly issue summaries passes the gate but stays outside that ranked set until its unknown data-readiness rating is resolved. Hold and Stop candidates are retained for traceability, not ranked.

Ratings and totals

Compact scorecard view: the first six scorecard columns.
CandidateGate statusVFDPriority score
FAQ reply draftsPass3339
Product-spec lookupPass2338
Weekly issue summariesPass23UNot calculated
Order-status reply draftsHoldUUUNot calculated
Unreviewed refund denialsStopUUUNot calculated

Evidence, decisions, and actions

The remaining scorecard columns, kept separate so the record stays readable.
CandidateEvidence and uncertaintyDispositionNext step / open question
FAQ reply draftsV: Supported—100 requests/week × 6 min/request = 10.0 hours/week of current work. F: Supported. D: Supported—current, approved FAQ sources.Pursue nowCompare solution options. No material question currently known.
Product-spec lookupV: Supported—60 requests/week × 3 min/request = 3.0 hours/week of current work. F: Supported. D: Supported—current, approved product-catalog sources.Pursue nowCompare solution options. No material question currently known.
Weekly issue summariesV: Estimated—benefit is an estimate. F: Supported. D: Unknown—approved issue-category records have uncertain coverage.Investigate furtherCheck representative coverage of issue categories. Does the record set represent typical issues?
Order-status reply draftsV, F, D: Unknown—not assessed after the Hold gate. Gate evidence: order-record processing authorization is pending.DeferObtain or confirm processing authorization. Will it permit the intended order-record processing?
Unreviewed refund denialsV, F, D: Unknown—not assessed after the Stop gate. Gate evidence: the proposal removes required review and appeal.AvoidDo not progress the proposal as framed. No material question currently known.

Apply the decision rule

Build the use-case shortlist

Create a concise use-case shortlist for Harbor Office Supplies using the decision record.

  1. Write the ranked eligible set in order.
  2. Assign a disposition to each of the five candidates.
  3. For every candidate, add a case-specific reason plus a practical next step or open question.

Do not use a score cutoff alone: keep incomplete, Hold, and Stop cases distinct from the ranked eligible set.

Write at least 350 characters (0/350).

Step 8 of 8

Make and defend the recommendation

Integrate evidence, gates, ratings, uncertainty, and next actions into a defensible use-case shortlist for Harbor Office Supplies.

Trace the recommendation

Trace the recommendation

From evidence to a decision

A defensible use-case shortlist is a decision record, not a pitch for AI. A reader should be able to trace every recommendation from the user problem, through gate status and criterion-specific evidence, to uncertainty and a next action.

Keep the five Harbor Office Supplies problem frames in view:

  • FAQ reply drafts: agents need reviewable drafts grounded in the current FAQ.
  • Product-spec lookup: agents need approved product details while answering requests.
  • Weekly issue summaries: the support lead needs a recurring view of issue categories.
  • Order-status reply drafts: agents would draft replies using order records.
  • Unreviewed refund denials: the proposal would deny refunds without review or an appeal path.

A Priority score can support an order among eligible candidates. It cannot turn a Hold or Stop into an eligible recommendation.

Decision traceability

A flow from a support-user problem through a gate, ratings, evidence, and a ranked decision with a next action, with blocked proposals kept separate.

Keep the chain visible: problem → gate status → ratings and evidence → disposition → next step.

Read the evidence brief

Harbor Office Supplies evidence brief

Use this complete evidence brief for the final application. U means the numerical rating is Unknown, not low. Calculate only when Gate status is Pass and all three ratings are integers: Priority score = V + F + D, with a possible range of 3–9.

Current-work figures describe work potentially affected. They do not demonstrate AI time savings.

Ratings and totals

The ratings and totals are a compact view of the use-case shortlist evidence.

Priority score = V + F + D; calculate only for Pass candidates with complete ratings.
CandidateGate statusVFDPriority score
FAQ reply draftsPass3339
Product-spec lookupPass2338
Weekly issue summariesPass23UNot calculated
Order-status reply draftsHoldUUUNot calculated
Unreviewed refund denialsStopUUUNot calculated

Evidence and uncertainty

Use the evidence status attached to each criterion. The final recommendation must add a disposition and next step without inventing evidence.

Criterion-specific evidence for the final recommendation.
CandidateEvidence and uncertainty
FAQ reply draftsV: Supported—100 requests/week at 6 min/request, or 10.0 hours/week of current work. F: Supported—available drafting fit; agent review and manual fallback remain available. D: Supported—current, approved FAQ sources cover typical requests.
Product-spec lookupV: Supported—60 requests/week at 3 min/request, or 3.0 hours/week of current work. F: Supported—lookup fits existing work; review and manual fallback remain available. D: Supported—current, approved product-catalog sources match typical lookups.
Weekly issue summariesV: Estimated—benefit of recurring summaries is an estimate. F: Supported—available summarization fits the weekly review routine; a manual routine remains workable. D: Unknown—approved issue-category records have uncertain coverage.
Order-status reply draftsV, F, D: Unknown—not assessed after the Hold gate. Necessary authorization to process order records is pending.
Unreviewed refund denialsV, F, D: Unknown—not assessed after the Stop gate. The proposal removes required review and appeal.

Write and audit the use-case shortlist

Apply and audit the evidence

Make and defend the recommendation

Using the evidence brief, write a concise use-case shortlist and an audit of it.

  1. Name the first opportunity to explore and explain why it is stronger than the second ranked opportunity.
  2. Rank every other eligible candidate only where the evidence permits a rank.
  3. For all five candidates, record the required disposition, a case-specific rationale, a practical next step, and an unresolved question—or state that no material question is currently known.
  4. Defend the record: explain why the current-work figures are not demonstrated AI savings, and why the Hold and Stop candidates cannot be ranked even if someone claims they could be valuable.

Keep gate status separate from ratings and do not create a score for an incomplete record.

Write at least 700 characters (0/700).

Close with clear boundaries

A defensible recommendation

Compare your recommendation

Ranked eligible set

  1. FAQ reply drafts — Pursue now. It is first because its Priority score is 9 and V, F, and D are all Supported. Its 100 requests/week at 6 min/request describe 10.0 hours/week of current work, supporting a stronger Potential value (V) than the second candidate. This is not a claim that 10.0 hours/week will be saved. Next step: compare solution options. No material question is currently known.
  1. Product-spec lookup — Pursue now. It is second because its supported ratings produce a Priority score of 8. Next step: compare solution options. No material question is currently known.

Weekly issue summaries — Investigate further. It passes the gate, but Data readiness (D) is Unknown because coverage of typical issues is uncertain. Its Priority score is Not calculated, so it is not ranked yet. Next step: check representative coverage of issue categories. Open question: does the record set represent typical issues?

Order-status reply drafts — Defer. Its Hold status reflects pending authorization for order-record processing. It cannot be ranked or scored while that essential requirement is unresolved. Next step: obtain or confirm processing authorization. Open question: will it permit the intended order-record processing?

Unreviewed refund denials — Avoid. Its Stop status applies because the proposal removes required review and appeal. A claimed benefit cannot override that conflict. Next step: do not progress the proposal as framed. No material question is currently known.

Summary

Final review

The selected opportunities now move only to solution-option comparison. This shortlist does not choose a tool, authorize deployment, define a pilot, or approve rollout.

  • Keep the use-case shortlist traceable from the user problem to gate status, evidence, uncertainty, disposition, and action.
  • Rank only Pass candidates with complete integer ratings; a U rating leaves the Priority score Not calculated.
  • Current workload, including 10.0 hours/week, is not demonstrated AI savings.
  • A Hold leads to Defer and a Stop leads to Avoid. Neither result can be overridden by a high value claim.
  • Pursue now means compare solution options; pilot design and adoption planning are later decisions.

Tutorial completed

Congratulations! You completed: Prioritizing AI Use Cases for a Team

You completed the use-case shortlist. You can now take the highest-priority eligible opportunities into solution-option comparison.

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate