The first sixty seconds decide whether your game has a day thirty
We grey-box the core loop in week two and playtest it before commissioning a single piece of art. Here is what that has saved, and what it has killed.
Zaw Min Htet
Head of Games

We have killed three of our own game concepts at the grey-box stage. Each time it cost about six weeks and saved about six months, and each time somebody in the room argued that the art would fix it.
The art never fixes it.
Why grey-box first
A core loop that is not fun in grey-box will not become fun with art on top. Art raises the ceiling of an enjoyable loop; it does not raise the floor of a boring one. What art *does* do is make everyone in the room, including us, much worse at telling the difference — which is exactly why it has to come second.
So the schedule is: week one, design the loop on paper. Week two, a playable grey-box build. Week three, playtest with people who have never seen it.
What we measure in a grey-box test
Not "did they like it". Everyone says they liked it, to your face, on your laptop.
Time to first meaningful action. From launch to the player doing the thing the game is about. Over sixty seconds and something in the onboarding is in the way.
Unprompted second attempt. After a failure, do they start again without being asked? This is the single strongest signal we have found. If they put the device down, the loop is not there.
Session length without instruction. We say "play as long as you want" and then leave the room. Under four minutes on a casual title is a redesign, not a tuning pass.
Where they look for depth. Watch what they poke at when they get comfortable. That is where the meta-game wants to go, and it is almost never where the design document put it.
The Bloom Blitz case
Cobalt came to us with a match-3 prototype that tested well for five minutes and lost players by day three. Everyone assumed the mechanic was tired.
The grey-box tests said the opposite: unprompted second attempts were high, session length was fine, and players kept opening a progression screen that had nothing in it. The mechanic was working. There was simply no reason to come back tomorrow.
So we left the mechanic alone and rebuilt everything around it — a garden you decorate with match rewards, an energy economy tuned so paying is a shortcut rather than a gate, and a difficulty curve simulated against fifty thousand modelled sessions before implementation.
Day-30 retention came out at 18.4% against a category benchmark around 8%. We changed almost nothing about the part everyone wanted to change.
The uncomfortable part
Grey-boxing means telling a client in week three that the thing they have been excited about for six months does not work yet. That conversation is much easier in week three than in month seven, and it is the entire reason the stage exists.