settled-reach/docs/workshops/wheres-the-fun/lead-interview.md

title, description, type, status, workshop, agent, round, created

title	description	type	status	workshop	agent	round	created
Round 2: Interview Transcript	Full round 2 interview transcript with Jeroen on v0.1 playtest experience	workshop	archived	wheres-the-fun		2	2026-03-05

Round 2: Interview Transcript

Where's the Fun? Workshop | 2026-03-05

Interviewer: Workshop facilitator (consolidated questions from 9 agents) Interviewee: Jeroen (designer, first playtester of v0.1) Format: Interactive interview, questions presented in thematic groups

---

Group 1: The Vision and the Wall

Q1 (Ozzie): Close your eyes. The game is finished and fun. What are you DOING?

Jeroen: None of the offered frames (watching/realizing, feeling implicated, social manipulation) fit. "I want to live in the world and have impact. Own businesses, build relationships, hunt enemies, defend against enemies, build property, get a job (which could be detective). My ideal game would be playing The Sims Rimworld-style, from a first-person perspective (well third, but single character)."

Key finding: The vision is a life sim from a single-character perspective. Detective is a job you might have, not the core loop. The v0.1 vertical slice built around detective/smuggler was a narrowing that lost the broader vision.

---

Q2 (Gore): What were you actually DOING moment-to-moment in the playtest?

Jeroen: Mix of all three offered options — cycling between aimless walking, fighting the UI, and trying to process information.

Key finding: The actual playtest verb was "navigate confusion." None of the intended verbs (observe, investigate, engage) were operating.

---

Q3 (Gestalt): At minute 2, what did you think you were supposed to do?

Jeroen: Faint signal — there was something there but too weak to act on.

Key finding: The systems weren't completely silent. Something was reaching the player, but below the threshold of actionability. This suggests the feedback channels exist but are severely underpowered.

---

Group 2: The Confusion Type

Q4 (Gestalt): Was it "I know something is here" or "I have no idea what I'm looking at"?

Jeroen: "Mostly B with a hint of A, layered with the looming realization that the narrow scoping for v0.1 was actually a bad frame to work towards since we lost track of the broader brief."

Key finding: Predominantly uniform opacity (bad confusion), not engaged mystery (good confusion). But the deeper realization was meta-level: the playtest wasn't just confusing in the moment — it revealed that the v0.1 framing itself was wrong. The narrow detective scope had lost track of the life-sim vision.

---

Q5 (Araminta): Were you unable to READ the screen, or unable to ACT on what you read?

Jeroen: Both equally.

Key finding: Both attention management (visual hierarchy) and agency (what to do) were failing simultaneously. Araminta and the systems designers both have work to do, but visual hierarchy is needed regardless of the design reframe.

---

Group 3: The Emotional Loop

Q6 (Paula): Did Phase 1 feel like a stable world you belonged to?

Jeroen: "I had no idea what dot was who, or to be honest that they were people at all (had I not been involved in the sprints running up to this one)."

Key finding: The NPCs did not register as human beings. They were dots. The entire emotional stack (attachment -> moral arc -> complicity -> dual-lens reveal) has no foundation because the entities on screen are not legible as people. This is a more fundamental failure than anyone anticipated — not "the emotional loop didn't fire" but "the preconditions for recognizing there ARE characters didn't exist."

---

Q7 (Paula): Did any NPC feel like a person with stakes?

Jeroen: No one. No NPC registered as a person. They were all moving tiles.

Key finding: Zero NPC attachment. The moral arc literally cannot start. The Phase 1-to-2 gates (observing Naia's stress, Maret's anxiety) require the player to be watching specific people closely — but the people aren't legible as people.

---

Q8 (Gore): Did the complicity threshold ever fire?

Jeroen: "Seen the previous answer that the dots did not register as anything but dots, this question assumes way too much engagement to even start speaking in those terms."

Key finding: The question was premature. Complicity requires recognizing characters as people, recognizing your relationship to them, and then feeling implicated. The playtest never reached step one. The complicity theme exists only in design documents, not in the player experience. This is not fixable with better monologue timing or content — it requires the characters to become visible and legible first.

---

Group 4: The Monologue System

Q9 (Mellanie): Could you connect monologue lines to their triggers?

Jeroen: "It felt like it wanted me to know something, but no idea what it was connected to, what triggered it, and even how to relate the messages to each other since they were coming in scattered."

Key finding: The monologue system was perceived as intentional communication (it wanted to tell the player something) but failed on three axes: no spatial anchor to trigger source, no causal legibility, and no inter-message continuity. The lines couldn't build on each other because there was no thread connecting them.

---

Q10 (Mellanie): Did the monologue ever feel like your character's thoughts?

Jeroen: Hard to tell — given that the dots weren't people and the world wasn't legible, the question isn't answerable from this playtest.

Key finding: The monologue-as-interiority question is unanswerable until the floor exists. If the world isn't a place and the NPCs aren't people, the character's thoughts about them can't register as interiority. The system needs to be re-evaluated after the fundamental legibility problems are solved.

---

Group 5: Systems & Architecture

Q11 (Tyre): Was monologue the only planned channel for the knowledge graph?

Jeroen: "Always planned for more, like the mystery board with the wires connecting topics, a glossary of characters, a journal tracking communications, tele-communications, insert icons, AR type overlays on the world. The monologue was supposed to be a reasoning nudge and summary tool in the later stages. We descoped for v0.1, which brings me back to that v0.1 was not framed correctly. We learn this and do better for v0.2, possibly with a whole new game loop."

Key finding: The full information architecture was always planned — mystery board, character glossary, journal, comms, insert icons, AR overlays. Monologue was never supposed to carry the feedback burden alone; it was meant as a reasoning nudge in the later stages. The v0.1 descoping stripped the player of all their planned tools and then asked them to play. This confirms the scoping error: v0.1 didn't just narrow the story — it removed the player's interface to the world.

Process note: Jeroen explicitly requested that each Round 3 agent receive the full verbatim transcript of this interview, not just summaries. "I want all finesse communicated."

---

Q12 (Tyre): Where on the objectives spectrum? Is "no objectives" a principle or scope decision?

Jeroen: "I think the underlying reasoning was that, for replayability, the information systems needed to be framed in-world. This way different jobs, inserts, character budgets would have different tools (that they could aspire and grow towards) and not a GTA-style line leading to objective and large box that checks off mission goals. In fact missions should have varying levels of success. Or even failure declared and sold as success. There would be consequences (enemies, lower pay, no pay, getting fired, an innocent killed or in jail) but it would be possible."

Key finding: "No objectives" was never a design principle against feedback. It was a commitment to diegetic, in-world information tools that vary by job/insert/character build. Different characters would have different HUDs essentially — a detective's neural insert surfaces different information than a smuggler's street contacts network. The absence of objectives in v0.1 was the absence of these diegetic tools, not an intentional design choice for silence. Additionally: missions should have spectrums of success/failure with consequences, not binary pass/fail. A mission can "fail" and the player continues with consequences. This is a life-sim philosophy, not a mission-game philosophy.

---

Group 6: Verb System & World Legibility

Q13 (Gestalt): Did the verb priority fight the detective loop?

Jeroen: Didn't get that far — never reached the point of trying to observe specific NPCs. The dots weren't legible enough as people to target.

Key finding: The verb priority spec contradiction (Talk > Observe at close range) is a real design issue, but it's irrelevant to the current playtest because the player never reached the interaction layer. You can't have a verb problem when the entities aren't recognizable as interactable.

---

Q14 (Miri): What kind of place did Sova Transit feel like?

Jeroen: Game level with dots. No sense of place at all.

Key finding: Zero environmental storytelling landed. The setting design exists in documents but not in the player experience. Sova Transit's social geography (class dynamics, functional clusters, faction pressures) is invisible. The player saw a tile grid with moving sprites.

---

Q15 (Nigel): Should the storyteller detect first playthrough and pick a higher-pressure seed?

Jeroen: "Different approach needed. In fact, falling into a mission may be the wrong place to start, since so much of the character will need to evolve from where they start. A detective playthrough should basically be: player starts a game with a shortcut bookmark of starting as law enforcement (or any of the other ones. I feel we need to stop framing everything into the detective-smuggler tension, since that brought us knee deep in the wrong place) but anyways, as an example: after picking that bookmark, the game should start with onboarding at their new job, the enabling one by one of their new inserts, their weapon and weapon qualification training. Tycoon would start with a ping that their bank wants to talk at which point they are handed an inheritance (starting capital) and then the tools to start making investments and buy assets."

Key finding: This is the biggest reframe of the interview. The storyteller seed question is moot because the entire starting premise is changing. Instead of "which variant of the detective mission should you start with," the answer is "you shouldn't start in a mission at all." The game should start with CK3-style bookmarks: choose a career path (law enforcement, tycoon, smuggler, etc.), each with its own onboarding arc that teaches the tools organically. Detective is just one bookmark. The detective-smuggler tension is a storyline within the world, not the frame for the entire game.

---

Group 7: Remaining Questions

Q16 (Ozzie): Was the frustration "not built yet" or "wouldn't have cared even if it was"?

Jeroen: "C... with everything, it felt like the wrong game. I do really want the storylines of the gate builders and the tension between smugglers and the law be in the game and a lot of the patterns would still fit, but the focus felt myopic."

Key finding: Neither "not built yet" nor "wouldn't have cared" — it's "wrong game." The existing storylines (gate builders, smuggler/law tension) should survive as content within a broader world, but the v0.1 framing that made them the sole focus was myopic. The patterns (knowledge graph, perception system, monologue, moral arcs) fit into the broader life-sim vision — they just can't be the entire experience.

---

Q17 (Araminta): Would a 3-tier visual language have given you a foothold?

Jeroen: Would have helped.

Key finding: Even with all the fundamental problems, visual hierarchy matters. Araminta's argument holds: you can't evaluate any loop until the player can read the screen. Visual hierarchy is needed regardless of the design reframe. This is one thing that carries forward directly into v0.2.

---

Q18 (Tyre): Pull verb display forward to v0.1?

Jeroen: "This feels like a patch with the wrong priority. I think this and a lot more is needed."

Key finding: Small patches to v0.1 are the wrong frame. The scope of change needed is larger than verb display or monologue tuning. v0.2 needs to be designed from the new vision, and individual v0.1 fixes should be evaluated in that context.

---

Interview Summary: The Five Revelations

1. The vision is a life sim, not a detective game. Single-character Sims-meets-Rimworld. Detective is one job among many (tycoon, smuggler, law enforcement). The v0.1 detective/smuggler framing was a scope narrowing that lost the broader vision.

2. v0.1 was framed wrong. The descoping didn't just narrow the story — it stripped the player of all their planned information tools (mystery board, journal, AR overlays, comms) and then asked them to play with monologue alone. The playtest failure was predictable in retrospect.

3. The world isn't legible. NPCs are dots, not people. Sova Transit is a game level, not a place. No emotional loop can run on this foundation. The character legibility problem is more fundamental than anyone anticipated.

4. "No objectives" was never the principle — diegetic tools were. Different jobs/inserts provide different information interfaces. The absence of feedback in v0.1 was the absence of these tools, not design purity.

5. The game should start with job onboarding, not a mission. CK3-style bookmarks into career paths, each with onboarding that teaches tools organically. This replaces the storyteller seed variant system as the first-run structure.

What Survives

• The simulation engine (routines, perception, knowledge graph)
• The storylines (gate builders, smuggler/law tension) as world content
• The moral arc patterns (but as consequences within a broader life, not the sole focus)
• The monologue system (as a reasoning nudge, not the primary feedback channel)
• The visual hierarchy work (needed regardless)
• The diegetic information tool vision (mystery board, journal, AR overlays)
• The asymmetric information mechanic (different characters know different things)

What Changes

• The core loop: from "detective puzzle" to "live in the world, have impact"
• The starting experience: from "mission variant" to "job onboarding bookmark"
• The feedback architecture: from "monologue only" to "full diegetic tool suite"
• The vertical slice scope: from "one detective case" to "one career arc with world interaction"
• NPC presentation: dots must become people (art, names, behavior legibility)
• Place presentation: tile grid must become an inhabited space