A five-step guide to use Design Strategy for API design

Image for post
Image for post

Introducing Design Strategy

Design Thinking, as we know, is a methodology that was developed by IDEO[1] for creative problem solving. The core principle behind Design Thinking is to be empathetic with the customer, identify their pain points, their journey through the product, their opportunities and needs, and get to a solution that truly solves their most important problems first, instead of creating a product that customers didn’t need or won’t use.

Design Strategy is a way to combine Design Thinking with strategic thinking[2] to create a product that not only provides a creative solution to the problem but ties the solution in with the business goals. …

Managing data when there’s already a data management system to manage is relatively easier, and I wrote about some ways to tackle that problem as a Product Manager who takes it on here.

However, ideating from scratch on data management, as a PM for infrastructure or platform, is a little bit different and slightly more challenging. For starters, there might not be clear requirements for you start with as the PM, there might simply be a vague notion that the organization needs someone to manage the backlog of ad-hoc requirements coming in. In addition, there might not be a strategy around how these requirements ought to be prioritized, and to top it, your team might actually have several stakeholders with conflicting interests, and you, as a PM that’s starting out with the team, might not actually have the birds’ eye view of how to go about prioritizing because you don’t have complete information. …

Image for post
Image for post
The things you’ve got to think about with data

I wrote about how being a Product Manager for a data product is different than being a Product Manager for data here.

One of the questions I encounter more frequently from PMs managing data is about frameworks and metrics that we could use to efficiently track and manage all of our organizational data. In this post, I want to take some time to go over some processes that have worked for me, or for PMs I’ve worked with, when it comes to managing data.

Getting Product Managers to manage data is a relatively new development, and was a role traditionally handled by many different people, from Program Managers to Technical Product Managers, to even Data Engineers. It doesn’t matter what your title is, if you’re managing data to make it consumable by analytics, and if one of your primary goals is to make data generated from your product easily accessible and processed for analytics, these processes will work for you. …

Image for post
Image for post

On some of the product management groups and in online conversations, I have seen the term Data Product Manager become more popular in the past couple years.

Of course, the functions of a data PM existed even more the buzzword did, but just like every other fancy buzzword that beefs up the resumé, Data PM sounds cool, and obfuscates understanding at the same time.

The catch is, what you’re managing actually impacts the how you manage, so in this case, managing data and managing a data product are not interchangeable. …

About

ANWESHA BHATTACHARJEE

Product Manager, Data Products in Travel. I’m curious about human interactions and their reflection in data, and what that says about society at large.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store