-
Today we finished a workshop regarding Platforms as Product based on @TeamTopologies Course, #DomainDrivenDesign, and Starting with Why from @simonsinek Giving product purpose and not only engineering purpose has been crucial to define our vision 🙌 academy.teamtopologies.com/courses/platform-as-a-productPermalink On twitter.com
♻️ 4 Retweets ❤️ 9 Favorites Mood +3 🙂
-
@TeamTopologies @simonsinek We addressed things as: 👉 Platform Vision 👉 Platform Goals 👉 Personas aka our dev colleagues 👉 Thinnest Viable Platform 👉 DevEx 👉 Platform Adoption All of that with a product and business perspectivePermalink On twitter.com
-
@TeamTopologies @simonsinek It's so easy that we, as developers, we rabbit hole our conversations into technical stuff, losing perspective of why and for who we do it. We need to separate our engineering strategy from our product strategy. Being able to connect the dots between why a platform existsPermalink On twitter.com
-
@TeamTopologies @simonsinek We measure our success as: 👉 Other teams adopt the platform only if they find it useful instead of a top-down decision 👉 It has an impact on cognitive load 👉 See a decrease in issues in production by concentrating forces on making our system reliablePermalink On twitter.com
-
@TeamTopologies @simonsinek Today, we started behaving in a product approach. Still, long road ahead to be a real Platform as a Product. We can get back to the old habits so easily and be lost in the engineering specifics and lose the high-level perspective. Here is where leadership helps keep directionOn twitter.com