3 ms·
Have to second this. I used to have so many 'started in excitement, but probably never going to work on it ever again' projects. Then I started an 'Ideas' boar
by bgdam 6y ago
Have to second this. I used to have so many 'started in excitement, but probably never going to work on it ever again' projects.
Then I started an 'Ideas' board on Trello, and forced myself to put ideas there instead of working on it immediately. I am not allowed to work on an idea unless it's been on the board for atleast two weeks.
This forces me to spend a lot more time thinking past the initial one-line idea, and refining it. Eventually, for about 90% of the ideas, by the end of the two week period, I've come to the conclusion to discard it.
So now, the 10% that I do end up working on, are much more likely to see sustained work being done on them.
- highfrequency 6y agoThis is interesting! To clarify: in the first two weeks, you don't allow yourself to work on the idea (eg start writing code), but you do allow yourself to research the idea. And you find that the initial research phase usually turns up compelling reasons not to undertake the project after all. Is this right? How do you prevent the research phase of a new idea from distracting you from your current project?
- bgdam 6y agoI usually have a fixed block of time for working on side projects on weekends. The research phase usually happens through the week, whenever I have the time to think about it. My problem generally is splitting the weekend time across too many projects, with newer ideas displacing older ones. Having much fewer ideas to work on in total, helps me spend more time on them.