We use Google Calendar, and it is generally the best solution in my experience. But not just a daily event; an actual time, with a meeting invite that anyone re

We use Google Calendar, and it is generally the best solution in my experience. But not just a daily event; an actual time, with a meeting invite that anyone relevant joins, to run each task together. It helps knowledge transfer and helps guarantee that it happens. Documentation, like with most meetings, is thrown into Notion or whatever; just quick and dirty. Example: test our database backup restore process. Everyone hops on; leader logs into the cloud provider; confirms that the backup strategy is what we expect (which is documented in the description of the meeting invite); confirms that database backups exist in line with that policy; confirms they're of a reasonably expected size; we click one for staging -> restore to a new deployment -> wait for the cloud provider to set everything up, use that 5 minutes to talk with one another about stuff -> set up the database username/password; log in to AWS Secrets Manager -> update credentials -> roll the deployment to pull in the new credentials; confirm everything looks good; and tear the old (again: staging) deployment down. A second person on the call is tasked with documenting everything we did, taking screenshots of the screen share, and getting it all into a wiki. For us, it takes less than a half hour, do it every quarter or so, usually scheduled for a Friday afternoon where we can also talk about weekend plans and enjoy some drinks. Eyeballing dashboards is a harder one; a similar thing we do, similar to the last example, is more of a Performance Review, which is bi-weekly. We've got a collection of dashboards, database index metrics, etc; we all get together for a half hour and review all of them similarly. If anything looks unacceptable, we generally backlog two tickets: one to adjust our Slack/Datadog alerts for it so the next time we don't find out during the review, and another to remediate.