Improving Workflow & Approval Process For Content Flow
summary
Shows a concrete approval pipeline: request → sanity check → approval group with roles and handoffs defined, and guidance to map every change into that basic flow. Recommends auditing current inputs (one client had 50 intake paths and a seven‑foot wall of documented steps) and reduce 50 touchpoints to 5 while keeping working processes. Stresses reviewers with product knowledge, a white glove approach for resistant teams, and measurable goals: faster approvals, consistent cross‑channel messaging, and fewer rework loops.
AI-written summary · about
chapters (5)
- 0:00Breaking content silos
- 4:38Start with existing processes
- 8:51What is workflow?
- 10:56Basic approval process
- 16:00Q&A
related talks
22mPer Aspera ad Productum: Turning Processes into Products
46mManaging The Process
18mDesign Patterns For Efficient DevOps Processes
39mUntangle The Mess In Your Team’s Process
36mMore than words: Reviewing and updating your information architecture
27mProduction pipeline without clogging
29mOvercoming bureaucracy to succeed at digital transformation
29mCode review, do you speak it?