Want to collaborate?

Right now, you can get in touch with me for a few things:
Participating in User Research
Guest lecturing
Open Source Contributions
+ more

Michel Cantacuzene

  • @michmich
  • Product Manager | CMU Software Management '22
  • he/him
  • Mountain View
Software Management @ Carnegie Mellon University Silicon Valley.

Leader with a multicultural background 🇫🇷🇺🇸🇨🇦🇹🇳🇯🇵
Experience in Software Engineering 💻
And a passion for making the products of tomorrow 🚀
Read more
I'm available for
Michel's Collections

Articles and blogs

1 Highlight
May 03, 2022
May 03, 2022
Demo'd Care.io's new product and had a great conversation with Dima about the company and possible improvements i could see.
Proud to say I am not burnt out yet 💪
Good luck to the Care team! Excited to see how the product grows.
Read more
Apr 12, 2022
Apr 12, 2022
Rehighlighted by Michel Cantacuzene
Had a great morning learning from Matt's product management experience.
Our discussion helped me find some skills I can improve on and helped me solidify my career goals.
Gave Matt some insight as to how I use Polywork and some possible improvements.

Thank you Matt! 
Read more
Product Director, Polywork
Apr 12, 2022
Enjoyed chatting with Michel about my journey in product management and got some great feedback about Polywork.
Product Director, Polywork
Feb 13, 2022
Feb 13, 2022
Released a fix for a breaking change in Svelte-kit.
Svelte recently released svelte-kit v-2.0.0 which caused a breaking change in my sveltekit-adapter-chrome-extension.
Just released a backwards compatible fix. 
Read more
Feb 13, 2022
Feb 13, 2022
Started learning Flutter!
Excited to see what I'll be able to build with it!
Read more
Feb 09, 2022
Feb 09, 2022
My previous start up, Sweater Planet (prev. The Sweater Guys)  has been acquired! 
Excited to see how the technology is used in the future!
Read more
Feb 01, 2022
Feb 01, 2022
I went too quickly in my previous post about my product management adventure (link in the comments)....

I jumped the gun and started talking about implementation. The truth of it is that there are 2 important planning steps that did before starting the implementation.

  1. Defining the success of the product
  2. Identifying the #metrics we need to capture to identify that success  and causes of success.

The success of my product was based on its goal (which goes back to the problem I was trying to solve). 

My primary goal was to create save user’s time by creating a platform where they could find, create and share a specific type of content. 

My secondary goal was to improve the user experience interacting with this type of content to make it more engaging (although we will not address this second goal for the time being). 

I would then consider the product successful if:

  • Users were saving time by finding the content on the site quickly (from google or anywhere else on the site)
  • At least 5% of Users engaged with the content by sharing it, searching for other content or creating some themselves (quality content and interested audience)
  • At least 2% of visitors were retained week over week (stickiness)
Although these seem arbitrary at first, they serve as the foundational goal for my MVP as by seeing if these goals are met I will know what I need to work on to achieve them.

Taking inspiration from Alex Reeve's January 2021 post on product metrics (link in the comments), I attempted to Identify my NorthStar and Signposts metrics linked to my products goal and success definition. As this is an MVP I chose not to add specific Guardrail metrics but instead set lower-bound alerts for some of the Signposts metrics.

North Star: Average user engagement time


  • Number of users (for a given time period)
  • User source (direct? Social Media? Organic Search?)
  • Average page views per session (do users go to other pages which increases their engagement time? Do most of the users have to navigate to find the content they are looking for)
  • Monthly user retention (how many users come back month over month?)
  • Search Position and Click through rate (we want the content to be well tailored for the users and easily accessible)

  • Average engagement time under 8 seconds → content is not properly tailored to the user
  • Retention under 2% → not the right users or not the right content
  • Lower Search Position and Click through rate → content not engaging/important enough for Search Engines to promote it for users
By defining what success was and the metrics I needed to track to asses it, I had now a better idea of what to build and what to include for the MVP. I was now ready for the final planning step before implementation: the product release strategy and plan.

What do you think about these metrics? Which ones would you have chosen?
Read more