Iteration

“The iteration process is not thinking about things as 'We need to plan for the next 24 months.' Having a more agile type approach to everything - the storytelling your salespeople are doing, landing pages, logo design, brand itself. Being more open to everything being possibly iterated on using data to validate.”

“When you have great strategy but poor execution, you don't win because your strategy never makes it to the market. And what's even worse is that you have learned nothing. You don't know whether it was your strategy that was wrong or whether it was your execution that was wrong.”

“I often go with minimalist prompts. That's also how I code as well. I have a vague idea for what I want to build and iterate from there. Other people, product managers like to write PRDs and more descriptive things, and you can do either of those things.”

“It's not about making the right decision, it's about making the decision. Once you commit to a decision, you learn more post committing than in hypothetical analysis. As long as your decision is 70% right, you can iterate on that 20-30%. If you don't commit, you don't get any new high fidelity information.”

“There are many scaling laws when you build AI systems. This one is about when you put in more work, the product reliably gets better. We painstakingly identify places where it gets stuck and address them, tune the entire system quantitatively with a very fast feedback loop to improve it in the areas where it got stuck.”

“Open mics are the real live experiments. You put something out there, you get very clear micro feedback from users, and then you get tough feedback sometimes. And I think as product builders, that's actually one of the great skills to have, which is you sometimes launch stuff that have a fantastic vision, but the first version is not quite there.”

“The difference between people who use Claude Code very effectively and people who use it not so effectively is are they asking for the ambitious change? And if it doesn't work the first time, asking three more times because our success rate when you just completely start over and try again is much, much higher than if you just try once.”

“If you have a mechanism to listen to users, get something in their hands quite quickly and then get their feedback on it to run it back through a feedback loop, you're very unlikely to go wrong. If you don't have that feedback loop, go figure out how to create it.”