Graphic Design for Architecture with Adam Tarasewicz

Graphic design for architecture is not just about making things look polished. It is about helping people understand the idea, the place, the sequence and the value of the work.

In this Architecture Social conversation, Adam Tarasewicz talks about the overlap between architecture, web design, graphic design and storytelling. The lesson for candidates and practices is clear: presentation is part of the project, not the last-minute wrapper around it.

Watch: graphic design and architecture storytelling

Adam Tarasewicz’s conversation is useful for anyone trying to make architectural work clearer, sharper and easier to understand online.

Listen: web and graphic design for architecture

Prefer audio? The episode gives the longer conversation on graphic design, web design, creative coding and how architects can communicate work better.

You can also open the related Architecture Social podcast page.

Why graphic design matters in architecture

Architecture is full of complex information: drawings, diagrams, context, constraints, atmosphere, process and technical decisions. Graphic design gives that information hierarchy.

Without hierarchy, good work can feel confusing. With it, the reader can see the argument quickly and then choose where to go deeper.

What candidates can learn from this

• A portfolio page should have one main idea, not five competing messages.
• Typography and spacing affect whether the reader trusts the work.
• Captions should explain evidence, not repeat what is already obvious.
• A website or PDF should guide the reader through the story in the right order.
• Graphic clarity can make technical or conceptual work easier to assess.

What practices can learn from it

For practices, graphic design shapes how clients, collaborators and candidates understand the studio. A weak website can make strong work feel vague. A clear one helps people grasp the practice’s sectors, values, process and personality.

That matters commercially. People are more likely to trust a practice when the story of the work is easy to follow.

Common mistakes

• Treating graphic design as decoration rather than communication.
• Using too many type sizes, colours or diagram styles on one page.
• Letting a beautiful image hide what the project actually does.
• Forgetting that the first reader may only skim for thirty seconds.
• Making the website or portfolio harder to navigate than the project itself.

Architecture Social view

Stephen’s recruiter view is that presentation does not replace substance, but it does decide whether people understand the substance quickly enough. In a busy hiring process, that matters.

Next step

Pick one project and rewrite the page around one clear question: what should the reader understand in the first thirty seconds? Then let the drawings, captions and layout support that answer.