As a Product manager and also a DDD enthusiast I use both of these mindsets to think about whether the software could've been architected differently to make users happier. How could these things be related? Well, according to my experiences when architecting a software or even when searching for subdomains, the result can be quite different when you really get to know your end users and incorporate these learnings into models.
In this talk I would like to show you the above through a concrete example: what happens if you don't understand your users' behaviour and more importantly if you don't realise that there might be different types of users using your product. Also I will show what to do if you don't have direct connection with the end users.
Decoding Paradoxes: Why are many good ideas in Software Delivery counter-intuitive
How does deploying more frequently improve quality? How does slack time in a team improve reliability? Why should we do it more often if it hurts? These are counter-intuitive concepts that don't make sense at first, and you'll be met with a bewildered stare...