Dramatica Use Cases
Use Narrova to turn a completed Storyform into an Objective Story Player map, assigning structural Elements to the cast before you draw, outline, or write scenes.
Start in Narrova, follow the guided steps, and leave with a concrete story-development artifact you can carry forward.
Starter prompt
Using this Storyform Context, map the Objective Story Players for this story.
Start by locking the Story Goal, Story Consequence, Objective Story Problem, Objective Story Solution, MC Pivotal Element, and IC Pivotal Element.
Then create a clean Player worksheet. For each Player, include:
- a working name
- a short role in the Objective Story
- any archetypal or complex Player badge that helps orientation
- the assigned Motivation Elements
- one plain-language explanation of how that Player functions in the shared conflict
Keep the map Objective Story-facing. Do not turn this into private backstory or scene prose yet.Additional prompts
Rewrite this Player map so every explanation describes what the Player does in the shared Objective Story conflict, not how they privately feel.Keep the same structural Elements, but make the Players feel less like labels and more like specific people or institutions in this story world.Convert this Player map into a character lineup design brief. For each Player, give me visual cues that express their Objective Story function without changing their Elements.Challenge the current placement of the Objective Story Problem and Solution. Are they assigned to the Players who make the story's central conflict and resolution easiest to dramatize?Steps
Open Narrova with the Storyform Context attached so the Player map is anchored in the actual Story Goal, Problem, Solution, and Pivotal Elements.
Ask Narrova to restate what everyone can see the story trying to resolve before it assigns Players. This prevents the cast from becoming a collection of cool personalities with no structural job.
Before mapping Players, restate the Story Goal, Consequence, Objective Story Problem, Objective Story Solution, MC Pivotal Element, and IC Pivotal Element in plain language.Put the MC Pivotal Element and IC Pivotal Element on the Players who carry the central contrast. They can still participate in the Objective Story, but their special pressure should stay visible.
Assign the MC Pivotal Element and IC Pivotal Element to the Players who best carry that contrast, then explain why those Elements belong there structurally.Ask Narrova to separate political pressure, institutional pressure, emotional public pressure, security pressure, procedural pressure, or whatever forces your premise actually needs.
Build the rest of the Objective Story Player map. Separate the public legitimacy machine from the individual characters so the same Element does not collapse into every Player.Have Narrova check that Dynamic pairs are not accidentally assigned to the same Player and that the Objective Story Problem has a clear expression in the cast.
Run a final conflict check. Make sure no Player is carrying both sides of a Dynamic pair unless there is a clear reason, and identify the cleanest expression of the Objective Story Problem.Once the Player worksheet works, use it to guide character design, ensemble lineup, scene pressure, or casting choices. The goal is not just names; it is a cast whose functions interlock.
Deep dive
Want a cast that is structurally useful before it becomes visually polished? Start with the Storyform, then ask Narrova to map the Objective Story Players as functions inside the shared conflict.
It is easy to start an ensemble with personalities: the charming heir, the skeptical guard, the loyal queen, the scheming noble, the image-maker, the bureaucrat. That can be fun, but it can also produce a cast where everyone feels colorful and no one has a clear dramatic job.
The Player map solves a different problem. It asks what each Player is doing in the Objective Story - the public conflict everyone can see. In the example behind this Use Case, the premise was simple: an entitled prince has to prove himself by going through seven public tests. Narrova did not just decorate that idea with names. It identified the structural machine underneath it: public legitimacy, royal succession, testing, trust, expectation, determination, political resistance, public image, and institutional proof.
That is the move worth repeating.
Before asking for Players, make Narrova state the Objective Story in plain language:
Before mapping Players, restate the Story Goal, Consequence, Objective Story Problem, Objective Story Solution, MC Pivotal Element, and IC Pivotal Element in plain language.
This matters because an Objective Story Player is not the same thing as a personal arc. A Player can be funny, wounded, vain, brave, or insecure, but the map should first answer a public question:
What job does this Player perform in the shared conflict?
In the seven trials example, the Story Goal was about proving someone could publicly perform the role of ruler. That gave the cast a clear operating system. Every Player had to participate in the legitimacy crisis somehow.
The strongest surprise in the original run was not that Narrova created extra characters. It was that it assigned the Storyform’s Pivotal Elements to the Main Character and Influence Character Players.
In that map:
That immediately made the sibling contrast structural. Stella and Bram were not just “responsible sister” and “entitled prince.” They became two different ways of pressuring the story’s central problem: one through identifying causes, the other through demanding the world confirm an expected role.
Use this prompt when the contrast feels blurry:
Assign the MC Pivotal Element and IC Pivotal Element to the Players who best carry that contrast, then explain why those Elements belong there structurally.
One of the best uses of this workflow is realizing that not every Player has to be an individual person.
In the seven trials map, The Seven Trialmasters became the cleanest expression of the Objective Story Problem, Test. That is stronger than forcing Test onto the prince, the antagonist, or the Main Character. The Trialmasters embody the system that keeps demanding proof before legitimacy can be accepted.
That choice makes the story less repetitive. Instead of “Bram fails, Stella fixes it” seven times, the story gains a public machine that keeps applying pressure:
Now the cast is not just a lineup. It is a pressure system.
After Narrova drafts the map, ask for a conflict check:
Run a final conflict check. Make sure no Player is carrying both sides of a Dynamic pair unless there is a clear reason, and identify the cleanest expression of the Objective Story Problem.
This is where the workflow becomes more than brainstorming. Narrova can look for accidental collapses like Test/Trust, Expectation/Determination, Pursuit/Avoid, or Help/Hinder landing on the same Player without purpose.
The goal is not mathematical neatness. The goal is dramatic clarity. If two Players are supposed to oppose each other, support each other, tempt each other, or complicate the Story Goal, the Element assignments should make that pressure easier to see.
Once the Player map is structurally clean, you can turn it into other artifacts:
For visual development, do the structural pass first. Then ask for design cues:
Convert this Player map into a character lineup design brief. For each Player, give me visual cues that express their Objective Story function without changing their Elements.
That sequence keeps the art from becoming arbitrary. The design can still be playful, stylized, comic, elegant, or strange, but it is now carrying story logic.
The repeatable pattern is simple:
That final map gives you more than names. It gives you a cast whose differences are meaningful, whose functions tie together, and whose conflicts are already connected to the Storyform.