Skip to main content

Story Moves: Arrangement as Inquiry

Research to Story (RTS) Prototype Feature

info

This feature is in development. Story Moves is a planned scaffold for the production phase of the RTS workflow. The exercise itself originates from workshop practice and is being adapted into the RTS application.

The Problem: Scripts Are Not Plans​

In academic settings, students are often asked to write a script for a podcast or video essay as the primary "bridge" between research and production. Faculty can assess the script as a written artifact, but this approach assumes that a polished script will naturally become a compelling multimodal work.

It rarely does.

Students arrive at editing software with words, but not with a plan. The script is aspirational text — important, yes, but detached from the temporal and sonic logics of audio composition. The editing interface then feels like a black box, a wall rather than a canvas. Faculty, in turn, often find themselves teaching "technical fixes" rather than guiding intellectual inquiry.

The Story Moves Solution​

Story Moves provide a scaffolded exercise between research and production. They ask students to reconceive their sources, arguments, and ideas as storyable units — discrete blocks of narration, evidence, and sound with a purpose in time.

A story move is:

  • A chunk of content: an idea, claim, event, or transition
  • Anchored in evidence: research, quotes, or media that can be heard, not just cited
  • Coupled with sonic choices: what the listener hears, and why it matters
  • Rhetorical: aimed at shaping the listener's journey, not just displaying knowledge

The critical insight is that Story Moves are not operating as a translation exercise. Students are not running their script through a multimodal version of Google Translate. They are not converting written arguments into audio form. They are doing something fundamentally more generative: discovering what their research can become when it meets a new rhetorical horizon.

By breaking research into story moves and arranging them, students confront questions that a script can never surface: What does simultaneity do to an argument? What happens when evidence is heard rather than read? What does pacing reveal about stakes? As Godard once observed, a story must have a beginning, middle, and end — but not necessarily in that order. Story Moves make that insight actionable.

Arrangement as Inquiry​

This exercise originates from workshop practice, where I've seen firsthand what happens when students stop trying to "translate" their writing and start composing with arrangement. The shift is profound. In the act of arranging story moves — deciding what comes first, what gets juxtaposed, what evidence sounds like rather than reads like — students routinely discover:

  • Simultaneity: Ideas that seemed sequential on paper can exist together in sound, creating resonance a linear script cannot produce
  • Pacing as argument: The rhythm of a piece carries meaning. Silence, acceleration, repetition — these become rhetorical choices, not technical afterthoughts
  • Non-linear structure: The "logical" order of a research paper is almost never the compelling order of an audio narrative. Arrangement forces students to find the story order
  • New demands on evidence: Sources that worked as citations on a page may not work as sonic material. Students often must return to their sources — or find new ones — when they confront what evidence needs to do in sound
  • The return to the question: Perhaps most importantly, the act of arranging frequently sends students back to the original research question itself, because the medium reveals gaps, tensions, and possibilities that writing alone could not

This is the core point RTS makes through Story Moves: the intellectual labor of the learner is not to figure out how to pour their writing into production software. This framing, production as a neutral delivery mechanism is, to be frank, the problem. The solution is to reframe it as a generative space where inquiry continues — and often deepens.

A story move, simply put, is an exercise of generative inquiry.​

Pedagogical Rationale​

Story Moves foreground a dimension of intellectual labor that is often overlooked: the cognitive and interpretive work of making.

At their core, Story Moves are for the student first and foremost. They function as a scaffold that:

  • Compels students to re-imagine what evidence they are presenting and how
  • Surfaces gaps in sources and invites new directions of inquiry
  • Forces a reckoning with the analytical resistance of an imagined audience
  • Encourages reflection on rhetorical decisions like pacing, sequencing, and sonic impact

Because Story Moves capture this generative process, they naturally become assessable artifacts that reveal genuine domains of scholarship.

Faculty, in turn, can see and respond to:

  • How students mobilize sources as sonic evidence
  • How students anticipate audience experience in their sequencing and sound design choices
  • How methodological questions arise from the act of making
note

The purpose of Story Moves is to scaffold making as legit scholarship. Assessment follows because the intellectual work is real. This also reframes production as more than an unimaginative technical hurdle, but as another layer of scholarly inquiry. (a core theme that informs this whole endeavor)

note

A longer treatment of arrangement as inquiry — including its relationship to rhetorical theory and compositional practice — is forthcoming on a separate site (and a separate but integratable app). This document focuses on Story Moves as they function within the RTS framework.

Story Moves and Invisible Literacies​

The Story Moves process scaffolds narrative planning, but it also does more: it surfaces the invisible but essential literacies of scholarly making that RTS highlights through Black Box Micro-Engagements (BBMEs).

Like BBMEs, Story Moves embody several interconnected pedagogical purposes:

  • Demystifying originality → showing that scholarly and creative work is relational, collaborative, and situated in networks of influence and support
  • Normalizing help-seeking → making it clear that gathering sound, editing clips, or seeking technical support is part of inquiry
  • Preparing for scholarly ethics → by tying each move to evidence and sound, students are continuing the work of acknowledgment, citation, and attribution practices
  • Reinforcing RTS philosophy → inquiry is reframing as much as answering, and tools are not magic funnels but prompts for asking, searching, listening, and adapting

Digital Organization and Archiving​

Story Moves also train students in digital organization and archiving habits that sustain creative research. In order to make a source "work" in a story move, students must:

  • Source materials ethically
  • Save and name files reliably
  • Attribute sources clearly
  • Retrieve clips for editing across platforms
  • Explore file conversion dilemmas and friction

These are invisible but crucial scholarly practices. Without them, inquiry collapses into lost files, rushed production, or broken citations.

note

By requiring students to connect narration, evidence, and sound for each move, the Story Moves table functions as an early archive of their creative and scholarly workflow. It cultivates habits of intentional saving, source tracking, and decision-making that extend into full production.

In this way, Story Moves complement BBMEs: both invite students to document their relational and infrastructural practices so that every act of making becomes part of the story of inquiry itself.

The RTS Alignment​

Within the Research to Story pedagogy, Story Moves align with and extend existing inquiry categories:

  • Spark of Inquiry → Which personal or course-based questions anchor the opening move?
  • Inquiry as Story → Which scholarly tensions or debates structure the middle moves?
  • Stakes and Significance → Which moves foreground public impact and disciplinary lenses?
  • Puzzles and Unknowns → Which gaps emerge when sources resist arrangement into sound?
  • Listeners and Lens → Which final move articulates a core takeaway for the audience?

App Affordances​

The Story Moves feature in RTS will include two complementary views:

Table Mode (Scaffold Inquiry)​

  • Students map 4–6 moves with fields for narration, evidence, audio, and purpose
  • Gaps flagged: narration with no evidence, evidence with no sound plan, etc.
  • Integrated asset log for media curation, citation, and file management

Timeline Mode (Arrange Composition)​

  • Moves visualized as blocks along a timeline, with tracks for narration, evidence, sound, and transitions
  • Students stretch and order blocks to match a target duration (e.g. 5 minutes)
  • Visual emphasis on pacing, balance, and rhetorical rhythm

Both views can be exported as PDFs or CSVs, scaffolding student agency and also providing faculty with a window into the process.

There is no magic funnel​

Story Moves dismantle the "magic funnel" myth — the assumption that well-written ideas simply pour into editing software and emerge as compelling podcasts. Instead, they reveal that production is a site of inquiry and not the bow to wrap it up at the end. The act of arranging story moves generates new thinking: about evidence, about audience, about structure, about the research question itself.

By embedding Story Moves into RTS, I'm interested in the position of the production phase as a continuation of the generative work that began in Movement 1. Students learn to see their final artifact as more than a “presentation of research" but as the outcome of compositional thinking that reshapes the research itself.

Next Steps​

  • Prototype Table Mode as an MVP within RTS
  • Build export functions for faculty feedback and student reflection
  • Explore Timeline Mode as a stretch feature for visual pacing and arrangement
  • Integrate Story Moves with the broader RTS inquiry framework, ensuring every move reflects back on Spark, Story, Stakes, Puzzles, and Lens

Deployment Options​

Standalone App (Workshop Tool)​

  • Independent of RTS
  • Useful for any workshop, class, or independent creator
  • Could be a simple web app (React, no backend needed for MVP — local storage or export)
  • Shareable via URL

RTS Integration​

  • Story Moves as a feature within the RTS workflow
  • Connected to session data (topic, synthesis, deep dive insights feed into story move creation)
  • Stored in Supabase alongside other RTS data
  • Part of the living ledger — arrangement decisions become part of the audit trail

Both​

  • Build standalone first, integrate into RTS later
  • The standalone version proves the concept and serves the workshop
  • The RTS integration adds contextual intelligence (e.g., AI could suggest story moves based on completed deep dives)

📌 Summary:
Story Moves scaffold the intellectual work of making. They give students a generative exercise in arrangement (instead of a magic process of translation, a studio instead of a stage) that surfaces new questions, new demands on evidence, and new rhetorical possibilities. They reveal invisible literacies of digital organization and relational practice, and because they surface real domains of scholarship, they consequently provide a range of assessable artifacts for faculty engagement.

Further Reading​