Glowst

Publishing, community, and the weekly read of what the comments were actually asking for.

I ran day-to-day content operations on a channel that grew to 2.69 million subscribers and 749 million views. Upload cadence, the schedule, and the check after publish were mine. So was the community, in the channel’s voice.

Problem

At that scale the comments are a second show. Ignore them and the titles go stale. Answer them carelessly and the voice breaks. A handful of threads need a person above me, not a clever reply.

Process

I kept the publishing schedule and QA. Each week I wrote a recap of sentiment, repeated themes, and anything new in the lane. Those recaps were allowed to change the next title, the thumbnail, and the topic. Sensitive interactions were flagged up instead of handled in public.

Solution

• A cadence the channel could keep, with a check after every upload.
• Community management in voice, with a path for the threads that should not be a comment.
• Weekly audience notes wired to creative, not filed away.

Results

• 2.69M Subscribers
• 749M+ Lifetime views
• Weekly Sentiment turned into the next title
• 1 voice Including the replies

Justin Moran · Marketing Specialist · Chicago, IL · LinkedIn · Resume (PDF)