
## 1. Get the fundamentals right, early

### Draw before you model

![Draw before you model](/images/Lessons/sketch-like-an-architect/sketch-like-an-architect-hand-sketching.jpg)

Learn to draw by hand first. Don't rush to the computer — hand sketching builds the eye that software can't teach you, and it's the fastest way to test an idea before you've committed hours to a 3D model. A five-minute sketch can kill a bad idea before it costs you an evening; a five-minute idea straight into Rhino usually just gets defended instead of tested. Keep a pencil within reach at your desk, not just in your bag — the ideas worth having tend to turn up mid-thought, not when you've sat down specifically to have one.

### SketchUp and Rhino before Revit

![SketchUp and Rhino before Revit](/images/Lessons/complete-beginner-guide-to-rhino/complete-beginner-guide-to-rhino-hero.webp)

Don't sleep on SketchUp and Rhino. Both are far more intuitive and design-friendly than Revit, brilliant for testing form and massing fast without getting bogged down in documentation logic. [Revit is your end game](/lessons/rhino-3d-course-beginners/) — the tool you'll live in once you're in practice — not something to rush into now. Learning it early doesn't make you a better designer; it just means you spend first year fighting software instead of ideas. There's plenty of time for Revit once you actually have something worth documenting.

### Learn the art of model making

![Learn the art of model making](/images/Lessons/the-guide-to-architectural-model-making/the-guide-to-architectural-model-making-hero.jpg)

[Concept models are so important](/lessons/architectural-model-making-course/) — they show your design process, not just the finished result. A tutor can read a rough study model faster than a rendered image, and it forces decisions a screen lets you dodge, because a chipboard box either stands up or it doesn't. Keep every study model, even the ugly ones. They're evidence of thinking, and a crit that goes well often comes down to being able to show the three failed ideas that led to the one that worked.

### Present to your family first

![Present to your family first](/images/Lessons/the-perfect-presentation/the-perfect-presentation-hero.png)

Practice presenting to your own family before you present to a crit panel. If they can follow your idea without the jargon, your crit audience definitely will. It's the fastest sense-check there is for whether a narrative actually holds together, because family won't nod politely through a weak argument the way a coursemate might. If you catch yourself reaching for architecture-speak to paper over a gap in the logic, that's usually the exact spot your tutor will find it too.

## 2. Build a routine that survives the term

### Treat studio like a 9-to-6

![Treat studio like a 9-to-6](/images/Lessons/architecture-student-guide-vol-1/00_Screenshots/Lesson%208%20-%20The%20Final%20Submission.jpg)

Treat your uni days like a proper working day. Don't fall into the trap of all-nighters — they feel productive, but you don't actually gain anything from working through burnout and low energy. Protect the routine and the work gets better, not worse. The students pulling consistent 9-to-6s tend to out-produce the ones pulling occasional all-nighters, because tired decisions are usually bad decisions, and you end up redoing them anyway. Treat sleep as part of the studio kit, not a luxury you've earned.

### One core task, not ten tabs

![One core task, not ten tabs](/images/toolkit/focus-mode.webp)

Structure your days around a single core task rather than juggling ten things at once. Context-switching is the quiet killer of a design day — pick the one thing that actually needs to move forward, and let everything else wait. Before you sit down, decide what "done" looks like for that one task, and don't let yourself wander into polishing a different part of the project instead. It feels like progress; it's usually just avoidance of the harder decision.

### Keep a sketchbook, day one

![Keep a sketchbook, day one](/images/Lessons/sketch-like-an-architect/sketch-like-an-architect-mid-page.jpg)

Keep a sketchbook from day one, no matter how tatty it gets. Tutors love seeing one that's actually been used — the more weathered, the better. It's proof of thinking, not just a portfolio prop, and it becomes a genuinely useful record once you're three projects deep and can't remember why you made a decision. Don't buy an expensive one you're precious about; the good sketchbooks are the ones that get ruined.

### Back up like your degree depends on it

![Back up like your degree depends on it](/images/toolkit/project-tracker.webp)

Because it does. A dead laptop the week of a crit won't earn you any sympathy from a tutor who's seen it a hundred times before. Get into the habit early — it's one less thing to lose sleep over. Set up automatic cloud backup once, properly, and forget about it; the students who lose work are almost always the ones who meant to back up "later." Later is the week your hard drive decides to die.

## 3. Think like a designer, not just draw

### The narrative is the design

![The narrative is the design](/images/Lessons/architecture-student-guide-vol-1/00_Screenshots/Lesson%202%20-%20Narrative%20and%20Precedents.jpg)

The **why** behind your building, and how every design move ties back to it, is what separates a 2:1 from a first. A scheme with a strong, consistent narrative reads as intentional even when a detail is rough — one without it reads as arbitrary even when the drawings are polished. Test it constantly: for every decision you make, you should be able to say why it exists in one sentence, without shrugging. If you can't, the decision isn't finished yet.

### Site analysis isn't just data

![Site analysis isn't just data](/images/toolkit/site-analysis.webp)

[Learn how site analysis actually applies](https://archademia.com/toolkit/) to a scheme, not just the numbers. Sun paths, wind, topography and context are only useful once they're shaping actual design decisions — the data side is the easy half. A site analysis page full of diagrams that never resurface in the design is wasted work; the good ones show up again in section, in massing, in your narrative. Treat it as research for the building, not a box-ticking exercise before the "real" design starts.

### Study the RIBA President's Medal winners

![Study the RIBA President's Medal winners](/images/picks/20-tips-architecture-school/riba-presidents-medals.png)

Go through past [RIBA President's Medal](https://www.presidentsmedals.com) student winners, project by project. Literally all of the answers to a good scheme live there — precedent, narrative, presentation, the lot. It's some of the best free education you'll get outside your own course, and it's a level up from generic inspiration boards because every project on there has already survived a serious crit. Don't just look at the pictures — read the project statements and work out why the judges picked them.

### Buy one Taschen "Complete Works"

![Buy one Taschen Complete Works](/images/toolkit/moodboard.webp)

Get at least one [Taschen](https://www.taschen.com) "Complete Works of…" book — Tadao Ando, in my case. Nothing teaches you how the greats actually think faster than sitting with an architect's entire body of work in one place, project after project. You start to see the repeated moves, the obsessions, the ideas they kept returning to and refining over decades — the kind of pattern you'd never spot from a single building on a lecture slide.

## 4. Play the game as much as the brief

### Show up to studio, every time

![Show up to studio, every time](/images/Lessons/architecture-student-guide-vol-1/00_Screenshots/Lesson%201%20-%20Introduction%20and%20Initial%20Crit.jpg)

Attend studio as much as you possibly can. It's a political game as much as a design one — visibility earns you brownie points that grades alone won't. Tutors remember who's actually in the room, who asks questions, who's engaged with other people's projects, not just their own. The relationships you build in studio are also the ones that get you references, job leads and studio recommendations later — that starts with just turning up.

### Start your portfolio in year one

![Start your portfolio in year one](/images/Lessons/the-perfect-portfolio/the-perfect-portfolio-hero.jpg)

[Keep track of your portfolio](/lessons/architecture-portfolio-course/) from day one. Don't leave it to the final term, scrambling to reconstruct process shots and reasoning you've half forgotten — log every project as you go, even the ones you think you'll never use. You'll be glad of the option later, and a portfolio built up in layers over years reads very differently from one assembled in a fortnight of panic before graduation.

### Your cohort is your first network

![Your cohort is your first network](/images/community/industry-connections.webp)

The people next to you in studio are your first professional network, not just classmates. You'll lean on each other through crits now, and through practice for years after — architecture is a small industry, and you will keep bumping into the same people for the rest of your career. Be generous with feedback and help now; it's the cheapest goodwill you'll ever build, and it comes back.

### Learn to take a crit on the chin

![Learn to take a crit on the chin](/images/Lessons/architecture-student-guide-vol-1/00_Screenshots/Lesson%206%20-%20Thorough%20Design%20Crit.jpg)

The critique is where the real teaching happens, not the studio desk. Learn to take it on the chin — treat it as data about the work, not a verdict on you. The students who improve fastest are the ones who can hear "this isn't working" without hearing "you're not good enough." Write feedback down in the moment, even the bits that sting; you'll want it later, once the defensiveness has worn off.

## 5. Make the final presentation count

### Push the medium of your final crit

![Push the medium of your final crit](/images/Lessons/the-perfect-presentation/00_Screenshots/Lesson%209%20-%20Creating%20Professional%20Presentation%20Boards.jpg)

Play with the medium of your [final presentations](/lessons/the-perfect-presentation/). Projectors, screens, work hanging from the ceiling, print on acrylic or fabric, framed boards — whatever fits the story. See what you can pull off, then build from there. A final crit is one of the only times you'll have full control of the room — use it. The medium should say something about the project, not just display it.

### Photograph your process as you go

![Photograph your process as you go](/images/Lessons/the-guide-to-architectural-model-making/00_Screenshots/Lesson%207%20-%20Farnsworth%20House%20Model%20-%20Part%201.jpg)

Photograph your models and drawings as you make them, not just at the end. You'll want progress shots for your portfolio later, and you won't remember to recreate them once the project's done. It takes thirty seconds and a phone camera; the alternative is trying to fake "process" shots after submission with a half-hearted rebuild, which never looks convincing.

### Start making before the idea feels ready

![Start making before the idea feels ready](/images/Lessons/the-guide-to-architectural-model-making/the-guide-to-architectural-model-making-mid-page.jpg)

Don't wait for "the good idea" before you start modelling or drawing. Most good ideas are found through making, not before you pick up a pen or a scalpel. Waiting for clarity before you start is usually just procrastination wearing a design-process costume. Make something rough, react to it, and let the next decision come from what's actually in front of you rather than what's still in your head.

### Read outside architecture too

![Read outside architecture too](/images/Lessons/the-perfect-presentation/00_Screenshots/Lesson%207%20-%20Colour,%20Texture,%20and%20Visual%20Style.jpg)

Read outside architecture — art, film, product design, nature. Precedent isn't only buildings, and pulling from further afield is usually what makes a narrative feel genuinely yours rather than borrowed. The students whose work stands out in crit are rarely the ones referencing the same six famous buildings everyone else is — they're the ones who noticed something nobody else was looking at.


https://pub-a37e1d10eac04e559906b2a193dd1126.r2.dev/Architecture_School_Success_Without_All-Nighters.m4a

Watch a full architecture student project built from narrative to final submission, session by session — the kind of one-to-one mentoring that rarely makes it past studio walls. Plus the full course library, the toolkit, and a community of architects further down the road than you.

Want a mentor walking you through all of this, live?

Twenty things I wish someone had told me on day one of architecture school — software order, studio politics, and the habits that actually last.

Audio companion

ArchAdemia Support

Audio companion

ArchAdemia Support

Welcome back!