CP104: When "We'll Figure It Out Later" Becomes Your Firm's Most Expensive Decision

When "We'll Figure It Out Later" Becomes Your Firm's Most Expensive Decision

The client mentioned it halfway through the schematic design presentation. Looking at the entry sequence, she said, "I think we want something special here, something that really announces the building."

The project architect nodded. "Absolutely. We'll develop that as we move into design development."

No one asked what "something special" meant. No one discussed budget implications or whether "announces" meant material quality, spatial drama, or architectural signature. The conversation moved to the next board.

Three months later, during a construction document review, that entry became a problem. The client was expecting a custom feature, something sculptural, distinctive. The team had been working within standard details and a budget that didn't include what she was imagining. By then, drawings were coordinated, consultants had moved on, and the schedule was tight.

The real cost wasn't the meeting to realign expectations. It was the trust that eroded when the client realized she'd been imagining something the team had never committed to building.

The Pattern Nobody Names

Architecture firms don't struggle with deferred decisions because teams lack experience. They struggle because "we'll figure it out later" has become a reflexive response to uncertainty, a way to keep meetings moving and preserve momentum.

The assumption is that deferring a decision pauses it. What actually happens is the decision keeps moving forward anyway, just without ownership. Everyone forms their own interpretation and proceeds accordingly.

A project manager assumes one path forward. A designer works toward another. The client carries a third version entirely. The gap doesn't become visible until someone presents work that exposes the misalignment, usually after significant effort has gone into parallel assumptions that were never reconciled.

This plays out across project types and firm sizes. The mechanism is always the same: ambiguity is acknowledged but not resolved, and the firm proceeds as if clarity will emerge naturally once more information becomes available.

It rarely does. What emerges instead is rework, schedule compression, and conversations about why the budget doesn't cover what someone thought was always included.

Why This Feels Efficient

The pressure to maintain momentum is real. Meetings are full, deadlines are tight. Pausing to resolve a question feels like it's slowing the project down.

So uncertainty gets noted and moved downstream with the promise of future resolution. The decision to defer feels pragmatic, even responsible. Why commit before you have complete information?

The problem is that early phases, when energy is high and commitments are still fluid, are exactly when decisions are cheapest to make. Information is never complete, but waiting for it creates cascading dependencies that make later decisions far more expensive.

Principals often assume clarity without realizing it. Because you've seen similar situations before, the path forward seems obvious. But the team doesn't have your context. The client doesn't share your mental model. What feels clear to you remains ambiguous to everyone else.

Where the Cost Actually Shows Up

The immediate cost of a deferred decision is invisible. It's what doesn't happen; the conversation that would have aligned expectations, the trade-off that would have been explicit, the constraint that would have shaped work from the beginning.

The visible cost comes later, when that early ambiguity forces redesign.

A vague assumption about what "flexible workspace" means leads to a layout that doesn't match the client's operational needs. The team redesigns. Redesign forces coordination changes. Coordination changes affect the schedule. What could have been resolved with an hour of conversation early becomes ten hours of correction later, plus the relationship strain from discovering misalignment after commitments have been made.

A firm working on a multi-phase institutional project faced early questions about building classification and occupancy that couldn't be definitively answered. Rather than pausing or establishing clear decision criteria, the team noted the uncertainty and proceeded. When regulatory constraints finally surfaced months later, they invalidated core assumptions about how the building could function.

The client wasn't upset about the regulatory limits, those were real constraints. They were frustrated by the gap between what they'd been led to expect and what was actually possible. The firm had allowed them to imagine a version of the project that couldn't be built, and no one had said so clearly enough to stop it.

What Teams Learn

When "we'll figure it out later" becomes the pattern, teams adapt.

They learn that clarity won't arrive until there's a problem. Confidence erodes. People escalate more, take less initiative, or make quiet judgment calls they shouldn't have to make because no one has explicitly decided anything.

Over time, talented people grow tired of repeatedly patching gaps that could have been addressed upstream. The work becomes less about solving meaningful problems and more about recovering from avoidable mistakes.

Building Operating Discipline Around Decision Points

The alternative to deferral isn't complex, it's uncomfortable.

It's pausing a client meeting to say, "Before we move forward, we need to be clear about what this means and what it will require." It's naming budget tension when it first appears, not after design has advanced. It's acknowledging that two people are describing the same thing differently and stopping to reconcile the gap.

These moments feel risky. They slow the conversation. They surface conflict that could have been deferred. But they're far less costly than addressing the same issues after commitments have formed and work has proceeded in different directions.

A firm started treating ambiguity differently after several projects hit similar patterns. Instead of noting uncertainty and moving on, they began pausing to establish decision criteria: "We can't resolve this completely today, but here's what we'll use to decide when we can." The criteria became shared operating logic. When the decision arrived, it didn't require rebuilding context or realigning expectations, everyone was working from the same framework.

What changed wasn't the complexity of their projects. It was building operating discipline around decision points instead of defaulting to deferral.

Making Decision Discipline Systematic

The firms that avoid this pattern don't rely on individual discipline or better intentions. They build decision clarity into how they operate.

They recognize common decision points where ambiguity typically hides (scope boundaries, budget assumptions, design intent, phasing logic, approval authority) and design explicit practices around those moments. Not rigid processes, but operating rhythms that surface and resolve uncertainty before it travels downstream.

This becomes part of how the firm works: at project kickoff, certain questions always get answered. At phase transitions, specific criteria always get confirmed. When clients introduce new ideas, particular conversations always happen before proceeding.

The operating discipline isn't about perfection or eliminating all uncertainty. It's about distinguishing strategic deferral, waiting for information that will materially change the answer, from operational avoidance of uncomfortable but necessary conversations.

Firms that build this discipline into their operating model don't eliminate ambiguity. They stop letting it move forward unowned, which is where the real cost accumulates.

What to Notice

Over the next few weeks, pay attention to how often "we'll figure it out later" appears in your firm's conversations.

Notice when it's genuinely strategic, deferring a decision because you're waiting for information that will materially change the answer and when it's avoidance of an uncomfortable conversation that could happen now.

Notice what happens after those deferrals. Does clarity emerge naturally, or does the ambiguity travel downstream until it creates friction? Do teams proceed with confidence, or do they hesitate because no one has actually decided anything?

The pattern will show you where your firm lacks operating discipline around decision points and whether you're mortgaging future time and trust to preserve present momentum in ways that don't actually serve the work.