Platform Engineering Maturity Model Assessment We are looking for feedback on this pilot assessment, so please share your thoughts. Investment Who builds your platform? Ad-hoc groups Temporary teams or individuals working together informally Technical team Dedicated platform team with general technical skills Product-focused team Dedicated team with technical, product, and design skills Full specialist team Dedicated team with comprehensive specialized roles Where do new platform capability needs come from? Crisis-driven Urgent, immediate needs Problem-driven Fixing existing issues Strategy-driven Planned roadmap of features Community-driven Planned features plus community input How do you validate new capabilities with platform users? No involvement Users aren't part of the validation process Informal feedback We ask for feedback in an ad-hoc way Co-creation Users help define what capabilities are needed Full partnership Users involved throughout definition, testing, and release How is your platform initiative funded? No funding No direct investment or budget Basic funding Money allocated to form a dedicated team Results-focused funding Funded team with clear expected outcomes Strategic investment Funded team with outcomes plus community building Adoption How do platform users discover its capabilities? By chance Users stumble upon features accidentally Scattered sources Information exists but in inconsistent places Central catalog Single place to find capabilities, users start there Interactive catalog Single source plus users request missing features How do platform users select tools? Build their own Users typically create custom solutions Platform considered Users look at the platform but often choose alternatives Platform evaluated Platform compared fairly with other options Platform preferred Platform is the first choice over alternatives How does your organization encourage platform use? Little support No clear guidance, only local advice Basic support People understand the platform's value but adoption is still low Good support Platform use is a clear goal that individuals embrace, creating momentum Strong support Everyone understands the value and actively engages with the platform beyond basic use How does the platform team encourage adoption? Build it and they'll come Assumes good capabilities will naturally attract users Leadership engagement Platform team works with user team leaders Planned promotion Each new capability has an adoption strategy Community focus User engagement is as important as building features Interfaces How do users access the platform's capabilities? Request-based Users ask the platform team to provide what they need Self-service tools Users access tools and components themselves One-click access Users get capabilities instantly from a central location Customizable access Users get instant access and can customize results Does the platform team consider developer experience or productivity? Not considered Developer experience and productivity aren't priorities Occasional consideration Sometimes discussed but not systematically addressed Regular focus Developer experience is regularly considered in platform decisions Core priority Developer experience and productivity drive all platform choices How are capabilities offered to end users? Individual tools Stand-alone tools or components Fixed solutions Pre-approved solutions that can't be customized Self-service solutions Users can access approved solutions themselves Composable solutions Users can build and customize their own solutions How is onboarding supported? Heavy support needed Users need deep help from the platform team Some support needed Users can self-serve but often need assistance Minimal support needed Users can self-serve with almost no help No support needed Capabilities integrate seamlessly with existing tools Operations How do users find out about platform updates? No communication No announcements are made Standard location Updates shared in a consistent place Updates plus roadmap Standard location includes future plans Automated notifications Standard location plus proactive alerts How do teams request new platform features or capabilities? Individual assessment Platform teams evaluate and plan each request separately Self-service Application teams build what they need themselves Centralized requests Teams ask platform teams to build features for them Shared ownership Clear process with defined roles, working toward a service-based model How does your platform team deliver and maintain capabilities? Informal support Reactive approach, fixing issues as they arise Defined processes Standard processes exist but teams apply them differently Centralized management Standard processes managed centrally with shared responsibilities Automated management Standardized, automated approach with clear responsibilities and minimal disruption How is the platform's evolution managed? No planning No formal process or long-term plan Team prioritization Platform teams gather and prioritize requests Goal-aligned process Defined process that evaluates requests against organizational goals Product economics Platform managed as a product with economic decision-making Measurement Have you agreed how platform success will be measured? Unclear success It isn't certain what success looks like Conflicting views Different opinions exist but aren't aligned Broad agreement Organization has alignment on what success means Insight-driven metrics Data used for learning and improvement, not just targets How do you measure the business outcomes of platforms? No measurement We don't report against business objectives Proxy metrics We measure feature success using adoption or time saved Success-first approach No feature added until we know how to measure success Continuous improvement Teams constantly refine metrics and data collection How is user feedback collected and used? No participation Users don't participate and don't feel heard Informal feedback Casual mechanisms exist for user feedback Dedicated ownership: Product manager or team member drives feedback collection User contribution Users actively contribute to the platform How do you collect user satisfaction with the platform? No structured collection We don't collect user satisfaction in a structured way Surveys and monitoring We use surveys or forums to understand user sentiment Active structured approach We actively seek user satisfaction through structured methods Cultural priority User satisfaction is embedded in our culture