TALAMANA · THE AI LITERACY MAP FOR ARCHITECTURE AND DESIGN · Studio Practice · AGE 19—22 · POSITIONAL · HELD
AI across the project arc
AI goes where the nights are lost, never where the design is decided.
Our position
AI fits differently at each stage — research, brief, massing, iteration, drawings, communication — and one rule decides where it goes. The real risk is not being replaced by the machine. It is working with one that nobody is directing. Direct it like a brilliant, tireless junior: fast, visually impressive, and with no regard for structure, budget or human use unless you supply them. This is a friction map, not a tool list.
> Reduce friction, not judgment.
Why we hold it
Because the failures we see in studios are failures of direction, not of tools: a stunning render of a scheme nobody decided, a research dossier nobody verified, an option set nobody curated. A friction map puts the tool where the nights are lost and keeps it out of where the design is decided.
The strongest objection
Friction is sometimes the safety mechanism. Checking a dimension twice, reading a clause slowly, drawing the section by hand, reconciling two schedules that should agree: these feel like friction precisely because they force the mind through the work, and that forcing is where errors get caught and understanding gets made. "AI wherever it reduces friction" risks automating away the process that creates the judgment the map says it protects. The line between friction and judgment is not fixed, and from the inside it may not be findable: what feels like friction to a student — the hand section — may be the judgment being formed. A small study of thirty-six architecture students found generative AI helped novices in conceptual design and gave experienced designers no measurable gain; it is too small to make a law of, but it points the same way — where AI helps depends on who is sitting there, and a map drawn for a studio may be wrong for the people in it.
What would make us revise it
If the tools begin carrying design decisions end to end — brief to scheme — with results clients and juries accept, "reduce friction, not judgment" stops describing a boundary and starts describing a preference. If studies keep finding the benefit lives entirely with novices, the map becomes a map of expertise rather than of project stages, and we redraw it. And if we find, in our own workshops, that the steps we mapped as friction were the steps where the checking happened, the map gets a third mark beside yes and no: friction that is doing a job. Reviewed every edition.
Try it
Draw your project's arc, stage by stage. Place each AI use you actually made on it. Mark each: friction reduced, or judgment replaced? Then name one stage where you keep AI out on purpose.
Take it to crit
Can the student say where in their project AI works for them, and where it would replace the very part that is the point?
What this idea builds on
What this idea opens up
Sources
- reduce friction, not judgment
- Jiang, Xiao, Hurley & Liu, 2026 (arXiv:2601.10696)
- The AI Design Director Protocol — the-ai-design-director-protocol
Open this idea on the map · The complete map · Logika · RBDS AI Lab, India · revised every edition.