I'm going through a bit of a phase at the moment, so I'm biased. It's "show me the incentive and I will show you the outcome".
I used to find that an interesting idea, not sure if true or not. Nowadays a few years later, I'm almost hyper focusing on it, because I'm noticing that it is mostly true. Like, there's some room for individuality but when things _matter_ (e.g. livelihood, etc.), then the incentive seems paramount for most people.
My friend who is still there says this is his last ever programming job, after that manager he wants nothing to do with this industry, and that is a shame.
enterprises just love layers and layers of management. can't get enough of it. No CEO has ever seen a management layer he didn't like.
This is super common and a very bad sign. As an employee, you are disposable in this type of culture, though it should go without saying.
> enterprises just love layers and layers of management. can't get enough of it. No CEO has ever seen a management layer he didn't like.
Bc more warm bodies in your org looks better on the resume. Managing 200 people on paper is more impressive than managing 20.
I think the management skill nobody talks about is how managers should realize they are part of a team and their focus should be on whatever the team's goal is, not in finding the perfect way to apologize. As the article says: "Your job is to ship working software that adds real value to users, to help your team grow, and to create an environment where people can do their best work."
I couldn't give a rat's ass if a manager doesn't apologize to me in a way that makes my eyes water, admitting his humanity in the process, if that manager doesn't insist on making the same mistake and getting in my way all the time.
Good for you if you consider yourself so emotionally detached from work that you can let go of the fact that work relationships are still human relationships. However, you sit comfortably in the minority. Most people carry the human aspect of their work relationships into work. Ignoring that is step 1 of being a really bad manager.
This doesn't mean we don't set appropriate boundaries or avoid giving feedback. It does mean that a great manager navigates the nuances of work relationships and work itself. It also means a great manager will adjust their approach depending on the personal needs of each employee. For instance, if I was your manager and truly believed what you're saying here*, I'd just give you the brass tax feedback and keep everything about the work itself.
* And I don't. From my experience most people who take this stance have been conditioned that emotions are bad. We are big emotional bags of meat. The people I've managed with this mindset tend to be the hardest to manage. Eventually something hits their feels, they can't handle it, and the erratic behavior begins. I much prefer people who are forward with their emotions. When something happens they can vocalize it appropriately allowing me to address it. When they have feelings about feedback received, making a mistake, or doing something bad I can easily acknowledge and validate those feelings while maintain the feedback & boundaries.
But this is part of the point, while for you that might not matter, your manager cannot assume this. Other people DO care.
One of the ways your manager can mess us is by assuming you don't care about that...
We are all humans, not robots. Heck, even the LLMs mess up.
You can say that again. In another window, I am iterating with one for fixing my site CSS.
In any situation, I've always believed it is better to let people we're all human and it's ok to take risks and make mistakes.
It's not about management skills.
It's also impolite to use "nobody" in it.
To me, that means 1. To identify the issue that occurred (especially when you caused it), and much more importantly, 2. Put systems into place that prevent it from happening again.
Employees can feel very clearly when a manager lacks accountability and as part of mid and especially high level management (if your goal is actually improving both output and quality of people's lives) to not just say you did something wrong, but actually put your skin in the game ensuring what happened will not happen again (usually it means being better at saying no or aggressively managing prioritization rather than heaping additional tasks on people).
The neurology often results in good systems thinking.
The diversity results in lifelong disciplined improvement of social interactions.
Here's the doc for responding to mistakes: https://docs.google.com/document/d/1AqBGwJ2gMQCrx5hK8q-u7wP0...
And here's a video with Matt talking about it in a little more detail: https://www.loom.com/share/651f369c763f4377a146657e1362c780
It's a very similar approach to the linked article although it goes slightly further in advocating "rewind and redo" where possible.
EDIT - The full "curriculum" is here: https://docs.google.com/document/d/18FiJbYn53fTtPmphfdCKT2TM...
The senior ICs are the squad leaders on the frontline with the rest of the team, knee deep in the same shit they are. It’s really THOSE people doing the constant day-to-day trust building, team leveling, shit getting done-ing, repairing…
And so yeah, a good manager lets those seniors just go be good at that, not bogging them down with work that is a complete waste of their potential. It’s a bit of a symbiotic relationship really, because a manager with no such seniors on the team won’t have the firepower to crush goals, and a senior without a good manager will never be allowed to excel.
Getting on with people long term is often about making them feeling acknowledged and being clear about what makes them valued.
The real trick to 'repair' is not to make hollow promises. Managers can be perceived as failing when an external event happens and they haven't planned for it, or they bet against it happening. This can kick off a whole chain of events, including pushing team members into crunch time or 'impossible positions'. Its rare that you can stop the external event or a similar one from happening, so promising it won't is hollow.
The next hollow promise commonly made is 'when it happens I won't let X happen [to you]'. The problem here is often that you probably will. In two ways: either X happening is clear in hindsight but not with foresight, so you'll probably make similar decisions again; or, the team member ending up in an unhappy situation is the best of a bad bunch of options.
I've had to place people in positions where they had insufficient support and excessive demands. Sometimes I knew this going in, and sometimes I did not.
You also have to be careful about passing the buck - if you're the manager you need to be clear with yourself about what your job is and whose issue any given problem actually is. Do you help your team interact with third parties, or do third parties interact with your team through you? How much are you supposed to represent your teams needs to management (e.g. pushback) vs how much are you supposed to represent your management's desires to the team (e.g. pushdown).
If you are caught passing the buck to shirk responsibility by your reports or by management you will lose a lot of trust and respect very quickly. You can always pushback or pushdown harder to appear 'good' to one party, but at some extreme that is going to lose you your job. Its your choice how to play this - so own the choice.
I always made that clear to my employees, but after that, my employees' interests generally came second (over my own).
It seemed to work. I was a manager at the same company for over 25 years, and my bosses were really tough (but fair).
He was also close to retirement and didn't care about moving up the ladder. Many bad managers do and will sacrifice you and the rest of the team to make themselves look better.
Acknowledging what happened, taking responsibility, and reconnecting.
...is a reflex, not a tactic.
Love this book! Just read it. Must read for parents, IMO.
We all know those friends that you can’t criticize because they’ll take it poorly.
Love Your Errors
It's not a failure, it's an opportunity for improvement
No shame, no blame
Second, when things go poorly, accept responsibility. When things go well, give credit to the team.
ChrisMarshallNY•2h ago
I think that helped make me a decent manager. At least, my employees seemed to think so.
But I could be wrong.
BubbleRings•1h ago
I especially like OP’s point #1. “I know I did x, sorry about that” is so much more powerful than “Sorry you let yourself get upset that I did x”.
ChrisMarshallNY•1h ago
Another important aspect is the context. A lot of people are good at public excoriation, and private apology.
If I show my ass in front of a bunch of people, the apology is not an apology, unless it's made in front of the same people.