You can find these #platform engineering resources at: https://lnkd.in/eztzjbTi Take a stab at mapping yourself to the model. Find your baseline. Take inventory. It works really, really well. If you'd still like help getting started with your team's platform initiatives then book a time with Seth McGaugh here: https://lnkd.in/eUZc2R7F
Transcript
As far as kind of measuring and looking at how things change overtime, because a lot of us are here to figure out what the heck of platform is and how do we get started. It was one of the reasons we wanted the maturity model or built that in the 1st place. From a measurement standpoint and thinking about where we get started, we have to start with a, a baseline. We have to actually document our platform. So when we look at that, our first measurement of the platform is just our inventory, mapping out the capabilities that we need, making sure we have a clear understanding of who our users are and what they actually need, what tools we have. In place and making sure that that's documented. That also goes back to operations and interfaces. Your documentation is an interface. It helps people understand how they're supposed to use the platform and leverage the platform to get their jobs done. So the best place to start is to get that inventory in place and use it as a tool to define who is responsible for what today. Over time, as you learn more about your users and more about the capabilities they need, that will change and you'll be able to introduce new capabilities and swap out old. Capabilities and start to move on that path to migration. Now that goes back to another measurement, which is like you could call it I guess Net Promoter score or something similar, but how well do your users actually understand how to use the platform it that could be if you're providing a platform to 3rd party users, does your documentation enable them to get the full experience from what your platform provides is that there does that exist for most cases it does not exist so getting that. Documented measuring how well users can leverage your platform and effectively use your platform is important, but then that all leads down to velocity. I wanna make sure that as we introduce these new capabilities that we're helping people get their jobs done easier and faster, that we ship products. And that could be a data workload that's generating report, that's a product. It could be a new app that we have developing that's a product. It could be, you know, a, a sales report that needs to be sent over to my my super, that's a product. So is our platform enabling them to do those kinds of things? But it's it starts by working through the process and map yourselves to the maturity model. It actually works really, really well.To view or add a comment, sign in
