4 ms·
Baby steps 1) Start with ancillary or related tasks. Basically any task that will be needed for the project but maybe not now, and that won't mentally task you
by nocommandline 6y ago
Baby steps
1) Start with ancillary or related tasks. Basically any task that will be needed for the project but maybe not now, and that won't mentally task you a lot. E.g. pick a color scheme, register a domain, come up with your Call to Action/tagline. Draw up a list and check them off as you do them. Checking them off gets the motivation to work flowing
2) Put your design down on paper, essentially write down your pseudo-code/process flow. It's easier on the brain and actually is a good help when you finally start coding (lots of people start coding without having fleshed out the design)
3) Assign yourself a daily time quota to work. Start small e.g. I must do at least 1 hour on this project everyday. Starting small means you're able to meet your target. As time goes on, you'll find yourself blowing past that time and doing more work.
4) Focus on getting something out (very very rough but call it V1). Don't focus on a polished output. Having a first version no matter how rough tends to get the juices flowing so you can refine
5) Be willing to accept that you will not be productive on all the days and don't beat yourself up on those days. I think that feeling guilty on the days we don't 'accomplish' stuff makes us wallow in self-pity which even makes us less motivated to work.
What you're going through is usually my experience towards the end of a project i.e. my struggle is to actually push through and finish the project. I wrote about this on the blog of my most current project (see my profile)