- New features also add tech debt, complexity, cost, bugs, makes you slower, and will lose you some sales that way.
- At 0 features you really need to implement features instead of messing about with the bugs in the devops scripts.
- At e.g. Windows scale, maybe stop messing about with new features nobody asked for and fix some bugs, yes.
- In a Laffer-curve-like effect, there must be a point where it peaks and it's better to fix bugs than to implement a new feature.
- It's a very difficult to identify where you are in the curve.
- One of the measures is simple "do X, get money from this guy I have on the phone"
- The other measure is fuzzy, lags, is subjective, can't be traced to a particular feature.
Good luck!
When customers aren't signing up because of lacking feature -> build features. When customers are churning because of bugs -> fix bugs. Else -> somewhere in the middle
- New features also add tech debt, complexity, cost, bugs, makes you slower, and will lose you some sales that way.
- At 0 features you really need to implement features instead of messing about with the bugs in the devops scripts.
- At e.g. Windows scale, maybe stop messing about with new features nobody asked for and fix some bugs, yes.
- In a Laffer-curve-like effect, there must be a point where it peaks and it's better to fix bugs than to implement a new feature.
- It's a very difficult to identify where you are in the curve.
- One of the measures is simple "do X, get money from this guy I have on the phone"
- The other measure is fuzzy, lags, is subjective, can't be traced to a particular feature.
Good luck!