Comment by brandall10

Comment by brandall10 10 days ago

3 replies

With all due respect, outside of staff+ levels, if your reports are off in the weeds being productive building the wrong things, isn't that more of a management problem? Even very persuasive reports should require sign-off on how they spend large chunks of time. It's a hallmark of good management to push back and regularly ensure goals are aligned. Empowering employees is important, but that should be for the 'how', not the 'what'.

Your visibility is above theirs. You are regularly in meetings they are not. There is a distinct information asymmetry. It's your responsibility to convey what is important. Same with your manager to you, your skip to them, and all the way up the chain. No matter what the company's overarching goals are, at the IC level they may only have enough visibility to understand how valuable the business segment/team they're on is and read between the lines and move to another team.

Yes, really good employees can learn and bubble things up from cross-functional work or skip meetings to cover their supervisor's blindspots, but that's not a good look and could be potentially harmful, ie. could damage relationships if not handled carefully.

Being resource constrained is not an excuse. Hire or slow down. Business can't support it? Well, it's not a great business. Inmates running the asylum and all that jazz. Scapegoating reports for operational failings is toxic.

landedgentry 10 days ago

Agreed.

> I have given poor reviews to people who invested lots of time and energy in projects and probably even did good work on them, because they were _completely_ off strategy and completed before anyone who knew better could tell them they were a waste of time and energy.

Alignment is really hard to do when management claims they're there to "support" engineers and their decisions, and not dictate from above. I see this as a great CYA move, couched in empowering language.

It is even harder when they visibly reward shiny new features while trumpeting a pivot to reliable infrastructure, only to change their mind and behavior on a whim. Mixed signals.

timssopomo 9 days ago

I totally agree with everything you said about information asymmetry and responsibility to provide context. Maybe I didn't explain clearly: it's not an operational failing if someone just decides to "take initiative" to solve an irrelevant problem without telling their boss. It's not the managers job to monitor everything their employees do. It is their job to state goals, assign work, and monitor progress.

  • brandall10 9 days ago

    One off things here or in the name of taking initiative... drawing down tech debt, POC's to prove a point, internal tools to help grease team productivity, sure. Stuff that a dev might do on their own time that they ensure doesn't get in the way of their assigned work.

    But large chunks of work that form the corpus of a performance review? No. I've been doing this 26 years now and the only time I've seen that kind of maverick behavior on a team is when a manager is overwhelmed/distant/checked out or simply afraid of a particular employee because they're a chaos agent with a bit too much power, and IME, pretty dang rare.