If it’s really common sense, it should be easy for you to explain why. So let’s all agree to never use “common sense” again.
~ Ben Cotton
I feel like we should use, “I think it’s obvious that…” That makes it very clear—to the listener, but also to myself—exactly what I’m glossing over and why.
Now it may turn out that what a junior employee sees as a problem that they don’t have an answer to really isn’t a problem. On the other hand, some problems are much easier to identify than they are to fix. This is particularly true with ethical and cultural problems.~ Ben Cotton from, https://funnelfiasco.com/blog/2018/02/15/dont-need-answer-report-problem/
This piece is short, so my pull-quote may not make complete sense. I don’t like to pull-quote so much that you can get away with NOT reading the source because, in general, if I’m linking to it then I think the source is important enough to be read entirely.
Ben raises a point here that jumped out at me once I saw it. I’ve been hearing and saying that same piece of advice and, yeah… it’s wrong. Yes, if you can bring a solution (or solutions, or even a half-baked first attempt at a solution) with the problem report, great! …but do not—never under any circumstances—refrain from speaking up when you see a problem. It’s either not a problem and you’ll level up when someone explains it, or it is a problem, or it’s a system in-built blind spot that is a problem… or… you know what? Just speak up.