[J-FALL] Empathetic Architecture

Transcript

1. the human factor you might be missing when designing your system # jfall.
2. Do you think you're empathetic when you are building software?
3. Agenda • Introduction • Empathy • Socio technical systems • Conway’s law • Hidden Monoliths • Team Cognitive Load • Takeaways
4. @ About Me Rafael Maia Developer / Architect / Lead • Works as Solution Design Chapter Lead at ABN Amro • DDD, Event Driven, DevOps • Java, Golang and JS • Lives in Zaandam, Netherlands • Plays for amateur clubs: Futsal and Volleyball • Loves outside, BBQ, beer, Friends, family and sleep early! in/rafmaia92/ @rafmaia92 www.rafaelmaia.nl
5. What is Empathy? The ability to understand, share, and resonate with the feelings and perspectives of others.
6. What is Empathy? • Understanding someone's thoughts or perspective. Cognitive Empathy • Feeling what someone else feels. Emotional Empathy • Understanding, feeling, and being moved to help. Compassionate Empathy
7. Importance of Empathy • Builds trust • Fosters open communication • Cultivates positive relationships.
8. What does empathy have to do with designing systems? - everything
9. Empathy as a Pillar • Human-Centric Design • Collaboration and Communication
10. Socio-Technical Systems
11. Socio-Technical Systems (STS) A socio-technical system (STS) encompasses both the social and technical aspects of an organization, recognizing that the performance and well-being of one component affect the other.
12. Socio-Technical Systems Technical: Infrastructure, hardware, software, and technology-related processes. Social: People, culture, communication, relationships, and organizational structure
13. The Unicorn Project
14. The Unicorn Project – key concepts • The Five Ideals: • Locality and Simplicity • Focus, Flow, and Joy • Improvement of Daily Work • Psychological Safety • Customer Focus • The Age of Software and Data: Emphasizing the importance of delivering software quickly to the market to meet business objectives. • Overcoming Organizational and Technical Debt: Highlighting the challenges and struggles developers face due to bureaucratic hurdles and outdated systems.
15. Maxine's journey at Parts Unlimited showcase • Silos and Communications • Adaptive Challenges • Empowerment and Autonomy • Interdependence
16. Success on STS The theory stipulates that the success of the socio- technical system is a product of the interactions between these subsystems.
17. #Takeaway 1 Align Technical & Social Systems
18. Conway’s Law Conway's Law predicates that the design of any system will mirror the communication structure of the organization that designed it.
19. Conway’s Law Implications • Organizations with fragmented communication will produce fragmented systems • Organizations with effective, cross-functional communication will produce more integrated systems.
20. Conway’s Law Impact Recognizing the influence of organizational structure on system design can lead to more conscious design choices and potentially better system architecture.
21. Hidden monoliths Result from companies with fragmented or isolated communication structures. These monolithic structures are unintended, but they emerge because subsystems aren't truly decoupled.
22. Decoupling Systems Proper decoupling requires not just technical adjustments, but also organizational changes. Without balancing both, companies accidently reinforce monolithic architectures.
23. #Takeaway 2 Respect Conway’s Law
24. Team Cognitive Load
25. Team Cognitive Load Team Cognitive Load refers to the collective mental effort used by a team in working memory while performing tasks.
26. Related to the inherent difficulty of the task. Intrinsic Load Extraneous Load Germane Load
27. Originates from how tasks are presented, affected by communication and resources. Intrinsic Load Extraneous Load Germane Load
28. Involved in constructing mental representations contributing to teamwork. Intrinsic Load Extraneous Load Germane Load
29. The tale of the boy of Code Ville
30. Once upon a time there was a boy learning how to code...
31. The Ultimate Backend developer • JAVA • C++ • Servlets • Linux Servers • Concurrency • Memory • Any other buzzword you can imagine
32. Full Stack Developer Hyper specialization DevOps Security Wizard Jedi
33. Too hard to catch up
35. •Hard to communicate •Impostor syndrome •Slow Deliveries •Bad Code/ Architecture •Not Happy •Burnout
36. And About the TEAMS Absence of Trust Fear of Conflict Lack of Commitment Avoidance of Accountability Inattention to Results
37. Reducing Team Cognitive Load • Clear Role Definition & Boundaries • Simplify & Prioritize • Effective Communication & Documentation • Limit Multitasking & WIP • Feedback & Supportive Environment
38. #Takeaway 3 Mind the Team Cognitive Load
39. Wrap up
40. So far, we have seem a bit of: Empathy STS Conway's’ law Team Cognitive Load
41. The Takeaways 1 • Align Technical & Social Systems 2 • Respect Conway’s Law 3 • Mind the Team Cognitive Load
42. Wait, the final and most important takeaway from this session
43. #Takeaway 4 Use Empathy, be nice and listen.
44. Please rate my session in the J-Fall app # jfall. in/rafmaia92/ @rafmaia92 www.rafaelmaia.nl Stay In Touch