There are many aspects to GTD, but which one is your personal hurdle? What is preventing you from getting things done? I am not talking about the methodology directly perhaps, but habits and tendencies that basically makes getting things done challenging. I want people to share and comment on their own insights and learn from each other. I think my biggest personal hindrance is multi-faceted, but essentially concerns project planning. The project I am struggling with the most concerns making an app. It's a side-project as I am mainly studying for my computer engineering degree, thus I have a few things to juggle. This project is something I have been very interested in making on and off for a few years, and recently I was able to at least consolidate all the information into a few places (being disorganised was my first struggle). This is all well and good, but I have a tendency to go around in circles and wasting time in my current process. I am at the prototype stage and I know in big chunks what I need to do; set up a backend server along with a database that can serve the mobile app. The problem is that I have a tendency to go overboard with how I do it. This may come down to a lack of experience along with perhaps insecurity (must be done the right way, pre-optimisation). A typical cycle might be a bit like this: research different backend technologies and databases wondering how this would be in a production setting (not relevant) with production principles such as scaling etc deciding a technology → then look for resources to learn deciding on using books (slow) and typically at a level that is too low and boring then get demotivated because it is boring and slow, ultimately forgetting why I am doing things repeat from the beginning again, or going back a few steps and repeat To be fair, I am not exactly saying GTD is the cause of this, but that I am struggling with this as a part of project execution. The cycle can be summed up like this: spend a lot of time researching things without the correct criteria mix in unnecessary system properties that aren't currently relevant, making it more complex taking the slowest and most comprehensive route as learning resource (books vs articles) become disillusioned and bored with what I am doing wait a few days and repeat the cycle One good things is that I do not want to quit, understanding that I have to change my ways for how I go about this instead of just throwing my hands up. While the actions I take are not just in the context of project planning, I am betting that most of the problems are based on that phase. After being frustrated by another cycle yesterday, I decided to take a step back and ask myself: "What are you doing?" There were a few insights that came from that question: know thyself: understand how you can corrupt the other bullet points by basically going on a tangent and not following your own advice keep it simple, stupid it's easy and common to think too far ahead (pre-optimisation) choose fun/fast over perceived perfection (slow, boring) be precise about what you are doing, how and why to ensure that you don't fall into the same cycle as before set up typical pitfalls, know when you are approaching them set the correct expectations: things are new, get familiar with it first and foremost continued from the last step, but another reminder to set clear borders on criteria how long do I actually believe is necessary to spend on this? any minor projects that take over one week, that is a red flag you already know a bunch of stuff, don't start over with things use your brain, there is nothing wrong with being a bit fuzzy with details and spending time thinking, you don't need a book or explanation for everything really stuck? find a short video or article from trusted resource find trusted resources and help and stick to them official documentation good forums good article sites books and videos courses are mostly too slow, comprehensive and boring don't worry what you are missing find appropriate materials to the cause at hand remind yourself what you are doing and why on a regular basis to keep focus enter the right mindset if needed before working on something keep the correct perspective and mindset for learning, avoid veering off Several of these points (when written) are obvious failures on my part regarding the planning stage of GTD. This along with some lack of self awareness (hopefully changing now), made for some real frustrating times when working on the project. I am pretty much a creative person that easily creates a behemoth of a project, making the organisation phase of NPM a daunting task. Perhaps I have set up a high bar on the project I am working on along with studies (from prior work I know this is easily a full-time job), so keeping up with is difficult. There are other tangents I could go on, such as having a system to ensure that I know what I previously did to avoid confusion. But I think this can be done through a weekly goal, using daily updates and weekly reviews for that purpose. Hope this was informational for people struggling in the same area and encourages you to share some of your own struggles and insights. Now I will do my weekly review, with an improved mood than I had when originally starting to write this post.