I love this take, and it's one that’s very much needed. AI’s impact on democratising execution velocity raises many important questions. Not only that, it is also forcing a rethink of what really matters in building durable businesses that solve real customer problems. Building fast and at scale is easier now; the more productive question is whether anyone wants what you are building. I think the way to approach it is to build fast enough to test and iterate, gather real user feedback, drop or pivot what doesn’t work, and scale what does.
Thank you, and yes, exactly. Though I'd push the sequence one step further. The question isn't just whether anyone wants what you're building while you're building it. It's whether you have a clear hypothesis about that before you start. Not a hope. A hypothesis- specific enough to be wrong. Who is the customer, what are they doing today instead, and why would they want this? If you can't answer that precisely before you write a line of code, you're not testing. You're searching. And searching with a product is a much more expensive way to find out.
I love this take, and it's one that’s very much needed. AI’s impact on democratising execution velocity raises many important questions. Not only that, it is also forcing a rethink of what really matters in building durable businesses that solve real customer problems. Building fast and at scale is easier now; the more productive question is whether anyone wants what you are building. I think the way to approach it is to build fast enough to test and iterate, gather real user feedback, drop or pivot what doesn’t work, and scale what does.
Thank you, and yes, exactly. Though I'd push the sequence one step further. The question isn't just whether anyone wants what you're building while you're building it. It's whether you have a clear hypothesis about that before you start. Not a hope. A hypothesis- specific enough to be wrong. Who is the customer, what are they doing today instead, and why would they want this? If you can't answer that precisely before you write a line of code, you're not testing. You're searching. And searching with a product is a much more expensive way to find out.
direction > speed. great wisdom in here Anjali, thanks for sharing :)