METHOD / RESPONSIBILITY / REVIEW
Street Lab
Neomod Studios starts with a place the player can occupy. A network diagram becomes interesting when it belongs to a cabinet in an exposed street, a service desk expecting a handover or a lift that will not remain available forever. Our concept work connects those physical situations to limited fictional systems. The aim is to make a decision readable before making its presentation spectacular.
| Route design asks where the body is |
The route-design role traces entry, working position and departure. It checks whether a player can see enough of the area to form a plan and whether a change in that area explains a new risk. A route should remain meaningful when the neon lighting is removed from a sketch. If a corridor only works because an interface arrow tells the player where to go, the spatial explanation needs another pass. |
|---|---|
| Interface design asks what is actually known |
The interface role separates an observation from an interpretation. A connection can report that a branch changed without claiming to know why. A warning should identify the affected action and preserve enough context for the player to respond. We prefer a few traceable conditions to a single opaque risk score. The interface is fictional and deliberately avoids reproducing practical instructions for attacking real systems. |
| Art direction asks what deserves contrast |
The visual role uses magenta, cyan and restrained yellow against a dark city. It also decides where not to add detail. A working threshold needs a readable silhouette; a route edge needs separation from its reflection; a quiet shelter needs room for the eye to rest. Concept art is evidence of a proposed visual direction, not a screenshot of a completed game. We label development stages accordingly and do not invent release dates, awards or player reviews. |
| Review asks whether the explanation survived |
The editorial role compares the intended decision with the page or prototype that communicates it. Can someone identify the fallback route? Can they tell which condition ended a permission? Can they distinguish a partial result from an unexplained failure? These questions belong in the change record with their unresolved assumptions. The two concept dossiers use different pacing so that a shared standard of clarity does not become a shared mission template. |
