To be honest to ourself. For past 2 weeks, we failed to have even one active user.
It did look like we make something improved; polished UI, animation, landing page, profile, auth.
And majority of those didn’t contribute directly to our current stage and help get active user so we start learning.
From design to code , the whole cycle takes a lot of effort.
The code that improve / fix current problem might not be future proof often.
When there is new design & feature, it needs re-design structure. This is un-efficient.
Improve & iterate is important. How we keep speed at same time? I figure out what I feels rushing is because the speed of learning matter. When plan to serve multiple users, the fear of “product crash / not good” arise. Because this make our user funnel looks bad.
And we don’t need to care about user funnel at all before we even build & validate something people want.
Create a useful small subset, so we no need to delete it in future. When everything we do is useful and validated, even is a small step. We saved energy to work on something else. The most important: Your effort don’t wasted.
I think to reach the max speed of learning while keeping highest quality of future proof design / code is to derive small subset from how overall the product will be in future and make it work for one person.
Right now, for everything we built, planned before. We have to forget about it & start to derive things that might work for that one person.
Eventually we will know how it should scale after we get it worked for one person.