I have a similar, but not as well organized system. * If it is an idea for the thing I'm working on, I just file a ticket in the tracking system. It contains e

I have a similar, but not as well organized system. * If it is an idea for the thing I'm working on, I just file a ticket in the tracking system. It contains enough text to remind me of what it is, and let other team members iterate on it as well. It definitely infuriates some of the team members because the granularity of them can be tiny or huge, but the point is tickets can be refactored if needed. It also allows the whole team to discuss bigger things and gives the junior devs something to dive into when they need direction (e.g. lets refactor this like so... ). * I make a todo to flesh out an idea in my todo list if it is unrelated to my current project. Then during review my life times I can make a document about each idea, or add the idea to an existing idea. * i have a rough ranking for idea documents of "do it now", "do it sometime soon", "do it sometime (usually never...)", and "wtf was i thinking". If you ever figure out the 28h days thing - please share, I'll pay well for it.