The tech industry discovered systems thinking in the 1990s and has been congratulating itself ever since. Before that, management theorists claimed it. Before them, urban planners. Before them, ecologists. Everyone, it seems, believes they invented the idea that complex things are made of interconnected parts and that changing one part changes all the others.
They are all wrong. Architecture did it first. And architecture did it not as a theoretical framework but as a practice — a daily discipline of resolving competing forces into something that had to stand up, shelter people, and last.
I trained as an architect at EPAU Algiers. What the training gave me — and what I use every day in building companies — is not a design vocabulary or a formal repertoire. It is a mode of attention: the habit of looking at a system and asking how all its forces resolve, what is load-bearing, and what fails if you remove the wrong thing.
"Before software, before management theory — there was the architect staring at a site and asking: how do all the forces here resolve into something that lasts?"— N. Bouteraa
What architectural training actually teaches
A building is a system of forces in equilibrium. Gravity pushes down; the structure pushes back. Wind loads act laterally; the shear walls resist. The occupants need light, air, circulation, privacy, community — all of which make competing demands on the same geometry. The site has constraints: a north face that cannot receive sun, a neighbour who must not be overshadowed, a street whose scale must be respected. The budget has constraints. The programme has requirements. The client has preferences. The code has rules.
Architecture is the practice of finding a configuration that satisfies all of these simultaneously. Not sequentially — simultaneously. Because you cannot design the structure without designing the plan, and you cannot design the plan without understanding the section, and you cannot understand the section without knowing how the light will fall, and knowing how the light will fall requires understanding the orientation, which is a constraint from the site, which is where you started.
This is systems thinking. It has been systems thinking since Vitruvius wrote about it in the first century BC. The software industry did not invent it. They wrote new vocabulary for it.
The three architectural instincts I use every day
When I build companies, three things I learned in architecture school turn out to be essential in ways I did not expect.
The first is the load-bearing distinction. In a structure, most elements are finishes — they contribute to experience but are not structural. Remove them and the building is ugly but standing. A small number of elements are load-bearing: remove them and the building falls. The most important skill in architecture is knowing which is which. The most important skill in building companies is the same. Most decisions are cosmetic. A few are structural. Architectural training builds the instinct to tell them apart.
The second is iteration on constraint. Architecture school teaches you to work with constraints, not against them. A tight site is not an obstacle — it is the generator of form. A limited budget is not a problem — it is a design brief. Every constraint, properly understood, is a force that can be resolved into a better solution. This is the opposite of the instinct to wish constraints away. It is why I look at Algeria's regulatory environment, its informal market conventions, its capital limitations, and see design problems rather than excuses.
The third is the long time horizon. Buildings are designed to last decades. The decisions made at the beginning — the structural grid, the orientation, the material palette — will constrain everything that comes after. Architectural training instills a deep respect for foundational decisions and a consequent caution about changing them lightly. This is why FnarGroup is built as an ecosystem, not a series of independent products. The structural decisions were made for the long time horizon.
ARIIS — the Architecture and Real Estate Intelligence Summit — exists partly because of this conviction. The built environment is the most complex system most societies produce, and yet the people who govern it rarely think of it as a system at all. The summit is designed to change that: to bring together all the actors in the system and force a conversation about how the forces resolve.
The proof
Here is the proof that architecture is the first systems thinking: a well-designed building, built five centuries ago with no simulation software and no management framework, still stands. It has been repaired, adapted, and extended — but the structural logic has not failed. The forces were correctly understood at the moment of design. The system was correctly specified before the first stone was laid.
No software system built in the last fifty years has achieved this. Most are unrecognisable within a decade. Many are unusable within two. The buildings at EPAU where I trained were built in the 1970s and are still educating architects. The buildings they replaced were built in the 1840s and are still standing.
This is not nostalgia for stone and mortar. It is a claim about what good systems thinking actually produces: things that last because their structural logic is right. That is the standard I apply to every company I build. The software is the finish. The structural logic is the thing.