The best way to improve your product is to talk to your customers. The next best way is to talk to your development team.
Systems are becoming more fragmented, distributed. The number of devices running and interacting with these systems is increasing.
Echoes of yesterday's sessions - poor domain understanding leads to pain, unnecessary complexity and incorrect models.
Use "event storming" to involve all parties in modelling the domain.
Team leads should not be the only domain expert. The entire team should be involved.
The greatest understanding comes from immersing ourselves in the domain. We should always be looking for ways to improve our understanding. 
There are no perfect decisions and no absolute solutions. Everything is contextual.
Isolate modules that are high-value (monetary / ROI) so that these are not affected by low-value couplings.
A single model might not represent an entity correctly in all contexts. Know the boundaries of your context.
Contextual boundaries often correspond to separate teams.
Software Engineers should not blindly build what the customer asks for. We need to take the time to understand their business and design an appropriate solution.
