What Changes When a Project Needs a Crew Instead of Just Me

Most of my projects still run solo, or close to it, just me and maybe one assistant handling a straightforward brief. But every so often a project's scope crosses a line where solo execution genuinely isn't realistic anymore, multiple simultaneous setups, talent that needs managing separately from camera work, a timeline too tight for one person to physically cover. When that line gets crossed, almost everything about how I run the day changes.

I used to think the difference between solo and crew-based work was mostly a matter of scale, more hands doing the same basic job. It turns out the difference is closer to running an entirely different kind of operation, one where communication, delegation, and logistics matter as much as the actual photography. If you want to see how I plan around this shift in scope, the Adventure Travel Photographer's Playbook covers the planning side in more detail.

The Moment a Project Outgrows Solo Execution

The signal is usually a specific logistical problem rather than a general sense that a project feels big. Needing simultaneous coverage from two angles, managing talent separately from operating camera, or a timeline that physically can't be covered by one person moving between setups are the concrete triggers that tell me a crew is genuinely necessary, not optional.

I try to identify this early, during pre-production, rather than discovering it mid-shoot when it's much harder to add support quickly. A brief that looks borderline gets a hard conversation with myself, and sometimes with the client, about whether the scope actually requires more than one set of hands to execute well.

Once I've decided a crew is genuinely needed, the entire structure of the project shifts, not just the day-of logistics. Pre-production, budgeting, and communication all change shape well before anyone actually shows up on location, which is part of why catching this early matters so much.

Pre-Production Changes First

Solo pre-production is largely a mental exercise: I visualize the shoot day, walk through the shot list in my head, and prepare gear accordingly. Crew-based pre-production has to become external and shared, because everyone involved needs the same clear picture of the plan, not just the version living in my head.

This means mood boards, shot lists, and rough schedules get built out in a form other people can actually reference, not just notes I'd normally keep loosely organized for myself. Commercial shoots already lean this way given how tightly defined deliverables usually are, but crew involvement pushes that documentation even further.

Role assignment also has to happen explicitly during pre-production rather than being figured out on the fly. Who's handling which angle, who's managing talent, who's running a drone, all of that needs to be decided and communicated before the shoot day starts, not worked out through improvisation once everyone's already on location.

Communication Becomes a Deliverable of Its Own

Working solo, communication is internal and instant, I decide something and act on it immediately. With a crew, every decision has to be communicated clearly enough that other people can act on it correctly, which takes real, deliberate effort that solo work never requires.

I've learned to be far more explicit than feels natural, spelling out things I'd normally leave as an unspoken assumption when working alone. What looks obvious to me isn't necessarily obvious to someone seeing the plan for the first time, and assuming otherwise is one of the fastest ways to lose time or coverage on a crew day.

This extra communication effort pays for itself quickly once a shoot is underway, since a crew that understands the plan clearly moves faster and makes better independent decisions than one waiting for constant direction. The upfront cost in clarity saves real time across the actual shoot day.

The Team Huddle at the Start of Every Crew Day

Every crew-based shoot starts with a short huddle: the goal for the day, the planned looks or setups, and space for anyone to ask questions before we actually start moving. This takes only a few minutes but sets the tone for the entire day far more than any written shot list on its own could.

I trace this habit back to team sports and a leadership course I went through years before I ever ran a photo shoot professionally. A team captain doesn't succeed by micromanaging every player's move. They succeed by making sure everyone understands the goal clearly, then trusting people to execute their part of it.

That same framework applies directly here. A crew that leaves the huddle with a clear, shared understanding of the day's goal makes better decisions independently than a crew simply waiting for instructions at every step, which matters enormously once the shoot actually gets moving and things start happening in real time.

Delegating Without Losing the Creative Thread

The hardest adjustment moving from solo to crew work was learning to delegate technical execution without losing the creative through-line of the project. On a solo shoot, every decision runs through me directly. With a crew, other people are making real-time calls that shape the final work.

The way I hold onto creative control without micromanaging is by being extremely clear about the vision and the non-negotiables up front, then trusting the crew's technical judgment within that frame. I don't need to approve every individual camera setting, but I do need everyone aligned on what the final story actually needs to look and feel like.

This balance took time to find. Early on I either over-directed, which slowed everyone down and signaled a lack of trust I didn't actually feel, or under-directed, which occasionally let small creative drift accumulate across a shoot day into something that didn't match my original vision by the time we reached the edit.

What I Give Up Control Over, and What I Don't

I give up direct control over the mechanics of individual shots handled by other crew members, camera settings, framing decisions on a second angle, drone flight paths, trusting the person assigned to that role to execute it well within the shared creative brief we established during the huddle.

What I never give up is final creative approval on selects, sequencing, and how the overall story gets told in the edit. Multiple people can capture footage or stills on a crew day, but the decisions about what actually makes it into the final deliverable stay with me, since that's where the story actually gets shaped.

This split, shared execution, centralized creative decision-making, keeps a crew-based project efficient without turning it into a committee where every choice gets debated. It also matches something I've learned from experience: accepting client feedback as a gift, but also recognizing that no single person, including me, can be perfect solo, which is a big part of why producers and assistants matter in the first place.

Logistics That Barely Register Solo But Matter Enormously With a Crew

Meals, transportation, and scheduling around multiple people's availability barely register as considerations on a solo shoot. I eat when I'm hungry and move when I'm ready. With a crew, those same logistics become real planning problems that, if ignored, quietly eat into productive shoot time.

Permits and access considerations also scale differently with a crew. A single photographer moving through terrain or a location often draws less attention and requires less formal coordination than a visible group with additional equipment, which sometimes changes what's actually feasible for a given location.

I've learned to build buffer time into crew-based schedules that I'd never bother with solo, since coordinating multiple people's pace and needs almost always takes longer than the same task would solo. Underestimating that buffer was one of my earliest and most consistent mistakes moving into crew-based work.

Budget and Line Items Change Shape With a Crew

Every additional crew member becomes its own explicit line item in the estimate, day rate, travel, meals, lodging if the shoot is remote, rather than an abstract addition to an overall number. This level of itemization matters even more on crew projects than it does on solo ones, since the cost structure gets meaningfully more complex.

I also build in a slightly larger contingency buffer on crew-based budgets than I would solo, since more people moving parts means more potential for a schedule slip or an unexpected logistics cost that a tighter solo budget wouldn't need to absorb in the same way.

Clients generally understand why a crew-based project costs meaningfully more than a solo shoot once they see the breakdown, but that understanding depends on the same transparency I bring to every pricing conversation: showing exactly what each additional person and each additional logistics cost is actually buying them.

Pace and Flow on Set Change Completely

A solo shoot has a natural, self-directed rhythm, I move at my own pace and adjust instantly when something isn't working. A crew shoot has to move at a pace that accounts for setup and coordination time across multiple people and pieces of equipment, which is almost always slower per individual shot, even though total output across the day is often higher.

I've had to get comfortable with a different kind of patience on crew days, accepting that a setup involving multiple angles or a drone alongside ground coverage simply takes longer to execute than the equivalent solo shot, even when the final result justifies that extra time completely.

The tradeoff is real output volume and coverage variety that solo work simply can't match within the same shoot day. A crew slows down individual moments but expands what's possible across the day as a whole, and learning to value that tradeoff correctly took real adjustment on my part.

Mistakes I Made Early On Running a Crew

My first attempts at crew-based shoots suffered from under-communicating the plan, assuming people would naturally understand what I wanted the way I would if I were doing the work myself. That assumption cost real time and occasionally produced footage that didn't match what I actually needed for the final story.

I also underestimated logistics buffer time consistently in my early crew projects, scheduling days as tightly as I would for solo work and then watching that schedule slip once multiple people's coordination needs entered the picture. Building in more realistic buffer time was a lesson that took a few uncomfortable projects to fully absorb.

The biggest early mistake, though, was trying to hold onto too much direct control over every technical decision, which slowed the crew down and signaled a lack of trust that undermined the whole point of bringing other capable people onto the project in the first place. Learning to delegate technical execution while protecting creative decisions took real practice to get right.

Why I Still Choose to Work Solo on Certain Projects

Documentary and editorial work, where the story is discovered rather than executed against a fixed shot list, still benefits enormously from solo or near-solo execution. That kind of project depends on flexibility and instinct that's harder to coordinate across a full crew without slowing down the exact spontaneity that makes the work strong.

Personal, self-initiated projects also tend to stay solo by choice, not just necessity. Much of what keeps me motivated after a decade in this work comes from projects I've pitched and shaped myself, and there's a specific creative freedom in solo execution that a crew, however well-coordinated, changes the character of.

Knowing when a project genuinely needs a crew, and when it's actually better served by staying solo, has become one of the more important judgment calls I make during pre-production. Neither approach is universally better. They're suited to different kinds of projects, and mismatching the two costs more than most people expect.

How Client Relationships Shift With a Crew Involved

A client is used to talking directly to me on a solo shoot, which builds a certain kind of trust and immediacy that changes once a crew is involved. I make a point of staying the clear point of contact even with more people on set, so the client never feels like their project has been handed off to a room full of strangers.

I also introduce the crew to the client before the shoot day whenever possible, even briefly, so there's a human connection to each role rather than an anonymous group of hired hands moving around the location. Clients tend to relax more once they understand who's doing what and why each person is there.

On set, I make sure the client still sees me actively directing the creative decisions, even when other people are handling technical execution. That visibility matters for client confidence, since they're trusting the vision they hired me for, not just the collective output of whoever happens to be standing around with a camera that day.

This attention to the client relationship, even amid the added complexity of managing a crew, has kept repeat business strong even as my projects have scaled up in size. Clients who felt personally connected to a solo shoot need that same feeling preserved, just translated into a bigger, more coordinated production.

Scaling Back Down After a Crew Project Ends

A large crew-based project doesn't change how I approach the next solo shoot that follows it, and I've had to be deliberate about resetting my own mindset between the two modes rather than carrying crew-scale habits, more documentation, more formal delegation, into work that doesn't actually need them.

Solo work benefits from a looser, more instinctive process, and forcing crew-level structure onto a personal or small editorial project usually just slows things down without adding real value. I've caught myself over-planning a solo trip immediately after a big commercial production simply out of habit, before consciously stepping back into a lighter, more adaptive mode.

Being able to move fluidly between these two working styles, tightly coordinated crew management and loose, self-directed solo execution, has become its own skill over the years. Neither mode is the default setting. Each project gets matched to whichever approach actually serves it, and that match only works if I stay conscious of which mode I'm supposed to be in.

Reflection Questions

1. What's the specific logistical trigger, rather than a general feeling of scale, that would tell you a project genuinely needs a crew?
2. How explicit is your communication with collaborators compared to the internal decisions you make working solo?
3. Where do you draw the line between delegating execution and protecting your own creative decisions on a team project?
4. What kind of project would you actively choose to keep solo, even if you had the budget to bring on a full crew?

If you're planning your first crew-based project, the Adventure Photographer's Playbook covers how I structure pre-production, budgeting, and communication once a shoot outgrows solo execution.

Dalton Johnson is a professional adventure and editorial photographer with over a decade of experience creating images on all seven continents. His client work includes Patagonia, GoPro, Arc'teryx, Four Seasons, Nike, Rivian, Big Agnes, Ford Bronco, and 160+ other brands. He runs Dalton Johnson Media as a full-service studio, from pre-production through post and distribution.