30 Minute Guide

Profile photo for Christopher Clark
Not Yet Rated
0:00
Elearning
6
0

Vocal Characteristics

Language

English

Voice Age

Middle Aged (35-54)

Accents

North American (General)

Transcript

Note: Transcripts are generated using speech recognition software and may contain errors.
why I wrote Holtz. For an entrepreneur, there is always one nagging question that has to be answered every single day. What should we build next? As the CEO of two tech companies, this question waited me as soon as I opened my laptop in the morning and was still on my mind when I turned out the lights before bed each night. What do we build next is such an important question, because the answer determines whom you hire, how much you spend and most importantly, rather your company will succeed or fail the building phases, where your blood, sweat and tears, not to mention money all go. But how do we decide with the build? What determines which projects we should invest in improving versus which ones we should ignore? For most of the history of product development, employees built whatever the boss wanted than the bills. The leader of the company sent down orders from on high, and teams got to work turning that vision into reality. Sometimes the executive was right, and the innovation will be successful, but most often those at the top were wrong. Product teams will spend months, if not years, typically isolated from customers building products that no one ultimately wanted. The lack of user input led the countless product failures. More recently, the new philosophy of innovation has changed the way many companies do. Business entrepreneurs turn. Authors such a Steve Blank and aired rice have promoted building products through continuous improvements by constantly testing and validating ideas with customers. By listening to customers feedback, they argue, companies can decrease the eyes of building something no one really wants. I'm a subscriber, an advocate of Blank and Rice's process of customer development. However, I found something missing when I implemented the methodology, the answer to that same neck and question regarding what to build.