Complaints and proposals

There's a version of you that turns up to a meeting, describes what's broken accurately and at length, and leaves feeling like something happened.

Nothing happened. You moved a problem out of your head and into somebody else's, along with all the work of figuring out what to do about it, and that person already has a queue.

What separates a complaint from a proposal is who's holding the next step when the conversation ends. Attitude has nothing to do with it. Neither does positivity, which is mostly a way of asking people to be quiet in a nicer font.

The five lines that get acted on

Five of them. Works upward, sideways, and in writing.

What's broken, stated once, with a number or an example instead of an adjective. Deploys take forty minutes and we do six a day. Not "our tooling is painful."

What it's costing, in something the other person already cares about. Hours, money, a date, a customer, the odds that someone good quits.

What you'd do about it, with two options if you genuinely have two, one if you don't, and say which one you'd pick.

What you're doing by default. This is the line that changes everything and it's the one people leave out. "Unless you tell me otherwise, I'm starting on X on Thursday." Now silence works for you rather than against you, and the person you're asking gets to spend ten seconds instead of twenty minutes, which is the actual reason things get approved.

What you need from them, specifically. A decision, a person, ten minutes with someone, a budget line. If the answer is nothing, say nothing, and the ask stays credible for the day you need one.

Four minutes of writing, most of it. The reason people skip it is that the complaint is emotionally finished and the proposal isn't, and finishing it is the part that requires thinking about a problem you'd rather just be annoyed about.

"Bring me solutions, not problems" is a trap

I want to be careful here, because this idea has a bad version that does real damage.

Tell a team to only bring you problems they've already solved and you won't get fewer problems. You'll get fewer reports. The things people can't solve on their own are precisely the structural, expensive, above-their-pay-grade ones, which is to say the things you most need to hear about, and you've just priced them out of the conversation. Then you find out in an exit interview.

So the standard I'd actually hold is thinking, not solutions.

"I don't know how to fix this, here's what I've ruled out and here's what I'd need to find out" is a complete proposal. There's a next step in it. It shows the person spent something of their own before spending yours.

And one category should always arrive raw and immediately, with no thinking attached at all. Someone's about to get hurt, we're about to break the law, a customer is about to walk, a person on the team is in trouble. Say it the moment you know. Nobody should be polishing a document while that's true, and every person who works for you should be able to tell which category is which without having to guess.

Venting has a place, just not that one

None of this means being an unfeeling machine about work that's genuinely infuriating.

Frustration is useful. It's often the earliest signal that something is actually wrong, well before you can articulate what. What matters is where you put it, and the answer is one or two people you trust outside your reporting line, sometimes outside the company entirely. Get it out of your system there and let the residue turn into the thing you'll raise properly on Monday.

Downward is where it does damage.

Complaining about the exec team to your own team feels like honesty and reads like alignment, and it's neither. It teaches people that the way to handle a decision you dislike is to narrate your dislike of it, and it strands them completely, because they can't act on any of it. You have access to the person who made the decision. They don't. What you've actually done is transfer your discomfort to people with fewer options than you, which is worth being honest with yourself about.

Sideways into a peer group that's curdled is the other one. Some leadership teams have a real conversation in the side channel and a piece of theatre in the meeting, and once that's the pattern it's very hard to reverse. The people inside it usually think of themselves as the realists.

The decision you lost

Sometimes you'll do all of this properly and the answer is still no.

Say you disagree, once, clearly, on the record if it matters enough. Then commit, and commit visibly, because a leader who executes at half speed while making sure everyone knows they were against it does more damage than the original decision ever would.

Re-litigating it monthly is the complaint in its most expensive form. It costs the meeting, it costs your standing, and it quietly discounts the next objection you raise, which might be the one that mattered.

Set a review point instead. "Let's look at this again in a quarter, and here's the number that would tell us it isn't working." That's the honest version of not letting something go, and it's the only one that survives contact with people who are busy.

What changes when the room learns this

Problems start arriving earlier and smaller. That's the tell.

People bring you things while they're still cheap, because bringing something is no longer an admission of failure. The proposals themselves get better over a few months, since writing them is a skill and the first ones are always bad. Meetings get shorter, because the thinking happened before the room instead of in it.

Model it upward and it spreads faster than any amount of asking people to do it. Your team watches how you raise things with your own boss far more closely than they listen to what you tell them.