The phenomenon is known as 'the elves leaving middle earth', per a 2009 Steve Blank post:
https://steveblank.com/2009/12/21/the-elves-leave-middle-ear...
Per Steve's post, the real wake-up call is typically some beancounter deciding to charge for the free sodas in the break room. But I would agree that hiring a bozo manager is equally as much of a wake up call.
My advice for you, after I leave, you go pick up a few boxes of pastries for your employees. You've never done this, correct? Then I gave him the military salute and left not waiting for an answer.
Turned out he was the funny kind of blunt asshole. A year later I ran into someone still working there in that place where no one ever smiled. Apparently the boss got the boxes of pastries and told his employees it was my idea etc One employee told him I was right, I cant remember the last time you did anything nice because you never did, you are an asshole, you've always been, we should do this every week.
It was long long ago but I'm sure they still eat pastries every week.
The difference between one company and the next (eventho they do similar things) can be pretty strange. My mind flashes back to a few places I could only describe as a different kind of death that might be worse than conventional death. haha
But do those other engineers want to be managers? I've certainly picked up some of that work from time to time in my career, and yet if my boss told me, "congratulations, you're being promoted to manager!" I'd have to respond with, "congratulations, I quit."
You could either embrace this as the start of the hierarchy everyone is apparently so desperate to create. Or you could ignore this signal in favor of handshakes, smiles, buzzwords, or however else you intend to pick a manager from your outside funnel.
Part of this reluctance is an aversion to the busy work that often comes with a manager title. Work that managers create for themselves and other managers to legitimize their roles, but which actually impedes progress, and annoys or alienates talent.
Fundamentally, small companies that accomplish things tend to have relatively strong cultures, and external managers (by definition) are not necessarily part of that culture.
I've seen an external manager cause loads of issues because of this, even when they come in with the best of intentions.
In smaller companies, you are almost always much better off promoting internally for a number of reasons. Firstly, it demonstrates (assuming that you make the right person the manager) that there's a path for people on the team to progress. Secondly, they are already aware of the actual problems with the company, and (importantly) the kinds of solutions that are acceptable.
I currently work for a small, fast-growing company and our external manager decided to rebuild a core system at the weekends and push it to prod. Now, the system is actually pretty good (I dislike it stylistically, but i have niche tastes).
However, what this person didn't consider (because they were new) that the org was not going to give much (if any) time to move stuff over to this new system. As a result, we're about 50% of the way done 18 months in, and in the interim, we've had to not do a bunch of stuff that would actually improve our product.
Like, I remember (and HN hate this company so it's unlikely to be listened to) when FB started getting really successful (2013-15), we ended up hiring a lot of Google/Amazon managers and leaders externally and probably through negligence, they ended up destroying a bunch of what made the culture great.
Hiring bad managers is much, much worse than no managers, but if you promote an IC then they have a valid stepdown path if it doesn't work, which an external manager is less likely to have (or indeed, accept).
And thus concludes my Ted Talk about avoiding external managers.
This was a pretty good Ted Talk!
OTOH, unless you are the team lead, the amount of bike shedding from simply taking initiative and just making a tactical decision can be overwhelming. It's framed as "not building consensus first."
A PO recently chastised me after I worked with a user who wanted a date field to default to today. I was asked "who told you to do this, where is the JIRA that described this work?"
Many orgs do not view engineers as decision makers, simply as do'ers, which really I think highlights how the role of a software engineer is just misunderstood. Software engineers are more like writers than they are like carpenters. Consider for example the number of decisions made when writing a single sentence, let alone the upper management that can barely make a decision more fine-grained than the title of the book and whether it should have one or two main characters.
At this point we are almost certainly talking past one another. I've never been at a company where management didn't have the final say. In your world where managers don't decide anything important, I guess they are just HR secretaries? They have 1:1s with people and try to figure out who needs to be replaced and who should be promoted? What is that like?
> A PO recently chastised me after I worked with a user who wanted a date field to default to today. I was asked "who told you to do this, where is the JIRA that described this work?"
This is really the root of the problem. Implicit in all these titles ending in manager is decision making authority, and the selection process does not in practice produce better decision makers. A competent engineer experiencing a customer problem first hand is the smartest and best informed person in the room. They should be expected to make the best decisions about how to use their time and skills. But there is a charade that plays out involving * managers, who have been given decision making authority. They either agree ceremoniously or look stupid with little corrective consequence.
With regards to our differences, I view software management more as a leadership role rather than as a decision making role. We won't quibble that leaders need to make important decisions, we both agree there. Yet, providing direction is different from deciding direction. That is my point, software managers are deciding neither "what" nor "how", and thus their role is (IMHO) primarily more leadership rather than decision making.
By one metric, I'd suggest software managers are most responsible for helping their team maximize the ratio of time spent focused on-task to the time spent dealing on noise. While that is an interesting metric, it's still hard to tease out the effects of organization and team structure from the role of just one person who is meant to largely coordinate (AKA: direct or lead) and enhance those networking effects.
My standard joke is: We must be doing incredibly well if you have time to ask me that. Ideally the standard joke is followed by a [long] list of things they should or could be working on and then I force the conversation into that direction. If they ever bring it up again I remind them that they had already mentioned it and change the topic to actual work again. I've had a good few burst out in laughter going though the process specially the 3rd or 4th time.
Managers justifiably get a lot of flak, because management is fairly intangible, our society has decided to conflate authority and prestige with direction-setting, and there are just a huge number of incompetent managers.
But anyone that's tried a multi-person project without management understands the value of management. Someone has to step up and manage, and if it's your best engineer, you're spending a pretty valuable resource (their time) on something someone else might be able to do better.
Finding good managers is super hard, but a good manager can still be valuable, even though bad managers are frustratingly useless.
Basic rules of staffing university departments:
0. Generally don't hire your family or friends. The assumption of nepotism will be hard to shake.
1. Blind resumes and interview candidates and have a hiring committee rather than giving jobs out preferentially by a single hiring manager unilaterally, because there is a human tendency to hire people unintentionally reinforcing propinquity biases.
are you saying the ones doing the deferring should be managers, or the ones being deferred to?
This happens in every organization and you can't really fake it. The alternative to asking another person for help is becoming a low-performing lone wolf. Given the choice, people choose to reveal who they believe is competent.
Instead you should notice the natural hierarchy that forms based on everyone's desire to build things. Some of your engineers are already deferring decisions to other engineers, and you just have to pick up on that as you develop a leveling system. That's where a hierarchy should come from if you insist on it.
It sounds like this is already what's going on given that you have clumps of 3-4 engineers around leads. And the author even says "hierarchy is a property of self organizing systems". So clearly this system is self organizing and working. But the author has no skill for designing organizations, and doesn't know what to do if he can't hire managers and make it look like what he's used to.
It sounds like a bad culture fit. The CEO needs a VP who isn't stamping out the same organization job after job, and can embrace and extend what is already working at this company.