Episode Details
Back to EpisodesIf the Client Is on Top, the Pyramid Falls.
Description
Scrolling Threads, I came across a post by Mior Aizuddin Fahmi of Bunga Design Atelier, setting out a pyramid he'd been given by Kevin Mark Low: the project at the top, then subcontractor, main contractor, community, requirements and brief, consultants, architect — and the client at the very bottom. Put the client on top, and the whole thing collapses. Commenters pushed back immediately. Isn't the client the paymaster? No client, no project. Mior's answer: yes and no. We're talking about a great project. The client is the foundation that makes it possible — money, ambition, opportunity — but if every decision flows down from one person's preference, the community becomes an afterthought and you get a monument rather than a collective piece of work.
I'd take it a step further. What this really maps is knowledge. The client is the one person on that list who arrives without it — what they have is money, and money isn't everything. So the architect's job is to interpret everyone else's knowledge and educate the client, which is exactly what Kevin Mark Low told me years ago: teach the client, and if they aren't interested, they'll go and find a different architect. The subcontractor holds the craft, the main contractor the management, the community the social meaning, the consultants the technical reasoning. The architect stands beneath all of it and holds it up. And with great money comes great responsibility — the client carries the most of all.
Copyright 2026 Talk Architecture, Author: Naziaty Mohd Yaacob.
Do subscribe for premium content and special features which will help to support and sustain Talk Architecture podcast on a more in-depth explanation on design thesis and processes. These special commentaries and ‘how to’ explanations are valuable insights and knowledge not found elsewhere!