I think the last part you touch upon is one of the natural dangers of our profession. In my experience developers are simply extremely good at spotting potential issues in projects.
Which can be very good if you’re trying to minimise risks or estimate tasks. It can also be really bad if you’re doing it in the idea-generation part of a project, and it’s just too easy to carry your fault focus into those meetings. Especially if you go directly from development to a brainstorming workshop. I know that this is something I’ve had to work quite hard at myself. Thinking twice before speaking out, to make sure I’m going to contribute something useful. Typically my golden rule is to keep quiet unless what I have to say is positive or supportive. Because it’s exactly like you put it, it can be done.
Which can be very good if you’re trying to minimise risks or estimate tasks. It can also be really bad if you’re doing it in the idea-generation part of a project, and it’s just too easy to carry your fault focus into those meetings. Especially if you go directly from development to a brainstorming workshop. I know that this is something I’ve had to work quite hard at myself. Thinking twice before speaking out, to make sure I’m going to contribute something useful. Typically my golden rule is to keep quiet unless what I have to say is positive or supportive. Because it’s exactly like you put it, it can be done.