Resources

Things that should be useful even if we never work together.

Free, no email gate, no funnel trick. Take it, use it, and if it lands right, reach out.

Self-assessment

How AI-native is your product development?

Three questions, two minutes. The same diagnostic I run with founders and product leaders before scoping a retainer, distilled to the parts a team can answer over coffee.

Score each question 1, 3, or 5. Add the totals. The result tells you which of three spots most teams sit in, and what changes things.

Question 1 · Workflow vs. toolsIn the last six months, did you change how product gets built, or just which tools you use to build it?

1. We added AI tools. Claude, Copilot, ChatGPT are in the team's hands, but the workflow looks the same as it did last year.3. One stage changed. We restructured one part of the PDLC around AI. The rest still looks like 2024.5. Multiple stages changed. AI is load-bearing in how we ship. PRDs, sprints, customer discovery, or QA: at least two of those have been redesigned around AI capabilities.

Question 2 · MeasurementCan you point to a number (release velocity, defect rate, time-to-PRD, anything) that has moved because of AI in the last six months?

1. No. Either no metric has moved, or we can't tell whether AI caused it.3. Yes, but loosely. One metric moved, but we haven't isolated AI as the cause.5. Yes, with the work shown. At least one metric moved, and we can explain how AI changed the inputs.

Question 3 · DefensibilityIf a customer asked which 2 to 3 AI features in your product they couldn't get from a competitor, could your team answer in under a minute?

1. No clear answer. We'd struggle, or we'd describe AI features that any competitor could ship in a sprint.3. We have an answer, but it's thin. Real features, but the moat is shallow or we can't articulate it well.5. Yes: specific, defensible, easy to say. Specific features, specific differentiation, and the team agrees on the answer without rehearsal.

Pick a 1, 3, or 5 for each of the three questions to see your result.

Coming

More tools and frameworks on the way.

I ship resources as they're baked. Next: the build-vs-buy decision sheet.