Why Proximity to Projects Isn’t the Same as Value

A building can generate enormous financial value while the people most responsible for producing it remain inside relatively fixed economic structures.

The project succeeds.

The development value rises.

The operator profits.

The asset appreciates.

The city changes around it.

And yet the core project team often leaves with a fee, a salary, or another project.

The disconnect feels strange – because architects naturally assume proximity to important work should correlate with proximity to value. That assumption is worth examining carefully.

The profession confuses importance with position

Architecture requires years of training, legal accountability, technical judgement, and sustained creative effort. But systems do not distribute value according to difficulty, intelligence, responsibility, or cultural contribution. They distribute value according to structure and position.

This is a critical distinction – and one the profession tends to obscure.

Architecture often treats important work and valuable positions as the same thing. They are not. You can occupy an essential role in a system and still sit in a part of that system that doesn’t accumulate much economic upside.

The importance of the contribution does not determine the economics of the position.

Most architects spend years assuming these two things move together. They often don’t.

The closest people to production often have the least leverage

The closer someone sits to delivery – to execution, coordination, direct production – the more tightly their income typically attaches to time and direct involvement.

This isn’t unique to architecture. The same structural pattern appears across construction, film, consulting, manufacturing. The most visible workers are often operating in the least scalable layer of the system.

Not because they lack skill. Because production itself scales badly. This is part of the same time-for-money constraint that shapes much of architectural work. Effort and output can increase without structural position changing at all.

One architect managing a complex project can only manage so many projects. Expertise and proximity to the work don’t remove the ceiling – they just raise the rate at which you’re paid to stay inside it.

Project work is usually compensated transactionally. Position often compounds over time.

Production is paid once. Position continues generating returns after the work is complete.

That distinction is sitting underneath a lot of architectural careers without ever being named clearly.

Architecture trains people to prioritise craft over position

Architectural education overwhelmingly rewards authorship, design ability, technical competence, project ownership, critical thinking, and refinement. These things are taught with extraordinary rigour.

Very little attention is given to systems, ownership, leverage, distribution, licensing, recurring economics, or platform positions.

So architects learn – quite naturally, quite thoroughly – to believe that proximity to the project is proximity to value. The curriculum points in that direction. The culture reinforces it. The awards celebrate it.

What it doesn’t teach is the relationship between the work and the economic layer that surrounds it. That layer is often where the larger outcomes accumulate. But it sits outside the frame that most architectural education constructs.

This means that when architects notice the disconnection between contribution and economic position, they tend to explain it as an anomaly – bad luck, undervaluation, a management failure. Something that more experience or a better firm might fix.

The profession trained them to see the work clearly. It didn’t train them to see the system around the work.

The largest financial outcomes often sit one layer removed

Across many industries, the most significant value capture tends to sit at a remove from direct production.

Not inside the project. One step back from it.

Ownership rather than execution. Distribution rather than production. Systems that operate independently of any single individual’s time and involvement. Intellectual property that generates returns beyond the act of creating it. Assets that are appreciated while the creator isn’t in the room.

This isn’t a principle unique to architecture. It’s a structural feature of how value moves through most industries. Architecture isn’t an exception to this pattern. In many ways, the profession makes the underlying structure unusually visible.

The project fee is a payment for work done. The development gain is a return on position.

The work and the value are not in the same place. Understanding where leverage actually exists in architecture starts with that distinction.

The misunderstanding quietly shapes entire careers

Most architects spend years trying to move closer to projects. Closer to responsibility. Closer to delivery. Closer to the kind of technical complexity that signals seniority and competence.

And that trajectory is rewarding in many genuine ways – it builds skill, reputation, professional credibility. But it is still movement deeper into production rather than closer to leverage.

More responsibility. More complexity. More pressure. But only limited structural change in where you sit relative to how value actually accumulates. This is one of the structural reasons so many architectural careers appear to progress while remaining economically static.

A practice can be fully utilised, generating constant work, and still struggle to compound economically. The same structural logic runs through individual careers inside those practices.

This is the misunderstanding underneath a lot of stalled careers. Not a failure of effort or ability. A misreading of what progress in the right direction actually looks like.

Most architects spend their careers trying to move closer to the work.

Closer to the project.

Closer to responsibility.

Closer to delivery.

But across most industries, proximity to production is not where leverage accumulates.

If value does not primarily sit inside the work itself –

where exactly does it sit?