That’s not a disadvantage. But it requires a different kind of attention.
The Room Has Done This Before
The lease is signed.
The architect has started drawing.
The contractor is preparing budgets.
The move-in date is already being discussed.
To most of the people in the room, this feels routine. The broker has done this before. The architect has done this before. The contractor, the furniture dealer, and the technology consultants have all done this before.
The tenant has not.
That distinction is easy to overlook because everyone appears to be working toward the same objective. The project team sees a familiar sequence of planning meetings, design reviews, procurement activities, and construction milestones. The tenant sees a new office, a relocation, or a workplace project that simply needs to get done.
The difference usually becomes visible once assumptions start turning into decisions.
The Project Doesn’t Create Disagreement. It Exposes It.
Most organizations enter a workplace project believing they already understand how they operate.
Then the first test fit arrives. The first budget lands. The first detailed design package requires a response.
Questions that felt settled suddenly become topics of conversation again. What looked aligned at a high level starts becoming more difficult when space, cost, and operational consequences enter the discussion.
Growth assumptions become square footage decisions.
Workplace strategies become layout decisions.
Operational preferences become technology, infrastructure, furniture, and budget decisions.
One executive may be planning for growth while another assumes headcount remains flat. One department prioritizes collaboration while another prioritizes focus space. Assumptions that comfortably coexisted during planning suddenly have to coexist on the same floor plan.
The project didn’t create the misalignment. It revealed it.
The earlier that happens, the more options remain available.
The Experience Gap
What the project team possesses is not authority. It is context.
They know which decisions become difficult to reverse.
They know which delays eventually affect procurement.
They know that what appears to be a minor design adjustment can ripple through cost, schedule, fabrication, and implementation.
Most importantly, they understand the relationship between today’s conversation and tomorrow’s consequence.
They know these things because they have seen them before.
The tenant is learning those relationships while simultaneously making decisions that may affect the organization for years.
That is not a capability problem. Most organizations are fully capable of making good decisions. The challenge is that experience often remains invisible to the people who possess it.
The architect may assume the tenant understands what a test fit is actually committing to. The contractor may assume the tenant understands why a particular procurement decision cannot wait another month. The project team may interpret silence in a design review as agreement.
It usually isn’t.
The Standing You’re Not Using
Experienced project teams move quickly because they understand those relationships. They have already learned where decisions lead.
The organization is still learning.
That is why many tenants underestimate how much standing they actually have in the process. There is nothing unreasonable about slowing a discussion down long enough to understand what is being approved, what becomes difficult to change later, and what assumptions are embedded in the recommendation sitting on the table.
The project team works for the organization.
The experience belongs to the project team.
The consequences belong to the tenant.
The schedule can usually absorb another conversation.
It is far less forgiving of a decision that was never fully understood.
One final thought.
As your project moves forward, decisions start coming faster. Design meetings get scheduled. Furniture selections need approval. Technology deadlines approach. Vendors are waiting for answers. Before long, it can feel like the train has already left the station.
But don’t confuse momentum with necessity.
The project may be moving quickly, but you are still driving it. Despite the pressure to decide, you have every right — and every responsibility — to pause long enough to ask the hard questions:
Why are we doing this?
What problem does this solve?
What are the alternatives?
What happens if we don’t do it?
Is this based on our business needs, or just someone’s standard approach?
Am I getting what I actually want, or just what everyone else thinks I should have?
A good project team will not be bothered by those questions. They should welcome them. Better questions lead to better decisions, fewer surprises, and a workplace that actually supports your organization.
The train may be moving, but it isn’t leaving without you. It’s your project, your budget, and your workplace. Make sure the decisions reflect what you want, not just the urgency of the moment.
About the Author: Richard Neuman advises organizations on capital planning, project governance, and the executive decisions that shape successful capital programs. Over the course of his career, he has overseen more than $2 billion in capital investments across commercial real estate, healthcare, utilities, industrial, broadcast, and development projects. He writes about the organizational blind spots and executive decisions that shape capital programs long before construction begins.
Leading a major capital program or facing a complex capital decision?
Contact Richard.
Subscribe for insights on capital planning, project governance, and the executive decisions that shape capital programs long before construction begins.
