Skip Navigation
31 comments
  • Middle manager in an IT company here. My job description is saying "no" to requests outside the official pipeline, in order to shield my team from outside interference and burnout. I need a manager to fight for me whenever I pick a fight with one of the VPs who think we need to drop everything and refocus on their pet project.

  • When you have too many people working somewhere, it becomes impossible for one person to oversee everything. So you get multiple managers managing more specific groups, and then managers who manage the entire segment without knowing all the details or people. When a company gets even larger you'll need even more layers. There's only so much time and mental capacity that humans have, so at some point you need some multi-threading by involving multiple people.

    To me it kinda makes sense, and I don't really know how I'd do it differently if given the chance, but the higher level management does always seem to feel like some people making decisions high up in their ivory tower without knowing what is actually going on.

  • For a real answer:

    A manager can control what is done under them, but if one of their teams/members needs something done by another team they have no control.

    Their manager might control the manager of the other team though, so the decision goes up the line until it hits someone who has both sides of a problem under them and can make the decisions on priorities/cost etc of the requested action.

    In small companies, this may just be one or two layers, but in bigger companies it becomes a disfunctional disaster.

  • I love me a good manager. Luckily I was able to work with a few in my lifetime. The good ones have no problems managing your and their own work.

  • Myself and some other managers I know became managers for being competent at our science-based jobs when the company wanted to expand. Our education and career up until this point mostly had not involved learning skills like delegation, teaching, scheduling, and team-budgeting, not to mention the interactive social skills needed to successfully manage individuals.

    Some bad managers are just good workers that weren't able to suddenly learn these skills when their employer insisted they manage a team so it could pursue its endless quest for infinite growth by setting up hierarchies of workers. Good managers are either trained in management or extraordinarily talented.

  • Organizational structure can be seen as just style points. Gabe Newell of Valve famously does not do organizational structure. He didn't when he worked at Microsoft and he doesn't now. It's also been said per capita/employee no other tech company makes as much money as Valve.

    I hope he writes a book about it or something. As an executive at a large organization I'd love to know more and try to run my division like he does. But I don't want to just make it up as I go along....

    • What the heck does "does not do organizational structure" even mean? Valve must have some kind of structure.

      • I'm not sure they do have anything that looks like typical corporate America, but I don't know a lot more. I know at Microsoft everybody reported to him and from what I've been able to piece either that's not changed we Valve. But he obviously doesn't "manage" everybody, so how he does it I'm not sure.

        Most organizations are just a dictatorship by another name if we use the definition in The Dictators Handbook which states keep your essentials and influentials small in quantity so you can pay them for results. A democratic environment those groups are many so you can only win them over with policy and influence. I feel like he runs his organization like the second but I want to know more. A lot more.

31 comments