The least productive teams I've been a part of are the ones where everyone is waiting for their turn to say why an idea is bad. Sometimes being "too smart" can hold you back from building something genuinely new.
Shooting down ideas is not a skill
11–20 of 187 posts
Re: Shooting down ideas is not a skill
#12Re: Shooting down ideas is not a skill
#13Earlier quoted context omitted.
Oh, the irony...
Knowing how to stop a bad idea is a skill. Knowing when it's a bad idea is a skill. Knowing when you don't know is a skill. There's more than one skill in life. More than one may be applicable to a situation. Everyone on this forum has probably run into one of the "idea guys" who just need a tech cofounder to do the coding for 2% equity.
Re: Shooting down ideas is not a skill
#14Earlier quoted context omitted.
Knowing how to stop a bad idea is a skill. Knowing when it's a bad idea is a skill. Knowing when you don't know is a skill. There's more than one skill in life. More than one may be applicable to a situation. Everyone on this forum has probably run into one of the "idea guys" who just need a tech cofounder to do the coding for 2% equity.
I expect the comment was about your (pre-edit) "there doing" vs the current "they're doing", shame you didn't acknowledge your mistake in the change.
Re: Shooting down ideas is not a skill
#15Yes, it is. > The person proposing has been thinking about this for weeks or months. This doesn't mean they know what they're doing. Their thoughts can be bad .
Oh, the irony...
Re: Shooting down ideas is not a skill
#16Re: Shooting down ideas is not a skill
#17Re: Shooting down ideas is not a skill
#18Re: Shooting down ideas is not a skill
#19Re: Shooting down ideas is not a skill
#20uh no.
The best way (IMO) is "Look, I've tried that idea and X happened, you might have better luck, but be aware"