I make lists of things that need to be done during the day when I start - usually 3-10 things, and a list of things that might be deferred, which makes it easie

I make lists of things that need to be done during the day when I start - usually 3-10 things, and a list of things that might be deferred, which makes it easier to make sure I return to the right things when I get interrupted. If someone comes to talk to me, I write down any actions that come out of the conversation immediately, so I don't lose track of them, and try not to promise to resolve them immediately - that adds to the above list, so things naturally rotate in and out over time. I like to take half hour walks to think - that helps ensure that I'm really working on the right things on a longer timescale, even though I get distracted on details at times. With code, interruptions have forced me to think in terms of breaking work up into small, atomic commits. It makes it harder to do larger design/refactoring exercises, but it forces you to get better at splitting work up. With smaller tasks, I tend to make a lot of tickets to track what needs to be done over larger timespans, which conveniently makes it easier to delegate.