3 operator notes a week on pipelines I'm fixing for founders and their teams, plays we’re running, and the decision rules that stop video from becoming your second job.
|
From the Arsenal: SOPs can reveal problems. Story Of The Day: Bob was walking me through a bunch of docs. There were A LOT of them. To be honest there were so many I even lost track listening. After he went over them I asked: and he said: what he meant was this: The resources technically existed. On paper, it looked like a perfect SOPs. They knew parts of it could be better. So no one was fixing it. So what Bob is saying is: After trying all the usual fixes: Maybe we need better SOPs. Nothing seemed to solve the slowdown. The team wasn’t really following the SOPs. So the work kept drifting outside the process. But something important did happen. Documentation didn’t fix the pipeline. Where work paused. And that’s the moment most teams don’t pay attention to. Takeaways: A 20-page SOP is a paperweight if no one is following it. How to Apply It Today:
Pro tip: When you identify those moments jot something down like this " The work stopped here because ____" As promised: dialing in your video workflows 1% at a time. Want help launching, scaling and upgrading video operating systems? That’s what we do inside DenimStitch. Find the clog, fix the clog. P.S. Here's me at the gun range yesterday in Augusta. But If you want to see if your current pipeline needs plumbing, I'm opening up 3 slots to do an hour work session reply "CAPACITY" (ESPECIALLY IF SOPs AREN'T WORKING). I'll get back to you with some open dates next week. Happy Friday. |
3 operator notes a week on pipelines I'm fixing for founders and their teams, plays we’re running, and the decision rules that stop video from becoming your second job.