• ☆ Yσɠƚԋσʂ ☆@lemmy.ml
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    6 months ago

    Another aspect of the problem is that people making the decision of what programs to use don’t actually have to use them.

    • ___@l.djw.li
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 months ago

      As long as the reports that the C-suite gets look pretty, that’s all that matters. Have seen that one from both sides.

      “I need five developer hours to implement a UI for this manual process that is time sensitive and exposes us to significant risk if we screw it up. Oh, and I’m the only one who knows how to do it in prod, so we have a bus problem.”

      “Nah, I want reports…. Wait, why did we write an HO4 policy in Corpus Christie, AFTER the hurricane warning was issued?”

      “See above, and prioritise things that matter.”

    • adhocfungus@midwest.social
      link
      fedilink
      arrow-up
      2
      ·
      6 months ago

      This is what I’ve seen too. Directors come back from a conference and suddenly we’re learning a newer but objectively worse system. Obviously the grunts using the systems aren’t consulted, but are expected to be team players through this educational experience.