Approvals are a UX problem, not a process problem
Every team we've talked to runs approvals in a Google Doc and a Slack thread. We think the tool is the problem — not the team.
If you've ever shipped social at scale, you know the dance. Marketer writes the post in a doc. Designer makes the image in a separate file. Everyone comments in a Slack thread. A reviewer approves by saying "looks good." The post goes out — and two weeks later someone asks what actually got published.
The fix isn't more process
Every team we've worked with has tried the process fix — a better checklist, a stricter SLA, a named approver. They help briefly, then decay. The underlying problem is that the tool doesn't know what a "post" is. It's a doc, a thread, a file, and a Buffer entry, none of which know about each other.
Make the object first-class
In Postbolt, a post set is one object. Every draft, caption, image, comment, approval, and published URL attaches to it. Status is visible. History is immutable. No thread, no doc, no lost context. That's not process — that's a data model.