How to Explain an Interactive Game to a Friend: Describe What You Do
“Lots of choices” does not explain play without concrete actions. Use role, goal, input, feedback, constraints and how a run ends to describe an imaginable experience through a fictional lost-letter game.

Start with what your friend does in the interactive game
To explain an interactive game, begin “Who do you play, what must you achieve, and which actions move you forward?” Add visible changes after actions, limits and how a run ends. Your friend can then judge whether they want to do those things.
“Lots of choices” and “an immersive story” describe your feelings, not whether they will read, search, control a character or compare clues. Replace “many choices” with “decide which traveler to ask first, then where to search for lost property” to give an imaginable activity.
“Interactive game” is a broad working term, not an independent type under a unified standard; most games already involve interaction. We practice introductions with narrative works, but can also fill in movement and dodging in action games or rotating and combining in puzzles.
Separate layers: text and illustration are presentation media; choosing whom to question is interaction design; recovering an item is a goal; only three investigations is a rule. They can describe one work together without an exclusive classification box. Pause and fast-forward do not directly count as in-world decisions.
Build an experience card with six fields
Fill the card before composing the introduction. Prioritize observable facts over “rich,” “free” or “stunning.” Copy these questions and replace answers for another work.
| Field | Question to answer |
|---|---|
| Role | Who am I, and in what capacity do I participate? |
| Goal | What do I hope to achieve this run, and what counts as achieving it? |
| Input | Which concrete actions do I repeat, and how do I submit them? |
| Feedback | What new information or changes appear after actions? |
| Constraints | What limits actions or uses attempts? |
| How a run ends | When does it stop, and how does it close if the goal is unmet? |
The role need not be a named protagonist; it can be a dispatcher or an operator without a story identity. Keep goal and ending separate: “Find the letter” is a goal, while “Finish after submitting the result” explains flow. The letter may remain unfound at submission.
Pair input with feedback. Add “receive a spoken clue” to “ask a traveler.” “Click buttons” alone does not explain what the buttons do. If a field only permits “it depends,” acknowledge unconfirmed information rather than invent rules.
Example: fill in The Lost Letter in the Waiting Room
The Lost Letter in the Waiting Room is an original fictional teaching example. Rules, events and copy illustrate writing, not real user cases, tested results or product features.
A small station is closing, and a traveler asks a temporary attendant to find a missing letter. Text and static illustrations present the story; location lists and dialogue options accept actions. First define the example’s rules so the introduction can be checked.
| Field | Example entry |
|---|---|
| Role | Temporary attendant helping a traveler find a lost letter |
| Goal | Find and return an envelope matching the traveler’s description |
| Input | Select a traveler to question or a location to search; reread collected clues anytime |
| Feedback | Questions add spoken records; searches show items or empty places; investigation attempts decrease |
| Constraints | Three investigations total; each question or search uses one; reading records is free; no real-time countdown |
| How a run ends | Submit early if desired; after all three attempts, you must submit a found envelope or report not found, then end |
The approaching closure supplies story context; investigation count is the actual limit. Do not call it a speed challenge or imply slow reading causes failure. Submission means returning a found object or reporting results, not guessing a location and calling it found.
Turn the card into an introduction, then walk through
This description keeps gameplay information but withholds the hiding place:
In this text-and-illustration interactive game, you are a temporary attendant helping a traveler recover a letter before the small station closes. Select travelers to question or places to search, then compare clues to choose your next step. Each question or search uses one of three investigation attempts; rereading records costs none, and there is no race against time. Return a found envelope early if you wish. When attempts run out, submit your result; the story ends even if you have found nothing.
Now reveal a fictional path to check whether the description holds together. The opening gives the owner’s description: a white envelope with a red line on the seal. Investigation one asks the cleaner, who says “Someone just put the loose things from the bench into locker seven.” Two attempts remain.
Investigation two searches locker seven and finds a blue suitcase containing a white envelope. One attempt remains. Inspect its description free of charge, confirm the red seal line matches and choose to return it. The ending shows the owner confirming and thanking you; the run ends without spending the last attempt.
Another path searches the empty bench first, then asks the cleaner and searches locker seven. The same goal need not require the same order. Searching three unrelated places instead requires reporting not found. The introduction must include that ending, not promise “You will eventually solve the mystery.” These are rule illustrations, not play records.
Shorten for the conversation and restore details when misunderstood
If asked only “How do you play?”, say “You’re an attendant with three questions or searches to find a lost letter, then return it or report that you have not found it.” Add selection controls, free rereading and no countdown when asked about operation and pacing. The six fields are a reminder card, not a script to recite every time.
For someone focused on controls, start with selection, reading and comparison. For story interest, explain why the attendant helps, then actual actions. Order can change; limits cannot disappear to make the pitch sound exciting.
Three phrases distort expectations. “Every click changes fate” exaggerates rereading; “Explore the station freely” hides fixed locations and three attempts; “Multiple endings to unlock” skips ordinary player activity. Replace them with concrete actions, explicit scope and honest closure for a checkable introduction.
Review on paper: circle executable verbs, mark one visible response and locate the unsuccessful ending sentence. Ask a friend to restate the first step, what it reveals and what happens when attempts run out. This is a suggested review method, not one this article has performed or validated.
The card explains play tasks; it cannot prove fun or replace a complete review. Do not guess unseen branches or features to fill fields. Clearly stated known actions and acknowledged uncertainty help a friend judge better than a vague label.


