yes/no + Snowflake

[Kurt Luther]

Regarding how to integrate our yes/no system with the Snowflake
method, I can think of several possibilities...

* Use yes/no to flesh out an overall storyline, then use the Snowflake
method to summarize it into a paragraph with 5 sentence (setup, 3
disasters, ending).

* Use yes/no to flesh out an overall storyline, then summarize it into
one sentence. Then use the Snowflake method to expand the sentence
into a paragraph w/ 5 sentences.

* Use yes/no to flesh out an overall storyline, with structured
prompts based on Snowflake (setup, disaster 1, etc.) Then summarize
as a Snowflake paragraph w/ 5 sentences.

Other ideas, or opinions on these?




--
Kurt Luther
www.kurtluther.com

[Robin]

Since yes/no with elements gets people to generate most of the characters, setting + plot, which are the basics for a story, I like using yes/no to get the storyline + asking them to summarize into 1 sentence at the end. Then using Snowflake to make the 5 sentences. ..And it'd be relative easy to integrate into existing code

Robin
___________________________________
ROBIN N. BREWER

[Kurt Luther]

So Robin votes for #2... any other opinions? It would be great to
decide this today (or soon) so we can move forward.

--
Kurt Luther
www.kurtluther.com

[Yotam Gingold]

I vote for #1 or #3.

I think that summarizing the entire questions story into a single sentence (#2) would get rid of a lot of good stuff; #1 essentially summarizes/focuses it into 5 sentences.

Alternatively, the current "conflict"/"resolution" prompts could be changed into snowflake prompts (#3).

Yotam

[robinb...@gmail.com]

It looks like there was a tie between all 3 options. Final decision?

 

Robin
Sent from my Microsoft Surface