I tried similar approaches to the ones commented here but in the end none worked: delivery took longer plus quality suffered. I am not aware of your unforeseen

I tried similar approaches to the ones commented here but in the end none worked: delivery took longer plus quality suffered. I am not aware of your unforeseen circumstances but for me the solution was to plan the whole week and if I'm programming that's it, no interruptions except emergencies. I feel fine if I lose a day or a day an a half to 'unproductive tasks' if the rest of the week I was commiting like a maniac. I learned that 99% of emails, calls and IMs can wait for hours and that's fine; in fact, some communications expire if left unanswered for a few hours, no need to answer at all. After planning for weeks I learned to plan for months. I now know that I can do one big project every 4-6 mos and one small one ever 3-4 wks. The rest of my recipe is discipline, which I completely lack, so every now and then I need to reset the process. Normally the big projects are paying the bills while the small ones are what I call R&D (product ideas). Don't let one of those 'super good ideas' interrupt a work in progress until you've completed an MVP ready for testing/first couple of customers. Finally: if feasible hire help.