Leadership, systems and people built to run without me

When I joined Think Bright Marketing in 2023, the marketing team for a national generator network of roughly 80 locations across 23 states was three people: the owner, a paid ads specialist, and a social specialist. There was no lifecycle email, no video capability, and no real operating system. For the first stretch, I was the function. Before anyone was hired to help, I stood up the capabilities myself: architected the lifecycle email program from scratch, built the video production capability on my own equipment until the results justified the company investing in a proper kit, and built a field-staff ID and verification program from nothing.

Building the capabilities was only half the job. The harder half was making all of it run without me, and that split into two problems. The first was the operating system: I inherited a weekly cadence that had quietly become the place where work went to be postponed, because the person running it had no way to judge whether one specialist's task actually outweighed another's, so deferral became the default. The second was the people: across both organizations I kept ending up with team members who were early in their careers or hired into a role narrower than the work actually required. Someone had to close that gap, and closing it was the same job as fixing the system: both were about making the work not depend on me being in the room.

Rebuilt the operating system. I took the weekly cadence over and put a real decision at the center of it: any time a task came up, three questions got asked before anything moved, is it prioritized, what's the actual priority, does it outrank what's already scheduled. That turned deferral from a reflex into a decision someone had to defend. I added a Friday review with no place to hide, every task from the week marked complete, stuck, or carried, with notes required on anything unfinished. Underneath it, I built the standards stack: if it's a task we need to do, it goes into Monday.com, stated repeatedly and enforced, and I recommended, justified, and built out a network-attached storage system so video assets, backup, and client sign-off all had one reliable home.

Developed the specialists into owners. This was never a generic development plan, it was one specific, named gap per person, closed. Ali, on the web side, shipped fast but skipped review, and coaching him to slow down and route through approval turned him into someone who could run roughly a hundred web properties without check-ins. Amanda was hired for social, but I cross-trained her into email and video to unblock my own capacity, and she went on to scale the lifecycle system across 18 accounts and map the audience data structure herself. At the credit union, I coached a multimedia developer to weave organizational mission into his output, developed an email specialist twice (first into business-side lifecycle campaigns, then into owning the digital signage network entirely), and moved an intern into IT where data was his stronger discipline. The pattern held every time: one specific gap, and afterward the person could operate without me reviewing their work.