Hi @Pedro Ainessil! Sorry for the late response, we had a DevOps team building activity yesterday pm (my first time go-karting! 🏎️ 😅).
Thanks for your question. I don't think that delivering value fast through small incremental steps has to compete with delivering quality and reliability. On the contrary, I believe that holding on to changes and delivering them in larger increments would make it much harder for our small team to cover all the surface and ensure it's bug free and stable. Especially as we don't have the time to create very thorough end-to-end and integration test suites, only some lower level unit tests for the trickiest parts. Our QA has to be done in the field, in collaboration with devs. Having very small increments allows us to work with them to ensure everything works as expected in their real world scenarios.
Also, with our early adopters, we benefit from them having more patience and will to make do with a few kinks and imperfections, that would be more damageable to our larger audience. But, in order to preserve that patience and good will from our early adopters, we treat them as VIPs, prioritizing fixing any issues they may encounter, spending time with them live to address those issues. That way, they feel important, supported and know that the risks they are taking by being early adopters is well balanced by our high level of engagement with them.