I've been struggling with the same issue for a long time. Building chocolab.com.au has had be jumping from being a Chocolatier, a pick/packer, programmer, marketer, designer, manager and all the business admin that goes with it, and now balancing running it with my other projects. In the first few years the biggest mistakes I made was not treating myself as a limited resource, and not limiting the scope of what I could accomplish. Although I do have a co-founder, the same time balancing issues still occur. Echoing what @EbrahimKhalilHassen said, my first impression of "Mission Control" is that you need to narrow your use case, and build the smallest version of your concept you can (which could just be a small part of your vision). Try to off load, or simply avoid doing things that don't play to your strengths. These days if an idea will take me more than a week or two to launch initially into a useable version (thats live for other people to use), I don't build it. As the risk of burning out after a few months and never actually finishing it is not worth it.
Hey Spencer, thank you. That really resonated with me. Just the other day I heard a podcast with Seth Godin where he spoke about the fact that humans are terrible at understanding the "sunk cost" concept. And this is so true for me. I have invested a lot of time and energy into Mission Control. It will be extremely hard to a) let go of it or b) remove features and narrow the use case. To be honest, I have already reduced the use case and removed features in the past weeks. I got carried away because I was not able to keep it simple while also creating something meaningful and different.
If you have a moment and are willing to elaborate on your first impression: Would you be able to point your finger at the part that you feel I could/should remove/reduce? What should I focus on from your perspective?
Thing is you don't have to completely let go of everything, you can launch and then add features later. Do you have a list of features that are done and not done? Try to remove the ones that are not done first. I personally would remove the data & analytics part to launch, and work on adding this later when you have a userbase to get feedback from on what data they would actually want/need.
I've been struggling with the same issue for a long time. Building chocolab.com.au has had be jumping from being a Chocolatier, a pick/packer, programmer, marketer, designer, manager and all the business admin that goes with it, and now balancing running it with my other projects. In the first few years the biggest mistakes I made was not treating myself as a limited resource, and not limiting the scope of what I could accomplish. Although I do have a co-founder, the same time balancing issues still occur. Echoing what @EbrahimKhalilHassen said, my first impression of "Mission Control" is that you need to narrow your use case, and build the smallest version of your concept you can (which could just be a small part of your vision). Try to off load, or simply avoid doing things that don't play to your strengths. These days if an idea will take me more than a week or two to launch initially into a useable version (thats live for other people to use), I don't build it. As the risk of burning out after a few months and never actually finishing it is not worth it.
Hey Spencer, thank you. That really resonated with me. Just the other day I heard a podcast with Seth Godin where he spoke about the fact that humans are terrible at understanding the "sunk cost" concept. And this is so true for me. I have invested a lot of time and energy into Mission Control. It will be extremely hard to a) let go of it or b) remove features and narrow the use case. To be honest, I have already reduced the use case and removed features in the past weeks. I got carried away because I was not able to keep it simple while also creating something meaningful and different.
If you have a moment and are willing to elaborate on your first impression: Would you be able to point your finger at the part that you feel I could/should remove/reduce? What should I focus on from your perspective?
Thank you!
Thing is you don't have to completely let go of everything, you can launch and then add features later. Do you have a list of features that are done and not done? Try to remove the ones that are not done first. I personally would remove the data & analytics part to launch, and work on adding this later when you have a userbase to get feedback from on what data they would actually want/need.