Every workplace has that one colleague who has an opinion about everything. Spiritual leader Gauranga Das called out this exact dynamic in a recent LinkedIn post, arguing that people who actually offer solutions do more for a team than the ones who just poke their nose in every idea. The post clearly hit a nerve, plenty of professionals jumped into the comments agreeing that ownership and constructive input are what actually make a workplace function.
The colleague with an opinion on everything
You know the type. Every idea becomes a problem, every suggestion gets picked apart, every plan comes wrapped in reasons it won’t work. That’s the scenario Gauranga Das opened with, and the twist is what happens next. Ask that same person what they’d do instead, and the criticism often just… stops. Silence where the alternative should be.
Finding problems is easier than finding solutions
There’s a reason for that silence. Spotting what’s wrong with an idea takes a few seconds. Building something better takes time, thought, and a willingness to actually be responsible for the outcome. That’s the gap Gauranga Das was pointing at, criticism alone doesn’t move anything forward. It only becomes useful once it comes with an idea attached.
Why solution-oriented people stand out
The people who add real value, Gauranga Das argues, aren’t the loudest ones in the room or the ones with the sharpest critique. They’re the ones who try to actually fix things, offering an alternative, volunteering to test something out, helping a colleague work through a mess. That shift, from “here’s what’s wrong” to “here’s what we could try,” changes the whole tone of a conversation.
Here’s the post:
Contribution changes how teams actually work
Teams work better when people feel like they can bring ideas to the table, not just flag problems. He isn’t saying concerns shouldn’t be raised, they should. He’s saying a concern lands differently, and does more good, when it comes with even the beginning of an answer attached, rather than being left for someone else to solve.
Criticism still has a role, it just needs a partner
None of this means criticism itself is the enemy. Catching a real risk or a genuine flaw before it becomes a costly mistake is valuable, sometimes essential. The problem Gauranga Das is describing isn’t criticism; it’s criticism with nothing else attached to it. A team needs people willing to question ideas, sure, but also willing to help build the better version.
Offering a solution means owning it too
Here’s the part that makes solutions harder to offer than complaints: once you suggest something, you’re on the hook for it. You might have to explain how it’d actually work, defend it against pushback, or help see it through. That’s exactly why criticism feels safer. But teams that push through that discomfort and take ownership anyway tend to collaborate far better than ones that don’t.Before you criticise an idea, ask yourself if you’ve actually got something to add. That doesn’t mean nodding along to every proposal or staying quiet about real concerns, it means pairing the concern with a question, a clearer explanation, or better yet, an alternative. Even a rough, half-formed solution gives a team something to work with. A pure complaint doesn’t.
What people said rack
The post clearly struck a chord. One commenter said healthy organisations run on ownership, that the real difference is staying with a problem long enough to help fix it, not just naming it. Another pointed out something most people have seen firsthand: someone can list ten problems in a meeting and contribute nothing, while the person who shows up with just one workable idea ends up being the one who actually moved things forward.
From complaining to contributing
What spiritual leader Gauranga Das is really describing is a habit so common it usually goes unnoticed, the gap between critiquing and contributing. Raising concerns still matters. But teams grow when people are willing to sit with a problem long enough to help solve it, not just name it and move on. Identifying an issue should be where the work starts, not where it ends.
