3 ms·
I've found that if I can't just complete a certain feature, task or function on my product, and it keeps dragging on, then there is likely a reason for it being
by happybuy 8y ago
I've found that if I can't just complete a certain feature, task or function on my product, and it keeps dragging on, then there is likely a reason for it being too difficult (more than just laziness on my part!)
A good approach when this happens is to redefine the feature. Either by reconsidering its importance, investigating different ways to achieve a similar outcome or mostly decomposing the feature into even simpler and more minimal deliverables and implementations.
Then deliver the extremely minimal implementation.
In a lot of cases you then come back and make it more rounded later on, or in many cases, the simpler deliverable is actually all that is required and you move onto something else entirely.
It's taking a disciplined and strict MVP approach to every task you have and focusing more on continual delivery as a north star. This tends to work because – as noted by the author – giving up on a side project is the biggest risk and one of the larger reasons for failure (you can't succeed if you don't show up).
By always delivering something/anything you get the satisfaction and reward of progress which is a lot of times all that is needed to keep going.