How do you a design a feature if you don’t know for whom it is for? How do you define SLOs (Service Level Objectives) if you don’t know what your users expect from you? How do you design performance tests and workloads if you don’t know which user behavior to simulate?In this episode we have Barbara Ogris, Sr Product Experience Designer at Dynatrace, who walks us through the concept of target personas that she helped establish within Dynatrace. It changes product and observability discussions from “as a user I want …” towards “as Archie I have this need …”. Listen in and learn about design thinking, using empathy maps to define your target persona and how this can be applied to many aspects in software engineering.Barbara on Linkedinhttps://www.linkedin.com/in/barbara-ogris-6a0b6011b/Dynatrace Blog: Terminology matters: how to enhance user experience by aligning names with expectationshttps://www.dynatrace.com/news/blog/terminology-matters-how-to-enhance-user-experience-by-aligning-names-with-expectations/Atlassian persona template: https://www.atlassian.com/software/confluence/templates/personaMIRO persona template: https://miro.com/aq/ps/templates/personas/?utm_source=google&utm_medium=cpc&utm_c[…]aIQobChMI6J7Juqql-QIVCOJ3Ch3jtwWwEAAYASAAEgLxT_D_BwE&loc=9062705Adobe XD: how to define a persona: https://xd.adobe.com/ideas/process/user-research/putting-personas-to-work-in-ux-design/