Sometimes they can be incorporated in another project without much effort (they are not worth doing on their own but while doing something else it can make sense. With a visible list everyone can know what has been thought of and given low priority – they might be sparked by an idea either to give reasons why that should be a higher priority or as in brainstorming to propose another idea… You can look at the list when thinking about a redesign and incorporate whatever might make sense.

When staff have little blocks of time items can be assigned for them to work on (ofter serving double duty – getting the job done and serving to provide a task that provides some employee development…) – these tasks often may not be picked because of priority but a combination of priority, educational lessons and available time, skills…

Over the years working in IT (which may lend itself particularly well to tasks that don’t make sense as stand alone items but make sense to remember whenever certain parts of the code are going to be improved), and coaching staff I have found keeping a list of all the ideas useful.

You do have to be able to separate the tasks that really require proactive effort and those that might be nice to get to but realistically are fairly low on the priority list. I must admit I have not seen others find keeping a more detailed list useful but I do.