beyond exams: project-based learning in academic programs at aelo swiss academy

On a Thursday evening last January, the largest seminar room on our campus bore little resemblance to an examination hall. Sixteen students, arranged in four teams, took turns presenting a market-entry analysis to a panel made up of two faculty members and an invited practitioner from the logistics sector. There were no sealed question booklets and no ticking clocks. Each team had roughly twenty minutes to defend a recommendation it had spent the better part of a term building, and the questions from the panel were the kind that no amount of memorisation could fully answer. Why this market and not the neighbouring one. What would you do with half the budget. Which of your assumptions worries you most.

Scenes of this kind recur every term at AELO Swiss Academy, and they are not enrichment activities bolted onto a conventional syllabus. Project-based learning is a structural feature of the academic programs here, woven into how modules are sequenced, how contact hours are used, and how grades are assembled. This article explains what that looks like in practice, where the model demands care, and why we have kept written examinations alongside it rather than discarding them.

what a written paper cannot reach

A well-constructed examination remains one of G1000 training the most efficient instruments in education. It is standardised, comparable across cohorts, difficult to outsource, and reasonably good at verifying whether a student has command of foundational material. Research on retrieval practice also supports the plain observation that preparing for and sitting an examination strengthens memory of the tested content.

The limitation is not that examinations do these things badly. It is that they measure a narrow slice of what graduates will eventually be asked to do. Professional work rarely arrives as a well-defined problem to be solved alone in ninety minutes without sources. It arrives as ambiguity: an unclear brief, incomplete data, competing stakeholders, a deadline, and colleagues whose schedules do not align with yours. A student can score highly on every written paper in a program and still be unprepared for the first genuinely open task placed on a desk in an office, a laboratory, or a client meeting.

Project-based learning exists to close that gap, and closing it requires more than adding a group assignment to the final month of a course. It requires that the project be treated as primary rather than decorative, with its own architecture, its own assessment discipline, and its own honest account of failure modes.

how projects anchor the term

In most academic programs at AELO Swiss Academy, each term contains one extended project, typically running between six and ten weeks, undertaken in teams of three to five students. Faculty members write the brief, but the brief is tied deliberately to the learning outcomes of the module, and wherever possible it is drawn from a real organisational context, such as a partner company or a public institution, with confidentiality respected where it matters.

The cycle through which a project moves is broadly consistent across programs:

1. Scoping. Teams translate the brief into a researchable question, agree on deliverables and internal deadlines, and submit a one-page plan that the supervisor must approve before work begins.
2. Inquiry. The team gathers evidence through fieldwork, interviews, data collection, literature review, or early prototypes, depending on the discipline.
3. Midterm critique. A structured review with the supervisor and a peer team, at which the approach is challenged and the scope may be revised.
4. Consolidation. The deliverable is completed, rehearsed, and accompanied by a contribution log recording who did what.
5. Defense. A public presentation to a panel, followed by individual questioning and a short written reflection submitted afterwards.

The shape of the work varies by field. A module in data methods might culminate in an analytical report and a working dashboard. A management module might produce a feasibility study or an operations plan. Design-oriented modules tend to end with a prototype and a documented rationale for the choices behind it. What does not vary is the expectation that students justify their decisions in front of people who are entitled to disagree with them.

The January panel mentioned above illustrates the point. The brief had come from a regional logistics firm wrestling with delivery scheduling in a dense urban area. Two of the four teams concluded that the firm's stated hypothesis was the wrong one and said so, with evidence. Whether or not the firm acts on those findings is beside the pedagogical point. The students had to weigh incomplete data, commit to a position, and defend it against informed scepticism. That sequence is difficult to replicate on paper.

marking the work, not the noise

Assessment is where project-based learning either earns its credibility or loses it. An unexamined group grade rewards the loud and punishes the conscientious in silence, so the rubric at AELO Swiss Academy separates dimensions that a single mark would blur. The weights below are typical, though they shift somewhat between foundation and capstone terms.

| Criterion | Typical weight | What assessors look for |

| --- | --- | --- |

| Analytical rigour | 25% | Sound method, defensible assumptions, honest treatment of limits |

| Execution quality | 25% | Completeness, accuracy, professional standard of the deliverable |

| Collaboration | 15% | Documented contribution, responsiveness to feedback |

| Communication | 20% | Clarity of the defense and handling of panel questions |

| Reflection | 15% | Quality of the written post-mortem and self-assessment |

Two mechanisms keep individual accountability intact. First, contribution statements and peer evaluations are collected at the midterm critique and again at the defense, and they can move an individual mark within a team. It is not unusual for the spread between the highest and lowest individual marks in one team to span a full grade band, and when it does, the panel is required to justify the gap in writing. Second, the oral defense includes a period of individual questioning in which each member must answer without the shelter of the group. A student who has coasted through the term tends to be discovered there, quickly and fairly.

Markers themselves are subject to discipline. Faculty hold calibration sessions before each assessment window, borderline defenses receive second marking, and a sample of projects is reviewed against the rubric by a marker who was not involved in supervision. None of this eliminates judgement, and it is not meant to. It keeps judgement anchored to criteria that students can read in advance.

the supervisor's chair

Supervision is the least visible part of the model and, in my experience, the one that determines most of its quality. Each team receives a short weekly check-in, usually fifteen minutes, and formal milestone reviews at the midterm stage. Written feedback on milestone submissions follows within five working days, so that a course correction arrives while there is still time to make one.

I recall a supply-chain project from a previous year in which a team spent the first two weeks building an impressive-looking proposal for warehouse automation, complete with renderings. At the midterm critique the supervisor asked a single question: what evidence did they have that automation, rather than inventory policy, was the bottleneck? They had none. The team spent an uncomfortable week re-examining the data, discovered that stock rotation, not picking speed, was driving the cost overrun, and rebuilt the project around inventory segmentation. The final report was good. The pivot, and the discomfort of the pivot, taught them more than the report did. Students who have been through that experience once tend to scope their evidence earlier in every project that follows.

where the model strains

An honest account requires admitting that project-based learning has real costs, and that some of them fall on exactly the people a school most wants to serve.

The first cost is calendar. Projects consume weeks that a lecture-based course would spend on coverage, so faculty must make deliberate choices about what to set aside. Sequencing matters enormously: foundational content has to be laid down before a project can build on it, or teams will flatter their own ignorance. Programs that treat projects as a substitute for content, rather than as a structure for applying it, produce confident students with thin foundations.

The second cost is the fragility of teams. Most groups work, some excel, and occasionally one collapses, whether through illness, withdrawal, or irreconcilable disagreement. There is a protocol for this: the supervisor intervenes early, work is redistributed, and grades are adjusted against the contribution record. The protocol is necessary, but it is an admission that collaborative assessment carries administrative weight that an examination never does.

The third cost is adjustment. Students arriving from examination-centred schooling often find the first project disorienting. They ask for the correct answer, and the honest reply is that there is none, only better and worse defensible positions. For that reason the first-term project is deliberately narrow, with more scaffolding and a tighter brief, and the supervisor's role in that first term leans toward coaching. By the second or third project, most students stop asking what we want and start asking what the problem requires. That transition is the point of the whole design, but it is not frictionless.

Finally, some material simply does not suit the format. Technique-building in mathematics, statistics, or a foreign language still requires repetition and drills. A project can motivate that repetition; it cannot replace it.

examinations have not been retired

It would be a misreading of our practice to conclude that AELO Swiss Academy has done away with examinations. Written papers remain in place across the programs, typically accounting for around forty percent of the final module grade in foundation subjects, with the project carrying the remainder. In capstone terms the balance tilts further toward the project, but the examination component survives everywhere in some form, and for good reasons.

Examinations verify individual command of fundamentals, which a team grade can only approximate. They serve as a check on academic integrity in an era when a polished report no longer proves that its author wrote it. And the act of preparing for one consolidates knowledge in ways that distribute nicely across later use. The design question, as we see it, is never whether to examine but in what proportion and for what purpose. A degree in which every grade is a group artifact would be as distorted as one in which every grade is a three-hour paper.

what students actually take with them

Ask graduates what the projects gave them and the answers cluster around a handful of capacities: the ability to scope a vague problem, the habit of documenting decisions so that others can audit them, the nerve to present work that is unfinished in places and to say plainly where it is, and the discipline of recovering from critique without treating it as insult. These are precisely the capabilities that hiring panels probe in interviews, and they are difficult to claim without evidence.

The portfolio solves that evidentiary problem. A student completing a program here leaves with a set of artifacts, each one defended in public and graded against a published rubric. In a job interview, walking an employer through a pivot story, through what the team got wrong in week two and how it found out, says more than a transcript line ever could. I have watched a former student do exactly that, spending ten minutes on the failure before reaching the recommendation, and seen the interviewer lean forward rather than back.

questions worth asking before enrolling

Project-based learning has become a popular phrase, and phrases travel faster than practice. Families and applicants evaluating any program that uses the term, including ours, are right to probe beneath it. The questions we encourage people to ask, here and elsewhere, are these:

• How much of the grade rests on individual work, and how is team contribution verified?
• Who writes the project briefs, and are external organisations genuinely involved?
• What happens when a team member fails to deliver?
• How are markers calibrated, and can students see the rubric before the project begins?
• What does a completed project portfolio actually look like at the end of the full program?

We answer these questions at every open evening, and we are more comfortable being asked than being admired. A school confident in its assessment design should be able to show the rubric, the moderation records, and a sample defense, and we make a practice of doing so.

the grade that follows a student out the door

The deepest change that project-based learning produces is not in what students know but in what they believe a grade is for. Under an examination-only regime, a grade is a verdict, delivered once, at the end, by someone else. Under a project regime, a grade is an accumulated argument: a plan that was approved, a critique that was survived, a contribution that was logged, a defense that was given, and a reflection that admits what the team would do differently next time. That is much closer to how professional reputations are actually built.

Nothing in this model is effortless, for students or for faculty, and the trade-offs described above are permanent features rather than teething problems. But when a cohort stands up in January and answers the panel's hardest question with evidence instead of improvisation, the reason we arrange the term this way stops needing explanation. The work speaks, and the students have learned to make it speak.