settled-reach/docs/workshops/wheres-the-fun/round1-araminta.md

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

title	description	type	status	workshop	agent	round	created
Round 1: Diagnosis — Araminta (Visual Designer)	Araminta's visual design diagnosis questions on fog, HUD, and signal-to-noise	workshop	archived	wheres-the-fun	araminta	1	2026-03-05

Round 1: Diagnosis — Araminta (Visual Designer)

Workshop: Where's the Fun? Date: 2026-03-05 Focus items: 3 (fog edge), 4 (stance indicator), 6 (HUD polish), 8 (context menu), 10 (signal-to-noise)

---

Framing

Items 3, 4, 6, and 8 are clearly visual execution problems — broken rendering, unplaced UI, unstyled chrome. They're real and fixable. But item 10 (signal-to-noise) sits at a harder boundary: it's about attention management, which is fundamentally a visual design responsibility. Too many simultaneous signals of equal visual weight means the player has no way to know what to look at first.

The question I'm trying to answer: is the fun gap something visual design can fix, or is it something visual design is masking?

---

Questions

Q1: When you hit the testing wall, what were you looking at?

Item 13 says you couldn't figure out what to do. I want to know where that confusion was located — on screen, or in your head.

When you sat there not knowing how to proceed, was the issue:

• (A) You could see things happening (fog moving, NPCs walking, monologue firing) but nothing told you which of those things deserved your attention?
• (B) You understood what everything on screen was, but had no idea what to do about any of it?

Option A is a visual hierarchy problem — fixable with design. Option B is a mechanical/agency problem — visual design can't solve it, it can only decorate the confusion. I need to know which wall you hit.

---

Q2: If the screen had a clear visual tier — danger in red, opportunity in amber, ambient in grey — would that have been enough to give you a foothold?

Item 10 (signal-to-noise) is the one item where I have the most direct leverage. If I establish a strict three-tier visual language for all feedback (critical / relevant / ambient) and enforce it across monologue text, HUD elements, sound indicators, and NPC behavior cues — would that give you enough priority information to start making decisions?

Or would you still be standing there thinking "okay, I know this is important — but I still don't know what I'm supposed to do with it"?

This tells me whether item 10 is a design problem I own, or whether it's downstream of a missing feedback loop that no amount of color-coding will fix.

---

Q3: The context menu and stance indicator are placeholder-styled — floating text, no chrome. Did the lack of visual treatment make those elements feel untrustworthy, or was it the information inside them that was confusing?

Items 4 and 8 are my clearest short-term tickets. But before I style them, I want to know which problem I'm solving.

If the stance indicator had an icon, a keybind label, and was anchored to the minimap frame — would you have understood what it was for? Or would it still have been opaque even with good visual treatment?

Same for the right-click menu: is "this looks like a debug tooltip" the problem, or is "I don't understand what these options mean or when to use them" the problem?

The answer changes what I build. Chrome on a confusing interaction makes it look intentional. That can be worse than leaving it obviously unfinished.

---

My Hypothesis

Strong art direction will not fix the fun gap — but it will clarify whether a fun gap exists.

Right now, the visual noise makes it impossible to tell if the player is confused because the mechanics are wrong, or because the mechanics are right and invisible. Establishing visual hierarchy (item 10) and anchoring UI to the world (items 4, 8) is not polish — it's diagnostic infrastructure. We can't evaluate the core loop until the player can read the screen.

The fog edge (item 3) is the only pure visual bug with no mechanical dimension. Fix it regardless.