CONT-LOSE-SOP-003: Why Behind-the-Scenes Content Failed on ETHUM LinkedIn Company Page

CONT-LOSE-SOP-003: Why Behind-the-Scenes Content Failed on ETHUM LinkedIn Company Page (Saved as Knowledge — Do Not Repeat) ═══════════════════════════════════════════════════ Status: ❌ Loser Knowledge SOP Created From: CONT-EXP-013 Owner: Fatima (LinkedIn ETHUM Company Page) Enforced By: Nabeel Abbas Review Cycle: Reference before any LinkedIn page content experiment ═══════════════════════════════════════════════════ WHAT FAILED & WHY ────────────────────────────────────────────────── 1. BEHIND-THE-SCENES CONTENT DIDN'T RESONATE ON A COMPANY PAGE Behind-the-scenes posts ("This week our team ran 7 experiments. 4 failed. 3 won.") underperformed vs polished thought leadership posts on the ETHUM LinkedIn company page. The hypothesis assumed transparency and real results would humanize the brand and drive curiosity. In reality, LinkedIn company page audiences expect authoritative, polished content — not casual team updates. → Behind-the-scenes content works on PERSONAL profiles (Pascal, Haider, Nabeel) where authenticity builds trust. On COMPANY pages, it reads as unprofessional or unfinished. 2. COMPANY PAGES ARE NOT PERSONAL BRANDS People follow company pages for expertise, frameworks, and value — not for a peek behind the curtain. The casual tone and "here's what we're testing" angle made ETHUM look like they were still figuring things out, which hurt credibility rather than building it. Test post engagement was 20-30% LOWER than the polished thought leadership control post. Comments were minimal. Shares were zero. → Transparency on a company page = perceived inexperience, not relatability 3. LINKEDIN ALGORITHM FAVORS POLISHED CONTENT ON PAGES LinkedIn's algorithm prioritizes company page content that positions the brand as an expert or thought leader. Behind- the-scenes content doesn't trigger the same engagement velocity signals (saves, shares, link clicks) that framework and insight posts do. Net result: Lower reach, lower engagement, worse overall performance. → The algorithm doesn't reward "realness" on company pages the way it does on personal profiles WHAT TO DO INSTEAD ────────────────────────────────────────────────── ✅ Keep behind-the-scenes content on PERSONAL profiles only Pascal, Haider, Nabeel can post "Here's what we tested this week" and it builds trust. Same content on the company page looks unpolished. ✅ Company page = polished thought leadership ONLY Frameworks, insights, case studies, client results. No casual team updates, no "here's what failed" transparency posts. ✅ If you want to show results, frame them as case studies Instead of: "This week we tested 7 experiments. 3 won." Use: "How we helped a B2B SaaS client increase pipeline by 42% in one week using this exact framework." Same data, different framing. One is professional, one is casual team chat. ✅ Save experimental transparency for internal channels Behind-the-scenes updates belong in: - Pumble (internal team communication) - Weekly all-hands (internal updates) - Personal LinkedIn profiles (Pascal/Haider sharing process) NOT on the ETHUM company page. RULES GOING FORWARD ────────────────────────────────────────────────── ❌ NEVER post behind-the-scenes or "here's what we're testing" content on the ETHUM LinkedIn company page ❌ NEVER use casual tone on the company page Professional, authoritative, polished ONLY ❌ NEVER share "what failed this week" transparency posts Company pages need to signal confidence and expertise, not ongoing experimentation ❌ NEVER assume what works on personal profiles will work on the company page — the audience expectations are different ✅ DO post behind-the-scenes content on: - Pascal's personal LinkedIn - Haider's personal LinkedIn - Nabeel's personal LinkedIn - Internal Pumble channels ALTERNATIVE EXPERIMENTS TO RUN INSTEAD ────────────────────────────────────────────────── 1. Client Case Study vs. Thought Leadership Control: "3 reasons B2B sales teams fail" Test: "How we helped [Client] fix their broken pipeline in 30 days" 2. Framework Post vs. Insight Post Control: Single insight with explanation Test: Multi-step framework with visual 3. Tagging Team Members vs. No Tags Control: Post with no tags Test: Same post tagging Pascal or Haider to expand reach