index 2727ded..b39b115 100644
@@ -12,15 +12,8 @@ teams demo by clicking around randomly — "and this does X, and over here is Y,
## why it's a gotcha
-without a narrative, features feel disconnected and forgettable. judges can't follow why each feature matters. it feels like a feature tour, not a solution to a problem.
+without a narrative, features feel disconnected and forgettable. judges can't follow why each feature matters. it feels like a feature tour, not a solution to a problem. this is what happens when you [[emphasize-live-demo|emphasize the demo]] but forget that the demo needs a story.
## the fix
-demo as a user story. "imagine you're [persona] and you need to [goal]. you open the app, you do this, then this happens, and now your problem is solved." every feature click should advance that story.
-
-## see also
-
-- [[emphasize-live-demo]] — structure the demo with purpose
-- [[memorize-one-liner]] — the narrative starts with the one-liner
-- [[pitching-matters-as-much-as-product]] — narrative is what makes a pitch work
-- [[slides-as-documentation]] — another way to lose the narrative
\ No newline at end of file
+demo as a user story. "imagine you're [persona] and you need to [goal]. you open the app, you do this, then this happens, and now your problem is solved." every feature click should advance that story. the narrative starts with your [[memorize-one-liner|one-liner]], and the story is what makes [[pitching-matters-as-much-as-product|the pitch actually work]].
\ No newline at end of file