---
title: "Why Do People Stop Asking Questions?"
type: case-study
url: https://sparkchapter.com/case-studies/why-do-people-stop-asking-questions
published: 2026-08-16T17:34:12.973Z
modified: 2026-08-16T17:34:41.409Z
author: "Muhammad Ali Imran"
reading_time: 7 min
license: "CC BY 4.0, attribute to SPARK Chapter"
---

# Why Do People Stop Asking Questions?

*What we learned from running a summer camp where nothing was required.*

> Carl Sagan noticed something uncomfortable about education. Small children ask questions constantly, and ambitious ones — why is the sky blue, what happens when you…

Carl Sagan noticed something uncomfortable about education. Small children ask questions constantly, and ambitious ones — why is the sky blue, what happens when you die, how do you know. By high school, most of them have stopped. Something happens in between, and it isn't growing up.

We have a theory about what happens, and last summer we built a camp to test it.

A five-year-old asking why the sky is blue risks nothing. A sixteen-year-old asking the same thing in a graded classroom risks being marked — by classmates and by the institution — as someone who doesn't already know. When everything you say might be assessed, silence is the smart move.

If that's right, then curiosity isn't destroyed. It's priced out. And if it's priced out, it should come back when the price is removed.

## Removing the price

We ran a free six-week camp in Islamabad for 35 students, from Grade 8 to university. We removed every mechanism that attaches a judgement to not knowing something, and kept the difficulty exactly where it was.

-   **No attendance.** Come when you want, leave when you want, tell us nothing.
    
-   **No grades, marks, or ranking.** At any point.
    
-   **No compulsory homework.** We sent a short note before each session about what to read — framed so students would arrive with a *question*, not with completed work. We never checked.
    
-   **No lecturing in discussion.** We moderated and explained when asked. We didn't set topics.
    
-   **No mockery.** Ideas got explored, including the wrong ones. That rule applied to us first.
    

Each session ran two blocks. A technical block on Python, data handling, machine learning, and web development. And an open discussion block with no syllabus whatsoever — across six weeks it moved through abiogenesis, theology, history, epistemology, cinematography, physics, art, and how vampire folklore forms. Every topic came from a student.

We also told them, out loud, that we weren't their teachers. We know more, we'll say so, we'll help — but nobody in this room is scoring you.

## Nobody believed us

By week two, half the room was gone.

Thirty-five students had registered. Thirty-five came on day one. By day two we were down to around seventeen, and we'd built a camp with no register and no way to call anyone back.

The strange part was the feedback. Day one averaged **4.24 out of 5**, with nothing below a 3. Nobody said it was bad. They said it was confusing.

One student asked us — entirely reasonably — to restructure the discussions around clearer questions instead of topics that "mainly lead to debates." Another complained that a political discussion had reached no conclusion, which is an accurate description of open enquiry and a completely fair complaint if you're expecting a lesson.

They weren't rejecting the camp. They were trying to map it onto the only model of a classroom they had, failing, and going home.

That's the first real finding. You can't just announce that the price is gone. Students have a decade of evidence saying otherwise, and they will test you for weeks before they update.

## Then they came back

By session four we were at roughly thirty students — about **86% of everyone who registered** — and it held to the end. Absences from then on came with reasons given in advance, which hadn't happened during the dip.

The detail that matters is easy to miss. Ratings held steady — and rose — across exactly the stretch where the room nearly doubled by taking back its most skeptical members. Returning the confused students didn't drag the numbers down. The week-two problem was never fit. It was legibility.

We now treat this as a fixed cost: **about two sessions and about half your room.** That's what it costs to get students into a classroom with no verdict in it. It also means this can't be done in fewer than four sessions — you'd deliver the dip and nothing else.

## The questions came back

Here's what we were actually looking for.

At the end we asked students what they wanted to explore next. Not what they'd enjoyed — what they were curious about now. The answers were things nobody had taught them:

The simulation hypothesis. Gödel's incompleteness theorems. The arrow of time. The Ship of Theseus. The hard problem of consciousness. Mohenjo-daro and lost civilisations. Islamic history taught slowly enough to live with rather than memorise. One student didn't name a topic at all — she asked how you unite people who fundamentally disagree with each other, and how large a cause has to be before that becomes possible.

Another told us she'd started reading history between sessions, for no reason, and that she'd never thought of herself as someone interested in history.

These are Grade 11 and 12 students in Pakistan, weeks away from a board exam system where a question with no marks attached serves no purpose. They wrote down questions anyway.

## What was actually blocking them

The mechanism showed up in how students explained their own failures.

In a graded room, difficulty becomes one of two things: resentment of the institution, or the conclusion that you're not capable. Neither appeared in our data. Instead students blamed method, preparation, or circumstance — and said they'd keep going.

> "I found the course class a little difficult because I couldn't fully understand what we were trying to do at first. But I'll study and practice it on my own, so I'm sure I'll be able to understand and get it done."

One student had tried to teach herself machine learning a year earlier, failed, and stored it as a fact about herself:

> "It wasn't necessarily because I was 'bad' at it; I simply hadn't found a way of learning it that worked for me. After these six weeks, I've started to see ML a little differently, and I might actually explore it further, because maybe I'm not as bad at it as I thought."

We didn't teach her machine learning. We changed what her earlier failure meant.

The clearest case runs straight through our feedback forms. On day two, a student was encouraged to ask a question, tried, and felt she'd embarrassed herself:

> "That's why I don't ask questions. But you advising to try, I tried to get out of the shell but left embarrassed. Won't do it again."

That is the exact moment a person stops asking questions, caught as it forms — one attempt, one perceived humiliation, one resolution never again.

By session four she was among the most engaged people in the room, and her only complaint was that it ended too soon. By the final survey she was asking for career guidance and to join the team.

The resolution didn't hold because nothing in the room sustained it. Nobody scored the failed question. Nobody recorded it. The next session carried on as though it hadn't happened.

**So here's our answer. People stop asking questions because not knowing acquires a verdict, and questions become expensive. Remove the verdict and difficulty stops producing avoidance — it produces persistence instead.**

## What else we found

**Discussion carried the camp.** Chosen as the most enjoyable activity 37 times against 21 for the technical block. Asked what mattered most to their development, students ranked mentorship (15 of 19) and discussion (14 of 19) above hands-on coding (9).

**Technical skill was our flattest result.** Only 3 of 19 felt "very prepared" technically, against 12 of 19 on confidence. Two structural reasons, neither about grades: our cohort ran from Grade 8 students who hadn't met calculus to university students who'd passed calculus without ever understanding it, which no single curriculum survives — and coding needs rehearsal between sessions in a way discussion doesn't. A compulsory once-weekly camp would have produced the same number, plus resentment.

**Given real freedom, students asked for structure.** Ours independently requested practice work, pre-reading, review sessions, and more frequent classes. Nobody made them. A constraint you choose isn't a burden — which is a more useful finding than the one we set out to test.

## What this doesn't prove

We're not claiming schools should stop assessing. Schools have to certify, and certification requires measurement. Nothing here speaks to that.

We're also missing our own counterexamples. Around five students never returned, and roughly a third of those who finished didn't complete the final survey. Anyone who found the freedom genuinely unpleasant is invisible in our data. Every finding here carries a silent clause: *among those who adapted.*

And our students self-selected into a six-week intellectual camp during their holidays. That's a group already inclined to do well without being made to.

* * *

## What happens next

We've asked this cohort to go and run sessions of their own. The only number that tells us whether we built a camp or a method is how many of the thirty do it within a year.

---

Source: https://sparkchapter.com/case-studies/why-do-people-stop-asking-questions
SPARK Chapter, a student innovation community at NUST H-12, Islamabad.