sjparkinson / uncomplicated.systems Goto Github PK

one thing that I think has always confused me about "D&D gamedays" is how you handle the branching factor (participants may ask for data/suggest approaches you haven't prepared). Is the solution to keep it "on rails" (I think the article suggests linearizing)?

https://twitter.com/jhscott/status/1174188491820941312

@snakescott, I don't have Twitter and couldn't see an email so figured I'd answer you here (convoluted I know!).

From my experience people do go on different branches, and we've let them. But in feeding the incident information one page at a time, the moderator as you suggest can keep the incident on one track, while still exploring potential other routes it could have gone down.

Mainly this is to minimise the effort involved in creating and running the workshops.

There's heavy emphasis on the leading questions in our workshops on what actions would the teams take. At the moment we are interested in spreading the foundational knowledge on how to lessen the impact of incidents for our users, and the very brute force actions we can take to improve the situation (e.g. failing over), rather than digging deep into our systems and potential root causes and all the tools we have available for debugging (kinda how we used to handle incidents, ish).