My Approach to Thinking Architecture

 

Architecture as analysis, experience, and decision-making

Architecture is often understood through its visible outcomes: drawings, models, and approved plans. However, architectural thinking begins long before representation. Design is not an act of immediate creation, but the result of analysis, evaluation, and informed decision-making under real constraints.

My approach to thinking architecture is grounded in this reality. Architectural decisions are shaped not only by form and function, but also by cost, time, regulations, and human uncertainty.

Architecture as analysis

Architecture is a discipline of decisions, many of which are irreversible once a project moves forward.

Before any formal solution is proposed, analysis is required. This includes understanding context, use, scale, circulation, and regulatory frameworks, but also financial limitations and approval processes. These factors are not secondary; they define what is feasible and what is not.

In practice, a project may meet all technical and regulatory requirements at a given moment, yet still be affected later by external changes beyond the architect’s control. Shifts in municipal criteria, administrative transitions, or regulatory reinterpretations can alter approval conditions even after a project has been formally delivered.

Architecture must therefore be understood as a process operating within systems, not in isolation.

Cost as a design parameter

Cost is not merely a budgetary issue; it is a design parameter.

Every architectural decision carries economic consequences, from material selection to spatial configuration. When cost is not addressed clearly from the beginning, projects are exposed to delays, revisions, and unrealistic expectations.

From experience, I have found that many design conflicts do not arise from poor design, but from unresolved financial decisions. Architecture requires clarity, not only in drawings, but in agreements and scope.

Indecision and responsibility

Client indecision is a recurring reality in architectural practice.

There are cases where a project reaches completion, approvals are coordinated with local authorities, and formal delivery is made, only for revisions to be requested long after sometimes under new administrative conditions that were not in place during the original process.

When regulatory parameters change due to institutional transitions, such as changes in government or municipal personnel, the architect’s responsibility must be clearly distinguished from circumstances beyond their scope. Architecture operates within frameworks that evolve, and not all outcomes can be retroactively controlled.

This reinforces the importance of decision-making at the right time. Architecture progresses through defined stages, and revisiting completed phases often involves new costs, new approvals, and new conditions.

Experience beyond aesthetics

Architecture is ultimately experienced, not just reviewed on paper.

A project can comply with regulations and still feel unresolved if decisions were postponed or compromised. Spaces reflect the clarity or ambiguity of the process that produced them.

For this reason, I approach architecture as a balance between analysis, experience, and responsibility. Decisions must be timely, justified, and aligned with real conditions, rather than deferred in pursuit of certainty that rarely exists.

The purpose of this approach

This blog is a space for architectural reflection grounded in real constraints.

It examines architecture not as an idealized product, but as a sequence of decisions shaped by users, costs, institutions, and time. By approaching architecture through analysis, experience, and decision-making, design becomes a structured response to reality rather than a purely formal exercise.

Architecture gains value when it acknowledges its limits and works intelligently within them.