One of the architects I caught up with recently said something that really resonated with me:
"You can see the what, but not the why."
That line describes one of architecture's quieter problems. The drawings survive, but often the reasoning behind them slowly disappears over time.
- Why was this detail chosen?
- Why did the design change?
- What concern did the engineer raise in a meeting six months ago?
- What happened in the conversation that never made it into the minutes?
An industry that still runs on oral history
So much of architecture still relies on oral history — sitting beside the right person, overhearing conversations, asking questions. Some of the most valuable learning I ever had came from senior architects sketching over tracing paper and talking through how they were thinking in real time.
Not polished presentations or formal training. Just conversations, judgement and experience.
Very little of that ever got captured in a way that others could meaningfully learn from later. And I think it's fair to say the industry has accepted that as normal for far too long.
It's the problem we're building lintil to solve — keeping the why alongside the what, so the reasoning behind a project doesn't fade with time. Register your interest →