EDITORIAL JOURNAL / VOL. II / 2025
CHAPTER / 01• 2025•Conceptual demos

BRÜNN STUDIO

Architecture studio

"A conceptual demo that reimagines how an architecture studio communicates its criteria, methodology, and processes."

BRÜNN STUDIO
Conceptual demos
01
FIG 01. Structural representation of the solution© Gonzalo Daniel Vega
01 / CONTEXT

The starting point of the challenge

I developed BRÜNN STUDIO as a conceptual demo for UXnicorp. The idea wasn't to make another "pretty" architecture website — it was to research the industry and understand how to present a studio in a clearer, more useful, and more distinctive way. I wanted to build something that conveyed criteria, not just aesthetics.
02 / RESEARCH

Digging beneath the surface: What did I investigate?

I analyzed numerous architecture studio websites and many shared the same problem: they looked good but explained very little. I found:

  • Huge galleries with no context.
  • Confusing navigation.
  • Portfolios that looked like photography studios.
  • An excess of aesthetics.
  • Very little clarity.
  • Overly generic contact forms.
  • Sites that were visually attractive but difficult to understand from a UX standpoint.

I also noticed something important: many websites showcased projects, but didn't help anyone understand how the studio actually worked. It wasn't clear what approach they had, what type of projects they did, what the process was like, or even whether they were the right studio for that particular client.

INSIGHT REVEALED
THE SYNTHESIS

"The problem wasn't just visual. Most studios already had "beautiful" websites. The problem was they weren't conveying criteria. They showed results without explaining decisions. It felt like someone could visit, see some nice images, and leave without truly understanding what the studio did or whether it was what they needed. So I decided to focus on clarity, context, and methodology — not just aesthetics."

Understanding this pillar completely transformed the tactical direction of the project, allowing unnecessary noise to be filtered out and focusing on strict value.

03 / TACTICS

Tradeoff Analysis: options on the table

Building custom software requires honestly evaluating scenarios. No architecture is perfect — every decision has a price:

OPTION 1
Traditional visual gallery

Visually attractive, but poorly differentiated and with little context about the studio.

OPTION 2
Highly experimental layouts

Greater visual impact, but worse clarity and navigation.

OPTION 3
Prioritize explanation and structure

Less immediate spectacle, but far better real understanding of the studio.

OPTION 4
Pack the site with animations and effects

More eye-catching, but worse performance and more distraction.

04 / DETERMINATION

The Decision: The path chosen

I designed an experience that tries to explain how the studio thinks, not just show finished work. That's why I structured the site around philosophy, methodology, process, project criteria, and the context of each project. The projects aren't presented just as images — they're presented as explained architectural decisions. I also avoided overloading the site with unnecessary animations or experimental elements. The idea was for the project to breathe, feel clear, and make it easy to quickly understand whether the studio was the right fit for the visitor. Even the contact form was designed through that lens, since an architectural consultation needs more context than just "name, email, and message."

WHAT ACTUALLY WORKED

The project managed to convey a much clearer identity than many of the references I had analyzed. The combination of structure, content, whitespace, typography, and contextual explanation helped the site feel more human and understandable, without losing its contemporary and elegant focus. The balance between aesthetics and performance also worked well: I aimed to maintain an attractive visual experience without relying on heavy animations or unnecessary resources.

LIMITATIONS & TRADE-OFFS

The gallery prioritizes visual experience and narrative over advanced exploration. That helped keep the experience cleaner and more editorial, but sacrificed things like filters, deeper categorization, direct navigation between project types, and individual pages optimized for SEO. I also chose not to experiment too much outside the gallery. I preferred to maintain clarity and consistency over adding unnecessary visual complexity. Additionally, as a conceptual demo, many decisions were born from research and criteria, but haven't yet been validated with real users or usage metrics.

FROM GONZALO'S PERSONAL LOGBOOK: WHAT WOULD I DO DIFFERENTLY TODAY?

"I would better separate each project into individual pages to improve exploration, scalability, and SEO. I would also rethink part of the gallery to maintain the visual experience while making it easier to find specific projects. And I would probably go even deeper into the process and decision-making sections, because that's exactly what ended up most differentiating this project."

Retrospective note after launch
Gonzalo Daniel Vega — 2025 — SFV Catamarca, Catamarca