[jnem]

I disagree. Ive seen too often the person who is willing to say X,Y,Z is wrong, but cant offer a solution to solve X,Y,Z. Its the solution that matters. Bringing your CEO or any higher-up a problem without a solution is just adding to the noise that busy person already has to deal with. The whole purpose of an employee is to take an existing or new problem off of the CEOs plate.

[TheOtherHobbes]

This is fine in theory, but most solutions require time, resources, people, money... all things that employees lower down the hierarchy are unlikely to have.

If you're saying 'Bring a suggested solution but don't try to implement it without buy-in', that's a slightly different process.

The issue of who notices/fixes/prioritises/analyses tactical and strategic problems, and who assigns resources for the fixes, can make or break companies.

It's not a simple problem. I suspect a lot of popular solutions are probably sub-optimal.

[jnem]

True, if we get down to the nitty gritty, its not as simple as I portrayed. My intent was to say, bring an idea for a solution, don't just bring a problem. If I had two employees who came to me with the same problem, and one came prepared with a recommended solution and the other one didn't, it would be clear to me who the more valuable employee is.

[Retra]

If my CEO is going to demand internal pre-prepared solutions to everything, then I'd demand that they be competent enough to not need my input anymore.

I mean, "hire someone who knows how to fix this" is obvious enough that it needn't be stated, nor defended behind this "bring an idea for a solution, don't just bring a problem" talk.

Which frankly sounds like something a motivational poster writer should be saying, not someone concerned with running a business. Platitudes are rarely the solution to a meaningful problem, in my experience.

[jnem]

No one said demand.

[Retra]

No one said "take everything literally" either.

[harryh]

You're 100% right and I definitely should have said that. Presenting a good solution to the problem is critical.

[q2]

If you visit a doctor with a problem, will you go along with possible solutions or you will point out problem and expect solution from doctor?

If you are QA engineer, you will point out issues with the tool but making reasonable and appropriate solution is developer's job. Is n't it?

You can point out the problems with your car but you cannot fix them and may be mechanic/engineer can offer solutions.

So I disagree that people should not point out issues if they do not know solutions.

CEO's need not have to solve all on their own and they can route them to appropriate experts for solutions. If that is not possible to solve immediately, offer a time line. If CEO still think, that is not problem/issue at all, let him offer convincing reason. So we have multiple options here rather than suppressing discussion.

Many managers use this type of logic to suppress debate,dissent,discussion ...etc and gradually people shut their mouths even if problem is right in front of their eyes. I think this is avoidable.