How Geoff Robinson’s Project Management Lessons Apply to Video Production
Complex productions usually become stressful before they become obviously off track.
The problem is often not that the crew is working too slowly or the client is asking too much. It is that important work, changes, risks, or decisions are happening without everyone seeing the same picture.
Geoff Robinson is the COO and co-founder of Rolling Wave Consulting, where he works on complex, multi-stakeholder projects across enterprise and healthcare environments. His approach combines structured project management with the human side of delivery.
For Beverly Boy, that translates directly to larger video projects involving multiple departments, locations, decision-makers, vendors, and rounds of approval.
Robinson’s five formal lessons are to plan the work, act as the buffer and translator between client and team, make invisible work visible, give the team somewhere to raise concerns, and have difficult conversations before the project ends.
Give Everyone the Same View of the Project
Robinson uses a simple high-level plan to show major workstreams, dependencies, and when different groups will be involved.
The plan does not need every detail at the start. It needs to show how the pieces connect and when more information will become available.
That is useful for complex video production.
A Beverly Boy project involving corporate communications, legal, marketing, local crews, executives, and post-production can quickly become difficult if each group sees only its own part.
A simple production roadmap can show script approval, shoot dates, legal review, rough cut, revisions, final delivery, and distribution handoff.
People do not need every answer on day one. They do need to know when their input will be required.
Translate Between the Client and the Crew
Robinson describes the project manager as both a buffer and translator.
Clients and delivery teams may have legitimate needs, but those needs do not always arrive in a form the other side can act on. The project manager turns them into clear requirements, questions, risks, or deliverables.
That is one of a producer’s most important jobs.
A client may say, “We need this to feel more premium.”
The editor needs something more specific.
Does that mean different music? Slower pacing? Fewer graphics? More executive footage? A different opening?
Beverly Boy can reduce revision cycles by translating broad feedback into clear production decisions before it reaches the crew.
Make Scope Changes Visible Early
Robinson says scope often changes gradually through meetings and side conversations rather than through one major decision.
He recommends documenting changes early so everyone can see the connection between scope, schedule, and budget.
Video projects face the same problem.
An added interview, another cutdown, a new location, or a revised script may sound small individually. Together, they can change the project.
For Beverly Boy, documenting those changes does not need to make the relationship rigid.
It simply gives the client and production team the same record of what changed and what that change affects.
That helps the client and production team discuss schedule and cost changes before they become late surprises.
Track Work That Is Easy to Miss
Robinson shares an example where a development team appeared to be missing deadlines.
The real problem was that developers were receiving work directly through Slack messages and verbal requests outside the official planning process. The work was being completed, but nobody managing the schedule could see it.
Once that work was documented, the conversation changed. The issue was no longer whether the team was working hard enough. The real workload became visible.
Production teams can experience the same thing.
Extra client calls, new graphics, alternate exports, file transfers, research, and last-minute review requests all consume time.
If those tasks remain invisible, the crew can look slow when the real issue is that the workload changed.
Good production management makes that work visible before frustration builds.
Give the Crew a Way to Raise Problems Early
Robinson emphasizes giving people a simple place to record concerns.
On one long project, his team used a whiteboard for worries and later moved those items into the formal risk log. The purpose was to capture concerns before people carried them around or forgot to raise them.
A Beverly Boy production does not need the same exact system.
But the crew should know where to raise a risk.
A coordinator may see a timing problem. A DP may flag a location limitation. An editor may notice missing coverage. A producer may see an approval bottleneck forming.
Those concerns are easier to solve while they are still small.
Review the Project Before It Is Over
Robinson recommends lessons-learned conversations during long projects, not only after delivery.
His midpoint reviews ask what is working and what could improve while there is still time to change the experience for the team and client.
That is useful for multi-day shoots, recurring series, and long corporate campaigns.
Beverly Boy can pause after an early milestone and ask:
Are approvals taking too long?
Is the crew receiving enough information?
Are client notes clear?
Is the schedule still realistic?
Small adjustments made halfway through the project are more useful than discovering the same problems during the final postmortem.
Keep Speed From Replacing Judgment
Robinson also makes a useful point about AI: speed does not replace direction.
He describes AI as a force multiplier rather than a compass. If the requirement is unclear, technology can simply produce the wrong result faster.
The same principle applies to video workflows.
AI can help with transcripts, research, organization, and versions. But the production still needs a clear objective, accurate inputs, and human review.
Faster execution is useful only when the team is moving in the right direction.
Team Beverly Boy’s Takeaway
Robinson’s strongest production lesson is simple: make the work visible.
When the client and crew can see the plan, changes, risks, and responsibilities, many difficult conversations become easier.
For Beverly Boy, that means clear roadmaps, documented scope changes, useful feedback channels, and reviews that happen while there is still time to improve the project.
Conclusion
Complex video projects do not stay on track through effort alone.
They stay on track when people can see what is happening, understand their role, raise concerns early, and adjust the plan before small issues become larger ones.
This article is based on an interview originally published by Authority Magazine. Read the full interview here.
