i think this is one reason that, at Canonical, you can't really get an idea past the starting gate unless you have a decent engineering spec to go with it. how will you build it? how does it actually meet user's needs (even if you're inventing a need)? what are the detailed scenarios that explain how users will interact with the executed idea? is it suitable for FOSS/crowdsourcing PRs? And most importantly, can you write down how someone off the street would easily be able to tell that you've implemented a useful idea? Ideas don't go away -- we use Trello for those, and they go in our backlog -- but engineering-wise, NASA-countdown-to-launch-wise, HTH do you get that idea into something practical, useful, and presentable?