Ask any teacher in Oujda or anywhere else in Morocco what they actually want their students to walk away with after two years of Bac English, and "critical thinking" comes up almost every time. It sits right there in the Ticket to English and Visa to the World syllabi, usually next to words like "autonomy" and "21st-century skills." But ask the same teachers how they build it in a 45-minute period with 38 students, and the answers get vague fast. This post is about one method that actually works, and that most of us already use without naming it properly: collaborative problem-solving.
I've been teaching English for over three decades now, and if there's one thing I've watched shift in that time, it's the failure of the lecture-and-recite model to produce students who can actually reason through a problem they haven't seen before. Collaborative problem-solving isn't a trend borrowed from a TED talk. It's a structured way of putting students in front of a real difficulty, in small groups, and forcing them to think out loud, disagree, and defend a position before they get an answer. Done right, it builds exactly the kind of thinking the Bac exam rewards — and, more importantly, the kind of thinking students will need long after the exam is over.
What Collaborative Problem-Solving Actually Means
Collaborative problem-solving, often shortened to CPS in education literature, is a learning approach where a group of students works together to analyze a problem, weigh possible solutions, and arrive at a shared decision — usually one that has no single "correct" answer printed in the back of a textbook. The problem has to be genuine. Not "fill in the blanks about pollution," but something closer to: "Your town council has 2 million dirhams and three competing proposals for how to spend it on the water crisis. Decide which one you'd fund, and be ready to defend it against another group."
Three things separate this from a regular classroom activity. First, the outcome is genuinely uncertain — even the teacher doesn't hand out a model answer at the end, because there isn't one right answer, only stronger and weaker arguments. Second, the students need each other; the task is built so that no single student can solve it alone, either because the information is split between them or because the reasoning demands more than one perspective. Third, the process is visible — students have to externalize their thinking through talk, negotiation, and sometimes written notes, rather than just producing a final product silently.
Why It's Not the Same as "Group Work"
I want to be blunt about this because I see the confusion constantly, including in my own classroom over the years. Putting four students at a table and telling them to "discuss the text together" is group work. It is not collaborative problem-solving unless there's an actual problem to solve and a reason they can't just split the labor and stitch it back together at the end.
A worksheet where each student answers two questions and then they compare answers is not CPS — it's parallel work with a shared table. Real CPS tasks are designed so that dividing the labor doesn't actually work, because the solution requires combining perspectives, not just combining answers. That distinction matters enormously for critical thinking, because critical thinking doesn't get exercised by copying a partner's answer into your notebook. It gets exercised by having to justify your reasoning to someone who disagrees with you, in real time, in a language you're still mastering.
The Cognitive Link Between Collaboration and Critical Thinking
Critical thinking is often described in vague terms — "analyzing," "evaluating," "synthesizing" — words that show up on Bloom's taxonomy posters in every staff room but rarely get broken down into what a teenager actually has to do differently in the moment. Here's a more concrete version: critical thinking happens when a student has to justify a claim, consider an alternative claim, and revise their own position based on new information or a counter-argument.
A student sitting alone rarely does all three of those steps voluntarily. Left to themselves, most students form an opinion and stop there — there's no social pressure to test it. Put that same student in a group of four facing a genuine problem, and something different happens. Someone else in the group has a different idea. Now the first student has to explain why their idea is better, which forces them to actually examine their own reasoning instead of just asserting it. That's the mechanism. Collaboration doesn't add critical thinking as a bonus feature — it creates the social condition under which critical thinking becomes necessary rather than optional.
This is close to what Lev Vygotsky called the "zone of proximal development" — the idea that students can often do, with the support of peers, what they can't yet do alone. Applied to reasoning specifically: a group can often construct an argument more sophisticated than any single member could produce solo, because the back-and-forth catches gaps that one mind alone would miss.
What Changes in the Classroom When You Use It
I'll list what I've actually observed, not what a training manual promises.
Students start asking "why" instead of "what." In a lecture format, students ask what the answer is. In a CPS task, because there's no single answer to fish for, the questions shift toward why one option beats another. That shift alone is most of what critical thinking is.
Weaker students get pulled up, not left behind. This is one people worry about — that a struggling student will just ride along on the stronger student's ideas. In practice, a well-designed task where each student holds a piece of information the others don't have prevents that. If Ahmed has the only copy of the budget figures, the group can't move forward without him contributing, regardless of his English level.
Language production goes up dramatically. This is specific to us as EFL teachers. A CPS task forces students to negotiate meaning in English — to ask for clarification, to disagree politely, to restate someone else's point before responding to it. These are exactly the functional language chunks that show up in the Bac's production sections, and students practice them under real communicative pressure instead of copying a dialogue from the textbook.
Mistakes become data instead of embarrassment. When a student proposes a flawed solution to the group, the group tests it and finds the flaw together. Nobody's grade dropped for it, and the correction came from a peer, not a red pen. That changes how students relate to being wrong.
I remember a group in a 1st Year Bac class a few years back that spent almost ten minutes arguing over whether a proposal was realistic, purely because one student — usually one of the quietest in the room — refused to let the group move on until the numbers actually added up. Nobody had asked her to be the group's accountant. She just couldn't let a weak argument pass unchallenged once she had the cost data in front of her. That's not a skill I taught her in a grammar lesson. It surfaced because the task gave her a reason to use it, and a group that had to listen because they needed her card to finish.
I've also seen the opposite happen, which is worth being honest about: a group that includes one dominant personality can occasionally steamroll the discussion regardless of how the information is split. That's not a flaw in the method so much as a reminder that CPS still needs a teacher circulating, listening, and occasionally redirecting a conversation toward the quieter student holding a card nobody's asked about yet.
Why This Matters for Moroccan Bac Students Specifically
Two things make this especially relevant for our students. First, the Bac English exam's production section increasingly rewards argumentation — essays that take a position, anticipate a counter-argument, and defend a choice, rather than descriptive writing. A student who has spent a term defending positions out loud in front of skeptical classmates writes a stronger argumentative paragraph than one who has only ever written in silence.
Second, most of our students are heading toward university programs — engineering schools, medical prep classes, business faculties — where oral defense of ideas, whether in French, English, or Darija, is a daily reality. The lycée is often the last structured opportunity to build that muscle before the stakes get much higher. If the only skill we build is vocabulary recall, we're preparing students for an exam that no longer fully exists in its old form, and we're under-preparing them for what comes after.
A Five-Stage Model You Can Use Tomorrow
Here's a structure I've refined over many years of trial and error, adapted for a standard Moroccan classroom period.
1. Frame the problem (5 minutes)
Present the scenario clearly, in writing and orally. State explicitly that there is no single correct answer and that groups will be judged on the quality of their reasoning, not on guessing the "right" solution.
2. Distribute information unevenly (5 minutes)
Give each student in the group a different card, fact sheet, or role. This is the step most teachers skip, and it's the one that makes or breaks the task — without it, the strongest student just does everything.
3. Group deliberation (15–20 minutes)
Students combine what they know, argue for their preferred solution, and work toward a group decision. Circulate but don't intervene unless a group is completely stuck. Resist the urge to correct grammar mid-discussion; that can come later.
4. Cross-group challenge (10 minutes)
Pair two groups together. Each presents its decision, and the other group is required to ask at least two challenging questions. This step is what pushes students from "we agreed" to "we can defend it under pressure."
5. Debrief and individual reflection (5–10 minutes)
Ask each student to write two or three sentences: what changed their mind during the discussion, if anything, and why. This individual step matters — without it, some students coast through the group phase without doing any actual thinking themselves.
A Sample Task: The Water Shortage Debate
Since water scarcity is a live issue across the Oriental region and shows up regularly in Bac reading passages, here's a task I've used with 2nd Year Bac classes.
Scenario: A fictional town, Ait Salam, has a severe water shortage. The town council has a limited budget and three competing proposals: build a new desalination unit, repair the aging pipe network that currently loses 40% of its water to leaks, or invest in a public awareness campaign about household water use. Groups of four each get a card: one with cost estimates, one with a timeline for each project, one with public opinion data, and one with environmental impact notes. No student has the full picture alone.
See the group decision criteria I give students
Groups must rank the three options and justify the ranking using at least three of the following: cost-effectiveness, speed of impact, long-term sustainability, and public support. They must also state one weakness of the option they ranked first — a detail that consistently produces the most interesting writing, because it forces students to argue against their own conclusion honestly instead of just cheerleading for it.
What happens in practice: groups almost never agree quickly. The cost data pushes toward pipe repair, but the public opinion card usually favors the desalination unit because it "sounds modern," and someone always has to point out that popularity isn't the same as effectiveness. That argument, entirely generated by the students, is closer to real critical thinking than anything I could lecture them into producing.
Common Mistakes That Kill the Method
I've made most of these myself, so this isn't a list written from a distance.
Giving a task with an obvious right answer. If the "problem" is really just a comprehension check dressed up as a discussion, students figure that out within minutes and stop engaging seriously.
Grouping by ability level. Homogeneous groups of weak students tend to spiral without a strong voice to push the discussion forward; homogeneous groups of strong students often just agree too fast and skip the friction that builds thinking. Mixed groups, with information split unevenly as described above, work better than either.
Jumping in too early. Teachers are trained to fix confusion the moment we see it. In CPS, some of that confusion is exactly where the learning happens. Give groups longer than feels comfortable before stepping in.
Skipping the individual reflection step. Group energy can carry a weak student through the discussion phase with zero actual reasoning happening on their part. The written reflection at the end is what makes the thinking individually accountable.
Making group size too large. Above five or six students, someone always goes quiet. Four is close to ideal for a 45-minute period.
Treating the language correction and the thinking task as the same moment. If you stop a group mid-argument to fix a verb tense, you break the reasoning momentum they just built, and the next thing they say is usually shorter and more cautious than what they would have said uncorrected. I keep a small notebook during the deliberation phase and jot down recurring language errors — a mistiming with "would" and "will," a wrong preposition after "responsible" — and address them as a whole-class mini-lesson afterward, using anonymized examples pulled straight from what I overheard. Students get the correction, and the group discussion stays intact.
How to Assess It Without Losing Your Mind
Grading collaborative work fairly is the part most teachers dread, and I won't pretend there's a perfect fix. What's worked for me is separating three things: the group's final product (the ranked decision and justification), a short individual reflection written after the discussion, and a participation observation I jot down during the deliberation phase — just a quick tally of who spoke, who asked a question, who challenged an idea.
The individual reflection carries more weight than the group product in my grading, precisely because it's the one piece that can't be coasted through by a talkative groupmate. A simple rubric — clarity of reasoning, use of evidence from the task cards, acknowledgment of a counter-argument — keeps grading fast enough to be sustainable across five or six sections.
What the Research Actually Says
The theoretical backbone here goes back to Vygotsky's social constructivism and later work by researchers like Noreen Webb, who studied how the act of explaining a concept to a peer produces deeper understanding than passively receiving an explanation. More recent work on collaborative problem-solving, including the framework PISA has used in its own assessments since 2015, treats it as a distinct, measurable competency — one that combines social skills (establishing a shared understanding, managing conflict) with cognitive skills (representing and formulating the problem, planning and executing a solution).
What that framework gets right, in my view, is refusing to separate the social from the cognitive. A student who can reason brilliantly alone but can't explain that reasoning to a skeptical peer hasn't fully mastered it. The explaining is part of the thinking, not a separate performance layered on top of it.
Webb's research is worth dwelling on a little longer, because it cuts against a common assumption. Many teachers assume the student who benefits most from group work is the weaker one, riding on a stronger peer's explanation. Her studies actually found the opposite pattern more often: the student giving the explanation gains the most, because putting reasoning into words — especially words aimed at someone who might push back — forces a level of clarity that silent understanding doesn't require. That's a strong argument for rotating who explains what inside a group, rather than always letting your strongest English speaker do the talking while everyone else nods along.
Final Thoughts
None of this requires new equipment, an app, or a training certificate. It requires a problem worth arguing about, information split across the group so nobody can freeload, and the discipline to stay quiet longer than feels natural while students work through the mess themselves. The mess is the point. Critical thinking doesn't get built by watching someone else think clearly — it gets built by being forced to think clearly yourself, out loud, in front of people who might disagree with you.
If you're teaching in a Moroccan lycée and haven't tried a structured CPS task yet, the water shortage scenario above is a reasonable place to start — it's close enough to students' actual environment that they care about the outcome, and split card information keeps every student accountable. Adjust the numbers, adjust the scenario to your region — Oujda's water table isn't Agadir's coastline, and a task rooted in something students recognize from their own town will always pull more honest arguing out of them than a generic textbook scenario imported from nowhere in particular.
Try it once with a single class, keep the card system uneven on purpose, and resist the urge to rescue a group that's stuck in year two of arguing over which proposal actually makes sense. See what your students argue about. You'll probably learn as much from listening to them as they do from the task itself, and that's usually the clearest sign a lesson is working the way it's supposed to.