Isidor SelectionCriteria before scores

Small Studio

Judging Presentation Without Penalising Scale

A presentation criterion quietly rewards budget unless it is written carefully. The test is whether the visual choices serve the puzzle, not whether they cost a lot to produce.

Board: Isidor Selection Editorial Team·4 min read·Published 2026-11-09

“Presentation” is the criterion that lets a rubric smuggle aesthetic preference in under a neutral name. Applied carelessly it measures how much a game cost to make: orchestral score, hand-painted art, animated transitions. A two-person studio competing on the same scale loses before the session starts.

The fix is not to drop the criterion. It is to define it as a relationship — presentation in service of the puzzle — and to refuse the evidence that does not belong.

The failure mode, precisely

Judged as a production value, presentation is a monotonic function of budget. Judged as service to the puzzle, it is not: a low-resolution game with a perfectly legible board and an honest failure message can beat a lavish one whose effects obscure the mechanic.

Wikipedia’s account of puzzle video games emphasises problem-solving as the core activity over reflexes. That gives the criterion its anchor. If the core activity is reasoning, then presentation is good when it makes the reasoning legible, and bad when it competes with it — regardless of how expensive the competition was.

Four questions that do not measure budget

A presentation finding can be written from four observations that are budget-neutral:

  1. Legibility of state. Can you tell, at a glance, what the current puzzle state is? Where the pieces are, whose turn it is, what has already been tried?
  2. Signal-to-decoration ratio. How much of the screen moves, glows or animates while a decision is being made? Anything that moves without carrying information is a cost the player pays in attention.
  3. Feedback honesty. When something happens, does the game say what happened in language that matches the mechanic? An inaccurate sound effect or a misleading animation is a presentation defect even if it looks expensive.
  4. Consistency. Do the visual and verbal vocabularies stay stable across the game, so that a rule learned in level one still reads correctly in level forty?

Each of those is checkable from the artefact, and none of them can be satisfied by spending more money.

Where presentation and accessibility meet

Some presentation defects are formally accessibility failures, which is useful: it means the presentation criterion can borrow the accessibility criterion’s numeric standards rather than inventing aesthetic ones.

Contrast is the clearest case. The W3C’s Success Criterion 1.4.3 sets a ratio of at least 4.5:1 for text and images of text, with large-scale text at 3:1. A game with a beautiful but faint interface fails that test on a screenshot, and no art direction defends it.

Motion is the second. The Game Accessibility Guidelines’ cognitive basics include avoiding flickering images and repetitive patterns, and the intermediate tier recommends an option to turn off or hide background movement. Both are presentation questions with a checkable answer: is the option there, and does the game remain readable when it is enabled?

A third, less obvious one: whether the interface survives small screens. A richly decorated board has to remain usable when it is not wide enough for the decoration, and the presentation finding should say whether it does.

The “reads well at a glance” test

A practical proxy used in usability work generally is to put the interface in front of someone who has not been told what it does and see what they can infer. Wikipedia’s article on usability testing describes it as a technique to evaluate a product by testing it on users, and the underlying premise — that the designer cannot see their own interface — applies with full force to presentation.

For a selection desk, a bounded version is enough: take one screenshot of a mid-game state and ask a person who has not played the game to describe the state. Whatever they cannot describe is a presentation finding, and it is a finding about legibility rather than about taste.

What should never appear in the finding

Three things turn up in presentation sections and do not belong there:

  • Comparison to a larger game’s production. “Not as polished as [a game with a ten-times budget]” is a scale comparison wearing a craft label.
  • Preference stated as observation. “The colour palette is unpleasant” is a preference. “The palette puts two board states at a contrast ratio below the AA threshold” is an observation.
  • Effects described as merits. Particle work is not craft when it is the only visual idea in the game; it is decoration, and the criterion should say so.

The scale-neutral version

Written for a small studio, a presentation criterion should reward:

  • a board or screen state that is readable in one look
  • feedback that names the actual mechanic rather than the genre
  • restraint where motion would compete with thought
  • an option to reduce the decoration
  • consistency across the whole game

Written that way, presentation stops being an award for the biggest budget and becomes an award for the clearest one — which is a criterion a two-person studio can win.

Sources

Written for: Someone writing or auditing a rubric who suspects the presentation criterion is really measuring production budget and wants a version that does not favour large teams.

AI assistance recorded as: AI draft, not edited. Review status: approved.