I noticed the same a long time ago. Given N tasks, it's good to first "open" some of them that seem difficult, think about possible solutions, and gather any missing facts. If the solution doesn’t "click" when it usually should, just delay it. The answer may come later that day or even after a couple of days.

Paradoxically, it takes more time to solve tasks one by one than to solve them in parallel. There’s also more satisfaction when tasks can be completed in a convenient order (convenient from the developer's point of view, not management’s).

Interestingly, I experimented with applying the same approach to a game of Wordle, and I noticed that the cumulative time spent on the puzzle decreases when taking breaks. And by that, I mean thoughts are elsewhere during those breaks.