On the flip side, it’s somehow easier to get people to attend scheduled meetings.

  • jjjalljs@ttrpg.network
    37·
    3 days ago

    Running games has definitely helped me run meetings.

    • Establish turn order.
    • let people finish their thought instead of immediately following some dumbass tangent
    • take notes
    • phase@lemmy.8th.world
      23·
      3 days ago

      In my domain (IT, with On-Call), there’s a practice called “Wheel of Misfortunes” or “Game hour”. This is in fact a short TTRPG session to simulate incident. This works very well. I am a paid DM 1h per week for my colleagues :)

      • kvadd@lemmy.world
        6·
        3 days ago

        I would love to hear more about this if you can go in to more details?

      • ilinamorato@lemmy.world
        4·
        3 days ago

        Oh neat, our team does this but we call it “WTF Wednesday.” Usually the most senior engineer digs back into our incident log and tries to reproduce it in our dev environment, and we live-solve with him playing the role of the customer.

        • phase@lemmy.8th.worldEnglish
          2·
          3 days ago

          It is the same thing. In our case it’s not attached to the seniority. The person ending their shifts replays its incident when there has been one, with the person who is taking the pager after them. We are deeper in the infrastructure so we don’t have customers but we roleplay stakeholders (lead/head, principals, developer). My favorite is the person who has experienced something wrong but it is only this person and bad luck :P

          • ilinamorato@lemmy.world
            3·
            3 days ago

            Yeah, I think the goal is to eventually make it irrespective of seniority, but right now he’s the only one with 15+ years of institutional knowledge on the application, so he’s trying to pass on as much as he can to reduce our bus factor.