The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Set up the encoder and stream settings for the live show on Saturday at 9pm. Configure resolution…
Execute — do the immediate task
+Set up the encoder and stream settings for the live show on Saturday at 9pm. Configure resolution to 1080p60, bitrate to 6,000 kbps, keyframe to 2 seconds, and the ingest server nearest our East Coast audience. Name the stream with the show title and the date, save the stream settings, and deliver the encoder configuration file to Marco by Friday 3pm so he can test it.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I load encoder settings, make the stream easy to watch and stable — highlight the…
Improve — make it easier to accept
+Before I load encoder settings, make the stream easy to watch and stable — highlight the recommended resolution and bitrate for viewers on mobile vs desktop, surface the recommended keyframe and ingest server up front, and flag any encoder settings that might trigger buffering for viewers on slower connections. Make a one-line checklist Marco can paste into his encoder.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+During tests the studio uplink dropped frames at 1080p60 and Marco says lowering bitrate fixes it.…
Decide — diagnose the stuck moment
+Encoder tests show dropped frames at 1080p60 from the studio uplink.
During tests the studio uplink dropped frames at 1080p60 and Marco says lowering bitrate fixes it. I’m afraid lowering quality will disappoint subscribers and I can’t change the ISP tonight. What’s the best compromise for setting so the live show runs reliably while preserving perceived quality? Recommend concrete encoder values, fallback settings, and what to tell the audience if quality changes midstream.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last five streams we waste hours tweaking encoder values, chasing different upload speeds,…
Become — change the pattern
+We keep rebuilding encoder settings for every stream and losing testing time.
Over the last five streams we waste hours tweaking encoder values, chasing different upload speeds, and redoing tests the day of the show. Where are we losing efficiency — inconsistent presets, no documentation, or no upstream QA — and which habit to change first? Recommend a standard encoder preset library, one person who owns testing, and a three-step validation to stop ad-hoc fixes.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other video platform work people do in YouTube.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.