Library
On Writing and Worldbuilding, Volume I · 2 of 13
On Writing and Worldbuilding, Volume I
Fiction Writing CRITICAL

The Depth Gap and Integration Principle

On Writing and Worldbuilding, Volume I Timothy Hickson
depth-gap integration craft-philosophy how-not-what functional-storytelling

Problem This Solves

Most writing education suffers from what Timothy Hickson calls the "Depth Gap" -- advice that tells writers what to do but never explains how or why. Writers are told to "introduce your main character" or "open with a hook," but these are things virtually every book already does. The real craft question is how to construct a hook that serves the story's larger structure, or how to introduce a character in a compelling way. Without that mechanical depth, advice is not actionable.

This shallow approach also breeds a second problem: story elements treated as decoration rather than function. Prologues exist because "fantasy novels have prologues." Magic systems exist because "fantasy needs magic." Worldbuilding details pile up because the author finds them interesting. The Integration Principle counters this by demanding that every element -- from magic systems to fictional empires to exposition -- must be functionally integrated into the narrative, serving character development and conflict rather than existing as ornament.

Key Principle

The Depth Gap: Writing craft education overwhelmingly names techniques without explaining their mechanics. Knowing what a hook is does not help a writer construct one. Knowing what foreshadowing is does not explain which of six distinct techniques to deploy or when. The gap between labeling and executing is where craft actually lives.

The Integration Principle: Every story element must have a functional narrative purpose. A magic system must shape character arcs and conflict, not just exist as worldbuilding flavor. A religion must interconnect with culture, politics, and economy. An empire's mechanics must generate story tension. Hickson calls this the "Architect Allegory" -- every element in the structure must bear narrative weight, or it should be removed.

These two ideas form the book's thesis: close the depth gap by teaching how techniques work mechanically, and ensure every technique serves the story's integrated whole.

Good Examples

  • Hard magic systems (Sanderson's Allomancy): The rules of Allomancy are explained in detail because the magic directly solves problems in the plot. The reader's understanding of the system is proportional to its role in resolving tension -- this is functional integration. Exposition about the magic passes the "problem-solving test" because it helps characters (and readers) navigate conflict.

  • Rick Riordan writing Percy Jackson: Riordan originally wrote Percy Jackson and the Lightning Thief for his son Haley, who has ADHD and dyslexia. This illustrates that the only real obligation is to write the story you wish to read (or share). The depth of the craft serves the story's purpose, not an external checklist of rules.

  • The Backwards Planning Method: By starting from the climactic scene and working backward to derive core scenes, then applying three-act structure, every scene exists because the ending demands it. Nothing is decorative; everything is integrated by design.

Bad Examples

  • "Five Tips For" style content: Surface-level advice such as "introduce your main character early" or "give your villain a motivation." These tips are technically correct but functionally useless -- every published novel already does these things. The advice names the technique without explaining the mechanics of execution.

  • Decorative worldbuilding: Magic systems, religions, or political structures that exist in isolation from each other and from character arcs. A magic system that has no bearing on how characters solve problems, or a religion that never intersects with politics or personal conflict, fails the integration test.

  • Magibabble: Saying a lot but meaning very little about how magic works. Elaborate terminology and lore that sounds detailed but provides no functional understanding the reader can use to anticipate or evaluate story outcomes.

Key Quotes

"These are fine tips to give, but they aren't actually helpful. Okay, a writer has to introduce their main character, but how do we go about doing that in a compelling way?" -- Timothy Hickson, Preface

"Not videos on topics too broad to be helpful, but educational and detailed breakdowns of very niche and specific elements of storytelling with clear, coherent, and in-depth discussions about how we might write a satisfying story." -- Timothy Hickson, Preface

"My personal position is that an author owes no obligation in their work other than to write the story they wish to read." -- Timothy Hickson, Preface

Rules of Thumb

  • When evaluating any writing advice, ask: does this explain how to execute the technique, or does it just name the technique? If it only names it, the advice is shallow.
  • For every story element you create (magic system, political structure, religion, prologue), apply the integration test: does this element serve character development, conflict, or thematic resonance? If it serves none of these, it is decoration.
  • Use the problem-solving exposition test: if a piece of information does not help characters solve or understand a conflict, it does not belong on the page.
  • Design constraints before powers. Limitations, weaknesses, and costs generate more story than abilities do (Sanderson's Second Law).
  • Treat writing techniques as tools for making stories more satisfying, not as commandments. There is no objectively correct way to write.
  • Seek specificity over breadth: a deep understanding of one narrow technique is more useful than shallow familiarity with twenty.

Related References