Back to Blog
Feature-TriggerJanuary 26, 20264 min read

One Board, 20 References: How Architects Actually Think

Architecture isn't linear. Your brain holds site photos, precedents, sketches, and constraints simultaneously. Finally, there's a tool that works like you think.

Right now, in your head, you're holding:

  • The site photo showing the morning light
  • That stair detail from the project you visited in Barcelona
  • The client's comment about wanting "cozy but not dark"
  • The structural grid your engineer sent yesterday
  • The Pinterest image the client keeps referencing
  • Your sketch from the coffee shop
  • The budget ceiling you keep bumping into
  • All of it. Simultaneously. Interconnected.

    This is how architects think. Not in lists. Not in sequences. In webs of related information, all present at once.

    So why do your tools force you into files and folders?

    The Mismatch Between Mind and Tool

    Your brain works spatially. Ideas sit near related ideas. Connections form organically. Everything is accessible.

    Your computer works hierarchically. Files in folders. Documents opened one at a time. Connections maintained only in your memory.

    Every time you switch between a reference image and your drawing, you break flow. Every time you hunt for that photo you saved somewhere, you lose momentum. Every time you try to see everything at once and can't, your thinking is constrained by your tools.

    What If Your Tools Matched Your Thinking?

    Picture a single canvas with everything on it:

    The site analysis corner:

    Site photos. Sun diagrams. The neighbor's ugly wall you're trying to screen.

    The precedent collection:

    Projects that inspire this one. Details worth referencing. Materiality ideas.

    The design zone:

    Your current floor plan. Sketches. Options you're considering.

    The constraints section:

    Structural grid. Budget breakdown. Client requirements.

    The client vision:

    Their Pinterest board. Photos of spaces they love. Their written brief.

    All visible. All one zoom-out away. All connected.

    This is what architecture thinking looks like when externalized properly.

    The 20-Reference Test

    Try this exercise:

    Open a current project. List every piece of information currently influencing your design:

    1. Site dimensions

    2. Site photos

    3. Zoning constraints

    4. Client program

    5. Client inspiration images

    6. Your sketches

    7. Reference projects

    8. Material ideas

    9. Structural requirements

    10. Budget constraints

    11. Code requirements

    12. Consultant input

    13. Previous versions

    14. Client feedback

    15. ...

    Most architects hit 15-25 items easily.

    Now: how many of those are currently visible on your screen?

    Probably one. Maybe two.

    The rest are in your head, in other files, in emails, in memory.

    Externalizing the Web

    When you put all 20 references on a single canvas, something shifts.

    You stop trying to remember. The information is there. You see it.

    You see connections you missed. That site photo and that precedent detail suddenly relate. You notice because they're both visible.

    You think faster. No file switching. No memory strain. Just thinking.

    You communicate better. When the client asks "why this approach?", you can show them—the precedents, the constraints, the evolution.

    Building Your First Reference Board

    Start small:

    1. Open Spreadboard

    2. Create a project canvas

    3. Spend 30 minutes dropping in everything relevant:

    - Site photos and drawings

    - Client requirements and inspiration

    - Your sketches and options

    - Reference projects and details

    - Constraints and consultant input

    Don't organize perfectly. Just get it on the canvas.

    Now zoom out. Look at everything.

    Feel the difference? You're seeing your project the way your brain wants to think about it.

    The Surprising Benefit: Better Client Conversations

    When clients see your reference board, they understand your process.

    "Oh, this is why you showed us that building."

    "I see how our inspiration connects to what you're proposing."

    "Now I understand why you keep mentioning the site constraint."

    Your design decisions stop being mysterious. The reasoning is visible.

    Clients trust the process because they can see the process.

    The Working Board vs. The Presentation

    Your reference board isn't your client presentation. It's messier. It has dead ends and abandoned ideas.

    That's fine. You might create a curated version for presentations. But your working board—with all 20 references visible, connected, and active—that's where the actual thinking happens.

    Some architects keep both:

  • A working board that evolves with the project (messy, complete)
  • A presentation view that's curated for client understanding (clean, focused)
  • Same canvas, different zoom levels and visibility.

    The Mind Finally Externalized

    Architecture has always been about holding complexity. Balancing constraints. Seeing relationships.

    Your mind does this naturally. Your tools usually don't.

    An infinite canvas with all your references, finally, matches how you actually think.

    Try it with your current project. Put everything on one board.

    Feel your brain relax. You're not trying to remember anymore.

    You're just thinking.


    Finally, a tool that thinks like you do.

    [Try Spreadboard free](https://app.spreadboard.in/login) — one board for everything your brain is holding.

    Ready to transform your architecture presentations?

    Try Spreadboard free and create your first interactive client presentation in minutes.

    Get Started Free

    Topics

    architect thinking processarchitecture design referencesvisual design thinkingarchitect workflow canvas

    Related Articles