I've moved on from a method like this to an even simpler one: Do The Most Important Thing Now. It's usually completely obvious what the most important thing th

I've moved on from a method like this to an even simpler one: Do The Most Important Thing Now. It's usually completely obvious what the most important thing that I need to do is. And if it's not then I can ask other people around me and clarify. When that's done, The next Most Important Thing is obvious again. Mostly this is about software product dev where The Most Important Thing is a feature or bug fix or something that's going to take a few hours at least. It's mainly about not shoving thousands of ideas into the Backlog where they will just never get done. Instead of a whole development plan that gets caught up in old assumptions and stale priorities, just Do The Most Important Thing Now and keep doing it. At some point The Most Important Thing will be shipping the product in time for the marketing event.