Killed off our roadmap in favor of a continually updated list of 'no's.'

Each of our meetings ended up with us having a roadmap that was much longer than before we started planning. Some good idea appeared, it seemed reasonable, and went into a document that just kept growing and growing, while our shipped output did not budge an inch.

Three months ago we tried something else. We maintain a list of things we won’t be doing and the rationale behind each decision - be it mobile apps, Slack integration, or white labeling. Every time someone asks for one of those features, we just direct him to the explanation instead of going over the same ground.

Ironically enough, being explicit about what not to do somehow led to our projects being completed faster. Wonder if anyone out there ever tried an approach like this instead of a regular roadmap and how well it worked after team grew beyond initial few members?