Sprint 1 — The flip side

My other series focusses on sharing tips and concepts with data scientists who want to learn more about product. I’m giving that POV a break for a moment, and sharing my thoughts on how to transition from a product manager to an ML product manager.

I started working in a product-focused company immediately after earning my PhD. The job was with a company that was new to incorporating ML into their software. Lucky for me, this was my second career and so I had maturity that helped deal with some difficult discussions. I have…


Sprint 5 — Done yet?

This is a continuation of a series that started here. The article is based on my own experience as an ML PM, yours may be different.

Scientists are curious individuals. In my experience, we also tend to be perfectionists. Especially afflicted are those that have a PhD.

Software products are developed in an iterative way. Design, build, QA, and then release. Repeat. Every release will have bugs. And, every release will have room for improvement.

These two realities may be at odds with each other.

As a data scientist in a product team, it is…


Sprint 4 — Product Integration

This is a continuation of a series that started here. The article is based on my own experience as an ML PM, yours may be different.

The last article was all about the documentation required to assist in productizing your work. What does it mean to productize something? And what about ML in a product?

The process of creating something new is messy and often has unexpected challenges.
The process of creating something new is messy and often has unexpected challenges.

Products are a special consumer of ML. When I start working with a data scientist that is not familiar with product, I try to teach them about the most important concepts for the integration of ML:

  • Automated — The models…


Sprint 3 — The Docs

This is a continuation of a series that started here. The article is based on my own experience as an ML PM, yours may be different.

During sprint 2, I wrote about the product team from from the perspective of a software company that uses ML to implement specific features. I hope that I managed to convey the following:

The development team writes code to create a maintainable, optimized software product using a process to ensure an acceptable level of quality. These objectives are different from yours.

What does this mean? Well, most likely (in…


Sprint 2 — The Team

I am an ML product manager sharing my perspective based on my own experience in software products. This is part of series to explain to aspiring Data Science professionals what is like to work in a product role. The start of the series is here.

As cliché as it is, no one does it alone. Not even the super techie with the unbelievably good idea that makes a bazillion dollars. To get a great idea into a product that will make customers glad that they bought it, takes a lot of talented people. With respect to this article, The Team…


Sprint 1 — Intro

I am an ML product manager. What does that mean? Well, I do all the regular PM stuff such as:

  • talk to customers,
  • identify requirements,
  • write specs and stories,
  • prioritize features,
  • work with Dev and QA to implement the feature…

Also, I have a technical background that includes image and signal processing, machine learning, engineering. Prior to working as a PM, I worked as a data scientist (DS), before it was commonly called that. Which means I also:

  • consider what problems should have ML in its solution,
  • work with DS to make their work productizable,
  • work with Dev on ML…

Tyna Hope

An ML product manager. Bio on LinkedIn. Opinions expressed are my own.

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