Field Notes

Someone in a meeting tells the room what the timeline needs to be.

The people who actually know what it will take to hit that timeline are in the same room. They say it will not work. The meeting ends. The timeline stands.

This is not a story about one project. It was a pattern I watched repeat across almost every complex retail build early in my career. The decision-maker has one set of information. The expert has another. In a well-governed project, those two sets of information are reconciled before anything is locked. In most projects, they are not.

The GC knows what the site actually looks like after demolition begins. The trades know what they can realistically produce in the available time. The store development lead on the ground knows which assumptions in the schedule are real and which ones were built to satisfy a leadership conversation. The expert in the room has specific, hard-won knowledge about this project, this site, this supply chain, this vendor.

The decision-maker has a goal.

Those are not the same thing, and in retail store development, the gap between them is where the most expensive problems live.

I have been in that room more than once. On one project, the team spent more time negotiating internally with leadership than with the GC and trades actually executing the work. Leadership wanted a date. The people doing the work said the date was not possible. The date was kept. The team absorbed the consequences. And when the store opened at exactly the date the experts had said it would, not the date leadership had set, no one revisited who had been right.

On another project, the lighting system the design called for could not be delivered in time. The version that would have worked meant a delay. The delay was not accepted, so a compromised version was pushed through to hit the date. It could not carry the load it was being asked to carry. The connectors failed repeatedly. The store never fully recovered from it. Putting it right meant closures and operating constraints that ran long after opening, and remediating the shortcut cost far more than the delay it was meant to avoid ever would have. The decision was not made to save money. It was made to avoid a delay the timeline would not absorb. The timeline held. The store paid for it for the rest of its life.

The pattern in both cases was the same. The expert’s read was accurate. The decision-maker’s read was shaped by something else: a personal timeline, a date on a calendar, a goal that had more to do with how the opening would look than with how the project would hold. The expert was then asked to execute inside a set of constraints they had already told the room would not work. They did their best. The project paid for it. The store team paid for it. The customer experienced it. And by the time the full cost of those decisions was clear, the person who made them was no longer with the company. The override followed no one. The consequences stayed with the stores.

Fixture Installation during Construction | QTC Retail Solutions

What is missing in those moments is not better expertise. The expertise was already in the room. What is missing is a structure that requires the expert’s knowledge to be reconciled with the decision before the decision is made, not discovered in the consequences after it.

The owner-side governance layer is not there to second-guess the GC or override leadership. It is there to make sure the expert’s read gets into the decision before the decision is locked. That the lighting cannot carry the load it is being asked to carry. That the realistic opening date is November 4, not mid-October. That the gap between what leadership wants and what the project can deliver is named and addressed upstream, not downstream.

Somewhere in the middle of that project, I started asking the decision-maker one question whenever a date or a target arrived without a basis. Based on what? Not as a challenge. As a genuine request for the information behind the number. What were you told, by whom, and when, that produced this date? More often than not, the honest answer was that the date was based on how the opening would look, not on anything the site, the trades, or the schedule could support. The question did not always change the decision. But it moved the burden of proof to the person setting the target, which is where it belonged.

The store opened on November 4. Exactly when the expert said it would.

Nobody in the room that day remembered the meeting where the other date was set.

Leave a Reply

Your email address will not be published. Required fields are marked *