Earlier quoted context omitted.
This seems impossible to fix in a divisional org structure, where each division owns their P&L. If I'm in division A, and division B wants something from us that won't make a difference on my P&L (or will just add costs [headcount]), why would I be incentivized to help? If they pay for it though, that's a fee for service. Seems fine. It's all internal accounting anyway, so it's mostly fake.
It can work if the unit of currency is sufficiently divisible. Headcount often isn't. (Also, headcount is more a rate of spending than a unit of currency. I want to buy some work from your team, not subscribe to it!)
Bayer is getting rid of bosses and asking staff to ‘self-organize’
491–497 of 497 posts
Re: Bayer is getting rid of bosses and asking staff to ‘self-organize’
#492Earlier quoted context omitted.
I'm been really frustrated by OKRs specifically. The whole system does a great job of appearing to empower a bottom up approach while actually being implemented as a top down, authoritarian system. It sounds great to be metric and goal driven, allowing employees to decide for themselves how to best reach those business goals. I've never seem it implemented this way though. Instead, I've seen leaders define goals and…
We're explicitly given top-down OKRs, which we're required to align our own "bottom-up" OKRs to, and then we're not empowered to meet our own OKRs, because product management alone steers the ship.
Re: Bayer is getting rid of bosses and asking staff to ‘self-organize’
#493Earlier quoted context omitted.
Maybe there is a cultural difference here. I see repeated 1:1 sessions as micromanagement, like being treated as a kid that needs their hand held. I don't want to discuss work items on 1:1 with the manager, I want to discuss them in a group setting because it is the group as a whole that solves the tasks. I also want the input from other members in the group instead of only the managers view. In my country we do pers…
No, there isn't a cultural difference. 1. If you want to discuss work items in a group setting with 22 people, it's an inefficient use of time. 2. If a manager has 22 direct reports, it becomes nearly impossible for them to do anything but manage, which make the whole team less efficient. 3. A manager ought to be expected to, and have time to, mentor their employees. This is impractical with such large teams, and the…
Managers do not need to mentor. Actually an independent mentor is better as there would be no conflict of interest. A person can get a mentor from another team as long as both are willing. If there are more mentees seeking mentorship than mentors, you can rotate the mentors or double/triple assign them especially to those who seek to switch to management track. In reality though, there are more mentors than mentees it seems. At least that's my anecdotal observation.
20 people management is very well possible. You don't need to have 1:1 with directs every single week. If you do it bi-weekly (every two weeks), the meeting cost to the manager would be 2 sessions a day. Managers tend to join every single meeting under the sun. That's how they fill up their time and appear(!) to be busy. In reality, they can cut down the meetings down to %25 and nothing would change.
Let's look at lowest level managers. They can meet 20 directs bi-weekly for 0.5hr. Let's add 0.5hr follow up work after each 1:1, which is way generous. So that totals up to 20 x (0.5 + 0.5) / 2 = 10hr. Let's assume their own 1:1 with their own manager to take 1hr bi-weekly or 0.5hr weekly as they need to discuss both team and personal issues. They can meet with peers and their manager weekly for 2hr. They can meet with sub-teams (let's assume max 4 teams) weekly (4 x 1hr) for status and problems. And at the end of the scrum (bi-weekly), they can meet all the directs for demos and postmortem for 2hr. If there are some other technical meetings they do not need to attend unless they are absolutely needed but this shouldn't be often. Leads are perfectly capable of handling those and report back if they're hesitant, which, again, shouldn't happen often. Meeting tally up should be around 18hr. For a 40hr week that's less than half. Let's assume they're dragged into some technical meetings for 5 more hours that's still 23hr. Remaining time should be more than enough to sifting through emails, quarterly duties (e.g promos, end of quarter status, next quarter strategy/goal setting) and occasional emergencies.
For mid-level managers (generally directors), they don't have to meet with teams but we assumed their 1:1 would cost 0.5hr/week. Their follow-up should be much less though as they should be able to make decision on most of the issues on the spot. But let's add a quite generous %50 on top which would sum up to 0.5hr x 20 x 1.5 = 15hr. I think they should meet with tech leads (skip-level) too if they're one removed from the lowest level. They can meet them for 0.5hr every 8 weeks which should take at the very maximum, 20 x 4 (leads) / 8 * 0.5hr = 5hr/wk but it'll probably take less. Tally up is 24hr (if you add peer & direct meetings). Mid-level managers may get more randomized but they need to be efficient at what to get involved and what not to. Majority of the middle-managers make the mistake here. They get involved more than they can chew as they're micromanagers and/or they respond to every single demand from their own manager, practically doing the manager's job for them. This is because their promo is generally tied to their manager's attitude toward them but this should be changed. How you can change this is a separate topic I can get into, if needed but let's skip it for now.
For high level managers (generally VPs), their time would be spent less on skip-1:1s & technical meetings but more on strategy and status meetings. I believe they would have even more time at their hand than directors if they're vigilant on the time sunk on the emails.
Then you have CEO at the top or you can have SVPs if number of your ICs is above 16K. But, yes 20 people management is possible if managers are cognizant of their time and boundaries of their responsibilities and if they actually work instead of appear to be working.
But let's face it, it ain't happening because managers are A) either people who doesn't want to work anymore but need the money so they'll just carry on until they f-up big time and then switch companies and rinse & repeat, B) or, they overstep their boundaries, C) or, they don't know how to do prioritization and time management, D) or a combination of some/all above.
Re: Bayer is getting rid of bosses and asking staff to ‘self-organize’
#494Earlier quoted context omitted.
Yes, this is my mantra. Senior Only-Developers are attracted to complex problems and try to make things using as many language from the "advanced" book as possible. That's why I like all-round developers better, they have a bit less to prove by making "smart and complicated" code.
the benefit of complicated is that it filters out the people who suck so they can't fuck up the code
Re: Bayer is getting rid of bosses and asking staff to ‘self-organize’
#495Earlier quoted context omitted.
You can just have a queue. I’ve seen departments that basically function as an internal vendor of services to other departments. First in first out. Fixed schedule to expect turn around on most requests. No one complains. Seems quite pragmatic and fair.
FIFO is not an efficient way to prioritise work, though. Unless all work has about the same value and urgency, in which case, I guess, that sounds nice.
Re: Bayer is getting rid of bosses and asking staff to ‘self-organize’
#496Earlier quoted context omitted.
Don't play the hero. Unless you want to get rewarded with even more work. Do the job you are assigned to or ask for a raise.
Sure, I'm aware of it, but having your team abjectly fail isn't good for your continued job prospects either. You shouldn't be the hero, but you also don't want to have your team get fired for want of you spending 2 hours of work a week keeping it on track.
I am not saying this from the perspective of someone who is slacking off at their job but from the perspective of someone who did too many heroics and only nearly avoided burn out. If your team gets fired because of one persons work/efforts or the lack thereof then something is seriously wrong AND there is a risky bus factor of 1. Please take my advice, the grass is always greener on the other side.
Re: Bayer is getting rid of bosses and asking staff to ‘self-organize’
#497Earlier quoted context omitted.
That also just doesn’t make sense to do because most employees don’t understand the business and are terrible at defining OKRs.
They probably aren't good employees then, honestly. My scenario here is entirely dependent on leaders trusting their reports, if that isn't possible then at best they can try to force objectives down from the top. I'd argue that still won't work, and in my experience it hasn't. Id your employees don't understand the business or aren't good at defining goals, you've failed them as a leader. Maybe they shouldn't have b…
This is incredibly naive. Even in single product companies you can have excellent employees (e.g. a CNC machinist) who don’t know anything about the pricing, regulatory, and legal aspects of the company.