Resilience Coffee/2025/10/17

• transition from managed service to self-hosted, uptime/mttr
  • SaaS -> managed -> self-hosted
  • Unique per customer
  • "Each deploy was an incident"
  • "Professional services" -> enterprise billing model, executive sales model, additional staff per customer
  • Patching, Helm charts? appliance approach?
• Design/systems thinking
  • User research
  • Human factors
  • Huge overlap with RE
  • Erika Hall's "Just Enough Research"
  • Sheryl Cababa's "Closing the Loop - Systems thinking for Designers"
  • Design less as artifacts and more as process for discovery as a group
  • Design process and incident response
  • Universal design
  • https://design.ncsu.edu/wp-content/uploads/2022/11/principles-of-universal-design.pdf
  • Design as tradeoff
  • Architecture connections
  • "How Buildings Learn" https://en.wikipedia.org/wiki/How_Buildings_Learn
  • Problem-framing
  • Double Diamond: https://en.wikipedia.org/wiki/Double_Diamond_(design_process_model)
  • confirmation bias and research for leaders
• how to support oneself doing resilience engineering
  • If you have to teach your market, you don't have a good market.
  • The market doesn't know they need it, at least in software
  • Everything has software in it, and everything software has something else in it
  • Some industries want it more
  • what industries inherently value resilience more than others?
    • top industries are: finance, cyber, gaming, health, e-commerce, aviation - but for different reasons
• when to coast