BETA
This is a BETA experience. You may opt-out by clicking here

More From Forbes

Edit Story

Take A Product Management Approach To Data Monetization

Following
This article is more than 2 years old.

Central to treating data as an asset, data monetization should align with familiar research and development (R&D) and product management/marketing approaches. Not to oversimplify the many challenges and activities involved in monetizing data, certain basic concepts will reap significant rewards if executed well. 

Evolve from Data Project Management to Data Product Management

Although you may already have a data leader such as a chief data officer (CDO), or an analytics leader, the first step toward data monetization is to designate a team tasked with identifying and pursuing opportunities for and generating demonstrable economic benefits from available data assets. They may report to a data and analytics executive, into the enterprise architecture group, a chief digital officer, or perhaps even a business unit head. 

Creating a distinct, dedicated data product management role is vital especially when business and data leaders agree on pursuing direct data monetization by generating revenue or other financial benefits from licensing or exchanging their data. Typically, companies already have a defined approach for managing and marketing products. Analogously, if you are considering licensing data in any form, you need someone whose job is to define and develop the market for the data asset and to productize it.

Finding qualified talent for this kind of role can be difficult. Traditional product managers may have an advantage over other candidates, even without significant knowledge of data and analytics. But why not consider hiring individuals with experience at a data broker such as Experian, Equifax, D&B, IRI, LexisNexis, Nielsen or J.D. Power? 

Ideally, the data product manager reports to the CDO (itself an emerging role for data-savvy organizations) or into a new data product line of business head. This chain of command, askew to the IT organization, underscores that data is a business asset, not an IT asset. Moreover, a data product manager provides a counterweight to data scientists, especially, who can get seduced and obsessed by intriguing problems that may be tangential to the business objectives.

Speaking of CDOs, Gartner’s most recent Chief Data Officer Survey finds that a CDO’s success is 3.5 times more likely when they’ve met data monetization objectives, versus only 1.7 times more likely when they’ve demonstrated return on investment (ROI) from data & analytics investments, and 2.3 times more likely when they’ve successfully reduced time to market. All the more reason to hire a dedicated data product manager. 

Borrow from the Traditional Product Management Playbook

The data product manager can and should borrow liberally from existing product management disciplines for:

  • Conceiving and planning new ways to monetize data,
  • Identifying or developing information markets among partners and others, and
  • Coordinating with IT, marketing, finance, legal, and other product management groups to execute information productization objectives.

Pythian CEO Paul Vallée, the former CEO and current board member of Canada-based Pythian, said company executives spoke about their experience in taking more of a product management approach. They determined a committee approach wasn’t getting things done, and that the company required a single owner to drive the process:

“We needed somebody who understood exactly how the business works. We needed someone who had been with the business a long time and had been involved in establishing our practices. That was what we needed to do in order to break through that inertia and to get rid of the committee for day-to-day decisions. Although a group of stakeholders should always be consulted throughout the project, at the end of the day, one person needs to be a leader.”

Similarly, Samir Desai, Chief Digital and Technology Officer at Abercrombie & Fitch, said the key is getting just the right individual into the role: “Not everybody is cut out to be an innovator. I think you need to choose someone who understands the business and the technology, and who has the right kind or personality fit to play that role.”

You May Already Be a Data Product Manager

Many data and analytics professionals believe they’ve been doing data product management for years without being officially anointed. “The title may or may not matter, depending upon the organization,” offered Steve Prokopiou, Data Product & Proposition Lead at First Central. “It’s about engaging with the business and delivering what they’re looking for by acting as a translator, asking sensible, structured questions about data usage and benefit. And perhaps adopting the language of product management in doing so.” Prokopiou also suggests that having the formal moniker might give one a mandate to get involved earlier during requirements specification, rather than waiting for incomplete or difficult to translate requirements to land on their desk. 

“A data product manager does need to be entrepreneurial but doesn’t necessarily have to have a product management background,” says Lillian Pierson who calls herself a data product manager within her own firm, Data Mania, a creator of educational content. She believes that treating almost everything you produce as an actual product compels you to take a more disciplined approach. Accordingly, Pierson advises that a data product manager should have a multi-disciplinary skillset, including: 

  • An understanding of analytics or data science and data strategy 
  • Knowledge of how systems and processes operate
  • Able to anticipate what technologies work well together 
  • Knowing how to design features and functions
  • Experience with performing market or stakeholder research 
  • And of course, a penchant for people. 

Refine the Data Product Vision by Working Backward

Legendary golfer Greg Norman says he plays each hole backward in his mind. “As I step onto the tee, my mind goes to the green. Before I decide which club to hit or how to play my tee shot, I want to know the exact position of the flag - once I know that, I play the hole backward in my mind.” 

Similarly, as a data product manager, it helps to start with a vision of what you want to produce. This is just the approach companies like Amazon take. 

Ian McAllister, the former director of Amazon Day, says that working backward begins by “[trying] to work backward from the customer, rather than starting with an idea for a product and trying to bolt customers onto it.” For each new initiative, a product manager writes an internal press release announcing a finished product. “Internal press releases center around the customer problem, how current solutions (internal or external) fail, and how the new product will blow away existing solutions,” commented McAllister. “If the benefits listed don’t sound very interesting or exciting to customers, then perhaps they’re not, and shouldn’t be built.” And if not, then the product manager should continue revising the press release until they’ve come up with something better. 

It may seem to be a lot of work for an idea that may never see the light of day. But as McAllister explains, “Iterating on a press release is a lot less expensive than iterating on the product itself...and quicker!”

Follow me on Twitter or LinkedInCheck out my website or some of my other work here