Find the use case worth building

1. 01Write up three short interviews: who does what today, how long it takes, what goes wrong

   ls interviews | wc -l

   You pass when: Three files, each with at least one number someone gave you (hours a week, claims a day, error rate).

   Check step 1 interviews/

2. 02List five candidate use cases and score each: reach, impact, confidence, effort

   The top score is rarely the most exciting idea. It is usually the dull task many people do every day.

   grep -c "^|" rice.md

   You pass when: A table with five scored rows and a total (reach times impact times confidence, divided by effort).

   Check step 2 rice.md

3. 03For the winner, write the success number and how it will be measured

   grep -n -i "success" BRIEF.md

   You pass when: A sentence with a number and a date, such as: 70 percent of claims under 100 decided with no human, at under 2 percent wrong payouts, by week six.

   Check step 3 BRIEF.md

4. 04Finish the brief: problem, users, success number, what is out of scope, what needs a human

   wc -w BRIEF.md

   You pass when: Under 400 words. A person who was not in the interviews can say what you are building and how you will know it worked.

   Check step 4 BRIEF.md

The check runs on the computer, not on your word: a step passes when its command exits with 0 there.