Building a Coaching Staff Workflow Around Film and Development

Mike Budenholzer spent two years logging and tagging film as the San Antonio Spurs' video coordinator before he ever got a seat on Gregg Popovich's bench as an assistant. Joe Prunty ran the same job nine years earlier, cutting and organizing film before anyone trusted him with a rotation decision. Both eventually ran their own NBA benches. The Spurs didn't build that pipeline by accident — they built it by treating film work as a defined role with its own ladder, not a task the head coach squeezed in between everything else.

You're running a version of the same problem the Spurs solved decades ago — you just don't have their staff. If you're the head coach who reviews every possession, builds every teaching clip, delivers every piece of feedback, and tracks whether players actually watched it, you're running four jobs at once. That can hold up for a few weeks. It rarely holds up for a full season.

Why a one-person film workflow breaks down

The pattern is familiar. A head coach watches the game film alone, clips a handful of possessions late at night, and either delivers feedback verbally in the next practice or doesn't get to it before the next game arrives. When that coach is traveling, sick, or buried in scouting for the next opponent, the film work simply doesn't happen that week — and nothing else in the program catches it.

Assistant coach responsibilities already vary widely by program — offensive or defensive focus, scouting, recruiting, player development — but the shared expectation is that each assistant carries a defined piece of the work rather than everyone doing a little of everything. Film-and-development work benefits from the same discipline. Splitting it across roles isn't about adding staff; it's about making explicit who is responsible for each stage before the season gets busy enough that it defaults to whoever has the least on their plate that week.

When to formalize this

A staff of two — a head coach and one assistant — can usually run an informal version of this by simply agreeing out loud who does what each week. Once your staff grows past two or three coaches, or once you're running individual development plans for multiple players at once, an informal agreement tends to drift. Tasks get duplicated, or more often, they get dropped because each coach assumes someone else has it.

The clearest sign you need a written workflow: you can't say, without checking, whose job it was to make sure last week's film got turned into a teaching clip a player actually watched. If that answer isn't immediate, the workflow is informal enough to fail quietly.

Four roles inside the development cycle

Brightfield's development cycle runs: observe before correcting, review film objectively, clip teachable moments, deliver concise feedback, assign learning, confirm player understanding, measure improvement over time, repeat. Every step in that cycle needs an owner. On most staffs, that ownership sorts into four functional roles — which can map to four coaches or to two coaches wearing two hats each.

1. The film tagger

Someone has to actually sit with the raw game or practice film and mark possessions by theme, player, and outcome before anything teachable can come out of it. This was Budenholzer's and Prunty's entry point into an NBA staff — in college and pro programs, it's the video coordinator's core job, securing film, logging it, and flagging possessions for the rest of the staff. On a smaller staff, it's whichever assistant is most comfortable with the film platform, assigned consistently rather than whoever has time that week.

2. The sequence builder

Tagged clips aren't a teaching tool until someone turns them into a short, thematic sequence — three to five clips with one point apiece, not a highlight dump. This role decides what the film is actually trying to teach this week and trims everything else out.

3. The feedback deliverer

Delivering the sequence to a player or group is a distinct skill from building it — it's the conversation, the questions asked before the answer is given, the tone. On many staffs this is the head coach or a position coach with the closest relationship to that player, even if a different coach built the sequence. Player development roles at the pro level are built almost entirely around this piece: daily individual work, direct relationships, and the trust that makes corrective feedback land.

4. The engagement tracker

Someone needs to know, across your whole roster, who has actually watched their assigned film and who hasn't — otherwise you have no way of knowing whether your development plan is running or just exists on paper. This role is easy to skip because it produces no visible output of its own; it's also the role whose absence is hardest to notice until a player falls behind without anyone catching it.

Common mistakes

• No named owner for tracking. Tagging and teaching tend to get assigned informally because they produce visible output. Tracking engagement rarely does, so it's the piece most likely to have no owner at all — assign it explicitly rather than assuming it happens by default.
• One coach doing all four roles by habit, not by plan. Even on a two-person staff, deciding in advance who tags and who delivers prevents the default of "whoever gets to it first," which usually means whoever has the most time that week.
• Roles that live in one coach's head. If the workflow isn't written down somewhere your whole staff can see, it disappears the moment that coach is unavailable. A short shared document beats an unwritten understanding.
• Confusing who builds a sequence with who delivers it. These are different skills. Assigning both to the same coach by default, rather than by who has the strongest relationship with a given player, can weaken the feedback conversation even when the film work behind it is solid.
• Treating the workflow as fixed once written. Rosters, staff availability, and season phase change. A workflow you don't revisit a few times a season tends to quietly revert to whoever's covering gaps that month.

How experienced staffs build this

The specific titles change by level — video coordinator, director of player development, assistant coach with a scouting focus — but the organizing idea is consistent across programs that have written about their own structure: each role exists so no single person is the bottleneck for getting film in front of a player with a clear teaching point attached. Video coordinators are frequently described as present in every coaching meeting and every game, which is precisely what let Budenholzer and Prunty tag and route film without waiting on Popovich to free up time — and precisely what eventually made them ready for more. Player development coaches, by contrast, are built around the individual relationship and daily contact with a player — a different kind of bandwidth than the video role requires.

If you don't have the roster to name four separate coaches to four separate jobs, you can still borrow the logic: pick two or three of these functions, assign them by name for the season, and treat the assignment as seriously as a defensive scheme. A workflow that depends on nobody's memory is a workflow that survives a bad week.

Connecting staff workflow to player development

General research on skill development consistently points to consistency of feedback mattering more than any single delivery mechanism — the specific method matters less than whether the loop runs reliably, week after week. That research isn't basketball-specific, but the mechanism transfers directly: a development cycle that runs reliably on a bad week teaches more, over a season, than a brilliant one-off session that only happens when a single coach has a free evening.

A development cycle that depends on one coach's bandwidth isn't a system — it's a habit that happens to be working right now. A workflow becomes a system once it survives that coach being out for a week.

Reflective questioning — asking a player what they saw before telling them what happened — is one of Brightfield's core film-review habits, and it belongs inside whichever role is delivering feedback, not just the coach who happens to be in the room that day. Splitting the workflow across roles doesn't just protect against one coach's schedule; it also means more than one person on your staff understands how to run a film-review conversation the way you actually want it run.

Where Brightfield fits

This division of labor works with a shared drive, a whiteboard, and clear verbal agreements — staffs ran versions of it before software existed for it, and the Spurs ran it with a chalkboard and a film projector long before either. Brightfield Scope is built for the version of this problem most youth and school programs actually have: a staff too small to hire a dedicated video coordinator, but still needing tagging, sequence-building, feedback delivery, and engagement tracking to happen reliably across more than one coach. It doesn't replace the roles above — it gives your staff a shared place to run them.