What I Learned the Hard Way About Gensler Company Size (and Why It Actually Matters)

Look, I'm not proud of this. But if my experience can save you from the same mistake, it's worth sharing.

In my first year coordinating with Gensler on a major office-to-residential conversion (back in 2022), I made a classic error. I assumed that because of their company size — I'd heard the numbers, 7,000+ people globally, 50+ offices — the communication chain was going to be a nightmare. Long approval cycles. Bureaucracy. Layers of management between me and the person who actually knew what they were doing.

So I over-engineered my comms. Massive PDFs. Detailed spec sheets. CC'd everyone I could find on their org chart.

The result? A $32,000 mistake (not counting the 6-week delay).

The Surface Problem: "They're Too Big to Be Responsive"

Here's how I saw it at first. I had a tight deadline — a developer client needed floor plan revisions within two weeks to meet a zoning deadline. I assumed Gensler's size meant I needed to "go formal" with every request. Use their official portal. Submit RFIs through proper channels. Follow the process they'd published.

I spent three days formatting a submission package. Full of details they hadn't asked for. I thought being thorough was the safest path.

It wasn't.

They came back with a single question: "Which of the three scenarios is your priority? We can't start until you tell us."

Three days of work. One question. I felt like an idiot. (I was.)

The Deeper Problem: What I Actually Misunderstood

Here's the thing about a firm like Gensler: their company size is a feature, not a bug — but you have to know which features you're dealing with.

What I didn't realize until my third major mistake (a $47,000 rework on a Miami high-rise interior project in September 2023) is that Gensler's scale works differently than I expected. I assumed:

• Big firm = centralized decision-making. Wrong. Their offices operate with surprising autonomy. The New York office doesn't necessarily know what the San Francisco office is doing.
• Big firm = standard processes. Not exactly. Each office adapts processes to local market conditions and client expectations.
• Big firm = slow response. In my experience, the opposite. Their scale means they have specialists on standby who can answer technical questions fast — if you know who to ask.

The mistake I made in the Miami project? I assumed the interior design team in their Chicago office used the same material spec conventions as their Atlanta team. Two different systems. The specs I sent were interpreted differently than intended. The result? floors that didn't match the approved sample. $47,000 in material replacement plus a two-week schedule impact.

We were using the same words but meaning different things. Discovered this when the material arrived and the project architect said, "Wait, we spec'd this as the accent, not the primary."

The Real Cost: Beyond Just Dollars

After the third rejection in Q1 2024, I sat down with my PM team and made a checklist. Here's what I'd learned about the true cost of assuming homogeneity:

1. Direct rework costs: The $47k Miami material replacement. The $12k in expedited shipping on a Denver project where I'd sent wrong spec sheets. An $8k structural review fee because I hadn't aligned assumptions with the local office's building code expertise.
2. Delay costs: Across three major projects, we lost an estimated 8-10 weeks total waiting for clarifications I could have avoided.
3. Reputation cost: Hardest to quantify, but real. After the second mistake, I noticed our contact at Gensler started copying their legal department on routine emails. That's a signal you don't want.

In total? I'd estimate roughly $89,000 in wasted budget across 18 months. All because I didn't ask a simple upfront question: "How does your office prefer to communicate spec changes?"

The Fix: Simpler Than I Expected

Here's what I do now, and it's embarrassingly simple:

1. First call, not first email. Before any project starts, I schedule a 20-minute call with the project lead at their specific office. No agenda. Just: "How does your team like to work?" The answer varies by office, by project manager, by region.
2. One-page brief. Stop sending 50-page spec packages upfront. Send a one-pager with three critical items: scope, schedule, and decision points. Let them tell me what else they need.
3. Check assumptions at every transition. Every time a project moves from one phase to another (e.g., schematic design to design development), I explicitly ask: "Are we still aligned on X?"

This approach worked for us, but our situation was a mid-size developer with repeat business. If you're dealing with a one-off project or a different developer structure, the calculus might be different. I can only speak to my context — 11 years in project management, last 3 specifically handling Gensler coordination. Your mileage may vary if your contracts or timelines are different.

What I Wish Someone Had Told Me

If I could go back to my 2022 self, I'd say: stop assuming the company size tells you everything. It doesn't. Gensler's size means they have resources. It doesn't mean they have a single process. The person on the other end of that email is as busy as you are. They want clarity, not comprehensiveness.

Is the premium of working with a global firm worth the complexity? Sometimes. Depends on context. Look, I'm not saying smaller firms are better. I'm saying the advantage of scale is access — but you only get that access if you ask the right questions.

The first question I ask now: "Who's my day-to-day contact in your office, and how do they prefer to receive updates?" Five minutes of verification beats five days of correction.

That's the checklist item I wish I'd had from day one. We've caught 47 potential errors using this approach in the past 18 months. Not all of them would have been costly. But the ones that were? The checklist saved us.