Too Many Voices, Not Enough Direction

How to Gather the Right Project Knowledge Without Turning Photography Planning Into a Committee Decision

AEC project photography often depends on information held by several different people. The project architect may understand the design priorities. Marketing may know what the firm needs to communicate. Business development may know where the current image library is weak. Operations or facilities may understand access, readiness, privacy, or other production constraints.

The problem is not that too many people have useful information. It is what happens when every contribution becomes a requirement and no one is clearly responsible for sorting one from the other.

Start With What You Need to Know

A common approach is to begin by asking who should attend the planning meeting. A better starting point is to ask what needs to be known before the photography plan can be finalized.

What matters most about the architecture? What does the firm need the imagery to communicate? Where does the existing image library have gaps? What site conditions could affect production? Who else may have a legitimate need to use the finished work?

Once those questions are clear, it becomes easier to identify whose input is actually needed and why. The objective is to involve people where their knowledge can improve the decision, not to give every participant equal control over it.

Useful Advice Does Not Require Equal Decision Authority

A contributor may identify an important technical space, a design detail worth documenting, or a production condition that changes the plan. Clear decision ownership should leave room for that information to improve the work without automatically turning every suggestion into scope.

Before involving someone in photography planning, it helps to distinguish between three roles:

Advise: They hold knowledge that can improve the plan.
Approve: They have legitimate authority over a specific decision, such as budget, access, privacy, scope, or usage.
Be informed: They need visibility into the engagement but do not need to participate in making the decision.

These roles can overlap, but they should not be treated as interchangeable. Not everyone who should know about the photography needs to help design the photography plan.

Gather Targeted Input Before the Meeting

One of the easiest ways to create unnecessary complexity is to circulate a photography plan broadly and ask everyone for general feedback. That invites people to evaluate decisions outside their expertise and makes it difficult to distinguish an important requirement from a personal preference.

More useful questions are bounded by what each person actually knows. A project team might be asked what part of the design would be easiest to misunderstand without intentional documentation. Business development might identify a project capability the firm’s existing library does not demonstrate well. Operations can flag conditions that could affect access or readiness. Another stakeholder may have a distinct usage need that should be addressed before production.

The same discipline becomes even more important when project photography is being shared across several firms. Participating architects, engineers, contractors, owners, and consultants may each have legitimate interests in the final image set, but financial participation does not automatically create equal creative direction.

Their requests should be gathered and filtered before they become part of the production plan. Some will expose genuine gaps in the proposed coverage. Some will serve a distinct stakeholder need worth accommodating. Others may expand scope without materially improving the project record.

Cost sharing can broaden the perspective without turning every participating firm into a co-director of the photography.

Where possible, this input should be collected before the planning meeting and consolidated into a working brief. The meeting can then be used to resolve actual conflicts, dependencies, or tradeoffs rather than collecting everyone’s preferences for the first time.

This is where The Briefing Structure becomes useful: the purpose of the meeting is not to build the plan from scratch, but to refine a brief that already reflects the right project knowledge and known constraints.

Complex Projects Need More Counsel, Not More Decision-Makers

At University of Michigan Health-Sparrow, the photography needed to account for architecture, clinical environments, engineering systems, active healthcare operations, privacy, and production access. No single source of information could reasonably define every requirement of the engagement.

Different forms of expertise needed to reach the planning process, but those inputs still had to become one coherent production direction.

Someone Still Has to Own the Plan

The accountable lead does not need to know everything personally. They need to know whose expertise matters, which input can materially affect the plan, what constraints are real, and where tradeoffs need to be made.

Before adding someone to the photography-planning process, ask what they know that the current team does not, what decision that knowledge can actually affect, and whether they need to advise, approve, or simply be informed. When cost sharing is involved, add one more question: does this request fill a legitimate gap, or is it simply another preference entering the scope?

The strongest photography briefs are built by gathering broadly, filtering deliberately, and deciding clearly. The right knowledge should reach the process. It should not dissolve responsibility for making the final call.

This article is part of the 517 Visuals AEC Visual Strategy series, which examines how project photography is planned, structured, and used inside AEC organizations.

Would you like keep up with our latest work?

Follow our happenings by subscribing to our social media accounts

Too Many Voices, Not Enough Direction