Years ago, I made the case to the leadership of a global consumer electronics company that it should acquire a relatively young streaming-device company. The TV screen was becoming a dumb pipe, and the value was moving to the software that decided what viewers watched. Owning the startup would let the company keep making world-class TVs while extending its reach onto screens it didn’t make.
The internal teams disagreed. The company had deep hardware expertise, strong engineers, and its own smart TV software. Why buy what we could build? A few years later, the company shipped its own streaming device. It wasn’t as good as the one that the startup created, it never gained traction, and the project was shut down.
That young company went on to go public and become a leader in streaming.
The story pains me to share even now, but it’s one that gets told over and over by other businesses as they wrestle with the decision to build, buy, or partner. Artificial intelligence has accelerated the pace at which businesses can develop new products, enter new markets, and reach new customers. AI also exposes gaps in a company’s capabilities, so leaders are facing the build/buy/partner question more often. Many are defaulting to the wrong decision: build.
Why does a bias for building in-house persist? The reasons include overconfidence (“I just need four people and six months”), not-invented-here syndrome, and what I refer to as launch bias, or estimating what it takes to launch, not what it takes to run the capability.
Source link







