When we designed Kalvium’s orientation week, we started from a single brief.
How do we make a first-year student aware, by the end of Saturday, of how learning at Kalvium actually works? Not by telling them. By making them experience it.
Most college orientations are forty-eight hours. A welcome speech. A rules walkthrough. A campus tour. A few forced ice-breakers. Then classes begin.
That format optimises for compliance. We were optimising for clarity. The two require different designs.
Here are the five design choices that shape the week, and the constraint each is solving for.
Design choice 1: First names only
This is the smallest visible change and the one that does the most work.
Every Kalvium student, from day one, calls every mentor, peer, and senior by their first name. No “sir.” No “ma’am.” No surname-with-title hybrid.
The constraint we were solving for: a first-year engineering student in India arrives with twelve years of classroom habit. The classroom habit is to wait for permission to speak. To not interrupt. To not ask a question that might be considered stupid. That habit will kill them in a Kalvium classroom, where the design assumes they will speak up, ask, and challenge.
You can lecture them about psychological safety, or you can change the protocol they use to address the room. The protocol change works faster.
In the real world (which is what we’re preparing them for) they will not call their manager “sir.” They will not email their teammate as “ma’am.” Engineering teams are flat in the way that actually matters: who has the better argument, not who has the older title.
What it looks like in practice. A mentor introduces themselves on day one. A student instinctively says, “Nice to meet you, Anil sir.” The mentor smiles and says, “Just Anil.” The student stumbles. Two days later, they don’t.
What we’d change. The first cohort still had pockets of “sir” reappearing in mentor sessions when the conversation got difficult. We now make the first-name rule explicit in the first hour of day one, with the reasoning behind it. The habit holds better when the reasoning is in front of it.
Design choice 2: Guidance, not answers
The phrase we use in orientation is, “We don’t spoon-feed.”
That phrase has done more work for us than any other line in the brochure, mostly because students who don’t like the sound of it self-select out before Semester 1 begins.
The constraint we were solving for: most students arrive with the assumption that learning means being taught. Receiving information, repeating it, getting marked on the repetition. A Kalvium classroom doesn’t work that way. The mentors don’t lecture and leave. They ask questions and wait. A struggling student gets a question, not an answer.
If a student isn’t prepared for that shift, the first week of real classes will feel like a betrayal. So we surface it in orientation. The mentors explicitly explain the model. They walk through how a typical “I’m stuck” conversation goes, and how it doesn’t go. The student gets to feel the difference before the stakes are real.
What we’d change. We used to underweight this in the first three days of orientation. Students were getting blindsided when the actual classes started. We now run a deliberate scenario on day two: a mentor sets up a small coding problem, intentionally doesn’t give the answer, and lets the room sit with the discomfort. It’s the most informative twenty minutes of the week.
Design choice 3: The peer-pressure conversation
On day three, students sit in a circle and talk, out loud, about a time they gave in to peer pressure. Not abstractly. Specifically.
The constraint we were solving for: an engineering cohort that doesn’t trust each other will not collaborate. Collaboration is the central structure of how learning actually happens at Kalvium. We needed a way to establish trust faster than the usual six-month settling period.
What we found is that trust forms quickly when one person admits a real, slightly embarrassing thing and is not punished for it. Most students have never done that in a college setting. Most of them have done it with one or two close friends. The orientation does it deliberately, with the whole cohort.
A mentor seeds the conversation by sharing their own example first. The students follow. Some stay surface-level. A few go deep. The depth doesn’t matter on day three. The willingness does.
What it does. By day five, the cohort is asking each other for help on a different register than they would have on day one. The peer-pressure conversation isn’t therapy. It’s the operational unlock for everything that comes next.
What we’d change. The first cohort version of this session ran ninety minutes. It was too long. The honest moments came early. The latter half drifted. We’ve shortened it to forty-five minutes, with a clear stop signal. Better to leave wanting more than to drift.
Design choice 4: Risk vs recklessness
On day four, the conversation turns to risk.
Students share stories of risks they’ve taken. Some good ones. Some that went wrong. One student, in our second cohort, talked about a reckless-driving incident that changed how he saw responsibility. The room got very quiet. The mentor didn’t move the conversation along. They let it sit.
The constraint we were solving for: Kalvium students will be asked to take risks constantly. They will apply for opportunities they aren’t sure they’re ready for. They will pitch a build idea that might not work. They will speak up in a session even when they might be wrong. The capacity to do that is built on a distinction most teenagers haven’t drawn yet: the difference between calculated risk and recklessness.
We name the distinction. We give the cohort the vocabulary. We show what it looks like to take an informed risk, own the outcome, and learn from the result.
What it changes. Once a cohort has the vocabulary of risk vs recklessness, the mentor sessions get sharper. A student saying, “I want to try this approach, even though I’m not sure it’ll work,” is now a different sentence than “I’m not sure what to do.” The first is a risk taken. The second is a problem to solve. Both have a place. They’re not the same thing.
Design choice 5: The late-to-class dare
Lighter, but doing real work.
If you’re late to class in the first week, you get a dare. Sing a song. Lead the next exercise. Take charge of a small group activity. The options vary.
The constraint we were solving for: time is the most under-respected resource in Indian academic culture. Being five minutes late to a class is treated as forgivable in most colleges. In an engineering workplace, those five minutes cost three other engineers’ time.
We could write a punctuality rule. Rules read once and get forgotten. We could fine students. Fines build resentment.
A dare that’s slightly embarrassing, slightly fun, very public, lands the lesson without building any of that. It’s punitive without being cruel. The cohort laughs. The student remembers. Next week, they’re early.
What we’d change. Some students with social anxiety were finding the dare disproportionately stressful. We’ve added a quiet opt-out (a private make-up task with the mentor instead) for students who flag it in advance. The signal still lands. The cost stays proportionate.
What an orientation week is actually for
A traditional orientation is for the institution. It tells students about the rules so the institution can hold them to those rules later.
A Kalvium orientation week is for the student. It tells them, by Saturday, whether the next four years are going to work for them. Some of what they encounter will be uncomfortable. Most of it is uncomfortable on purpose. The discomfort is the signal.
A few students, every year, decide by Saturday that this isn’t the programme for them. That’s a fine outcome. We’d rather they discover that in week one than in semester four.
For the rest, the week installs a default mode for everything that follows. First-name rooms. Question-asking culture. Trust earned through honesty. Risk vocabulary in place. Time taken seriously.
These five design choices are not the only ones in the orientation week. They’re the ones that, if any were removed, the rest of the programme would slowly stop working.
By design.