Before building or spending, explain the customer need, the supporting evidence
and the result you expect.
Products become expensive and confusing when things are added without a clear
reason. Intention keeps the product small, useful and connected to evidence.
A simple illustration
A team considers adding automatic follow-up emails. Before building, it defines
who needs them, what problem they solve, what evidence supports the request and
what result would show that the feature helped.
Thinking shift
Instead of Can we build it?
→ Ask What evidence says it should exist?
Try it yourself
Choose one planned feature or expense. Write its customer, problem, evidence,
expected result and success measure. Pause if any answer is missing.