Product Adoption: Don't Build Before You Feel Pull
The best time to solve a feature adoption problem is before development. Talk about the user's project, look for real pull, and don't build on polite interest.
The best time to solve a feature adoption problem is before development. Talk about the user's project, look for real pull, and don't build on polite interest.
Value and risk are correlated almost everywhere. You cannot remove the risk that comes with real value, but you can de-risk it efficiently. That is agile.
Most AI efforts start with tools and demos. Better to use product discovery to aim AI at a real business constraint and test the riskiest assumption first.
Spec-driven development looks like a step backward if you read it as requirements theater. The better frame: the spec is a higher-level language for intent.
Claude's /goal feature lets agents work until a completion condition is met. Most examples are output-oriented: tests pass, backlog empties. Outcome is missing.
The issue isn't the title on the org chart — it's who has the standing to make tradeoffs. How I think about ownership across teams, platforms, and groups.