Job Detail

rendered

Chris Meredith

Source URL

text://chris-meredith/1784517671983

Platform

other

Submitted

2026-07-20 03:21:11

Submitted By

api

Format

Short-form (9:16)

Extracted Content

11 Laws — Law 11 of 11: Brooks' Law Hook: "Adding people to a late project makes it later." Core explanation: Brooks' Law. Throw more bodies at a project that's already behind and it slows down, not up. Because the new people have to be trained, everyone has to talk to everyone, and the communication overhead explodes. Nine women can't make a baby in one month. Some things just take the time. Real-world example: A software team's behind, so the boss hires five more engineers. Now the original team spends all day onboarding instead of building. The deadline slips further. Congratulations, you paid extra to go slower. Talking points: Communication paths grow way faster than headcount. Ten people is forty-five conversations. Some tasks don't split. Understanding the problem is the bottlen...

Script Generation Prompt

Script

{
  "intro": {
    "emotion": "dry, direct, slightly sardonic",
    "dialogue": "A software team is behind deadline, so the manager hires 5 more engineers. The project ships 3 weeks later than if he'd hired nobody. That's Brooks' Law, and it's been true since 1975.",
    "duration_sec": 8
  },
  "outro": {
    "emotion": "wry, confident, punchy",
    "dialogue": "Brooks' Law is 50 years old and managers still violate it every quarter. One framework, one law, one less bad hire decision. Follow for the next one when it drops.",
    "duration_sec": 7
  },
  "scenes": [
    {
      "data": {
        "formula": "n(n-1)/2",
        "team_size_after": 10,
        "team_size_before": 5,
        "communication_paths_after": 45,
        "communication_paths_before": 10
      },
      "type": "data-viz",
      "narration": "Communication paths grow with the formula n times n-minus-1 divided by 2. Double your team from 5 to 10 and you don't double the conversations. You go from 10 to 45. Every new hire adds drag, not thrust.",
      "description": "Animated counter: headcount rising from 5 to 10 people. Simultaneously, communication paths animate in as connecting lines between nodes, exploding from 10 to 45. Number '45 conversations' pulses on screen. Split into 2 sequential shots: first half shows the headcount jump, second half reveals the communication path explosion.",
      "duration_sec": 9
    },
    {
      "data": {
        "left_label": "Before: 5 engineers, building",
        "right_label": "After: 10 engineers, onboarding"
      },
      "type": "comparison",
      "narration": "The new engineers don't arrive coding. They arrive asking questions. And the people answering those questions are your senior engineers, the ones who should be shipping. You paid extra to slow your best people down.",
      "description": "Split screen. Left side: original 5-person team coding, progress bar moving steadily. Right side: 10-person team, progress bar stalled while onboarding calendar invites pile up. Label left: 'Before hire.' Label right: 'After hire.' Cut between both sides with Ken Burns motion, no side held static past 4 seconds.",
      "duration_sec": 8
    },
    {
      "data": {},
      "type": "typography",
      "narration": "Some work is inherently sequential. Understanding the codebase, debugging a race condition, getting the architecture right. You can't parallelize comprehension. Nine women can't make a baby in one month.",
      "description": "Large bold text on dark background, animated word by word: 'Nine women can't make a baby in one month.' Hold 3 seconds, then crossfade to secondary line: 'Some tasks don't split.' Hold 3 seconds. Cut.",
      "duration_sec": 7
    },
    {
      "data": {
        "fix_1": "Cut scope",
        "fix_2": "Protect senior time",
        "fix_3": "Add people before it's late, not after"
      },
      "type": "messaging",
      "narration": "The real fix for a late project is almost never more people. It's less scope. Protect your senior engineers' time. And if you need to scale the team, do it before the deadline pressure hits, not because of it.",
      "description": "3-item list animating in one element at a time on a clean background. Each item holds 2-3 seconds before the next reveals. Items: '1. Cut scope' / '2. Protect senior time' / '3. Add people before it's late'. B-roll of a focused solo developer cuts in after the list completes, 5-6 seconds.",
      "duration_sec": 10
    }
  ],
  "metadata": {
    "title": "Brooks' Law: Why Hiring More Engineers Slows You Down",
    "captions": {
      "tiktok": "A manager hired 5 more engineers to save a late project. The deadline slipped 3 more weeks. Brooks' Law says this always happens. Are you making this mistake right now?",
      "youtube": "Brooks' Law (1975) states that adding people to a late software project makes it later. A team of 10 generates 45 communication paths, not 10. Senior engineers stop shipping and start onboarding. The real fix is scope reduction, not headcount. Covers the communication path formula, why some tasks can't be parallelized, and 3 fixes that hold up. Follow if you want the next one when it breaks.\n\n0:00 The law managers keep breaking\n0:17 How communication paths explode\n0:35 Why your senior engineers are the bottleneck\n0:50 The 3 fixes that work",
      "instagram": "A manager hired 5 more engineers to save a late project. The deadline slipped 3 more weeks.\n\nBrooks' Law has been documented since 1975: adding people to a late project makes it later. Communication paths explode, senior engineers stop building, and you pay extra to go slower. The fix is almost never more headcount.\n\nHave you seen this play out on your team?\n\n#BrooksLaw #SoftwareEngineering #TechLeadership #ProjectManagement #EngineeringManagement #StartupOps #Tech #ProductDevelopment"
    },
    "hashtags": {
      "tiktok": [
        "#BrooksLaw",
        "#SoftwareEngineering",
        "#TechLeadership",
        "#AI"
      ],
      "youtube": [
        "Brooks Law software",
        "why adding engineers slows projects",
        "software project management",
        "tech leadership frameworks"
      ],
      "instagram": [
        "#BrooksLaw",
        "#SoftwareEngineering",
        "#TechLeadership",
        "#ProjectManagement",
        "#EngineeringManagement",
        "#StartupOps",
        "#Tech",
        "#ProductDevelopment"
      ]
    },
    "channel_id": "chris-meredith",
    "source_url": "text://chris-meredith/1784517671983",
    "thumbnail_title": "MORE ENGINEERS MADE IT WORSE"
  }
}

Thumbnails

Variant 1

GPT Image

Imagen 4.0

Variant 2

GPT Image

Imagen 4.0

Variant 3

GPT Image

Render Jobs

audiocompletedAttempts: 0 · 07-20 03:28:40

compositecompletedAttempts: 0 · 07-20 05:07:12

Video Preview

Loading preview...

Studio

Chat with Claude Code to surgically edit this render without re-running the full pipeline.

Sessions

No Studio sessions yet.

Select a session or open a new one to begin.

Revisions

No revisions yet. The original render remains version 1.

Job Detail

Extracted Content

Script Generation Prompt

Script

Thumbnails

Render Jobs

Video Preview

Studio

Sessions

Revisions

Redistribute