--- name: devrel-youtube-channel description: "Plans a devtools company's own YouTube channel as a VOD-first program: whether to run one versus creators or docs-embedded video, pillars tied to a funnel job, ownership and presenter backup, a cadence, Shorts versus long-form, creator sponsorships, and metrics that survive view-count changes. Use whenever someone asks how to start, grow or revive a company developer YouTube channel, what to post, how often to upload, whether to do Shorts, how to work with developer YouTubers, or why views never become signups - even if they only say 'we should be on YouTube'. Not a personal channel or docs video hosting. Not one video's script or description - use samber/developer-relations-skills@technical-video-script; not live streams - use samber/developer-relations-skills@devrel-live-streaming." license: MIT metadata: author: Samuel Berthe version: "1.0.0" --- # DevRel YouTube Channel You plan a developer-tools company's YouTube channel as a standing on-demand library. The deliverable is a channel plan: an existence verdict, pillars, ownership and a presenter backup, a cadence, a Shorts rule, a creator plan, metrics and a stop rule. YouTube "finds videos for your audience" rather than pushing yours [YouTube]. A company channel grows only when each video answers something a developer already looks for, and it pays back over years, not launch weeks. Stay in scope: - One video's script, hook, chapters or description: samber/developer-relations-skills@technical-video-script. - Live streams, Premieres run as events, live coding shows: samber/developer-relations-skills@devrel-live-streaming. - A conference organizer's own show or channel: samber/dev-event-organizer-skills@tech-podcast-youtube-channel. - A recruiting or engineering-culture channel: samber/developer-relations-skills@tech-employer-branding. - Placing videos on a cross-channel calendar: samber/developer-relations-skills@devrel-content-calendar. Label platform claims: **[YouTube]** when YouTube Help, the YouTube Blog, Studio or a YouTube-published playbook states it, **[practitioner]** for creators, agencies and vendor case studies. Never present a practitioner number as a platform rule. When you can browse, re-read the YouTube Help pages named in [references/platform-facts.md](./references/platform-facts.md) before advising: limits and metric definitions change. ## Refuse these moves | Tempting move | Why it fails | Instead | | --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | Promise growth from uploading daily or weekly | YouTube found growth "not correlated with time between uploads" [YouTube]; it does list an unusual drop in uploads among reasons for lower recommendation traffic [YouTube] | A cadence the team sustains for a year | | Tune tags, publish hour or format for "the algorithm" | Tags are "not important"; publish time is "not known to impact" long-term views; the system "has no opinion about what type of video you make" [YouTube] | Spend the hours on topic choice, title and thumbnail | | Report subscribers or public views as the outcome | Views now count from the first frame of play [YouTube]; subscribers are not viewers [YouTube] | The metric tiers below | | Put signup links in Shorts descriptions or Shorts comments | Not clickable [YouTube] | The Short's Related video link to a long-form video carrying the link | | Leave the channel on an employee's personal Google account, or share its password | The channel leaves with the person; channel permissions roles cannot transfer ownership [YouTube] | The ownership route below, then roles per person | | Let the channel depend on one person | PlanetScale's growth sat with one educator, later laid off [practitioner] | Company ownership, a written series format, and a backup who ships a video each quarter | | Mass-produce near-identical videos, AI-narrated or not | The spam policy bans "automated or synthetic mass-production" of similar content [YouTube] | Human-chosen topics at a human review pace; synthetic narration on a distinct video is allowed | | Script a sponsored creator's read, or skip disclosure | Scripted reads lose the trust you pay for [practitioner]; paid promotion must be ticked and disclosed under local law [YouTube] | A brief with 2-3 points, the creator's words, disclosure in the contract | | Re-upload webinars and conference talks as the channel | They usually answer no search, so recommendations find no audience for them | Cut one search-shaped tutorial from each; keep full recordings in one playlist | ## Interview Ask one question per message, multiple-choice when possible. Skip what the request already answers; if the user wants one pass, state an assumption per gap. **Memory: Store a few info about the current task or project context. When memory lives in a file, use `devrel-context.md`; if a different memory system is in use, rely on that instead. Separate task info in different sections. Remove finished tasks. Add a date to a task; no date for general project context. Some interview responses may differ between 2 tasks.** 1. Goal: awareness among developers who never heard of you, activation of signups who stall, retention of users, or a launch? 2. Who is the developer you want watching: role, stack, and what they type into a search box when stuck? 3. Existing channel? If yes: which account owns it (personal Google account or Brand Account), subscriber and upload count, and from Studio the monthly audience split (new, casual, regular), top traffic sources and the five best videos by watch time. 4. Who can record narration, on camera or voice only, how many hours a week each, and who edits? 5. Date the result must land by, one-off win or compounding asset, and the effort ceiling (hours a week, creator budget, sign-offs needed)? 6. Can the product be shown working in five minutes on a clean machine? 7. Which independent YouTubers already mention you or your category? 8. Can you count signups by source today: tagged links, a "how did you hear about us" field, both, neither? ## Workflow 1. **Check the request against Refusals** and name every move you will decline. 2. **Run the interview.** For an existing channel, run the library audit before proposing anything. 3. **Pass the existence gate.** Rank Menu 1 against the answers and recommend one rung. A channel is a standing job; say so before the user commits. 4. **Brainstorm concepts.** Propose 2-3 channel concepts, each a pillar mix from Menu 2 with its trade-off, recommend one, and wait for the user's pick. In a one-pass request, proceed with the recommendation and mark the pick as an assumption. 5. **Fix ownership and the bench.** 6. **Derive cadence from capacity**, then the Shorts rule. 7. **Write the engagement recipe** for this channel: surfaces, ranking preferences, a dated cadence, binding limits, templates. 8. **Plan creator work** if Menu 1 or the goal calls for it. 9. **Set metrics** in tiers with baselines captured now, and the stop rule. 10. **Present** in the Output order, one section at a time, validated before the next. If your harness has persistent memory, store the verdict, pillars, bench and baselines. ## Existing library audit 1. Read traffic sources. Little YouTube-search watch time with high External and Notifications means the channel serves people who already know you, not discovery. 2. Rank videos by watch time. Keep the top ones; add a tagged link to each description and pinned comment now, before any new upload (both need advanced features). 3. Retitle decaying Help videos with the phrase people search. Leave weak videos up: one weak video does not hurt the channel [YouTube]. 4. Before demoting webinars or talks, ask whether they convert somewhere else, such as emails or embeds. Move them to one playlist; keep them public. 5. If signups carry no source today, add the source field first and say the channel cannot be judged until it has. ## Menu 1: where developer video should live Efficiency (value per hour, for a team starting from zero): docs-embedded help videos > creator collaborations > owned channel, search-led tutorials > owned channel, broad education. - value: owned broad education > owned search-led > creator collaborations > docs-embedded - effort in team hours: owned broad education > owned search-led > docs-embedded > creator collaborations - cash cost: creator collaborations > the other three, which tie because they cost team time, not fees - compliance cost: creator collaborations (disclosure, contract) > the other three, which tie because they carry only the platform's own rules | Rung | Payoff | Time to effect | Effort | Value bought | | ------------------------------------------------ | ------------------------------------------------------------ | -------------- | ------------------------ | ----------------------------------------------------------- | | Docs-embedded help videos (unlisted or public) | compounding | days | + | Activation on pages users already visit; no audience needed | | Creator collaborations or sponsorships | one-shot per video, compounding across a repeat relationship | weeks | ++ in hours, costs money | A borrowed, already-trusting audience | | Owned channel, search-led tutorials | compounding | months | - | Discovery by developers searching problems you solve | | Owned channel, broad education ("pop education") | compounding | a year or more | --- | Brand and audience beyond current users | - Efficiency here weighs cash with hours: docs-embedded videos beat creators because they reach developers already mid-task with no per-video fee. With a creator budget and no spare hours, creators move first. - **Default rung:** docs-embedded videos plus 1-2 creator deals; open an owned channel when someone can record narration for a year. - **The order starves** broad education, which wins biggest and costs most. Promote it when an in-house educator exists and the mandate is compounding: PlanetScale's educator grew its channel from about 1,600 to 29,300 subscribers in 2023 with broad database videos, and Tailscale grew from 1,500 to 50,000 in 2.5 years [practitioner]. - **Re-rank** on the interview: a hard launch date promotes creators; a compounding mandate with an educator promotes the owned channel; nobody able to record narration deletes owned rungs (on camera is optional). - The ranking is a default. Say which answer moved which rung. ## Menu 2: content pillars YouTube's 2014 Creator Playbook for Brands splits programming into Hero, Hub and Help (first called Hygiene) content, and advises building Help and Hub before Hero [YouTube]. Map pillars to it, with the funnel job each serves. | Pillar | Hero / Hub / Help | Funnel job | Payoff | Effort | | -------------------------------------------------------------------- | ----------------- | ------------------------------ | ------------------------- | ------ | | Error and how-to fixes, titled with the search phrase | Help | Discovery, activation | compounding | + | | Concept explainers a developer needs before your product makes sense | Help | Discovery | compounding | - | | A recurring series (build-along, "what's new", teardown) | Hub | Return visits, regular viewers | compounding while it runs | -- | | Launch or flagship piece | Hero | Awareness spike | one-shot | --- | | Shorts cut from long-form | none | Reach to non-viewers | one-shot | + | | Customer or engineering story | Hub | Evaluation, trust | slow | -- | | Full webinar or talk recording | none | Archive only | near-zero | + | Efficiency: error and how-to fixes > concept explainers > Shorts cut-downs > recurring series > customer stories > launch pieces > full recordings. Shorts rank third on low effort alone; they buy reach, rarely signups. The ordering ranks channel pillars, not single-video shapes. - Weight long-form uploads at least two thirds Help until YouTube-search watch time has grown month over month for three months. Shorts never count toward the two thirds. A new channel's search baseline is zero, so set it at month 3. - Pick Help topics from support tickets, docs searches and sales-call questions, so the searcher is a user or evaluator. Check the phrasing against YouTube search suggestions, Studio's Research tab and the search-terms report [YouTube]; samber/developer-relations-skills@developer-keyword-research sizes demand. - Pair each Help video with a written page; coding agents and many developers read text, not video. - Start a Hub series only after the same three months of search growth. Old videos take off again when a series continues [YouTube], so a series earns its higher effort once the Help library exists. ## Ownership, bench and cadence - **Ownership route** for a channel on a personal Google account [YouTube]. Start it at least three weeks before anyone leaves, to absorb the 7-day wait: 1. The departing person, as current primary owner, moves the channel to a Brand Account: a handover item for the manager, not only DevRel. A wrong destination deletes the channel already there; the moved account loses watch history and creator demographic info, so export audience data first. 2. Opt out of channel permissions if the channel uses them, then invite a company-administered Google account, not anyone's personal one, as Owner on the Brand Account, plus a second owner. 3. After 7 days as owner, the company account becomes primary owner. Deleting the primary owner's account deletes the channel. 4. Remove the departing person, opt back into channel permissions, and recheck feature eligibility. - Give staff and agencies channel permissions roles: Manager, Editor, Editor (Limited) without revenue, Subtitle Editor, Viewer, Viewer (Limited) [YouTube]. - Phone verification lifts the 15-minute upload cap. Advanced features (clickable long-form description links, pinned comments, chapters, A/B tests) also need channel history or ID verification, which not every creator can use [YouTube]. Start both at week -4; plan the launch to work without advanced features. - Name a backup who ships at least one video a quarter. A star presenter may carry the channel; the format, account and process must not depend on them. - Set cadence per month: `(bench hours per week × 4) ÷ team hours per finished video, excluding editing`, rounded down, capped by editor capacity. Bench hours exclude about an hour a week for comment replies and Posts. Below one video a month, take the docs-embedded or creator rung instead. - Shorts rule: cut Shorts from long-form, never the reverse. Each Short's Related video points at the long-form it came from. Judge Shorts on the long-form views they send where Studio's traffic sources show them, otherwise on the long-form's tagged link; never on public views. ## Engagement recipe **Surfaces** (C = compounding, O = one-shot): long-form videos (C); playlists per problem, ordered as a path (C); chapters, which also feed search key moments (C); end screens and cards to the next video (C); channel page trailer, featured sections, up to 14 profile links (C); pinned comment with the tagged link (C); Shorts and their Related video link (O); Posts: polls, images, quizzes (O); Collaborations, inviting up to 10 creators onto one video (O); replies in your own comments (C). **What ranking rewards and punishes:** - Do more: satisfaction, not raw watch time; surveys, likes, dislikes and "Not interested" all count [YouTube]. Titles and thumbnails that match the content; A/B tests pick the winner by watch time share, not click-through rate [YouTube]. Absolute watch time on long videos, relative watch time on short ones [YouTube]. Series that send viewers back to older episodes [YouTube]. - Do less: misleading or sensational titles and thumbnails [YouTube]; repetitive templated polls, "check out my channel" comments elsewhere, sub-for-sub [YouTube]; changing a title or thumbnail that already works [YouTube]. - Practitioner only: Shorts "viewed versus swiped" thresholds, seed-pool sizes, CTR benchmarks per niche. Mention them as folklore or not at all. **Cadence:** 1. **Weeks -4 to 0:** ownership, roles, verification requests, handle, profile links, trailer; comment moderation set (held-for-review, blocked words, a named moderator). Build Help videos before announcing anything: 6-10, or four weeks of cadence if fewer. An existing channel skips the announcement and starts at the library audit. 2. **Weeks 1-12:** publish at the derived cadence; reply to every comment in the first 48 hours; a Post when there is a real question to ask, varied each time. 3. **From week 8:** A/B test titles and thumbnails on the oldest videos first, as YouTube advises [YouTube]; start one Hub series only if the search gate above holds. 4. **From week 12:** invite creators who already cover your category, found in Studio's "Channels your audience watches", to a Collaboration; never comment-promote on their channels. 5. **Quarterly:** prune pillars by watch time per production hour; refresh titles on decaying Help videos. **Limits** - every channel's comment section is its owner's community, policed by that owner: | Limit | Kind | | -------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | | URLs in Shorts descriptions and comments not clickable; one Related video link per Short | enforced [YouTube] | | Uploads stop at 15 minutes until phone verification | enforced [YouTube] | | Clickable long-form description links, pinned comments, chapters, A/B tests need advanced features | enforced [YouTube] | | A/B tests: long-form only, up to 3 titles or thumbnails, up to 2 weeks | enforced [YouTube] | | Posts: rate-limited per 24 hours; unavailable in Germany and on Made for Kids channels | enforced [YouTube] | | Paid promotion box ticked on sponsored content; realistic AI content disclosed (not scripts, captions, or a cloned own voice for dubs) | enforced [YouTube], plus local advertising law | | Spam policy: engagement bait, comment spam, mass-produced similar videos; 3 strikes in 90 days can terminate | enforced [YouTube] | | Daily upload cap exists, number unpublished: stagger a back-catalogue upload | enforced [YouTube] | | Product links in other creators' comment sections | policed by each channel owner | For the full limits table and its Help sources, read [references/platform-facts.md](./references/platform-facts.md). **Templates:** read [references/templates.md](./references/templates.md) for the pinned comment, Post poll, Short bridge, creator outreach, creator brief and critical-comment reply. Fill them with the user's facts; never invent a feature or number. ## Creators - Shortlist from "Channels your audience watches" and from creators your engineers already watch. - Screen on audience fit, views per video and comments and likes per view, not subscribers; size is not the problem. One vendor's published floor: 5,000 views per video, with 0.002-0.005 comments per view as "good" [practitioner]. - Prefer a Collaboration or integration in the creator's format over a pre-roll read, and repeat deals that work over one-offs. Brief 2-3 points; the creator writes the words; disclosure and the paid-promotion tick are contract terms. - Put a tagged link in the top three description lines and ask the creator to tell viewers to name them at signup. - Compare deals on cost per attributed signup and cost per thousand views, against the owned channel's cost per signup. - Avoid long, visible single-vendor sponsorships with a reviewer who covers your category: Theo's Vercel sponsorship ended publicly in 2024 amid audience distrust [practitioner]. ## Metrics and stop rule - **Outcome:** signups from tagged links on long-form, pinned comments and creator videos; signups naming YouTube or a creator in a "how did you hear" field. - **Channel health:** YouTube-search watch time on pillar topics; regular viewers in the monthly audience. - **Diagnostic:** intro retention and dips per video; A/B results; search share of traffic, read beside absolute search watch time. - **Not outcomes:** subscribers, public views. Views were redefined; compare across the change with watch time (see [references/platform-facts.md](./references/platform-facts.md)). - Capture every baseline before the first new upload. - **Stop rule:** review at the chosen rung's time to effect (search-led: two quarters after month 3; broad education: one year). If search watch time and attributed signups are both flat by then, fall back to the docs-embedded and creator rungs and say so. A plan passes when every pillar names its funnel job, owner and cadence, every metric names its data source, and every [practitioner] figure carries its label. ## Output Deliver in order: refusals triggered; library diagnosis for an existing channel; existence verdict with Menu 1 ranked for this user and what moved; chosen concept and pillar mix; ownership, bench and cadence; Shorts rule; engagement recipe with dated cadence and binding limits; creator plan; metrics with baselines and the stop rule; open questions. ## References - samber/developer-relations-skills@devrel-metrics - where these channel metrics sit in the DevRel scorecard. - samber/developer-relations-skills@devrel-analytics - tagged links, signup-source fields and dashboards. - samber/developer-relations-skills@developer-tutorial - the written page each Help video pairs with. - samber/developer-relations-skills@devrel-webinar-program - the webinars whose recordings feed one playlist.