I really like the constructive spirit of the “propose” step. If you have a proposal, it is a defiantly worth bringing it up. However, there is an anti-pattern in management that’s says “don’t bring me problems(=complaints), bring me solutions(=proposals)”.
Why is that an anti-pattern? It is because of the position in the hierarchy people may experience the effects of the problem, but the solution may need to be way broader/systematic. Their proposals will most likely make little sense because they see any part of the picture and they would not want to bring them, so the problem will remain unseen and unresolved.
What to do instead? Invite people to share problems, even if they don’t have good solutions. And look for a systemic root cause for a lot of problems at once.
Agreed. A lack of a solution shouldn't stop someone from bringing forward a problem in a healthy work environment. But so few are even close to accepting feedback that would take their time.
Proposing a solution is usually doable for a technical problem, but so few problems are purely technical. And sometimes the only way to have your proposal taken seriously is to make sure no one could ever tie that effort back to you by the time it is adopted.
I think it is good to make a proposal if you can find one, but we don't want people to keep problems to themselves, because they have no proposal or solution for the complaint.
Love this. In my past career as IC, then manager, then founder of my own company my rule was, "bring solutions not problems."
This got hammered into me as a green engineer on a launch site where I asked my boss if I should do X or Y. He looked at me and said, "If you were the only engineer here what would you choose?" I said 'X' and explained why. He said, "great go do it" and I understood.
I've always thought that when complaining, the person should be assumed to be volunteering to [help] solve the problem.
I don't know about others, but for me, keeping that in mind helps me avoid pointless excessive complaining. When I do complain, yes, I do want to [help] solve the problem. Always. (Well, nearly always; I'm not perfect.)
Unfortunately, not all proposals are going to be accepted. As an example, I worked on the project which had serious blind spots from product perspective. I proposed to stop that silly thing and work on something important.
I wasn’t able to communicate it clearly enough, because the project was going on for many more months and has been closed for those reasons months later.
So, my lesson is people still might not like the proposal :)
My boss once told me HIS dad told once told him, "You can complain once. After that, do something about it or shut up." 😄 I've always followed that advice! I like this one though, as an addendum to that.
But complain even if you don't have a proposal when it's an issue of discrimination, harassment, hostile working environment, burnout...
I feel this. (Bad) Leaders hate this and will retaliate. But I agree, it must be done.
I really like the constructive spirit of the “propose” step. If you have a proposal, it is a defiantly worth bringing it up. However, there is an anti-pattern in management that’s says “don’t bring me problems(=complaints), bring me solutions(=proposals)”.
Why is that an anti-pattern? It is because of the position in the hierarchy people may experience the effects of the problem, but the solution may need to be way broader/systematic. Their proposals will most likely make little sense because they see any part of the picture and they would not want to bring them, so the problem will remain unseen and unresolved.
What to do instead? Invite people to share problems, even if they don’t have good solutions. And look for a systemic root cause for a lot of problems at once.
Agreed. A lack of a solution shouldn't stop someone from bringing forward a problem in a healthy work environment. But so few are even close to accepting feedback that would take their time.
Proposing a solution is usually doable for a technical problem, but so few problems are purely technical. And sometimes the only way to have your proposal taken seriously is to make sure no one could ever tie that effort back to you by the time it is adopted.
I would refine the message now to “attach a proposal if you have one”.
I was just about to write the same :)
I think it is good to make a proposal if you can find one, but we don't want people to keep problems to themselves, because they have no proposal or solution for the complaint.
I like this approach Kent! Thanks for sharing those insights. IMO, coming up with alternate solutions for different perspectives is a solid step.
Love this. In my past career as IC, then manager, then founder of my own company my rule was, "bring solutions not problems."
This got hammered into me as a green engineer on a launch site where I asked my boss if I should do X or Y. He looked at me and said, "If you were the only engineer here what would you choose?" I said 'X' and explained why. He said, "great go do it" and I understood.
I think Erik Dietrich (Daedtech) said this in Developer Hegemony, be a problem solver not a problem bringer. 😎
I've always thought that when complaining, the person should be assumed to be volunteering to [help] solve the problem.
I don't know about others, but for me, keeping that in mind helps me avoid pointless excessive complaining. When I do complain, yes, I do want to [help] solve the problem. Always. (Well, nearly always; I'm not perfect.)
Unfortunately, not all proposals are going to be accepted. As an example, I worked on the project which had serious blind spots from product perspective. I proposed to stop that silly thing and work on something important.
I wasn’t able to communicate it clearly enough, because the project was going on for many more months and has been closed for those reasons months later.
So, my lesson is people still might not like the proposal :)
One of my favorites so far. Definitely going to use the ‘complain and propose’ combo - feels even stronger than the overused ‘disagree and commit’ :)
I love these things that you dredge up from the archives. This one, in particular, has aged well.
hear hear.
I am pondering, what would be a good approach if you don't see a solution or a way forward.
An option could be proposing a way of finding out the solution, whether that is business analysis, technical insight, or something else.
My boss once told me HIS dad told once told him, "You can complain once. After that, do something about it or shut up." 😄 I've always followed that advice! I like this one though, as an addendum to that.
Absolutely nailed it. Engineers always come up with solutions. if just telling about problem then it is journalism reporting.