division-operating-modellisted

# division-operating-model **The problem this solves:** a solo operator can keep an entire platform in their head. The moment an agency grows past one or two people, that stops working — every hire brings their own habits, the vendor ships new features and playbooks faster than anyone reads them, and nobody owns making sure the whole team actually uses the platform the way it was designed to be used. The gap doesn't show up as a dramatic failure. It shows up quietly, as cost-of-goods-sold creep: five different tools doing the same job because nobody consolidated, and a platform subscription the agency is paying full price for while getting a fraction of its value. This is the operating model a member running a multi-person division built to close that gap — not a generic org chart, but the specific cadence and rules that keep a team aligned to one platform without an owner having to personally check everyone's work. > **The agency's job isn't to know every vendor feature. It's to have a system that > reliably turns "the vendor shipped something new" into "the whole team is using it > correctly, scoped to what we sell, by next month" — without that translation depending > on one person remembering to do it.** --- ## Say this to your agent > "Set up our division operating model for [platform]. Track every workshop/webinar/ > training [platform] publishes and confirm each staff member has completed it — this is > paid continuing education, not optional. Run a weekly team m