Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Team and Software: Making an Impact as an Archi...

Sponsored · SiteGround - Reliable hosting with speed, security, and support you can count on.

Team and Software: Making an Impact as an Architect

Many believe that software architects primarily structure software and make technical decisions. But in reality, it’s about much more: your ideas and decisions must be implemented by the team and aligned with all stakeholders. Moreover, the organization itself has a significant influence on the architecture.
That’s why it’s so important for architects to be effective - both within the organization and in the architecture itself. This talk demonstrates how to achieve that in practice, drawing on years of experience as an architect and architecture consultant.

Avatar for Eberhard Wolff

Eberhard Wolff

March 24, 2026
Tweet

More Decks by Eberhard Wolff

Other Decks in Technology

Transcript

  1. Teams and Software: Making an Impact as an Architect Eberhard

    Wolff Head of Architecture https://swaglab.rocks/ https://ewolff.com/
  2. Architecture IMHO Quality characteristics Technologies Won’t solve user friendliness Structure

    Maintainability Performance, maintainability, user friendliness, security …
  3. Software Architecture: Hard Skills • Software architects do need hard

    skills • Common knowledge • So why talk about it in details? • And: How are the skills useful if nobody listens to you? • You can hire, read, or learn hard skills quite easily.
  4. Let’s implement part of the system! There is just so

    much code you can write! But I stay in touch with the code and the system! Maybe – but will you see all of the system?
  5. “I must stay away from fighting the fire myself. …even

    though it is fun and I can do it.“ “I must lead and coordinate.“ “You could do it because you don’t know what fire fighting is about..“
  6. What is the Most Important Skill in IT? • We

    asked people at a technical conference. • Just an experiment • We did not really think about possible answers. • By far the most common answer: communication, soft skill …
  7. What is the Main Challenge in Software Architecture? • Survey

    through social media What is the biggest challenge in #SoftwareArchitecture in your opinion?
  8. What does that mean? • Most important skill in IT:

    Communication • Main challenge in software architecture: Soft skills
  9. Making an Impact: Convince! • Enforce the architecture you came

    up with. • I.e. convince others • Developers but also managers • Is this helpful? • Can you really make other do your bidding? • You can only really influence yourself.
  10. Making an Impact: Communicate! • Try to understand the different

    perspectives! • Provide feedback about your perspective! • Learn • …and make your knowledge usable
  11. Override Management? • Common exercise in my trainings • Result:

    Yes, we want to be able to override. • After discussion: Technical people just want to have a conversation. • I am happy that management does management things. • You can always escalate. • So: communication is the key.
  12. Communicate! • Architects sometimes accept management decision as final. •

    As a consultant, I am paid to provide feedback on them. • Why would architects not be able to do that, too? • So: Provide feedback! Management
  13. Fearless Change • Strategies to introduce ideas to organizations. •

    Token: To keep a new idea alive in a person’s memory, hand out tokens that can be identified with the topic being introduced. • Local Sponsor Ask for Help from first-line management. When your boss supports the tasks you are doing to introduce the new idea, you can be even more effective.
  14. Communicate! • Management: budget, deadline, politics • Translate your perspective

    into this world! • If your decision does not make sense in the management world – does it make any sense? • Helps to focus and set priorities Management
  15. Communicate! • Developers: experts for code and details • Ask

    for feedback and problems! • Architects are not super developers. • Architects work on a different level. • Goal: Support developers Developers
  16. Probably There is a Reason • Get a clearer picture.

    • Find contradictions in a perspective and make them explicit! • Find contradictions to others and make them explicit!
  17. Probably There is a Reason • What people do or

    say sometimes seems stupid or mysterious. • But in their mind, it makes sense. • If you figure out something is “stupid“ in five minutes, ...it is not hard to figure out. • Hard: Why is still implemented / said?
  18. Probably There is a Reason • Words make sense only

    in the context of values and motivations. • Try to understand their point of view! • Otherwise: How will you work with them? • Try to walk in their shoes! • You might call that empathy.
  19. “The death of human empathy is one of the earliest

    and most telling signs of a culture about to fall into barbarism.” Hannah Arendt German and American historian and philosopher https://commons.wikimedia.org/wiki/File:Hannah_Arendt_1955_(cropped).jpg
  20. Quality of Decision vs Autonomy •Decisions have two levels: Quality

    of the decision How the decision is made impacts autonomy •E.g. let the team decide or push a decision through?
  21. Quality of Decision vs Autonomy JavaScript Framework: Architect pushes decision

    through Quality of the Architecture Autonomy Architect probably thinks his / her decision is great
  22. Quality of Decision vs Autonomy JavaScript Framework: Architect pushes decision

    through Quality of the Architecture Autonomy Architect probably thinks his / her decision is great …but team might have some expertise. Even if it is great – is it worth it?
  23. Decisions •Moderate, listen, convince •Don’t enforce •Make your expertise usable

    •General rule for managing self-organization Architects Team
  24. Decisions / Moderation • Meeting • One person on the

    whiteboard. • Meeting will be dominated by that person. • Work will be sequential not parallel. • Discussion in pairs? • Post its? • …
  25. Socio-technical Architecture Reviews • Architecture reviews often focus on the

    software. • Software is a product of a social system i.e. a team. • Let’s focus on the team! • Result: Working teams instead of a slide deck.
  26. Auftragstaktik (Mission-type Tactics) • Unit gets a mission e.g. hold

    the bridge + a reason e.g. so we can retreat • Should reach the goal in whatever way they see fit. • Commander’s intent: If the retreat is done, no need to hold the bridge any more.
  27. Tenerife Aircraft Crash • Deadliest aircraft disaster • Two Jumbo

    Boeing 747 collided on the ground • Extremely senior crews • Including a KLM “rockstar” • Crashes have many causes! • Flight engineer: “Where is the other 747?“ https://creativecommons.org/publicdomain/zero/1.0/deed.en
  28. Crew Resource Management & Architecture • Use the expertise of

    the full crew! • The only thing the captains decides by themselves is to abort a take-off.
  29. Crew Resource Management • Use every resource to the fullest!

    • Resources: humans and technical tools. • This is about making air travel even safer. • This is not about making everyone happy. • Don’t confuse “happy” and “successful”.
  30. Can Pushing Through be Successful? •Other industries emphasize collaboration. •In

    particular, if the stakes are higher than in many software project. Architects Team
  31. Is this Culture? • No • Crew Resource Management and

    Auftragstaktik are learned and being taught. • At scale • In very practical exercises
  32. Interaction Retreat • Let’s spend a day to practice interactions!

    • With Martin Heider and Eberhard Wolff • We already did it for a customer with great feedback! • Interested? http://ewolff.com/interaktionsretreat.html
  33. Failure • Talks often make things seem simple. • We

    all fail all the time in communication. • Communication is never perfect. • Sometimes things are just clear in retrospect. • We are driven by not just by logic but also emotions.
  34. Conclusion •Being an architect seems to be about hard skills.

    •But it is a lot about soft skills …and you know it. • This can be taught and learned. • We all fail all the time.
  35. DRINK A VIRTUAL COFFEE WITH ME! Eberhard Wolff Head of

    Architecture https://swaglab.rocks/ https://ewolff.com/ https://swaglab.rocks/virtueller-kaffee/eberhard/
  36. Slides + more Powered by Amazon Lambda Email address logged

    for 14 days, wrong addressed emails handled manually Scan QR code or send email to [email protected]