[...]
So it was not meant.

The benefit of a solution based system is that every idea is handled itself and no one is missed. And it does not only work with solutions which could all come true.
It should be easy to reject a solution because of "other solution for this problem got more votes" or "easier solution taken / to expensive".

This could also based on a automatic system. Only "Solutions" with more than 10 Votes and 66% positive of them could get in the proposal workflow. The other ones are rejected automatically. (by vote of the community)

When a Brainstorm is finished in real life. You have always to made the decitions on a Solution level. So the Brainstorm system and the workflow should work the same way.

The old question. One Brainstorm, 19 Solutions. The first, popular solution is implemented. So the Brainstorm reached the target? What about the other 18 solutions?

With this system it shouldn't be a problem to decide: "We would implement Solution #1, #3 and #8."
The rest of it are overlapping, blocking with one of the implemented, to expensive or some of them are still good ideas for the future.
I'm sure. It's going this way at the moment. But no one could see it at the current Brainstorm in a clear way.

To make it easier for everybody:
Call it Idea instead of Solution. Call it only a solution when the implementation is on scedule.