I Playtested ChillBrain With My Mother — the Cuts, the Keeps, and the Fights We Had Over Timers
I'm an information security professional by day. ChillBrain is the game I built for my mother, Evelyn, who turned seventy this year. People sometimes ask how a systems person ends up shipping puzzle levels. The honest answer is: I didn't ship "levels." I shipped whatever survived an afternoon on her tablet — with her reading every word out loud, mis-tapping the cute thing that looked tappable, and occasionally apologizing to the game when it buzzed at her.
This is the playtesting diary I wish I'd written while we were in the thick of it. Not the polished design manifesto (I already wrote pieces of that). The messy middle: what we cut, what we kept, and the one argument we had more than once — timers.
How the sessions actually worked
We never ran a "lab." Evelyn lives a normal life. Playtesting meant:
- Her tablet, her sofa, her lighting (afternoon glare is a real enemy).
- Me sitting nearby with a notes app, not grabbing the screen unless she asked.
- A rule I had to learn the hard way: if I explain the puzzle while she's stuck, I contaminate the data. Watching silently for two minutes taught me more than ten minutes of coaching.
Early on I asked for "feedback." She gave kindness. Useful feedback arrived when I stopped asking and just watched where her finger hovered, where she squinted, and when she put the tablet face-down mid-level — not angry, just done.
Her friends eventually became second-wave testers. They are somehow harsher than she is, in the loving way of people who will tell you the truth after merienda.
Fight #1: timers (we almost lost this one)
I knew, intellectually, that countdowns are hostile to older players. I still tried a soft version once: not a red clock of doom, just a gentle "suggested pace" bar that filled as you thought.
Evelyn's face changed. She started rushing swaps she would normally consider. When the bar filled she said, quietly, "I was still thinking."
That was the whole argument. There is no kind timer. A timer turns a puzzle into a reflex game. Seniors are excellent at puzzles when you stop treating hesitation like failure. We deleted every time pressure mechanic — including the "helpful" ones — and never put one back.
Difficulty moved into move budgets, denser boards, and (later) modes that ask for planning instead of speed. Sessions got longer after the clock disappeared. That surprised me more than it should have.
Fight #2: the buzz that made her apologize
Early match-3 builds buzzed and shook the tiles when a swap did nothing. On a technical level it was "clear feedback." On a human level my mother apologized to a piece of software.
I still feel a bit sick remembering that. We rewrote the failure language into neutral or encouraging only. A failed level says something closer to "So close" and offers help. There is no losing streak theatre. Confidence, once dented, takes a long time to rebuild in someone who already suspects gadgets "aren't for them."
Cut: punitive haptics, scolding copy, anything that sounds like a teacher marking a quiz wrong. Kept: soft confirmations when a match does land — sound as proof, not atmosphere.
Fight #3: cute things that looked clickable
In Kitty Sort we briefly shipped a decorative basket that looked exactly as tappable as the real shelves. Of course she tapped it. Of course her friends tapped it. It was round, centered, and friendly.
The fix wasn't a tutorial tooltip telling seniors they were wrong. The fix was making the basket look inert — flatter, quieter — and making the real slots shout "I am usable" with outlines that light up when they can receive a kitten.
Playtesting rule that stuck: if two things look interactive, older players will treat both as interactive. Affordance is not decoration. It is the interface.
Fight #4: tiles that "fit" on my phone and not on hers
Developers are liars about screen size — mostly to ourselves. A layout that looked fine on my device squeezed pieces below comfortable thumb size on hers. The worst screenshot I ever received was basically a furry traffic jam of overlapping kittens.
We enforced a hard rule: pieces do not shrink below thumb size. If they cannot fit, the layout changes shape (fewer columns, more scroll) instead of punishing fingers. Scrolling is easy. Precision-tapping a thirty-pixel target is not.
Cut: clever dense grids that only I could operate. Kept: chunky tiles, capped board growth, big hit areas even when the puzzle gets hard.
Fight #5: drag versus tap-tap
Younger testers dragged pieces immediately. Evelyn taps: one tap to pick up, one tap to place. Neither group discovered the other method alone.
So we support both — carefully — so drag never steals the page scroll. Playtesting taught me that "teach them the efficient way" is the wrong instinct. Meet the gesture they already trust.
Fight #6: color alone is a trap
Color vision changes with age; contrast sensitivity drops; living-room light is rarely a studio. Every fruit in ChillBrain differs in more than hue: shape, colour, and a distinct pastel background. Nobody should need perfect red-green discrimination under a bright window to finish a level.
We cut a few early tile designs that looked elegant to me and muddy to her. Elegant lost. Readable won.
Fight #7: difficulty I "felt" versus difficulty she lived
I am a catastrophically bad judge of my own game's difficulty. Levels that felt "fine" in my hands were impossible for a careful first-time player past the early twenties. We only caught that by simulating thousands of playthroughs of a basic player and measuring win rates, then retuning goals against those numbers.
Playtesting with Evelyn was the qualitative half of that work. The simulator told us where the cliff was. She told us how it felt to fall off it — which helpers she reached for, which messages she trusted, when she wanted a free hint versus when a hint felt like cheating.
Cut: designer intuition as the source of truth. Kept: measure the floor player, not the ceiling player — then watch a real floor player anyway.
What we kept because she loved it (not because it was clever)
The dedication screen — "This game is dedicated to Evelyn" — is, according to her friends, the feature. Software that feels made for someone gets forgiven for small rough edges. Software that feels made for metrics does not.
Sound tied to her action mattered more than ambient music. A pop that confirms a match, a warmer cue for something bigger, a natural voice celebrating a four-match. Robotic device voices tested terribly. We also learned to respect reduced-motion settings without silencing joy: soften animation, do not mute confirmation.
Lifelines and helpers stayed soft currency earned by playing — never a wall mid-puzzle that demands a purchase to continue. Rewarded videos only when you tap the button. One banner outside the play area. Those weren't marketing slogans first; they were playtest scars from watching interruptive patterns make her put the tablet down.
The checklist I use before I call a build "Evelyn-ready"
After dozens of sofa sessions, this is what I check before I trust a build with her:
- No timers of any kind — including "helpful" pace meters.
- No punishment theatre — no scolding buzz, no shame streak.
- Touch targets bigger than the guideline, then bigger.
- Difference in three channels — not colour alone.
- Decorative things must look inert; interactive things must look alive.
- Tap-tap and drag both work; scrolling still works.
- Copy assumes she will read every word — because she will.
- Sound confirms her action; reduced motion never deletes confirmation.
- Difficulty measured against a floor player, then watched with a real one.
- Something human remains — dedication, kindness, a sense that a person made this.
If a feature fails that list, it does not ship — no matter how proud I am of the code.
What I'd tell another builder (or another son)
Playtesting with a parent is not QA theatre. It is a relationship with a tablet between you. You will want to defend your design. Don't. The mis-tap is the bug report. The face-down tablet is the severity rating.
Ship smaller. Watch longer. Apologize faster. Fix the thing that made her feel foolish before you polish the thing that made you feel clever.
ChillBrain is free to play in the browser at chilldaemon.com/chillbrain — 450 levels across gentle puzzle types, no timers, big tiles. If you want the design rules distilled, start with What I Learned Designing a Game for My 70-Year-Old Mother and From Match-3 to Kitty Sort. If you're choosing how to play tonight, the mode guides for Match-3, Kitty Sort, and Garden Paths are written from the same sofa sessions.
And if you're building something for someone you love: remove the clock. Then watch what happens to their shoulders.