5-question quiz on communicating platform strategy: roadmaps, build vs. buy, deprecation, and north star metrics. Advanced
0 / 5 completed
1 / 5
A platform product manager presents the "internal platform roadmap" to engineering leadership. How does an internal platform roadmap differ from a product roadmap for an external product?
Correct: B. An internal platform roadmap applies the same roadmap discipline as an external product but targets internal users (engineering teams). It is shaped by developer pain points, adoption data, and engineering productivity goals — not by market analysis or sales pipeline. Sharing it transparently with internal teams builds trust and reduces surprise deprecations.
Developer pain points, adoption metrics, engineering productivity data
2 / 5
The platform team is deciding whether to build an in-house observability solution or adopt a vendor product. A principal engineer frames this as a "build vs. buy decision." What factors most directly drive this decision?
Correct: B. Build vs. buy is a strategic decision weighing multiple factors: how differentiated the capability needs to be, what level of customisation is required, total cost of ownership over 3–5 years (including maintenance), vendor reliability, and whether the capability is core or supporting. Building is rarely cheaper short-term but may be necessary when no vendor solution fits the requirement well.
Factor
Favours build
Favours buy
Differentiation
Highly unique to your context
Commodity capability
TCO
Vendor cost exceeds build over time
Vendor is cheaper than build + maintain
3 / 5
A platform engineer says: "We need to communicate the deprecated endpoint's sunset date clearly to consuming teams." What is deprecation communication?
Correct: B. Good deprecation communication treats internal teams as customers: they need enough lead time to migrate, a clear description of what replaces the deprecated feature, and explicit dates for when support ends. Insufficient communication causes production breakages and erodes trust in the platform team.
Deprecation communication element
Why it matters
Sunset date
Teams can plan migration sprints around a concrete deadline
Migration path
Teams know what to move to and how to do it
Support window
Teams know when to stop raising issues with the old feature
4 / 5
A platform director says: "Our north star metric is time-to-first-deployment for new teams." What is a platform north star metric?
Correct: B. A north star metric is the one number that best captures the core purpose of the platform. It keeps the team aligned and prevents short-term optimisations that don't move the metric that actually matters. "Time-to-first-deployment" is a strong platform north star because it directly measures developer productivity and how frictionless the platform experience is for new teams.
North star quality
Why it matters
Single, unambiguous
Everyone agrees on what the platform is optimising for
Reflects user value
Improvements to it mean real developer productivity gains
5 / 5
The platform team announces: "We are releasing v2 of the deployment API while keeping v1 active for 90 days." What does maintaining versioned API contracts mean for an internal platform?
Correct: B. API contract versioning is a core practice of treating the platform as a product. Consuming teams build integrations with an expectation of stability. Breaking that silently creates production incidents. A 90-day parallel-run period gives teams time to migrate without emergency work, which builds trust in the platform as a reliable dependency.
Practice
Effect on consuming teams
Versioned API with deprecation window
Teams migrate at their own pace; no emergency production fixes
Breaking change without notice
Unexpected production failures; trust in platform erodes