"There are days in which I wish my biggest problem was the implementation of Kubernetes. I think you'll feel that with me. Cat Morris: Yes, that's the easy problem. Diana Montalion: We're going to talk about friction. The most important thing to know is that friction is a systemic issue. There isn't one primary cause. Cat Morris: We're going to start by telling you a little story. You are wrapped around our architecture and product campfire right now."
"Diana Montalion: We're going to focus on six different areas. Understanding the system. Fire that guy. You'll see what that means when that comes up. Designing knowledge flow. Becoming learning driven. Architecting relationships. Focusing on goals. Cat Morris: Actually, this is the theme that we want to tell you about through this whole thing, and that is architecture and product need each other. Our jobs are a lot more similar than we originally thought when we started writing this talk."
"Once upon a time, there was a software engineer and a systems architect named Diana Montalion. When organizations needed a "transformation", monolith to microservices, event-driven, domain-driven design, then let's get Diana, because this is what Diana does. She'll figure out how much it's going to cost us and when it will be delivered. This really isn't what I'm going to do. I always get really excited, because I love to do hard things. I love to solve difficult problems."
Friction in organizations arises from multiple systemic causes rather than a single source. Six focal areas for reducing friction are understanding the system; removing obstructive individuals or processes; designing knowledge flow; becoming learning driven; architecting relationships; and focusing on goals. Architecture and product functions must collaborate closely because their responsibilities and challenges overlap. Transformations like monolith-to-microservices, event-driven, and domain-driven design require assessing costs and delivery timelines. Organizational structures and processes often create barriers that slow change. Identifying what holds back change is essential to successful transformation.
#organizational-friction #systems-architecture #product-architecture-collaboration #transformation-strategy
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]