shannyshan Atlassian Team

Welcome to the community, @Sam Stable (daltonprock)! Thanks so much for the feedback - we're excited to hear that you like the new design :)

Hooray! We can't wait to see ya in person at Summit. Definitely come find us at the Statuspage booth 😊

Remember this?: BONUS: We'll be drawing one tip or story from this discussion at random on Friday, August 24th. The winner will receive a special HugOps gift package 🎁🎉 Well, we drew a winner on Friday and are excited to ship off a special gift to our winner. Drumroll please.... @Nick Coates - congrats! We will e-mail you…

Thanks for everything @Matt Doar and @Celina Zamora!!

Thanks so much for the follow-up, @Anton Perera!! Love hearing about learnings that come out of real incidents. This is a really great point you make. Incidents are messy and complex and you need to treat them as new puzzles to solve every time. You can have great processes and roles and tools in place, but you still need…

Thanks @Mirek!! Totally agree that great incident management starts with being able to quickly detect and resolve incidents before they affect our customers. "Detect: Atlassian knows before our customers do" is actually the first in our set of our Atlassian Incident Values. Good incident management should have a centralize…

Thank you for sharing @Anton Perera!! I love how you show the link between communication and trust. Downtime is inevitable, but being communicative and transparent is a HUGE differentiator in the SaaS world. Companies that get this right are way less likely to lose customers after a big downtime events. Always inform the…

💯💯💯@Manon Soubies-Camy - Thank you! Rally strong tips and tricks. We love the idea of putting the power in the hands of the customer. The last thing someone wants during a stressful incident is to have a clunky and complicated experience trying to get help. Also great how you point out the importance of communicating both…

Love these @Brittany Steed! Thanks for sharing! Plus, they can be remembered with an easy acronym... always E.A.T during incident response. 😉 "Keep adapting" is a really great one to call out. We always recommend holding a retrospective or incident comms review after an incident. Also great to see you're helping customers…

Excellent tips, @Kat Warner! Focus should definitely be on communication and returning to an fully operational state. Then, after recovery, you hold a postmortem or post-incident review to find the root cause and take steps to ensure the same issues doesn't happen twice. 💪 E-mail me (swinter@atlassian.com) for your HugOps…

@Nick Coates you are spot on with this!! Thanks for sharing. The best comms in the world are useless if your customers don't know what communication channels you're using (and where to find them). Love all of the ideas you've laid out for promoting them. If you're up for it, we'd love for you to expand on this in a guest…

These are awesome tips @Alana Fernando!! Thanks so much for sharing. proper communication gave us strength to pass that extra mile in proper incident management throughout these years. ^^^ THIS! So true. Communication really is 🔑 P.S. Email me (swinter@atlassian.com) so I can send you a link for a poster!

That's awesome! So happy to hear. Yes! Would love to see it up there 😄Have a great rest of your week, @Nick Coates! Cheers, Shannon

This is awesome @Eaniel Deads! I work on Statuspage so we are always super interested to see how teams are handling incident response. Thanks so much for sharing.