What I wish I emphasized to my engineering team at the beginning of the year
I think that taking one full month between releases is too long as it’s really frustrating to receive feedback (especially negative) on the old version of your application:- Your app is great, but the fact that X isn’t working turns me off.- Thanks. We’re aware of the issue and already fixed X. Just wait for the new update.
We’ve got to strive to do at least one release a week. To accomplish that, we have to be super disciplined about cutting out unnecessary features. Don’t try to load as many things as possible in the new update. Add one atomic component, test it thoroughly and send it to App Store. While they’re taking their time to approve the app, we can work on the next update. It’s also great for morale knowing that you saved your progress.
Prioritize the things you’re going to work on based on the following ratio u / t, where u is the utilitarian importance of the feature, t is the time it takes to implement it. No overthinking, very simple. For example, if it takes a week of the client work to create the floating separation between morning and evening rituals in the daily rituals list, toss it. That feature has zero utility even if it took you an hour to code.
Let’s focus and not do unnecessary things.
