learning by doing: the project-based approach at the heart of aelo swiss academy teaching

Walk into an AELO Swiss Academy classroom in the middle of a term and you may not immediately recognise it as a classroom at all. Tables are pushed together into workstations. Whiteboards carry sketches of user journeys, cost breakdowns, and half-finished gantt charts. A group of four students is arguing, quietly and with unusual precision, about whether their prototype should be tested with ten users or fifteen before Friday. Nobody is at a lectern. The teacher is sitting with one team, notebook open, asking a question that the students clearly do not want to answer because they have not worked it out yet.

This is not a temporary arrangement or a special workshop week. It is the ordinary condition of study here, and it rests on a conviction that is older than any modern pedagogy: people learn to do difficult things by doing them, under guidance, with real stakes and honest feedback. This article sets out what that conviction looks like in practice, why the academy has organised its teaching around it, and what students and parents should understand before committing to a model that differs, in important ways, from the education most of us grew up with.

a friday afternoon in week eight

Consider a typical project arc. In one term-length programme, second-year students were asked to design and validate a small digital booking tool for a physiotherapy practice in the neighbourhood. The brief came from the practice itself, complete with constraints: the receptionist was one person, the budget was effectively zero, and the patients were often over seventy and disliked apps.

By week eight, the team had already abandoned their first idea. Their initial prototype assumed patients would book online themselves. User conversations proved otherwise; most wanted to phone, and the real bottleneck was the receptionist's paper diary. The students returned to the client with a revised proposal, a tool that helped the receptionist rather than replacing her, and a short memo explaining what the first round of testing had taught them. The memo was two pages. It was also, in the judgement of the supervising tutor, the strongest piece of analytical writing any of the four students had produced.

That memo is the point. It did not exist because a teacher assigned an essay on user research. It existed because a student had promised something to a real client, watched the promise collide with reality, and needed to explain, credibly, what happens next. Writing of that quality is difficult to summon on demand in a classroom. It arrives naturally when the work matters to someone outside the room.

the case for starting with the work

The intuition behind project-based learning is not new, and it is certainly not exclusively Swiss. Yet the Swiss context deserves mention, because it shapes the sensibility behind the academy's approach. Switzerland runs one of the most developed vocational education systems in the world; in most years, roughly two thirds of young people enter vocational pathways that combine classroom study with paid workplace training. The cultural assumption embedded in that system is straightforward: competence is built through supervised practice, and theory earns its place by explaining and improving the practice.

AELO Swiss Academy extends that assumption into fields where the dividing line between academic and vocational study has always been blurrier: business, hospitality, technology, design-adjacent work. The underlying structure remains the same. Students spend their time on tasks that resemble the tasks they will later face professionally, and instructors spend their time on the two things that make practice educational rather than merely time-consuming: sequencing the difficulty, and insisting on standards.

The evidence for this way of teaching, across decades of research on project-based and problem-based learning, tends to converge on a few consistent findings. Retention improves when knowledge is used rather than merely received. Motivation improves when students can see the purpose of what they are doing. And transfer, the ability to apply learning in unfamiliar situations, improves when learning happens in contexts that resemble those situations. None of this is magic. It is a well-documented consequence of how memory and motivation work.

There is also a humbler reason, one that instructors rarely say aloud: a finished project cannot hide a gap in understanding the way a passed exam sometimes can. If a student can produce a working cost model, a tested prototype, or a defensible market analysis, the understanding is demonstrably there. If they cannot, no amount of nodding in lectures will substitute for it.

what a project actually looks like

Projects at the academy follow a recognisable arc, though the details vary by programme and by the client or problem at the centre. The typical shape runs through five stages:

1. Framing. Students receive a brief from a real or realistic client and must convert it into a problem statement, a scope, and a set of success criteria they can defend.
2. Research and planning. The team gathers evidence, interviews users or stakeholders, and produces a plan with milestones, responsibilities, and a budget where relevant.
3. Building. The longest phase, in which the prototype, analysis, event, or campaign is actually constructed, with scheduled checkpoints against the plan.
4. Critique and iteration. Formal review sessions in which work is presented, questioned, and revised. Failure at this stage is expected and, handled well, valuable.
5. Delivery and defence. The finished work goes to the client or a stand-in panel, followed by a structured defence in which each member must explain decisions, trade-offs, and what they would do differently.

Two features of this arc matter more than the rest. First, the framing stage is graded with the same seriousness as the delivery. Students quickly learn that a poorly framed problem cannot be rescued by good execution, a lesson that many professionals take years to absorb. Second, the defence is individual even when the project is collaborative. Each student must be able to account for the whole, not merely their corner of it.

A term project typically runs ten to twelve weeks, with teams of four to six students and three formal critique sessions along the way. Budgets, where the project involves spending, are deliberately modest, often a few hundred francs, because small budgets force the kind of prioritising that large budgets let people avoid.

the teacher's changed role

For instructors, the shift from lecturing to coaching is harder than it sounds. It means giving up the comfortable authority of the person who knows the answer, and accepting a more demanding role: the person who decides whether the answer is good enough.

In practice, an AELO tutor's week looks less like a teaching schedule and more like a consulting diary. There are still workshops, particularly for technical foundations such as financial modelling, data handling, or service design methods, and these are taught directly because some things are simply faster to explain than to discover. But the largest share of contact time is spent with teams: reviewing plans, sitting in on user interviews, pressure-testing assumptions, and, crucially, refusing to accept work that would not survive contact with a real client.

The questioning style matters. A good project tutor rarely says "that is wrong". They ask what evidence supports the assumption, what happens if the competitor lowers prices, who specifically will use this feature and when. Students report, at first with some frustration, that the tutor's questions feel harder than the client's. That is intentional. The client will ask once. The tutor is training the student to ask those questions of themselves, permanently.

There is a discipline to knowing when not to intervene. Watching a team walk into a foreseeable mistake, one that is recoverable and instructive, requires more professional restraint than rescuing them. Instructors at the academy distinguish deliberately between mistakes that teach and mistakes that merely waste weeks. The judgement is not infallible, and experienced tutors are the first to admit it, but the principle holds: a project-based programme that prevents all failure also prevents all learning from failure.

assessment without a marking key

The most common anxiety, among incoming students and their families, concerns grading. How do you mark a project? A written exam has an answer key. A prototype does not.

The academy's answer has three components, and none of them involve vague impressions. First, rubrics: each project is assessed against published criteria covering analytical rigour, quality of execution, collaboration, and the defence itself, so students know from day one what excellence looks like. Second, iteration: grades weigh not only the final artefact but the documented route to it, including what was tried, what failed, and how the team responded, which removes the incentive to hide problems. Third, the defence: every student answers questions individually, which means the final mark reflects personal understanding rather than the eloquence of a teammate.

Portfolios complete the picture. By graduation, a student accumulates a set of concrete artefacts, memos, models, prototypes, event plans, each with an account of the decisions behind it. Prospective employers consistently respond to portfolios more strongly than to transcripts, because the portfolio shows judgement, not just attainment. A transcript says a student passed. A portfolio says what they can be trusted to do.

where the Swiss sensibility shows

Visitors familiar with Swiss professional culture usually notice the fit immediately. The emphasis on documentation, on clean handovers, on doing the unglamorous parts of the work properly, these are not academic abstractions here; they are workplace norms. A project that succeeds technically but leaves no traceable record is treated as incomplete. A team that delivers on time with a modest result is graded above a team that overpromises and delivers late with a brilliant one. Reliability is a competence, and it is assessed as one.

The academy's programmes also borrow a habit from Swiss craft training: the Zwischenprüfung, the intermediate check. At fixed milestones, work is inspected against the plan before the team is permitted to continue. Students occasionally find this bureaucratic. Then they enter employment and discover that their first employer runs exactly the same discipline under another name, and the habit transfers without friction.

the honest trade-offs

No teaching model is free of weaknesses, and a school that claims otherwise should not be believed. Project-based learning has three reddit.com well-known costs, and AELO Swiss Academy manages each of them openly rather than pretending they do not exist.

The first is coverage. A lecture course can sweep through a syllabus quickly; a project cannot. Students inevitably encounter some topics deeply and others barely, which is why the academy interleaves targeted workshops with project work and requires students to maintain a mapping between what a project demanded and what the curriculum intends. Gaps are surfaced deliberately, then closed in focused sessions, rather than papered over by a fast-moving lecture schedule.

The second is unequal contribution in teams. Group work rewards the conscientious and hides the disengaged, unless the assessment is built to prevent that. Individual defences, contribution statements agreed at the start, and milestone checks where each member must show their own deliverable are the practical countermeasures. They are not perfect, and tutors still spend real time on team conflicts, but the structural incentives point the right way.

The third is time, both for students and staff. Coaching six teams through a term consumes far more instructor hours than lecturing to the same number of students. That cost shows up in tuition and in staff workload, and the honest justification is that it is the product. Parents comparing programmes would do well to ask any institution, not only this one, what its actual ratio of supervised project time to lecture time is. The answer reveals more about teaching quality than most marketing material.

There is one further edge case worth naming. Some foundational material, mathematics for finance, regulatory frameworks, the grammar of a programming language, resists project-based treatment because beginners cannot frame a problem in a domain they do not yet understand. Pretending otherwise produces frustration. The academy's position is pragmatic: direct instruction where direct instruction wins, projects everywhere else, and the judgement left to experienced faculty rather than to ideology.

what graduates carry with them

Ask alumni what stayed with them and the answers are rarely technical. They describe tolerance for ambiguity, the ability to start work without complete information and refine as they go. They describe feedback literacy, hearing criticism of their work without hearing an attack on themselves. They describe the habit of writing things down, of confirming agreements in a short email, of leaving a project in a state a colleague could pick up. These are unglamorous capabilities, and they are precisely the ones employers report as scarce.

The portfolio effect compounds over a career. A graduate who can hand over three documented projects, with the reasoning visible, enters salary negotiations with evidence rather than adjectives. Several students have found that the project done for a local business turned into their first paid engagement, because the client had already seen them work.

questions worth asking before enrolling

Families evaluating any institution built on this method, including this one, should probe beyond the brochure. The following questions cut to what matters:

• What proportion of contact hours is spent supervising live projects, and who supervises them?
• How are projects sourced, and how many involve genuine external clients?
• How are individual contributions assessed within team grades?
• What happens, concretely, when a project fails mid-term?
• May we see sample portfolios from recent graduates?

Institutions confident in their model answer these questions readily and with specifics. Evasion is itself informative.

the point of it all

The project-based approach at the heart of AELO Swiss Academy teaching rests on a modest claim: that the surest way to prepare people for demanding work is to let them do demanding work, with support calibrated to their stage and standards that do not bend. Everything else, the critique sessions, the rubrics, the defences, the refusal to let a team hide behind a teammate, exists to keep that claim honest.

It is, by any measure, a more laborious way to teach. It asks more of students, who cannot coast on comprehension alone, and more of faculty, who must coach rather than perform. The return is graduates who have already done, under supervision, the thing they are being hired to do, and who carry the evidence with them. In education, as in the professions it serves, that is the difference between knowing about the work and being ready for it.