Surprisingly enough:<p>* Politics within the organization<p>* Interfacing with legacy broadcast&#x2F;video library systems (f<i></i>* you Grass Valley, and your abomination of a video asset management system)<p>Serving video online is fairly straightforward, although it wasn&#x27;t always. We&#x27;ve come a long way from RTMP and progressive HTTP downloads. With HLS, MPEG-DASH, etc, you&#x27;re still moving the same bits, but you have a much better end user experience.<p>Netflix has original renditions for all of its content in S3, which they convert into multiple renditions based on bitrate and other video metadata, and their player then intelligently switches based on available bandwidth. Its (mostly) that easy, unless you&#x27;re the White House or SpaceX streaming to millions of people at once. That&#x27;s still a bit tricky, and you usually call Akamai, Limelight, or Encoding.com to solve that.<p>If I had to do it all over again, I&#x27;d create a small startup team (no more than 10-15 people) to create a platform that lets you white label so anyone could build their own Netflix with their own content (or licensed content) and iterate ruthlessly. Don&#x27;t partner on storage or CDN, just create modules that let you plug n play based on the rates you can get (API libraries all the way down). Setup a partnership department to hook customers up with hardware vendors (Apple TV, Chromecast, Roku, those folks). Keep in the front of your mind that tech is commodity but relationships are what&#x27;s going to put you in tens of millions of homes.<p>I left because no one realized how quickly other parties in the space (Hulu, Netflix, Amazon, Google, etc) were innovating. We&#x27;d spend <i>months</i> in the weeds, with little momentum on key features. In 5-10 years, broadcast is completely dead, its airspace auctioned off to cellular providers. This does not get through to traditional broadcast folks.