How to Time Review Codes and Embargoes

Timing review codes and embargoes—when you send reviewers your game and when their reviews can publish—affects whether reviews are ready and well-coordinated at launch. Sending codes early enough for reviews to be ready, and setting the embargo to coordinate the review release near launch, is what makes reviews support your launch rather than missing it or scattering.

Send review codes early enough for reviews to be ready

Reviewers need time to play the game and write their reviews, so review codes must be sent early enough for the reviews to be ready by launch. Sending codes early enough means giving reviewers the game with enough lead time before launch that they can play it and write their reviews in time—because reviewers need time to play and review, and sending codes too late means their reviews aren't ready at launch, missing the launch window when reviews most help. Sending codes early enough (with adequate lead time for reviewers to play and review) ensures the reviews are ready by launch, available to support the launch. The lead time needed depends on the game's length and the reviewers' schedules, but the principle is to send codes early enough that reviewers can complete their reviews by launch. Sending review codes early enough for reviews to be ready is the foundation of timing review codes, because reviews ready at launch support the launch (informing and persuading potential players at the crucial moment), while reviews not ready at launch (because codes were sent too late) miss the launch window. Send codes with adequate lead time, so reviews are ready when they most help—at launch.

Set the embargo to coordinate the review release near launch. Beyond sending codes early, setting an embargo—a time before which reviews can't publish—coordinates the review release near launch. Setting the embargo appropriately means setting the time before which reviews can't publish to a point that coordinates the review release near launch—typically at or shortly before launch—so the reviews release in a coordinated burst near the launch, maximizing their impact when potential players are deciding. An embargo coordinates the reviews to release together near launch (rather than scattering as each reviewer finishes), creating a coordinated burst of reviews at the launch moment that maximizes their impact and supports the launch. Setting the embargo at or near launch means the reviews release in a coordinated way at the crucial launch moment, when their impact on potential players' decisions is greatest. The embargo timing should coordinate the review release to support the launch—near launch, so the reviews hit when they most help. Setting the embargo to coordinate the review release near launch is what makes the reviews release in a coordinated, impactful burst at the launch, rather than scattering. Combining sending review codes early enough for reviews to be ready (so reviews are completed by launch) with setting the embargo to coordinate the review release near launch (so the reviews release together at the crucial moment) is what makes timing review codes and embargoes support your launch—codes sent early enough for ready reviews, and an embargo coordinating their release near launch, so the reviews are ready and release in a coordinated, impactful burst at the launch. Timing review codes and embargoes this way—codes early enough for ready reviews, embargo coordinating the release near launch—is what makes reviews support your launch, ready and coordinated at the crucial moment, rather than missing the launch (codes too late) or scattering (no coordinating embargo). Send review codes early enough for reviews to be ready, and set the embargo to coordinate the review release near launch, and the reviews are ready and release in a coordinated, impactful burst supporting your launch, which is what good timing of review codes and embargoes achieves. The timing ensures reviews are ready and coordinated when they most help your launch.

Scope is a decision, not an accident

Almost every overscoped game got that way one reasonable addition at a time, with no single decision ever feeling like the mistake. The finish line recedes a little with each new feature, and because the project always feels nearly done, the developer rarely notices how far the goal has drifted until they're exhausted and the game still isn't out.

Treat scope as something you actively decide rather than something that happens to you. Write down what the finished game contains, make every addition a conscious trade against that, and keep most new ideas in a backlog where they belong — because a small game you finish beats a large one you abandon.

Measure before you optimise

Intuition about what's slow, what's confusing, or what's driving players away is usually wrong, and acting on it wastes effort on problems that don't matter while the real ones persist. The developers who improve their games efficiently are the ones who measure first — profiling performance, watching real sessions, capturing actual errors — and let the data set their priorities.

It's slower than trusting your gut, but it's the only approach that reliably improves the game instead of just changing it. Find the biggest real problem, fix that, and measure again, rather than optimising guesses.

The first impression is most of the battle

More players leave in the opening minutes than at any other point, which makes the first few minutes the highest-leverage stretch of the whole game — and also the part the developer can least see clearly, having played it a thousand times. What feels obvious to you is often confusing to someone seeing it fresh, and that gap quietly costs you players before they ever reach the good part.

Get the player into the interesting part fast, let them feel competent quickly, and watch first-time players go through the opening without helping them. Nobody quits a game they're enjoying, so making the early minutes land is most of the battle for retention.

Small and finished beats big and abandoned

A folder of impressive unfinished projects teaches far less than a single small finished one, because finishing is where the hardest and most valuable lessons live — the unglamorous final stretch of bug-fixing, polishing, and shipping that ambitious abandoned projects never reach. Each completed game, however modest, builds the finishing muscle and the confidence that make the next one achievable.

So resist the pull of the dream project until you've shipped a few small ones. Scope to what you can actually complete, finish it, and let the experience of shipping make your bigger ambitions realistic.

Trust behaviour over opinions

People are unreliable narrators of their own experience — they're polite, they rationalise, they suggest fixes that miss the real problem. What they do tells the truth that what they say obscures: where they hesitate, where they get stuck, what they ignore, where they quit. The most valuable feedback is usually the behaviour you observe, not the opinion you're offered.

This is why watching beats asking, and why real data about what players actually do beats any amount of speculation. When several people stumble at the same spot, that's a problem worth fixing, regardless of whether any of them mentioned it.

Time review codes to reach reviewers early enough for their reviews to be ready by launch, and set the embargo to coordinate the review release near launch. Send codes with adequate lead time and coordinate the embargo near launch, so reviews are ready and release in an impactful burst supporting your launch.