Week 11: The Book Knows It’s a Book

Choose one part of the book readers normally ignore, and make the story need it.

Before the session

Bring simple materials for a short three- to five-unit prototype — paper, pens, scissors, cards, or your phone. You’re making one book feature necessary to the story, not building a fully bound object.

The Book Notices Itself

This is the main studio activity. Choose one normally ignored book feature:

Build a short prototype — three to five states, pages, spreads, or components — where that feature becomes indispensable to the story rather than decorative. Work through:

  1. Normal role — what would this feature normally do?
  2. Recognition — how does the story, character, narrator, or reader become aware of it?
  3. Use — how does the story actually use the feature?
  4. Consequence — what changes because the feature exists?

Stay with your one chosen feature rather than combining several — a single feature that the story genuinely needs is worth more than several features that are each merely noticed.

You don’t need a professionally bound physical book. Folded paper, loose pages, cards, rough mock-ups, simple digital screens, collage, typography, drawing, or photography are all legitimate, as long as the prototype communicates enough of the physical relationship to test the idea.

Studio check

Once you have your prototype, briefly answer:

  1. Which normally ignored feature did you choose?
  2. What is its normal role?
  3. How does the work acknowledge it?
  4. What happens because of it?
  5. What breaks if you remove it?

Question 5 matters most. If removing the feature leaves the idea working exactly the same, the feature is probably still decoration — revise until it is genuinely necessary.

This Week’s Misbehaviour — Use Something Nobody Reads

A separate 15–30 minute experiment from The Book Notices Itself — not another complete prototype.

Choose one small piece of book infrastructure that readers usually treat as purely functional — a page number, a contents-like label, a title, a margin, a running header, an end mark, or another small structural element. Make one quick page or spread where that element unexpectedly changes how the page is understood.

Briefly answer:

  1. What would the reader normally ignore?
  2. What happens when they notice it?

Keep it rough and small — this doesn’t need a full metafictional narrative.

Afterwards

Add your prototype and your Use Something Nobody Reads note to your Misbehaviour Toolbox. Week 10 had a character resist what the narrator, text, reader, or story expected. Week 11 asked the book to acknowledge the system that contains all of them. This is the last week that introduces a new technique — next week is about deciding which of the tricks you’ve collected are actually worth keeping.

The spec

What you bring to the session. Written so a reader can tell whether it has been met without asking you.

  • you have chosen one normally ignored book feature and built a short prototype where the story needs it
  • your prototype shows the feature's normal role, how the work recognises it, how it is used, and what changes as a result
  • the feature passes the removal test — taking it out damages the idea, it doesn't just remove decoration
  • you have completed this week's Misbehaviour, Use Something Nobody Reads