New City
Novel, UX Methodology Applied to Narrative Architecture
Updated February 2026
Every novel I’d attempted before followed the same arc: strong concept, exciting first act, gradual loss of coherence as the complexity outran what intuition could hold. The same failure mode I’d seen in enterprise platforms and brand systems. Not a failure of talent. A failure of architecture.
The question: what if I built the novel the same way I build everything else?
Governing constraint. One rule, derived before any structural decision: revelation comes through understanding, not through winning. If the story argues that understanding is the mechanism, then a conflict-driven structure contradicts it at the level of form. Everything that violates the constraint is architecturally wrong, not stylistically off.
Narrative architecture as information architecture. Kishōtenketsu (起承転結) chosen because it sequences the reader’s perception, not events. Applied fractally: 4 acts, 4 beats per act, 4 sub-beats each. 64 atomic units. The same reader journey logic at every scale, from a single scene to the full arc.
Beat specs before prose. Each beat is specced before writing begins. Equivalent to wireframing before visual design. Reader state, prose register, sensory palette, and structural function all designed per beat. The spec captures the reader’s designed experience, not the author’s intentions.
Three prose registers as interface states. Environmental narrator (orientation). Close third (observation). First-person somatic (immersion). Register transitions are state transitions, specced in advance. The shift from watching Henka to being inside her nervous system is an information event, not a stylistic choice.
The constraint propagates through every layer: story structure, worldbuilding, discovery mechanic, character arc. If any layer contradicts the governing constraint, it’s wrong. That test applies everywhere.
This is also where something broke. Months of ideation distributed across dozens of parallel sessions. When those sessions closed, the fragments survived but the continuity didn’t. The thread connecting character naming to narrative structure to flooded subway canals was severed. That loss produced the Savepoint Protocol.
Active, slow-burning. Beat spec system developed and tested against Act 1. Structural specification intact.
This is how I work. If it sounds like what you need, let's talk.