Correlated randomness in Slay the Spire 2: how it works

The game design community is buzzing about how a roguelike card game handles dice rolls, and buried inside that conversation is a genuinely useful lesson about how randomness affects trust, whether your product is a video game or a client-facing service.

What A Card Game Teaches About Predictability

Slay the Spire 2 is a turn-based deck-building game where random number generation (RNG, the system that decides what cards you draw or what enemies do) is central to every session. The developer's recent technical write-up on "correlated randomness" has caught significant attention from developers and designers because it tackles a deceptively simple problem: when things feel too random, people stop trusting the system, even if the system is mathematically fair.

The fix they describe is making random outcomes feel connected to context. Rather than each event being a completely independent coin flip, the game nudges results so that bad luck in one area tends to balance out elsewhere. Statistically it is still random. Experientially, it feels fairer. The player never feels cheated, even when the odds are against them.

The Gap Between Fair and Feeling Fair

This is not just a game design curiosity. It describes a tension that comes up constantly in how businesses present information to clients. A system, a process, or a tool can be working exactly as intended while still feeling broken to the person on the receiving end. That gap is where trust erodes.

We see this regularly when clients come to us after being burned by previous digital projects. The website technically loaded. The ad campaign technically ran. The numbers were not catastrophically wrong. But nothing felt coherent, and nobody explained the logic. The result was a loss of confidence that had nothing to do with the actual performance.

What This Means If You Run a Business

If you are a freelancer or small business owner delivering any kind of service that involves variable outcomes, this principle applies directly to you. Project timelines slip. Marketing campaigns underperform one month and overdeliver the next. Design revisions go in unexpected directions. These are normal fluctuations, but to a client who cannot see inside your process, they can look like chaos.

The lesson from the Slay the Spire 2 write-up is that transparency about the system builds more trust than the results themselves. When clients understand why something happened, even a bad outcome becomes manageable. When they have no frame of reference, even a good outcome can feel uncertain.

This also matters for how you present data. If you are reporting on SEO performance, social reach, or project milestones, raw numbers without context are almost meaningless. A client seeing impressions rise while traffic falls (a common scenario right now as Google surfaces more zero-click results) will reasonably assume something is broken. Your job is to make the system legible before the anxiety sets in.

What To Do About It

1. 1.Narrate your process, not just your results. Send a short update explaining what is happening and why, especially when outcomes are mixed. A two-paragraph email does more for client retention than a polished monthly report they do not understand.

1. 1.Set expectations around variability upfront. Before a project begins, tell clients which elements will fluctuate and why. Treat unpredictability as a feature of the work, not an embarrassing admission.

1. 1.Build checkpoints that let clients see the logic. Whether that is a shared project board, a weekly standup, or a simple loom video, let people inside the system rather than asking them to trust outputs they cannot interpret.

1. 1.If your metrics look confusing, explain them before you are asked. Impressions up, traffic down, is a real scenario affecting many businesses right now. Get ahead of it with a clear explanation rather than waiting for a worried message at 8pm on a Friday.

1. 1.Review your client communications for jargon. Wherever you use a technical term, add a plain-English gloss. Not for their benefit. For yours. Confused clients cancel contracts.