The method

Three rules the whole university runs on

Learn by building

Projects from week one. Every course ends with something you made, whether code, a case, a filing or a model, as well as a grade.

Real problems, real stakes

Briefs come from partner companies and live cases, not textbook exercises. Constraints, deadlines, ambiguity included.

Thinking over recall

You’re assessed on process: how you framed the problem, what you tried, why you chose your trade-offs. Like real work is.

A concrete example

One project, start to finish

A second-semester brief, the way it actually runs. (This one is illustrative; real briefs are set by partner companies each term.)

The brief
A logistics partner needs delivery-route estimates. Messy data and unclear scope, deliberately.
Build & iterate
Teams of four. Weekly reviews with the instructor, a working engineer, who critiques your approach rather than neatness.
Defend it
Present to faculty and the partner. Explain the trade-offs. Field the hard questions.
Portfolio
The project, your reasoning, and the review feedback go into your portfolio. Proof, not claims.

Assessment

What your grade is actually made of

Exams exist, because foundations need testing, but they don’t dominate. The weight sits on what survives contact with reality:

  • Project work: shipped, reviewed and defended.
  • Reasoning: your process, documented decisions and trade-offs.
  • Collaboration: how you work in a team, and how you take and give feedback.

Taught by people who do the work

Practitioner faculty bring this month’s problems into the classroom, and their networks with them. Who teaches you →

AI as a tool, not a threat

You’ll use AI the way professionals do, to build faster and check your thinking. Assessment rewards using it well rather than hiding it.

See it applied

Every program runs on this method

Pick a degree and see how the method shapes its four years.

See programs
FALL 2026 INTAKE · APPLICATION DATES TBCApply