Reflecting on the '36 Stratagems' Series: Shifting from Reactive to Strategic Narratives

After completing the initial sixth of a planned 36-story series, a developer paused to reflect on the narrative patterns emerging from their work. This introspection revealed a critical evolution in storytelling: a move from characters who react to problems to those who proactively shape outcomes. The shift, inspired by the ancient '36 Stratagems,' highlights how subtle changes in character agency can profoundly impact reader engagement and the perceived depth of a narrative.

What happened

After writing six stories in their "36 Stratagems" series, the developer conducted a self-assessment, a practice they maintain at significant milestones. This reflection was informed by an earlier experience with their "AI, Ego & Regret" series, which, despite individual story quality, eventually felt repetitive due to a consistent narrative engine: a system breaks, a protagonist fixes it, and their value is then recognized. This predictable structure, repeated 15 times, led to a sense of narrative staleness, even though each story ended in a win.

A pivotal moment occurred with story #15 of the old series, which introduced a character named Lena. Unlike previous protagonists who waited for the system to validate them, Lena was depicted as having agency from the outset, proactively "setting up the board herself." This marked a fundamental shift from technical problem-solving to strategic "mind games," where characters aimed to win through cunning rather than just reactive fixes. This experience solidified the developer's decision to move towards narratives centered on proactive strategic thinking.

The new "36 Stratagems" series explicitly embodies this proactive approach, with each of the first six protagonists employing a specific stratagem—such as "Deceive the Heavens to Cross the Sea" or "Loot a Burning House"—to achieve their objectives. The series is designed for characters to cross paths later, leading to wins and losses based on their strategic plays. Notably, story #4, "Wait at Leisure While the Enemy Labors," garnered the most comments, indicating a strong reader resonance with its strategic themes of patience and observation.

Why it matters

This evolution in narrative strategy carries significant implications for creators, particularly those involved in developing long-form content or series. Over-reliance on a predictable problem-solution loop, even with diverse scenarios, can lead to audience fatigue and limit the perceived complexity of characters. By embracing proactive, strategically-minded protagonists, creators can foster deeper engagement, drawing readers into the intricate "mind games" and tactical decisions rather than merely observing technical resolutions.

For developers and builders, this mirrors the transition from purely reactive debugging to proactive system design and strategic planning. Just as a compelling story benefits from characters who "set up the board themselves," a successful project benefits from teams that anticipate challenges and strategize solutions rather than solely responding to crises. This approach not only makes the creative or development journey more engaging for the practitioners but also for the audience, whether that audience is a reader, a user, or a stakeholder.

The strong reader response to story #4, which highlighted the value of strategic patience and allowing data to become its own evidence, underscores the power of indirect influence and timing. It suggests that narratives—and real-world projects—that explore the nuances of hidden information and carefully timed actions can resonate more profoundly than those focused exclusively on overt action or immediate resolution.

How to think about it

When approaching any creative or problem-solving endeavor, consider the agency of your central actors. Are they primarily reacting to external stimuli, or are they actively shaping their environment and anticipating future moves? For content creators, this means consciously designing character motivations and plot points around strategic intent rather than mere response. For developers, it translates to moving beyond bug fixes and feature requests to architecting systems that proactively address future needs or even influence user behavior. Frame challenges not just as problems to be solved, but as "boards" to be set up, where foresight and indirect action can yield more impactful outcomes than direct confrontation. This perspective encourages a more strategic, long-term view, fostering narratives and solutions that feel more dynamic and less predictable.

FAQ