This is how long does it take a user to complete an action. Since our product infrastructure team focuses on developer needs, one of the biggest metrics is how long does it take a developer to actually understand the tool, and then how long it takes them to integrate such that it is useful.
This is the number of developers or teams actually using the tool. When building an infrastructure product, it is important to make sure it is a general solution such that multiple teams can benefit, and hopefully many teams in the future semesters.
This is the number of errors a developer faces when they try to integrate your tool.
Before any team integrates, test the tool and walk through the integration process, and write DOCUMENTATION explaining how to do every part of the process. If possible, include screenshots and diagrams.
When a team wants to integrate, have them read through the documentation and ask you questions. If they don't ask questions, ask them questions to make sure they understand it. Once they start actually using the tool, be easily accessible to fix bugs. Since this is your first user, there often will be a couple of bugs you find or small features you need to add.
After the first team has integrated, explain that if a team finds a bug or has a feature request, they should POST AN ISSUE and notify the maintainers. Feature requests are a good thing, it means that there is a demand for the tool. However, you don't want there to be too many bugs, as developers will often choose to not use the tool if it prevents their application from working or often doesn't provide them meaningful data.