AI Scoping & Feasibility Checklist

An interactive, practical checklist to evaluate AI fit, data readiness, technical constraints, risk, and likely ROI—plus a simple scoring method and gating thresholds to prioritize use cases for prototyping.

Interactive Tool

AI Scoping & Feasibility Checklist

Use this interactive checklist to assess whether an AI use case is ready for a prototype. Answer each prompt honestly, capture notes, and follow the simple scoring guide below to prioritize work. This tool saves your responses so teams can compare opportunities and build a prototyping pipeline.

Scoring guide (simple weighted model)

  1. For each scale item (1–5) treat the response as its numeric value.
  2. Map select/yesno items to numeric equivalents where noted in the field help.
  3. Weighted total = (Objective & Metric 15%) + (Data readiness 25%) + (Technical constraints 10%) + (Integration & Ops 15%) + (Expected uplift & ROI 15%) + (Risk & Adoption 20%). Multiply each component by 100 to get a 0–100 score.

Gating thresholds (recommended)

  • Score ≥ 70: Proceed to a timeboxed prototype (MVP) with defined success metrics.
  • 50–69: Invest in data readiness, labeling, or narrower scope; re-evaluate after preparatory work.
  • < 50: Do not prototype; refine the problem or deprioritize.

Use the Recommended next step field at the end to capture a practical action. If you want automated scoring or dashboards, see Capability Enhancement notes below.

Short name that uniquely identifies this opportunity.
Who completed this checklist. Useful for follow-up.
Yes = objective is measurable and tied to a business metric (score maps: Yes=5, No=1).
Name the metric the project will move (e.g., reduce churn %, increase throughput).
One or two sentences describing the user/customer impact.
Select the best match. For scoring, map: None=0, Some unlabeled=1, Partially labeled=3, Mostly labeled=4, Fully labeled=5.
Consider completeness, accuracy, and relevance.
1.0 10.0
Provide a rough numeric estimate if known. Helpful for feasibility planning.
Enter numeric ms for real-time needs or type 'batch' for non-real-time. High real-time demands may increase cost and complexity.
Describe limits on model size, GPUs, cloud spend, or on-device requirements.
Estimate effort to integrate model outputs into existing systems and workflows.
1.0 10.0
Consider labeling needs, model retraining, monitoring, and MLOps effort.
1.0 10.0
A rough percent change (e.g., 5 = 5% improvement). Helps with ROI thinking.
Narrative estimate: key cost elements and expected benefits.
Is there an identified owner and decision-maker?
1.0 10.0
Likelihood that users will accept and adopt the solution.
1.0 10.0
Select any that apply. Presence of flags increases risk and may require gating work.
List potential biases, fairness issues, or reputational risks to consider.
Capture assumptions, data owners, timelines, or blockers.
Select a practical short-term action based on this assessment.
Optionally compute a weighted score using the scoring guide and enter it here. If you integrate this form with a spreadsheet or dashboard you can auto-calculate this.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.

Discussion

Comments and conversation will live here.