Beyond the excellent suggestions already provided, you might investigate having some tools on hand to run at a moments notice to discover what is happening on your server. Once you set up things like the Extended Events Sessions, for example, save those queries and keep them in a "troubleshooting" project inside SSMS that you can open and run. And you can also save them off in a shared folder that the team can access. You can examine using well-known troubleshooting procedures like sp_whoisactive by Adam Machanic and make them part of your troubleshooting process.