“I don’t know what I’m supposed to do.”
We heard some version of that sentence in nearly every other playtest we ran in 2026.
We Playtest Games runs professional playtesting for indie developers. 427 games we processed this year were independently flagged for unclear objectives by at least two of our three AI classifiers, using the same conservative consensus methodology used throughout the book. That is more than a third of everything we tested. The classifiers logged 1,139 distinct observations of objective failure across those games, every one of them anchored in a real thing a real playtester said during a real session.
That makes unclear objectives the second most common failure in indie games right now, behind only poor onboarding. And it is almost always the designer’s fault, not the player’s.
This post is the long-form version of Chapter 2 of our book Top 20 Indie Game Development Mistakes: What Your Indie Game Is Getting Wrong (And How To Fix It). If you like this, the full book covers the twenty most common mistakes in the same depth.
Why this keeps happening
You know where the objective is. You know the word “dock” means that specific pier. You know “his desk” is the third desk in the second room. You know the icon in the corner of the star map is the stellar region button. The player does not know any of this. They are in a new place, looking at a new UI, reading a new proper noun, and the clock is ticking on their patience.
Same root cause as onboarding: you are writing from inside your own head. When you wrote “his desk,” you saw his desk. When you wrote “gather supplies at the dock,” you saw the exact dock. The player sees a sentence and an open world.
On top of that, many games treat objective communication as a one-time event. The player is told the goal in an intro cutscene, or a pop-up, or an opening speech. Then it is never repeated. Ten minutes in, the player is asking out loud, “wait, what was I doing?” There is no quest log. There is no objective on the HUD. There is nothing to fall back on.
The third cause is a missing or broken navigation layer. No minimap. Or a minimap with icons and no legend. Or a map without a “you are here” marker. Or a waypoint system that does not update when the world changes.
The patterns we saw, over and over
When you cluster hundreds of playtest transcripts on this one mistake, the failure modes are not infinite. They take a handful of recognizable shapes. Here are the ones we saw again and again.
Pattern 1: No objective at all
The most common failure. The game starts. The player walks around. They press buttons. They hit walls. Nothing tells them what they are working toward.
The sentence we heard over and over was some variant of “I have no idea what I’m supposed to do.” Sometimes more direct: “There is no objective so far, no lore, no quest.” Sometimes more annoyed: “What’s my objective here? I don’t have any map, I don’t have any journal.” Sometimes resigned: “What’s the goal? What’s the game?” In one session, after twenty minutes of wandering, the tester said, “I’m completely stuck at this point. I’ve been roaming around with no idea what to do next.” In another, after a long opening: “I don’t think I fully understand how the base of the game goes yet.” In a third, after winning by accident: “How did I win? I don’t even know how I won.”
The assumption behind this pattern is usually that the goal is “obvious from context.” It isn’t. In our data, the games that did best on this metric were the ones that wrote the current objective on the screen and left it there.
Pattern 2: Named destinations the game refuses to point at
The game tells you where to go. It does not tell you where that place is.
“On his desk, is he kidding me? Is he not gonna tell me where his desk is? I just found him. How am I supposed to know where everyone has their desk?” “It literally says go to school, but I don’t know where the school is. Please at least give us a hint.” “Buy weapons from shop. Where? Where’s the shop? Is it this guy? He’s not the shop? What the hell?” “I was stuck at find a merchant part of game. Couldn’t find him.” “I still haven’t found the ginger. I have no idea where the ginger is.” “Where’s the labeling station?… That might have been signposted better somehow.”
The pattern is: the game uses a proper noun the player has never seen before, in a sentence that names a goal, with no waypoint, no compass, no marker on the map, no NPC pointing in the right direction. The player has to either memorize the world layout or play the rest of the game as a scavenger hunt.
If your design philosophy forbids markers, fine, but you need to compensate. Lighting, sightlines, NPCs that gesture, environmental funneling. And then you need to verify in playtest that any of it actually works on someone who has never seen the space.
Pattern 3: Maps that are decoration, not navigation
Many of the games we tested had a map. Many of those maps did not work as navigation tools.
“It doesn’t tell me where I am, but I can guess.” “I don’t see any icon indicating where my player is.” “I wish I had a legend that explained like what the different icons meant.” “It’s almost like I need a map. I don’t know where to go.” “The map seems wrong because I couldn’t find the fifth stash with the help of the map.” One playtester, after a long session of being lost on a large map, summarized it cleanly: “I don’t have a mini map, so I kind of just walking around places I’ve already been before, not really knowing where to look next.”
The four ingredients of a working map are not negotiable. A “you are here” marker. A legend that names every icon. A marker on the next objective. The ability to update when the state of the world changes. If your map is missing any of those, your map cannot answer “where am I and where do I need to go,” and your map is decoration.
Pattern 4: Win conditions the player has to reverse-engineer
In dozens of sessions, the tester reached what looked like an end state and could not tell whether they had won, lost, or were supposed to keep going.
“Did I win? What does this mean now? Did I win? Does this just go on forever is my question.” “Did I clear the level? Is the objective just to survive?” “If enemies keep spawning, what’s my win condition?” “How many spores do we need? Ten thousand?” “Up to round eight. No indication of what score we’re playing to exactly.” “I don’t know if there’s a quota for each day or how many deliveries I have to complete.” One tester reached level 10.1 in a fire-growing game, paused, and said: “I had reached 10.1 fire level, which I thought was what you were supposed to do. But I didn’t win.” Another finished an entire level at 93% trash cleared and noted: “I was able to complete a level with only 93% trash cleared, so the threshold might be 90%, but this should be communicated to the player.”
State your win conditions numerically, in plain text, on the screen. “3 of 5 ghosts returned.” “Reach 1000 food.” “Day 2 of 5.” Players who can see a target play with focus. Players who cannot, drift.
Pattern 5: Collectibles you are hoarding for unknown reasons
The player keeps picking things up. The game keeps making a happy little noise. Nobody has explained why.
“Why am I collecting spoons? Game, please tell me things.” “I still don’t know what stars are for.” “I haven’t been able to open a single thing with a key so far unless I’m blind or missing something.” “I don’t know what these open. I’ve yet to find a thing that needs these to be opened.” “I’m curious what the keys will be used for. I haven’t found a use for them yet.” “I don’t actually know the point of the game. I know it says to collect keys, but I don’t know how you earn the keys.” “I’m also not sure what to do with the light level, if anything.” One tester noted that anything they collected did not show up in a list or in the UI at all.
Every collectible needs a one-line tooltip on first pickup. What is this? What does it unlock? What is it used for? Keys, stars, coins, spores, shards, tokens, gems, gas, ginger. If the player is hoarding something and does not know why, that is a design bug, not a mystery.
Pattern 6: Stale hints, missing quest logs, and forgotten objectives
The game told the player what to do. The player skipped the dialogue. Or got distracted. Or paused for dinner. Or solved the puzzle and the hint did not update. Now the hint system is actively misleading.
“The pie hint didn’t change, which would be pretty frustrating… it’s still about this locked one I already got.” “I’m surprised you’re still showing me that hint. Just because I’m past that.” “There is no quest log or anything.” “It just tells me what to do. It doesn’t give me a hint like where the area could be.” One playtester asked for “some kind of quest log… so you don’t forget if you pick up the game a bit later.” Another, on a strategy game with one-time campaign briefings, told us: “Campaign objectives are only conveyed when you first go into the game, and not in-game.” A third skipped a dialogue and said: “I just skip through it and I end up missing what I’m supposed to be doing.”
Players skip dialogue. Players miss intro cutscenes. Players come back from a meal break and have forgotten. They need a source of truth. Give them an objectives screen accessible from the pause menu, and update it the moment their state changes. A hint that points at a puzzle the player already solved is worse than no hint, because it actively erodes their trust in the system.
Pattern 7: Rules you can only learn by failing
This is the failure mode that makes players quit. The game has a rule. The game does not tell you the rule. You break the rule. You lose progress, sometimes irreversibly.
“I mistakenly killed the guy with the card. I had to restart.” (The guard was the only source of a required keycard.) “Oh sabotage ah okay never mind I just wasted so much ammo for nothing.” (The mission required a specific sabotage interaction, not just destroying structures.) “There is a permadeath situation. I feel like that wasn’t explained unless I’ve missed it.” (Cards in this deckbuilder were permanently lost on death.) “Oh, because we don’t need to defeat him, we just need points, but we need a lot of points.” (The boss was a points race, not a kill, and the player only worked it out after losing the first attempt.) “I missed something. I just did things out of order.” (Quest steps had a required sequence with no indication.)
If a player can soft-lock themselves, lose a run, or fail a mission by doing something the game never warned them about, you have outsourced the tutorial to failure. Some players accept that. Most do not. Front-load the warning, gate the action, or make the consequence reversible.
Pattern 8: Modes and systems with no explanation
This pattern shows up in games with multiple modes on the main menu, multiple race variants, an unlocked-later second mode, or a secondary system that just appears one day. The player clicks the new option, the screen changes, and there is no introduction.
“What’s Abyss? I just clicked the button without knowing what it was… there’s no explanation of what Abyss mode is.” “I still don’t understand what the difference from all these three are.” (About Practice, Qualification, and Race in a racing game.) “I would like to understand what the altars are and how to activate them.” (After multiple runs.) “When I first made it to this screen, there was no explanation of like what I was doing here.” (About a world map.) “She assumes I’ve completed class one… I have no idea what I’m supposed to do. I feel completely lost.” (After being moved into a second mode automatically.)
If your game has a “Practice / Qualification / Race” menu and your player cannot tell you the difference after picking one, you have not introduced your modes. The same one-screen tutorial principle applies here: every mode, system, and screen the player can reach needs a one-time explanation the first time they open it.
How to spot this in your own game
Hand the controller to someone who has not played your game. At three points during the first hour, ask them: “what is your current objective?”
If they hesitate, your objective text is not surfaced well enough.
If they say something that does not match what your design doc says, your objective text is ambiguous.
If they say “I have no idea,” you have shipped a maze.
A few more specific checks.
- Is the current objective visible on the HUD, or one click away in the pause menu? Not “was it said in the cutscene.” Is it visible right now?
- If the objective names a place, does the game point the player at that place? Not just name it. Point at it.
- Does the objective text update the moment the player’s state changes? When they pick up the keycard, does the game know they have it?
- When the player first picks up a key, coin, gem, or resource, does the game explain in one line what that thing is for?
- Is there a way for the player to lose progress by doing something the game never warned them about? If yes: warn them, gate them, or make it reversible.
- Does your map have a “you are here” marker, a legend, and a marker on the next objective? If not, your map is decoration.
- For every game mode, system, and menu the player can reach, can they describe what it does after one minute of using it? If not, that mode is unintroduced.
The fix
Keep the current objective on screen. In a corner, under the minimap, or one hotkey away. If the player has to ask “what am I doing?” your UI has already failed.
When an objective names a place, point at that place. Waypoints. Compass arrows. Highlighted doors. Map markers. If your design philosophy forbids markers, you need a real, tested alternative: lighting, sightlines, landmarks, NPCs that physically gesture in the right direction. And you need to verify in playtest that the alternative actually works on someone who has never seen the space.
State win conditions and thresholds numerically. “3 of 5 ghosts returned.” “Reach 1000 food.” “Day 2 of 5.” We watched players reach 93% cleaned, wave 10, fire level 10.1, and a specific score, and ask out loud “did I win?” because the game never told them what the target was.
Explain every collectible the first time the player picks one up. A one-line tooltip. What is this? What does it unlock? Keys, stars, coins, spores, shards, tokens. If the player is hoarding something and does not know why, that is a design bug.
Warn the player about irreversible or costly requirements before they can fail them. If killing a specific enemy locks out progression, do not let the failure be the tutorial. Front-load the warning, gate the action, or make the consequence reversible. “Discovery through failure” is a beautiful design phrase that, in practice, makes players quit your game and refund it.
Give the player a map that works. Their location. A legend. A marker on the next objective. If your map cannot answer “where am I and where do I need to go,” rework it. If you cannot rework it, remove it. A broken map is worse than no map, because the player keeps trusting it.
Add a quest log or objectives screen accessible from the pause menu. Players skip dialogue. Players miss intro cutscenes. Players come back from a meal break and have forgotten. They need a source of truth. Give them one, and keep it up to date.
Introduce every mode and system the first time the player opens it. If you have three race variants, name what is different. If your game has a meta-progression layer, explain it the first time the player reaches it. Do not assume the menu name is enough. “Abyss” is not a tutorial.
What “fixed” looks like
A tester three hours into your game can tell you, without pausing, what they are doing right now, where they are going, and how they will know they are done. They never feel the lurch of “wait, what was I doing?” When they open the map, the map tells them something useful. When they pick up a weird purple stone, they get one sentence of explanation and the stone makes sense.
They are not exploring because they are lost. They are exploring because they want to.
That is the bar.
Get the full book
This is one of twenty chapters from our book Top 20 Indie Game Development Mistakes: What Your Indie Game Is Getting Wrong (And How To Fix It). The other nineteen mistakes (poor onboarding, stale hints, broken navigation, overtuned difficulty spikes, audio problems, and more) are covered at the same depth, with the same evidence base of real playtests and real players.
You can download the full book as a free PDF at weplaytestgames.com/book.
If you want to see your own game in our data with a passing grade on every one of these twenty checks, that is what we do. A one-hour professional playtest costs $20, and you get the transcript, the video, and the report. Ship something you would not be embarrassed to hand to a stranger.