State the player promise clearly

2400. Lesson identity

Module

5.15 — Creative direction

Lesson

State the player promise clearly

Academic type

Concept

Schema type

text

Order

1

Estimated time

30–40 minutes

CONTRABAND classification

NONE

This lesson establishes the creative north star that should guide later choices about mechanics, content, presentation, and technical scope.

2401. Learning objective

After this lesson, you can write a concise creative direction brief that states the player promise, identifies its priorities, and defines observable criteria for evaluating whether a feature supports that promise.

2402. Why this matters

A project can contain competent mechanics and attractive presentation while still delivering a confused experience. A clear player promise gives a small team a reference point when ideas compete for time or when a technical solution changes the intended experience. It also gives AI a usable boundary: instead of asking for generic improvements, you can ask whether a proposal reinforces the intended player experience. The promise does not replace design judgment; it makes that judgment easier to apply consistently.

2403. Prior knowledge

You should already be able to define technical gates for a small team, including observable conditions, inspectable evidence, owners, and failure actions, from the verified preceding lesson: 5.14 L2 — Define technical gates for a small team / 5.14 L2 — Definir controles técnicos para un equipo pequeño.

2404. Core concept

A player promise is a concise statement of the experience the game intends to deliver to its target player. It is not a feature list, genre label, slogan, or description of the production process.

A useful creative direction brief connects four elements:

1. Player: Whose experience is being prioritized?
2. Promise: What should the player repeatedly feel, do, or recognize as valuable?
3. Priorities: Which qualities must receive protection when trade-offs occur?
4. Evidence: What observable result would show that a feature supports the promise?

The promise should be specific enough to reject work. “The game should feel fun and immersive” cannot guide a difficult decision because almost any feature can claim to support it. “The player should feel like each risky delivery is a deliberate calculation under pressure” is more useful because it implies priorities such as meaningful risk, readable consequences, and decisions that matter within a short play session.

A creative direction brief is therefore a decision instrument. It should help answer questions such as:

• Does this feature strengthen the intended experience or merely add content?
• Which quality must survive if scope is reduced?
• What should a playtest observer be able to see or hear?
• What evidence would justify keeping, revising, or removing the feature?

2405. Mental model

Use the Promise → Priority → Proof model:

Apply the model when reviewing any proposed feature:

Proposed feature
      ↓
Does it reinforce the promise?
      ↓
Which priority does it serve?
      ↓
What observable proof would we expect?
      ↓
Keep, revise, or reject

The model prevents a common drift from creative direction into accumulation. A feature is not valuable merely because it is complete; it is valuable when its contribution to the promise can be explained and checked.

2406. Concrete example

Consider this hypothetical brief for a small stealth-delivery game:

Player promise: Make the player feel clever and exposed while planning and executing short, high-stakes deliveries through spaces that reveal information gradually.

Priorities:

1. Decisions must create meaningful exposure or safety.
2. New information must change the player’s plan.
3. Consequences must be readable after the player acts.

Observable criteria:

• In a playtest, players can explain what risk they accepted before beginning a delivery.
• At least one newly revealed detail causes players to revise their route or timing.
• After a failed delivery, players can identify which decision produced the consequence.

Non-priority: Expanding the number of locations before the existing delivery decisions are readable.

A proposed cosmetic customization system might be attractive, but this brief does not yet show how it strengthens exposure, information, or readable consequences. A route-planning feature has a clearer connection because it can be evaluated against all three priorities.

The example is not a universal formula. Its value comes from the relationship between the promise, the priorities, and the evidence.

2407. AI-native workflow

Use AI as a structured critic, not as the owner of the creative direction.

1. Write your first Promise → Priority → Proof brief without asking AI for ideas.
2. Give AI the brief and ask it to identify vague terms, hidden feature assumptions, contradictions, and criteria that cannot be observed.
3. Ask AI to propose questions that would help clarify the brief. Do not ask it to choose the project’s identity for you.
4. Revise the brief yourself and record which critique you accepted or rejected.
5. Test the revised criteria against one existing or proposed feature.

A useful prompt is:

Review this creative direction brief as a skeptical design lead. Identify language that is not player-facing, priorities that overlap, and evaluation criteria that cannot be observed in a build or playtest. Do not rewrite the promise. Return questions and specific reasons.

The human decision is the final one: the brief must express an experience the team is actually willing to protect.

2408. Common mistake

The common mistake is writing a promise that describes the game’s components instead of the player’s experience. “The game has deliveries, stealth, upgrades, and branching locations” may be accurate, but it does not establish what those components should make the player do or feel. Another mistake is listing ten priorities. If everything is protected equally, the brief cannot resolve a trade-off.

2409. Guided practice

Create a one-page creative direction brief using the following template:

Player:

Player promise: [one sentence, written for the intended player]

Priority 1:
Priority 2:
Priority 3:

Observable criteria:
- [criterion that could be checked in a build or playtest]
- [criterion that could be checked in a build or playtest]
- [criterion that could be checked in a build or playtest]

Non-priority or protected trade-off:

Feature decision:
Choose one proposed feature or content idea. State whether you would keep, revise, or reject it, and cite the priority and evidence that support your decision.

Use these tests while drafting:

• Remove the genre label. Does the promise still describe an experience?
• Replace each abstract word such as “immersive,” “fun,” or “deep” with an action, feeling, decision, or observable result.
• Rank the priorities. If two conflict, which one wins?
• Ask whether a playtest observer could collect evidence for each criterion.
• Apply the brief to one feature rather than leaving it as a statement of intent.

2410. Validation / evidence

Your completed brief is valid when it contains:

• one concise player-facing promise;
• no more than three ranked priorities;
• at least three criteria that can be checked through a build, playtest, or direct observation;
• one explicit non-priority or trade-off boundary;
• one keep, revise, or reject decision tied to a priority and a criterion.

2411. Scored practical assessment

Submit the one-page brief created in the guided practice. It must include one player promise, no more than three ranked priorities, three observable criteria, one non-priority or protected trade-off, and one justified keep, revise, or reject decision.

Score each dimension from 0 to 2 points:

A passing submission earns at least 8 of 10 points and cannot score 0 for observability or decision traceability. Revise and resubmit any brief below that threshold.

A strong brief can reject or reshape a feature without requiring a new discussion about the project’s identity. If your criteria cannot distinguish between two competing proposals, revise them until they can.

2412. Key takeaways

• A player promise describes the intended experience, not the inventory of features.
• Priorities make the promise useful when scope, technology, and content compete.
• Proof must be observable in a build, playtest, or player decision.
• A creative direction brief is successful when it supports concrete keep, revise, or reject decisions.
• AI can expose vagueness and contradictions, but the team must own the promise and its trade-offs.

2413. Next lesson

Next: 5.15 L2 — Direct coherent tradeoffs / 5.15 L2 — Dirigir intercambios coherentes. This lesson moves from writing the player promise and its evaluation criteria to using that brief to evaluate competing alternatives and direct coherent trade-offs.

2414. Knowledge check