Day Zero: The Metric Mandate Gate

Module 4 · Section 3 of 10

Day Zero: The Metric Mandate Gate

Before Day 1 begins, every AI project must pass through a single gate. Five questions, all requiring specific answers:

Question	Bad Answer	Good Answer
What specific number will change?	”Improve customer service"	"Reduce average ticket resolution time”
What is that number today?	”It takes too long"	"4.2 hours average (Q4 data, 12,000 tickets)“
What’s the minimum improvement that justifies investment?	”Significant improvement"	"Below 2 hours (52% reduction)“
When will you measure?	”After we have enough data"	"90 days post-deployment”
What result means you stop?	”If it’s not working"	"If not below 3 hours by Day 60, reassess approach”

This works at every scale. Here’s what the same gate looks like for a freelancer:

Question	Bad Answer	Good Answer
What specific number will change?	”Spend less time on research"	"Hours per week spent on client research”
What is that number today?	”Too many"	"6 hours/week (tracked over last 3 weeks)“
What’s the minimum improvement that justifies the subscription?	”Some time savings"	"Under 3 hours/week (50% reduction)“
When will you measure?	”When it feels faster"	"After 30 days of daily use”
What result means you stop?	”If I don’t like it"	"If not under 4 hours/week by Day 30, try a different tool”

The gate is binary. If you can answer all five questions with specifics, proceed to Day 1. If any answer is vague, go back and define the metrics before you start.

This isn’t red tape — it’s the difference between a project with clear ownership and a project with excuses.

Pause and apply: Fill in the Metric Mandate for the workflow you want to improve this quarter. If you can’t complete it, don’t skip ahead — that’s the gate doing its job. Use the Metric Mandate tool to work through it properly.

Use the Metric Mandate tool to work through all five questions before proceeding to Day 1.