๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

JE Labs
@JELabs2024
Just Empower the Ambitious | Strategic Growth Partner of 100+ Leading Projects | Fintech, AI, & Robotics | Founder @0xEvieYang
๊ฐ€์ž… June 2024
124 ํŒ”๋กœ์ž‰ ์ค‘    3K ํŒฌ
Most event write-ups are recaps: attendance, agenda, atmosphere. They prove an event happened. They don't explain why it was built that way. A while back we wrote about the design logic behind Creao's (@CreaoAI) Demo Day in Silicon Valley, an event for content creators with one simple ask: build your own Agent workflow, on-site. We've now turned that piece into a 90-second video. What it covers: 1/ Work backwards from goals. We set three objectives first (activation, distribution, relationships) and only then picked the format. A Demo Day was the format that could carry all three at once. 2/ Design participation intensity. We used the Yerkes-Dodson curve to keep the room in the useful zone: a clear build task and light public pressure from demos and voting, plus templates, credits and on-site support to lower anxiety. 3/ Behavior has to be designed. Creators don't lack motivation. They lack ability and a prompt, so the event was built to supply both. 4/ Distribution comes from participants, not the host. The most shareable material isn't your recap. It's what attendees made themselves, so those moments are planned in advance. 5/ "The energy was great" is not an evaluation. The signal that matters is whether the workflow traveled back into real work. Full Video below ๐Ÿ‘‡
๋” ๋ณด๊ธฐ