Chocolate Covered Broccoli

There's a concept in edtech design sometimes called "chocolate-covered broccoli,” the idea of wrapping genuinely educational content in enough sugar that kids don't notice they're learning. It sounds appealing in a pitch deck, but in practice it seldom works.

The research on this is pretty clear. Extrinsic motivators like animations, points, and reward moments produce short-term engagement spikes and long-term diminishing returns. Students habituate quickly and once the novelty wears off you're left with a noisier interface and the same underlying engagement problem.

The real lever for student engagement is intrinsic: content that feels relevant, achievable, and worth caring about. That shaped our design constraint from the start. Visual delight was on the table of course, but only where it was earned, meaningful, and tied to something students were genuinely doing.

Where, How, and How Much

Before designing anything, we mapped the full student, teacher, and whole-class journey across the platform to identify where celebration moments could feel earned rather than arbitrary. We weren't simply looking for places to insert delight, we were looking for moments where something genuinely worth acknowledging was already happening.

That mapping surfaced five distinct opportunity zones, each representing a different kind of achievement and a different relationship between the teacher and the student experience: completing a multi-step problem, finishing a session, reaching a unit milestone, a whole-class collective achievement, and a student's personal progress threshold. Each had different stakes, different audiences, and different implications for how much control teachers would want over triggering them.

Hands-On or Hands-Off

From a motivational standpoint, achievement recognition lands hardest when the goal was set by the person being recognized, eg. students who choose their own targets feel more ownership over reaching them. But from a practical standpoint, putting that goal-setting responsibility on teachers meant adding cognitive overhead to people who were already managing thirty students, a curriculum timeline, and a platform they were still learning.

We needed user input before we could resolve it. Rather than presenting polished mockups (which tend to anchor feedback to visual details rather than concepts) we used storyboards to illustrate each of the five celebration models. Storyboards let us test the idea of each approach: who initiates it, when it triggers, what it looks like for the student, and how much the teacher has to do to make it happen.

Celebrating the Narrative

The storyboard feedback was clear on two things. First, most teachers wanted the system to handle celebration automatically rather than providing them with yet another decision to make in the middle of a lesson. Second, and more importantly, every user responded more positively to celebration moments that felt connected to what they were actually learning, rather than generic reward animations that could have come from any app.

That second finding pointed us toward a narrative approach. Rather than isolated celebration moments, we designed a through-line that wove across the lessons themselves, creating a visual story that the whole class experienced together, with celebratory moments tied to collective milestones in that narrative arc. Completing a session advanced the story. Reaching a unit milestone unlocked a new chapter. The celebration wasn't a gold star appended to the work rather it was part of the world the content had built.

This also slyly solved the intrinsic motivation problem. When the narrative is genuinely interesting, students engage with the content to find out what happens next. The celebration becomes a byproduct of learning, not a bribe for it.

Feedback and Next Steps

User testing validated what the storyboard sessions had pointed toward, not "how do we add more engagement features?" but "how do we make the engagement feel like it belongs?"

Furthermore, the minority of users who did want more control gave us a clear roadmap for what comes next: teacher-configurable goal thresholds, student-selected narrative paths, and more celebration trigger points across the platform. The system was designed to accommodate those layers, we just didn't need them to ship something meaningful.