A mental model for rapid product development with no-code and low-code tools: sprint fast through experiments, accept that 95% work, and when you stumble, pause to diagnose before sprinting again. Alternating speed with deliberate slowdowns after setbacks maximizes progress.
Sprint and stumble. I find this to be a great mental model to be making better progress, especially when working with no-code, low-code tools that have such a quick learning curve where you can try a thing, test a thing, try a thing, test a thing. And the, and you can keep on moving forward. Let's try this. It keeps working. Try it. It keeps working. Try it. It keeps working. And so the model can be, let's move forward fast and then stumble. And then we hit something that doesn't quite work. I find that The things work well so often that we don't need to have our fear of the 5% getting wrong keep us using 95% that are going to go relatively right. If we can be moving forward fast and be able to eat the notion that we will eventually stumble, there's going to be something hard, and then we need to slow down to look, I find we will get maximum velocity. Move fast as long as you are confident and your things seem to be working. And then when we stumble, that's when we stop, we look around, and we make progress on what's next.
