5 exercises — practice the vocabulary for portal adoption metrics: active users, time to first commit, ROI, and developer satisfaction.
0 / 5 completed
Key portal adoption metrics
Monthly active users (MAU): Engineers who interact meaningfully with the portal each month.
Time to find service owner: How quickly can an engineer identify who owns a service?
Time to first commit: How fast can a new engineer make their first contribution using portal tools?
Developer satisfaction score: Survey-based measure of how useful and pleasant the portal is to use.
Portal ROI: Time savings (search, onboarding, duplication) multiplied by engineering headcount.
1 / 5
A platform team presents this metric: "Monthly active users of the developer portal: 142 out of 180 engineers."
What does active users mean in this context?
Active users is a standard product metric counting users who interact meaningfully within a time window — typically monthly (MAU) or weekly (WAU). For a developer portal, "meaningful action" means searching the catalog, viewing a service page, running a software template, or accessing TechDocs. Simply having an account does not count. 142/180 = 79% MAU is a strong adoption signal.
2 / 5
A CTO asks the platform team: "What is our time to find service owner?"
What does this metric measure?
Time to find service owner is a key developer portal ROI metric. Without a portal, finding who owns a service might require Slack messages, wiki searches, or asking around — averaging 10-20 minutes. With a well-maintained catalog, it should take under 30 seconds. Reducing this time has a direct impact on incident resolution speed and cross-team collaboration efficiency.
3 / 5
Complete the sentence from a platform team quarterly review:
"After launching the self-service scaffolding feature, our _____ decreased from 3 days to 4 hours — new engineers can now have their first commit in the same day they join the team."
Time to first commit is a developer onboarding metric that measures how long it takes a new engineer to make their first meaningful contribution. It is a powerful proxy for onboarding effectiveness and developer experience. A portal with software templates, clear documentation, and a software catalog dramatically reduces this time by eliminating the "where do I start?" problem.
4 / 5
Your platform team wants to make the business case for investing in the developer portal. Which statement best articulates portal ROI?
Portal ROI is best expressed as time savings multiplied by headcount. The most common value drivers are: (1) faster service discovery — less time paging people on Slack; (2) faster onboarding — new engineers productive sooner; (3) reduced duplication — teams can find existing services before building new ones; (4) faster incident resolution — ownership is immediately clear. Quantify these in engineering hours to make the business case.
5 / 5
A platform manager says: "Our developer satisfaction survey scores for the portal dropped from 4.1 to 3.4 this quarter."
How should this be interpreted?
Developer satisfaction surveys (often using a Likert scale or eNPS-style question like "How satisfied are you with the developer portal?") are a leading indicator of portal health. A drop from 4.1 to 3.4 is a significant signal. The right response is to investigate: run follow-up questions, conduct user interviews, or analyse which features correlate with lower ratings. Platform teams use this data to prioritise the product roadmap.