TEI 196: The messy middle of new product projects – with Scott Belsky

  Achieve your product goals without losing yourself along the way Creating a new product starts with excitement and the thrill of doing something different. The launch of the product is surrounded by cheers. For many product managers, it is the best part of their work. But between the project start and the launch is where the hard work occurs. It is the messy middle, full of rocky terrain that is woefully underestimated and misunderstood. The Messy Middle is also the name of a new book by my guest, Scott Belsky. Scott is the chief product officer of Adobe and founder of Behance, the leading creative network used by more than 12 million professionals. Scott has guided many teams through the messy middle of new product projects and ventures. In the interview, we’ll address a few of the topics from this book, including: * Build your narrative before your product, * Make one subtraction for every addition, * Do the work that needs to get done—even if it’s not your job, and * Identify what you’re willing to be bad at. Summary of some concepts discussed for product managers [2:00] Can you tell us about your role as Chief Product Officer at Adobe? My obsession is building products that enhance the customer experience. Adobe’s products serve a large portion of the creative world. I started in this role 9 months ago to help make sure Adobe is ready for the next generation of customers. Adobe acquired Behance, the company I founded. I helped Adobe move its tools into the cloud and make them easier to use for people once they got there. We’re also exploring new mediums like augmented reality. I was lucky to find a role that excited me in the short term and the long term. [4:17] Who is your book written for? The book is the outcome of years of writing down notes from meetings of boards that I’m on, as well as my own entrepreneur journey. I realized I had insight into what people were doing in the middle of projects that worked for them or worked against them. The book brings those insights together to navigate the volatility that people must endure when building a product or launching a new venture.  [7:25] What do you mean by building the narrative before you build the product? I encourage product teams to put together the mock-up of the splash page for the product before they even start building anything. This helps them narrow down the focus and determine what you want the customer to experience. This becomes a compass when it comes to prioritizing features. Uber did this when they were determining whether the company should be everyone’s private driver and more upscale or taxis on demand that were accessible to everyone. The decision about which type of message they were sending dictated how the rest of the product was developed. They chose “everyone’s private driver” and chose the branding accordingly. [11:50] How should product managers think about additions and subtractions? Simplicity is hard to achieve and even harder to sustain. We often deal with problems and difficult decisions by adding complexity. The product eventually becomes so complicated that customers flock to more simple alternatives. I recommend that whenever you are adding a new feature, ask if there is another feature you can remove. Do this knowing that the more complex a product becomes, the more likely some customers are to turn away from it. Behance used to have a tip exchange that we killed because it wasn’t part of the company’s core mission. When we killed it, we found an increase in the product’s core features. [17:03] How do you deal with people who say “that’s not my job”? In my experience, some of the greatest work is done by people doing work they don’t have to do. Those people are passionate enough about something to seek it out and ha...