4 ms·
Interesting. I read the article as if it was talking about problems that needed solving. You're talking about ideas that (in the interests of the business) need
by Beldin 5y ago
Interesting. I read the article as if it was talking about problems that needed solving. You're talking about ideas that (in the interests of the business) need shutting down.
I would probably go with "that's not a good idea" for the latter.
For the former, when brainstorming solutions, never shut down ideas. That's the whole point of brainstorming! If you want to point out downsides, try a variant of "I think you're on to something there, but how would we handle $DIFFICULTY?"
- franciscop 5y agoIt can be both, I read the comment you are answering to as problems that need solving. "A reimplementation of git" or "a home-made bug tracker" could be trying to solve the problem that they didn't have version control nor a bug tracker, but the proposed idea of creating one from scratch instead of using an existing one (in these clear-cut cases) is ill-advised.
- Yoric 5y agoIn this specific case, both git and a variety of bug trackers were available and very usable. Neither project answered a precise problem we encountered. Both might possibly have answered problems we might possibly have encountered when scaling up, something that never happened.
- PeterisP 5y agoSure, you should not shut down ideas when brainstorming solutions, but there's a point between brainstorming and implementation where the ideas do need to be reviewed mercilessly. The problem in the parent poster's company wasn't that they brainstormed about a home-made project tracker, it was that they went through with spending development effort on that. The brainstorming process is designed for generating alternatives, it's not suitable for choosing between alternatives, that needs to be done in a critical "anti-brainstorming" mindset.