I am new to product management and currently practice creating a PRD of a collaboration product for case study purposes. I will consider Figma as an example. In this product, the user can create a canvas, and then invite other people in teams to collaborate with.

Suppose the Dev Mode is a new feature, and the objective of the Dev Mode is to help the developer in the team minimize the time it takes to transfer UI to code.

When setting the success metrics for this feature, I thought it would be ideal to set the Time to transfer code from UI as a key metric to assess whether or not the Dev Mode helps developers save time. However, we cannot monitor the time for this process because there are activities outside of Figma. So, this metric cannot be measurable.

I decided to choose a more generic metric like Adoption Rate as a key metric. I don't know whether or not it is a good metric to set.

• If yes,
  • I don't know if the Adoption Rate counts at the user level (each user counts as a separate adopted "one") or at the project level (just need one developer in the team used counted as an adopted "one").
  • Dev mode is just occasionally used, not on a regular basis. So does it affect how we count the Adoption rate?
• If not, which one could be a good key metric in this case? What other support metrics should we use?

I hope someone can help me clarify this confusion.

Many thanks!