• Home
  • Blog
  • Gallery
  • Pricing
  • Home
  • Blog
  • Gallery
  • Pricing
Start creating

Create.Play.

Creator blog

Home/Blog/Product workflow

Write a “Not-to-Do List” Before Starting: How to Keep Your First Project Under Control

The most common failure in a first interactive film game is not a lack of creativity, but putting every good idea into the first version. Characters, scenes, branches, mechanics, and platforms keep multiplying until nothing gets finished. The solution is to establish a “not-to-do list” before writing the full script and define a trigger for each limit.

D
DramaFork Editorial TeamInteractive storytelling and AI production
2026.08.18Estimated reading time: 12 min
Cover of the blog article “Write a ‘Not-to-Do List’ Before Starting: How to Keep Your First Project Under Control”
Article contents
Creator blog
  1. 01Introduction
  2. 02Set Six Hard Limits First
  3. 03“Do It Later” Needs a Clear Destination
  4. 04Use the Promise to Players to Decide What to Cut
  5. 05Turn Scope into Countable Metrics
  6. 06The Four Most Dangerous “Small Additions”
  7. 07Audit Scope Once a Week
Back to article top

Introduction

The most common failure in a first interactive film game is not a lack of creativity, but putting every good idea into the first version. Characters, scenes, branches, mechanics, and platforms keep multiplying until nothing gets finished. The solution is to establish a “not-to-do list” before writing the full script and define a trigger for each limit.

A not-to-do list is not about cutting things out for its own sake. It protects the project's most important promise to players, focusing a limited budget on what actually needs to be validated.

Set Six Hard Limits First

The first is finished footage duration. Record the total amount of distinct video footage, not just the length a player sees in one playthrough. A fifteen-minute playthrough with three completely independent routes may require more than forty minutes of footage.

The second is major characters. Each additional character may add actor coordination, costumes and makeup, dialogue combinations, subtitles, localization, and states to test.

The third is scenes. Scenes include not just locations, but also production variations at the same location under different times, set arrangements, or states of damage.

The fourth is key choices and endings. The number of choices does not equal quality. The first version should prioritize a small number of choices that provide information, carry costs, and deliver feedback.

The fifth is systems. Relationships, evidence, resources, QTEs, clue searching, free-form input, and AI dialogue cannot all be core systems at once. Choose one primary system and add at most one supporting system.

The sixth is platforms. PC, Web, and mobile differ in input, video formats, performance, storage, and distribution. The first version should ideally have one primary platform.

“Do It Later” Needs a Clear Destination

Do not simply say a feature is postponed, because it will soon return under another name. Create three lists: must have in the first version, do after successful validation, and explicitly will not do.

The “do after successful validation” list also needs triggers. For example: add a second type of clue only when at least four testers can understand the evidence system in the three-minute prototype; add higher resolution only when video transitions are stable on low-spec devices; add hidden endings only when the entire main storyline is reachable.

To-do items without triggers turn into emotionally driven additions to requirements.

Use the Promise to Players to Decide What to Cut

The promise of 《零点回拨》 is to let players judge the credibility of calls from the future and character testimony, and change what happens after midnight. The first version therefore needs verifiable predictions, at least two characters with different positions, one bounded time variable, and multiple outcomes jointly determined by trust and evidence.

It does not need a freely navigable 3D customer service center, arbitrary questions entered by players, or a simulation of the company's entire business. These features may be interesting, but they do not directly demonstrate the core promise.

When the team debates a feature, ask three questions: If we remove it, can players still perform the core verbs? If we remove it, can the endings still reflect player behavior? If we remove it, can the three-minute prototype still validate the biggest risk? If all three answers are “yes,” it should not enter the first version.

Turn Scope into Countable Metrics

“Keep the scale manageable” is not actionable. Use a scope table:

Scope Item First-Version Limit Current Count Action When Exceeded
Minutes of distinct video footage 20 Reconverge branches or replace with text nodes
Major characters 4 Merge characters with similar functions
Main scenes 3 Rewrite as different states of the same scene
Key choices 8 Remove options without consequences
Full endings 4 Merge endings that differ by only one line
Core variables 5 Replace with tags or remove
Primary platforms 1 Move other platforms to the post-validation list

The numbers can be adjusted for the project, but whenever a limit is exceeded, the budget, dates, or other scope must be adjusted at the same time. Do not assume the team will absorb it through overtime.

The Four Most Dangerous “Small Additions”

The first is a new branch that adds content without adding understanding. Players see different dialogue but gain no new information, relationships, or abilities.

The second is adding a mechanic for promotion that cannot run throughout the work. A single clue-searching sequence at the opening does not justify marketing the work as an investigation game.

The third is reluctance to delete assets because they have already been produced. Sunk costs do not prove that content has value.

The fourth is treating technical possibilities as product needs. A model's ability to generate arbitrary dialogue does not mean the story should allow arbitrary dialogue.

Audit Scope Once a Week

The audit examines only four things: what was added, why it was added, what it replaces, and who takes on the additional testing. Any new requirement without a corresponding removal, budget change, or schedule change stays out of production for now.

Scope audits must also check for “hidden growth.” A character may not be new, but if that character needs completely different performances and videos in four states, production volume has already increased. Likewise, if the same office changes from daytime to three states—power outage, fire alarm, and damage—it cannot be counted as just one scene. Record the amount of distinct assets in the table so that identical names do not conceal real costs.

When a project truly needs to exceed a limit, make an explicit scope trade. For example, add an ending and remove an independent side storyline, or postpone a platform version. Record who approved it, why it is worthwhile, and the new acceptance date. This means the team is making product choices instead of quietly accepting a loss of control.

Once the not-to-do list is complete, put it on the project homepage instead of in personal notes. When choosing landscape or portrait orientation, or PC or Web, as the next step, use this list to judge which release format best fits the first version's capabilities.

Explore product capabilities Play interactive stories

Updated 2026.10.04

Explore this topicCharacter and worldbuildingMaking interactive films
PLAY / DISCOVER

Related works and experiences

Browse the works index
Interactive film · Concept preview

Ghost Detective Live

A paranormal detective investigates live while viewers send clues, distractions and tips that can reshape the case.

Interactive film · Concept preview

One Bed Left

One intensive-care bed remains and several patients need it. Every clinical decision carries a human cost.

Interactive film · Concept preview

The Black Rose Witness

Caught between a mafia marriage and a deadly testimony, a witness must decide whom to trust before the truth turns violent.

Interactive film · Concept preview

Elevator Thirteen

An elevator keeps stopping on a thirteenth floor that should not exist, where a missing reflection may know how to escape the loop.

Continue reading

Browse more articles
A character reference sheet, costume fabric, and silhouette studies are checked around the same collar detail.
Product workflow2026.09.26 · 15 min

What to Check Before Confirming DramaFork Character Assets: Identify the Person First, Then Check Emotion and Shot Fit

Do four things first, then decide whether to use a character image: identify identity anchors, break down costume states, write action requirements, and list scene conditions. Only when all four steps pass does the image enter the usable pool; if it only passes the "looks good" test, rework is likely later in the video and preview stages. The following uses a fictional teaching example: the character is Shen Yan, an adult postman, and the story takes place in a windy harbor city. The names, numbers, and quoted lines are all made up and are only used to demonstrate the order of judgment.

A delivery case prepared with acceptance materials according to device, network conditions, and target route.
Product workflow2026.09.28 · 15 min

Write the Delivery Goal Before Exporting: A One-Page Brief for the Recipient's Device, Network, and Verification Route

Before exporting, write a one-page delivery brief that clearly states the recipient device, network conditions, how to run it, the target route, and acceptance criteria, then decide whether to use a local asset package or a remote link package. The order cannot be reversed: first define how the recipient opens it and how they judge success, then choose the delivery format. Below, a fictional teaching example walks through the entire process, with the project named "Tide Post Office" and the recipients being two reviewers from the partner "Shoreline Studio."

A production process passes three review lamps before planning, script, and high-cost assets.
Product workflow2026.09.27 · 15 min

When to Pause Auto-Advance: Set Three Human Review Questions for a DramaFork Project

Auto-advance is good for quickly laying out the parts you have already thought through; pause only where "the cost of rework will spill over into many downstream steps." For a two-person small team, it is recommended to set only three checkpoints: before the plan is finalized, before the script is converted to storyboards, and before high-cost video batch generation. Each checkpoint answers only one question; once answered, either release or return it, without requiring confirmation at every step.

From a story to a playable world.

Create interactive narrative games with DramaFork: connect scripts, characters, shots, and choices into a playable first version.

Explore & play

  • Explore gallery
  • Interactive film
  • Text game
  • Character IP
  • Rankings
  • Works index

Create & collaborate

  • My creations
  • Film studio
  • Text-game studio
  • Character studio
  • Creator partnership

Reading room

  • Creator blog
  • Story topics
  • Article archive

Story guides

  • Interactive storytelling
  • Making interactive films
  • Designing text games
  • Character and worldbuilding

Plans & credits

  • Pricing
  • Credits

Policies & support

  • Privacy
  • Terms
  • Cookies
© 2026 DramaFork/DramaFork · Interactive narrative games
Press Enter to send, or drag away and release.