‹ BackHN Continuity

Thread

Doing Everyone Else's Job

215 points · 115 comments · luu

  1. ChrisMarshallNY · · focus · HN ↗
    I worked for a Japanese corporation, and a big part of their HR policy, was to move staff around the company. It was usually in 1- or 2-year stints (people would spend their entire careers at the company, so they could do this). Eventually, they would end up doing longer stints, where they would specialize.

    They would couple this with things like standardized coding and documentation styles, common tools, etc. Training on these standards was a regular thing for all staff.

    The idea was that they could rapidly move experienced staff around. It also helped staff to understand how their work was applied in an integrated system (having “blinders” on, is a fairly typical issue, with dedicated employees).

    It generally worked, but relied on their particular culture, and introduced a fairly significant amount of overhead and rigidity to the system. It would also mean that it takes a long time to cultivate experts.

    Personally, I’ve always enjoyed learning new stuff (still do). I actually enjoy taking on projects that I don’t know how to do. I wrote about it here: <a href="https:&#x2F;&#x2F;littlegreenviper.com&#x2F;miscellany&#x2F;thats-not-what-ships-are-built-for&#x2F;" rel="nofollow">https:&#x2F;&#x2F;littlegreenviper.com&#x2F;miscellany&#x2F;thats-not-what-ships...

    1. Eddy_Viscosity2 · · focus · HN ↗
      Military members also move on around the organization spending times in different parts for the same reasons. This is a strategy you apply when you want organizational resilience, but it comes at the cost of efficiency. You can&#x27;t have both at the same time.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.