At Juice, we’ve helped our clients launch dozens of data products that generate new revenue streams, differentiate their solutions in the market and build stronger customer relationships. Along the way, we’ve learned a lot about what works and doesn’t. In this series I’ll take you through what you need to know to design, build, launch, sell and support a data product.
Part 1: Getting Started
The first step in building a great data product is to pinpoint a customer need and determine how your unique capabilities will solve for that need.
A successful data product lies at the intersection of the three circles in the following Venn diagram:
Your customer’s pain point, an urgent problem they want to solve;
The characteristics of your data which can be brought together to solve that problem;
The capabilities you have to enhance the value of the data to make it as useful as possible.
Take the Academic Insights
data product we designed and built for US News and World Report as an example of finding this intersection. (1) Their customers, university administrators, needed to understand how they compare to peer institutions and where they could best invest to improve their performance and stoke student demand. (2) US News was sitting on decades of detailed survey data and rankings to compare universities of all types. This data was unique in its breadth and historical coverage. However, the data was essentially stored in old copies of the paper magazine, not a format that was conducive to delivering insights to their target audience. (3) That’s where our data visualization and user experience capabilities helped them turn this data into a web-based analytical tool that focused users on the metrics and peer groups they cared about.
Let’s dive a little deeper into those three elements:
1. Pain Points
We’ve noticed a temptation with data products to forget the cardinal rule of any product: it needs to solve a specific problem. Without this focus, a data product comes in the form of a massive 100-page PowerPoint deck or a collection of raw data tables. There may be value in the data, but it is clear the product manager hasn’t thought deeply about their customers and what the data can do to solve their problems. I spoke to a credit card executive recently who mentioned how his bank spent huge sums of money on benchmarking reports. Despite his deep experience, he was unable to make sense of the reports he was sent. These are lost opportunities to deliver powerful data products.
“Your users are your guidepost. And the way you stay on the right path in the early stages of a startup is to build stuff and talk to users. And nothing else.” — Jessica Livingston, co-founder of Y Combinator
With data products the core question of your user is: What information or insights will let you make better decisions and perform better in your job?
Look for those unique situations where indecision, ignorance, or lack of information are blocking smart actions. Rather than solving your user’s pain, you need to enable them to solve their own pain. Physician, heal thyself.
2. What’s unique about your data?
The foundation of your product should be data that is somehow unique, differentiating, and valuable. In our experience, the right raw materials can come in a few different forms:
Breadth: Do you have visibility across an entire industry? Or population segment? Breadth allows you to provide benchmarks and comparisons that aren’t otherwise visible to your customers. One of our clients has data on the learning activities of more than 60% of all healthcare workers.
Depth: Can you explore deeply the behaviors of individual people, companies, or processes? By drilling into these activities, you may have the power to predict future behaviors or find correlations that aren’t visible to others. Fitbit
tracks massive amounts of personal activity data from each individual user.
Multiple data perspectives: Are you in a position to combine data sources across industries or connect disparate data sources? By bringing together different perspectives on your subject, you may be able to answer new types of questions or explain behaviors through a multi-faceted perspective.
Naturally, having breadth, depth and multiple perspectives is best of all. Companies like Google, Apple and Amazon have profound data assets because they can both see human behaviors across a large audience and they know a lot about each individual.
3. Your value-added data package
It is seldom enough to create a data product that is simply a pile of data. That isn’t to say we haven’t seen many companies that believe that a massive data extract represents a useful solution to their customers.
People don’t want data, they want solutions.
How are you going to turn that data into a solution? There are many paths to consider:
Visual representations that reveal patterns in the data and make it more human readable.
Predictive models to take descriptive data and attempt to tell the future.
Industry expertise to bring understanding of best practices, presentation of the best metrics, analysis of the data, and thoughtful recommendations. Bake your knowledge of the problem and the data into a problem-solving application.
Enhancing the data through segmentation, pattern recognition, and other data science tools. For example, comments on a survey can be enhanced with semantic pattern recognition to identify important themes.
Enabling users with features and capabilities to make them better in their job. The user’s ability to analyze, present and communicate insights can be a value-add to the raw data.
If you can determine the right recipe of customer need, data and value add, then you’ve gone a long way toward defining the foundation of your data product. But before getting down to designing the data product, you’ll want to get the right people in place.
4. The right product manager
We’ve helped launch data products in many industries including healthcare, education, insurance, advertising and market research. The most important factor in turning a concept into a business is a quality product manager. The best product managers have a vision for the product, understand the target customers, communicate well, are definitive in their decisions and recognize the reality of technical trade-offs. For a more complete list of general product manager skills, check out this Quora answer
For data products, we’d emphasize a few more skills. The product manager needs to understand the data, what it represents and the business rules behind it. It helps if she is a subject matter expert, but if not, she should know when to bring in more expertise. Finally, she needs to understand the technical challenges involved with building a data product and be able to weight the impact of changes (which are often necessary as you learn more) against the benefits of launching sooner and gathering customer feedback.
5. Get stakeholder buy-in early
Kevin Smith of NextWave Business Intelligence
(a consultancy focused on data products) warns
: “Get the critical stakeholders involved and in agreement early or you’ll end up reciting the history of the project and why key decisions were made many times for many people.”
Launching data products is a journey that doesn’t end at the product launch. It also can push your organization into new and uncomfortable ground. These realities highlight the need to build broad support early in your process. Ask yourself:
Is IT on board to provide development support, data access and data security resources and sign-off?
Is the COO ready to provide resources after launch to support and maintain the product?
Is your legal team confident that the data you’ve been collecting and incorporating into your data product is available for this new purpose?
Is the marketing team ready to support a product launch that includes all the resources, collateral and creativity required of any new product?
Is the sales team in place to understand the product, the target audience and establish the sales framework for pushing the product?
“The secret to getting ahead is getting started.”
― Mark Twain
For data products, this means finding your sweet spot at the intersection of customer needs, your data, and data product value add. And then getting the right people lined up to make your product a success.
Part 2: Development
If “Data is the Bacon of Business
” (TM), then customer reporting is the Wendy’s Baconator. Sure it contains bacon, but nobody is particularly happy with themselves after eating it.
In a recent blog post
, we described the differences between customer reporting and data products. Those differences result in some very different functional requirements. In particular, data products require more C.L.I.C. D.R.A.G.
Context — Benchmarks, comparisons, trends, and/or goals that encourage decision-making.
Learn — Help and support features to train users to get value from the information.
Integration — Connections with other software systems to integrate with data and enable operational actions.
Collaboration — The ability to save insights and communicate them with other people. Decisions aren’t made on an island.
Documentation — Because data products live on and touch many people within your organization.
Reporting — To track usage of the data product.
Administration — Features to manage users and control permissions.
Guidance — To point users to the most effective ways to explore and understand the data.
This collection of capabilities gives some indication of the gap between your standard customer-facing reporting and a complete data product. To accomplish all of these, you’ll need more than a talented BI report writer and access to your database. In our experience, the recipe for building a successful data product is dependent on a number of specialized roles.
The Product Manager sets the vision of the product. He gathers the necessary resources to make the team successful and builds organizational support for the product.
The UI/UX Designer understands the user’s workflow and how to best guide the user to decisions. She crafts the interface and interactions to make the data intuitive. She’s also in charge of design application styling and all visual elements.
The Business Analyst translates application design into technical and data requirements. She’s responsible for documenting business logic as product decisions are made.
Front-end Application Developer
The Front-end Application Developer’s role is all about building interface elements, interactions, and data visualizations.
Back-end Application Developer
The Back-end Application Developer does everything the Front-end Developer does, only backward. Just kidding! But he does build the application server environment and define data queries to support UI interactions.
In addition to having the coolest title, he provides access to raw data sources. He understands and communicates the meaning of data fields and calculations to the development team.
The Data Scientist defines the questions that will help end-users make better decisions. She enhances data through predictive modeling and other advanced data analytics techniques.
He’s the general technical architecture of the product, responsible for figuring out how the application connects to data sources and integrates into other systems.
Quality Assurance Engineer
The Quality Assurance Engineer evaluates whether the data product meets the need and requirements set out in the design process. He also tests data accuracy and product functionality.
It’s a big load. That’s why you might want some help before going at it alone. At Juice, we’ve built a technology solution and an expert team
that fills out many of these requirements. We have a platform, Juicebox
, that ensures your application is a first-class user experience. Combined with our experienced design and implementation teams, we’ve got many of the resources covered. Our clients bring the product vision; we make it happen.
Our goal at Juice is to streamline the data product launch process so you can launch innovative data products in weeks, not months. Want to know more? Give Juicebox a try.