You volunteered to lead the first AI project, which makes you brave, because the base rate is brutal: researchers found the vast majority of corporate AI pilots stall without measurable impact. The pattern behind the failures is consistent — projects scoped like transformations instead of tasks. This guide is about the opposite move: a first project small enough to ship.
Why first AI projects die
The killer is scope. First projects get pitched as transformations — many workflows, every team, a steering committee — and researchers find the vast majority of corporate pilots stall without measurable impact. A second killer hides in tooling: generic chat tools bolted onto workflows they never learn from. Both failures share a root: the project was too big to finish and too vague to measure.
The shape of a first project that ships
A single task, for a single team, with a visible before and after. A named owner. A person reviewing every output. And 'done' defined before you start — the report drafts itself in minutes instead of an afternoon, say. Ship it, measure the time returned, tell the story simply, and you have earned the right to a bigger swing.

Build the skill before the project
Scoping well is a skill you can rep. Unscary, the iOS app from B43, trains it the way B43's in-person corporate courses do: short lessons on what AI does well, hands-on reps where you scope and check small real tasks, points and streaks to keep momentum, and a personal progress report that shows you getting sharper before the project needs you to be.
The bottom line
Your first AI project does not need to be impressive; it needs to be finished. Small, checkable, shipped — that is the whole playbook. The practice that makes it repeatable can start before the project does.
Ship the small win first — practice makes it repeatable
