a single source, nothing corroborates it
Edit the process down before you publish it
A format that is effortless for you to produce is not automatically worth anybody's time, so cut the raw process to the parts that are useful. Streaming an entire build is the standard failure: viewership falls episode by episode as the work turns into refactoring, debugging and tests that nobody wants to watch.
The method
- 01
Do not livestream an entire build as marketing: viewership declines episode by episode as the work turns into refactoring, debugging and tests that nobody wants to watch.
- 02
Cut content down to the useful parts rather than publishing your raw process, because a format that is effortless for you to produce is not automatically worth anyone's time.
What it returned
Zue published six weekly screencasts of himself building an app on Pegasus and the view counts formed a steady downward trendline, from a solid start to a few hundred views per video.
Zue decided to stop publishing full build streams and instead extract the useful moments into something closer to a highlight reel, while remaining bullish on the channel overall.
Sources
- Flailing aroundCory Zue · coryzue.com · Publish at least four screencasts showcasing myself building a new Pegasus app. · 2024-04-02
the second source
Three plays a week, for the phase you are in
No roundup of links, no news. Three tactics more than one builder arrived at separately, with the numbers each one returned and the disagreements left in.
More in social
- Concentrate on one platform until it works11 unconnected · contested
- Gather the audience before there is a product6 unconnected · contested
- Fire the launch into the audience you already have6 unconnected · contested
- Post the numbers, not the commentary5 unconnected · contested
- Republish the winners with a new hook5 unconnected
- Cut one long piece into weeks of social posts5 unconnected