IT professionals who get involved in new product development can learn from experts speaking at a 2017 product summit.

Guest Commentary, Guest Commentary

May 4, 2018

5 Min Read

What are the greatest high-tech products and services ever launched? Apple’s iPhone? Amazon Web Services? Adobe Photoshop? Netscape Navigator? Windows XP, the O/S that’s followed CIOs for so many years?

With the push for CIOs to be more customer-centric, IT teams are more involved with the product and customer experience than ever and asking themselves, “What are the product management rules of the road?”

At this past year’s Product Leader Summit, tech executives outlined the keys to developing innovative tech products, with big IT implications.

In order to launch the next ground-breaking Amazon Web Services or game-changing Microsoft Exchange Server, summit participants discussed four principles as fundamental to product management success:

1. Assemble a High-Performing & Empowered Product Team.  Amazon’s success with AWS, “arguably the best intrapreneurship venture of our time,” stems from its ability to assemble an autonomous, high-performing product team led by Andrew Jassy. That team was fully funded and enabled, which according to Spero Ventures Partner Ha Nguyen, is key.

“You want the product team to be very empowered to make the decisions,” said Nguyen. “If you’re simply giving your product team a list of projects or roadmap, you’re doing it all wrong.”

High-performing teams should have key members in specific roles, including a product manager, designer and engineer, and that it is critical they are co-located to enhance their collaborative work. “It doesn't simply mean that you're in the same building,” she said. “You want them to be co-located. Together.”

She also added that these teams need to be focused on results, not simply steps and tasks. “Allow teams to make decisions based on the data and on outcomes,” Nguyen said. “Give the product organization KPIs or objectives and then allow them to work through the process of customer discovery, product discovery and product validation.”

2. Identify Your Target Customer & Their Underserved Needs. With your product team assembled, how do you ensure you are focusing on the right goals?

Dan Olsen, author of The Lean Product Playbook, emphasized the importance of putting target customers and their specific needs at the center of the product development process. He outlined how target markets should be defined:  “You define your target customer by capturing all of the relevant customer attributes,” he said. “These attributes can be demographic, psychographic, behavioral or based on needs.”

The latter – needs-based segmentation – is critical, because target customer segments may wish to buy the same product for very different reasons. Olsen also discussed how to prioritize opportunities and identify which underserved needs to target by using what he calls “The Importance vs. Satisfaction framework.”

Olsen pointed to the growth of ride-sharing services such as Uber and Lyft as stemming from successfully addressing important but underserved needs, including convenience, affordability and reliability.

“[These types of needs] offer excellent opportunities to create customer value,” Olsen says.

3. Avoid Overkill by Building a Wedge First.  With target customers and needs in your crosshairs, Box CEO Aaron Levie added, set some parameters to the focus process by emphasizing the importance of starting simple.

“You see a lot of early-stage products that are insanely feature-rich,” he said. “They will never be disruptive, because you’re trying to be more comprehensive than the incumbent as opposed to simpler and just focusing.”

Levie’s advice to product teams at emerging companies is for them to ask themselves, “Is there a better way to create a wedge into a user base that you can then expand from?”

He pointed to his own example with Box, which took market share from feature-rich Microsoft SharePoint at just the time that file-sharing across users and devices was becoming exponentially more important. He encourages focus and warns of feature creep, saying feature requests “can truly wear down your entire product or engineering organization if you don’t think about these properly.”

How do teams balance and prioritize external requests and needs with the need to focus?  These are “moments of truth,” explained Levie. “You really have to be insanely clear in your North Star.”

4. Persevere Through the Valley of Despair.  With your team, target customers and needs, and focused strategy in place, everything should progress steadily, right?


In the case of Apple’s iPhone launch, months before their shipping deadline there were “seemingly insurmountable hardware hurdles….Apple's employees scrambled as managers bickered and executives locked horns,” according to Wired.

This is not uncommon, said Deb Liu, Facebook’s Vice President of Marketplace. She described the frustrating iterations and restarts required to manage product development and launch-oriented struggles as the “valley of despair.”

At these junctures, she said, product teams must persevere. She described launching Facebook’s mobile app install ad product in 2012 after several disappointing pilots: “We said, ‘You know what? We’re just going to figure this out together.’ And we did. Each time we had a challenge, we sat in that room and we puzzled it out.”

Liu’s team succeeded in piecing together the mobile app install product to the tune of hundreds of millions of installs and a run rate of hundreds of millions of dollars per year within two years.

Facebook’s Current Challenges

Now, with Facebook’s major data privacy issues turning in to ongoing front-page headlines and hours of congressional testimony by its CEO, the company as a whole is facing an entirely new “valley of despair.” How the company’s leaders respond, along with the new services and features they launch to protect end-users, should prove just as insightful as any of these four principles for product leaders and IT professionals.

Philip Levinson is Vice President of Marketing at EdCast, which uses artificial intelligence and machine learning to provide distributed knowledge cloud platforms for enterprises, including HPE, Dell EMC, Walmart, Schneider Electric, Accenture and others. Follow him on Twitter here.

About the Author(s)

Guest Commentary

Guest Commentary

The InformationWeek community brings together IT practitioners and industry experts with IT advice, education, and opinions. We strive to highlight technology executives and subject matter experts and use their knowledge and experiences to help our audience of IT professionals in a meaningful way. We publish Guest Commentaries from IT practitioners, industry analysts, technology evangelists, and researchers in the field. We are focusing on four main topics: cloud computing; DevOps; data and analytics; and IT leadership and career development. We aim to offer objective, practical advice to our audience on those topics from people who have deep experience in these topics and know the ropes. Guest Commentaries must be vendor neutral. We don't publish articles that promote the writer's company or product.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like

More Insights