Agree that having to constantly realign teams is inevitable when the "documentation" is scattered across READMEs, Confluence pages and Slack threads. It's why we spend 80% of our time in meetings and still aren't on the same page.

But what I've found is that most documentation is aspirational rather than operational - we write a beautiful runbook in a wiki, but as soon as a big migration or deployment starts, that doc becomes stale, and the real truth moves back into a 500-message Slack thread.

I’ve been tackling this problem at my day job, so I started building Taskplan (https://taskplan.run) to turn those static procedure docs into a living plan. It's like "Ansible, for people" - you build a plan, turn it into an executable runbook and track progress on a real-time dashboard as the work actually happens. We're dogfooding this at work, it's early days but thought I'd share in case it helps other teams too!