In real estate development, three parties sit at the same table. They share the same timeline, the same building, and often the same meeting room. But they are not playing the same game.
Projects rarely collapse completely. In my experience, that is actually the exception. What happens far more often is quieter and, in a way, more interesting: the project gets delivered, the building goes up, and somewhere in the process one or two parties walk away feeling like they lost. Nobody talks about it publicly. But it happens on almost every project.
Why? Because the three core stakeholders in any real estate development (call them Stakeholder A, B, and C) come to the table with fundamentally different ideas of what "success" means. And since nobody puts that on the agenda in week one, the gap quietly drives decisions, creates tension, and shapes who ends the project satisfied and who does not.
Here is how each party thinks about the three things that matter most: time, budget, and quality. Then I want to look at where common ground actually exists, and where each party needs to be honest about what they are being asked to give up.
The Three Players — Different Seats, Different Scorecards
Stakeholder A
Time
Delivery on schedule is everything. A delay is not just a construction problem, it is a financial event. Financing costs run. Market windows close. Commitments to future tenants or buyers are at risk.
Budget
The budget was set based on a return model. Every euro over that number comes directly out of margin. The goal is not to be cheap, it is to not exceed the number that was already justified to someone above.
Quality
Quality matters, but it is defined by the end user and the market position. Overbuilding is as much of a problem as underbuilding. The question is always: quality relative to what?
Stakeholder B
Time
Enough time to do the work properly. Compressed timelines mean errors, redrawn details, and change orders downstream. A well-paced design phase saves everyone time in construction, but this argument is always harder to make than it should be.
Budget
The fee is fixed early and rarely reflects what the project actually becomes. Scope creep, revision cycles, and last-minute value engineering all eat into it. The real goal is to protect the original agreement while still delivering something worth putting in a portfolio.
Quality
This is where identity lives. Quality is not just functional, it is reputational. A cut that compromises the design is not a neutral business decision. It is a mark on something they signed.
Stakeholder C
Time
Time is money in the most literal sense. Every week on site has a cost. The goal is to sequence work efficiently, minimize idle time, and avoid situations where incomplete design decisions stop progress on the ground.
Budget
Margin protection. The tender price already had risk priced in. Anything that changes the scope, adds complexity, or requires rework is a direct hit. The goal is to deliver within the agreed envelope and recover where possible.
Quality
Quality means compliance. Meeting the specification, passing inspections, and handing over a building the client accepts. Going beyond the spec is not a goal, it is a risk, because it might not be recognized or compensated.
Common Ground — Where Alignment Actually Exists
There is more common ground than it might seem. All three parties want the project to reach completion. Failure, real failure, where the building does not get built, is bad for everyone. Nobody wants that.
All three parties also benefit from clear information. Ambiguity is the shared enemy. Unclear drawings cause rework. Unclear scope causes disputes. Unclear expectations cause disappointed clients. Every party at the table has an interest in the information being correct and available when it is needed.
And perhaps most importantly: all three parties have their reputation tied to this project. A is associated with the asset. B's name is on the design. C delivered the building. Nobody wants a reference site they have to explain.
The problem is not that common ground does not exist. The problem is that nobody maps it out at the start, so when pressure builds, each party defaults to protecting their own scorecard instead of the shared one.
The Hard Part — Where Compromise Actually Has to Happen
This is where most conversations stop being comfortable. Compromise sounds reasonable in theory. In practice, it means someone gives something up, and that needs to be said clearly.
Stakeholder A has to decide early what the actual priority order is. Time, budget, and quality are three variables. In any real project, you can optimize for two of them. The project that tries to hold all three rigid at once is the one that ends in disputes. A needs to communicate the real hierarchy, not the official one, and commit to it.
Stakeholder B has to accept that not every design decision carries equal weight. Some elements are load-bearing for the project's identity and quality. Others are preferences. Knowing the difference, and saying it out loud, is what separates a consultant who is genuinely collaborative from one who is simply defending the drawings. The ability to distinguish between a design compromise and a design failure is a professional skill.
Stakeholder C has to be transparent earlier. The contractor who surfaces a problem in week two of construction rather than week twelve is protecting everyone. There is a culture in construction where problems get managed quietly until they cannot be, and that culture is expensive. Being the party that raises the uncomfortable issue early is not a weakness. It is what earns trust on future projects.
The Reveal — So, Who Is Who?
You already have an opinion. Each stakeholder above maps to a specific role in the industry. Which of them is the Client / Developer? Which is the Designer / Consultant? Which is the Contractor?
And more interestingly, which stakeholder do you identify with most? Which one do you think causes the most friction when goals are never discussed openly?
We have gone from reinforced concrete to parametric models and AI-generated floor plans. But if you strip away the tools and look at how we actually deliver buildings, are we that much better?
Somewhere in Riga, there is a residential block built in the late 1960s. The design was not chosen, it was assigned from a central catalogue, replicated across hundreds of cities with no regard for place, climate, or the people who would live there. Panels came off a factory line. Approvals were not negotiated, they were decreed. The building went up in days. It was not beautiful, not safe by modern standards, and not built to last. But it met its quota. Seventy years later, I find myself reviewing BIM Execution Plans on a major infrastructure project, coordinating across disciplines, managing version conflicts, waiting on design approvals, and occasionally I wonder: what exactly did we solve?
The post-WWII mass housing era in Europe was harsh in its own way, aesthetically flat, socially coercive, and designed more for quotas than for people. But it had something the modern industry often lacks: a repeatable, predictable delivery machine. That tension between what we have gained and what we have not is what this post is about.
PART I - THE POST-WAR BASELINE: SPEED WITHOUT QUALITY
After 1945, European cities needed housing at a scale and pace that had no precedent. The response across the continent, whether in Western Europe or behind the Iron Curtain, was largely the same: prefabricated panel systems, simplified typologies, standardised components. In France they called it the grands ensembles. In the UK, tower blocks. In the Soviet bloc, the Khrushchyovka. Different politics, same industrial logic.
This was real estate development stripped to its mechanical core. The client, in most cases the state, had one goal: units delivered. Quality was subordinate. Maintenance was deferred. But the production system worked. You could trace a panel from factory to facade in weeks. The feedback loop was short and the variables were few.
The post-war model was not a failure of ambition. It was a success of delivery, with all the consequences that come from building fast and thinking later.
The private market that followed, particularly from the 1980s onwards, brought quality back into the equation. Mixed-use developments, heritage sensitivity, sustainability targets, community consultation. All necessary. But with each layer of legitimate complexity, something else crept in: fragmentation. The developer, the designer, the contractor, the specialist subcontractor, each with their own contract, their own timeline, their own definition of done.
PART II - THE PRODUCTIVITY GAP: CONSTRUCTION VERSUS EVERYONE ELSE
If you work in construction, you have probably felt this comparison before. If you do not, the numbers are worth sitting with.
+10%
Construction productivity growth, 2000–2022
+50%
Total economy productivity growth, same period
+90%
Manufacturing productivity growth, same period
McKinsey has been tracking this since their landmark 2017 report Reinventing Construction: A Route to Higher Productivity, and the picture has not improved. Their 2024 follow-up, Delivering on Construction Productivity, confirms it: over two decades, construction added roughly 10% in economic value added per hour worked. Manufacturing added 90%. The total economy: 50%. These are not minor discrepancies. They represent a structural divergence that has compounded for a generation.
The car you drive today is assembled in a fraction of the time it took to build its equivalent in 1990. It has more features, tighter tolerances, and a longer expected lifespan. Meanwhile, the apartment block going up outside your office is being built by workers on scaffolding with hand tools and paper drawings, or in the better cases, tablets showing IFC models that are perpetually out of date.
Why? The answer is uncomfortable because it is not one thing. McKinsey's 2024 report identifies seven specific blockers. Among the most striking: construction companies historically spend less than 1% of revenue on IT, roughly a third of what is common in automotive and aerospace. According to ING Think's 2022 analysis Lagging Productivity in EU Construction, labour productivity in France and Austria has actually fallen more than 15% since 1995, while Belgium and the Netherlands managed a 20% increase, largely through early investment in digitalisation. The picture across Europe is not uniform, but the average is poor.
Every other major industry found a way to industrialise. Construction keeps reinventing the craft, project by project, site by site.
PART III - MORE TOOLS, MORE BUREAUCRACY?
Here is an uncomfortable question the industry rarely asks itself: when we introduce a new tool or process, does it actually make delivery better, or does it just add another layer of administration?
The honest answer is that the overhead wins more often than most people in the industry would like to admit. BIM was supposed to reduce coordination errors and compress timelines. In many cases it has. But it has also introduced its own overhead, BIM Execution Plans, clash detection workflows, model audit cycles, CDE access protocols. Each of these is defensible in isolation. Together, they can consume more management bandwidth than the paper-based coordination they replaced. The tool arrived. The bureaucracy came with it and stayed.
This is not an argument against new tools. It is an argument for discipline in how they are adopted. A new system earns its place in a workflow only when it demonstrably removes more friction than it creates. That test is rarely applied. The industry tends to adopt tools because a mandate requires it, because a client demands it, or because competitors appear to be using them, not because anyone has measured whether it shortens the delivery cycle or reduces cost. The result is an accumulating stack of platforms, standards, and reporting requirements that each made sense on the day they were introduced and now form a coordination burden of their own.
The discipline required is simple to state and hard to practice: new tools should replace something, not add to something. If a digital process sits on top of an analogue one rather than eliminating it, the net effect is negative. The productivity improvement comes from subtraction as much as from addition.
PART IV - WHAT HAS GENUINELY IMPROVED
The argument is not that nothing changed. It changed significantly. Just not in the dimension that matters most to clients, which is time and cost predictability.
Safety is unrecognisable compared to the post-war era. Environmental performance has advanced enormously. LEED, BREEAM, and Passivhaus certifications represent real engineering progress. The quality of materials, structural modelling, and fire engineering today would be difficult to explain to a 1960s site manager. And BIM, when used properly, gives projects a shared data environment that genuinely reduces coordination errors.
But here is an honest reading: most of these gains are about what we build, not how fast or efficiently we deliver it. Safety improved because regulation forced it. Sustainability improved because policy demanded it. BIM uptake in Europe has been driven significantly by public sector mandates, not by market demand for productivity. The industry rarely self-disrupts. It waits to be pushed.
PART V - THE FUTURE I ACTUALLY BELIEVE IN
Of the trends being discussed, modular construction, digital twins, regulatory reform, BIM mandates, the one that I think will matter most in the next twenty years is AI entering the design and planning layer. McKinsey's The Next Normal in Construction (2020) makes the case that the future of construction will look more like advanced manufacturing. I agree with the direction. But I think the transformation starts earlier in the process than most people assume.
The bottleneck in real estate development is rarely on site. It is in the feasibility stage, the design iteration, the planning submission, the permit cycle. A scheme that takes six months to get through planning and approval, and three months to build is not a construction problem. It is a pre-construction problem. And that is exactly where AI has the strongest near-term case: generative massing, automated compliance checking, drawing production, planning risk analysis.
But AI does not operate in a vacuum. The projects where it will deliver the greatest productivity gains are not bespoke, one-off commissions. They are the ones built on a foundation of standardisation, repeatable components, modular systems, defined typologies. Modular and prefabricated construction provides the stable input conditions that AI tools need to perform: consistent geometry, predictable specifications, reusable design logic. An AI that generates a floor plan for a custom, site-specific building is useful. An AI that optimises a modular housing scheme across fifty sites, with standardised components and a known cost model, is transformative. The two approaches reinforce each other in a way that neither achieves alone.
This is, in a sense, a return to the logic of the post-war era, but with the quality controls, sustainability ambitions, and design flexibility that the Khrushchyovka never had. Modular building today is not what it was in 1955. Volumetric construction can achieve passive-house performance, architectural variation, and structural precision that factory production in the mid-century could not approach. Pair that with AI-driven design optimisation and automated planning analysis, and you have a delivery model that is repeatable without being uniform.
I am not suggesting AI will replace architects or engineers in any meaningful near-term sense. But it will compress the cycle between concept and permitted scheme in ways the industry cannot currently imagine, because that cycle has been assumed to be slow for so long that no one questions it. The same way no one questioned why cars took months to configure and deliver until someone built a direct-to-consumer production line.
The deeper question, one I do not have a satisfying answer to, is whether the industry will adopt these tools on its own terms, or wait again to be compelled. My experience on one of the largest infrastructure projects in the region suggests that even on a project with genuine BIM mandates and sophisticated stakeholders, the gap between tool availability and tool adoption is still measured in years. And when tools do arrive, they often arrive alongside new administrative layers rather than in place of old ones. If that pattern does not break, the technology will arrive and the productivity improvement will not.
The tools are finally arriving. Whether the industry reaches for them, and whether it has the discipline to let them replace something, is a different question entirely.
CLOSING THOUGHT - ONE HUNDRED YEARS, AND THE CONCRETE IS STILL WET
Real estate development has changed enormously in a century. The materials, the modelling, the regulatory framework, the environmental ambition, all of it. But if you measure the industry by the metric that matters to every client who ever commissioned a building, delivered on time, within budget, to the agreed scope, the record is harder to celebrate.
We built faster in the 1950s. We built worse. We build better now. We build slower. And somewhere along the way, we added enough process, software, and reporting to keep entire teams occupied without anything being delivered faster. Somewhere in that exchange is a trade-off the industry has never fully reckoned with. The next chapter, I think, is about closing that gap. Not by going back, but by being honest that a gap exists, and that every new tool we introduce had better be closing it, not widening it.
Further Reading
- McKinsey (2024) - Delivering on Construction Productivity Is No Longer Optional. mckinsey.com
- McKinsey (2017) - Reinventing Construction: A Route to Higher Productivity.
- ING Think (2022) - Lagging Productivity Drives Up Building Costs in EU Countries. think.ing.com
- McKinsey (2020) - The Next Normal in Construction.
- Academic (2021) - Productivity Development in Construction and Human Capital: A Literature Review. arxiv.org/pdf/2104.00129
Questions for You, the Reader
- In your experience, does the productivity gap feel real on the projects you work on, or does the data not match what you see on the ground?
- The post-war model delivered units fast through standardisation. Is there a version of that logic compatible with today's quality and sustainability demands, or are those goals in fundamental tension?
- Every new tool brings its own administrative overhead. In your experience, does the benefit usually outweigh the bureaucracy, or is the overhead the part that sticks?
- Modular and AI-assisted design are often discussed separately. Do you see them as complementary, or do you think one approach can deliver without the other?
- If AI does compress the pre-construction cycle, who captures that value: the developer, the designer, or the client? And does it change who has power in the process?
- Has any project you have been part of genuinely surprised you with how well it was delivered? What made the difference, and was it replicable?