Sign in to confirm you’re not a bot
This helps protect our community. Learn more

Armchair Architects: Architecture and Ambiguity

Microsoft Developer
589K subscribers
<__slot-el>
<__slot-el>
1.6K views 2 years ago #AzureEnablementShow #ArmchairArchitects
Software architects are often called upon to create solutions to problems that are ambiguous. How do they deal with these often-nebulous situations? Join #AzureEnablementShow host David Blank-Edelman for a conversation with our #ArmchairArchitects, Uli and Eric, in which they offer their perspectives on how to avoid pitfalls such as false precision and confirmation bias. Resources • Read Eric's blog post: Architecture and Ambiguity https://techcommunity.microsoft.com/t... • Managing ambiguity – an emergent skillset   / managing-ambiguity-emergent-skillset-steve...   • User Experience Design Principles https://learn.microsoft.com/en-us/dyn... Related Episodes • Armchair Architects: So, you want to be an Architect? https://aka.ms/azenable/83 To watch more episodes in the Well-Architected Series, check out our playlist: https://aka.ms/azenable/yt/wa-playlist To watch more episodes in the Armchair Architects series, check out this playli …...more
...more

Introduction

0:00

How do architects respond when a customer approaches them with an ambiguous problem?

1:35

Isn’t ambiguity what Agile is supposed to solve?

2:51

You shouldn’t design a solution based on initial assumptions; get feedback and reset expectations along the way

3:12

Two things to keep in mind: how humans deal with ambiguity, and a clearly defined North Star

4:06

Uli uses Visual Studio Team Foundation Server as an example

6:06

Can architects get training to deal with ambiguity?

7:50

A lot of these principles come out of the User Experience discipline

8:28

How can you tell when you’re experiencing false precision or confirmation bias?

10:33

Don’t be an order taker; it’s ok to have an opinion and to challenge assumptions

12:34
Armchair Architects: Architecture and Ambiguity
37Likes
1,695Views
2023Jan 4
Software architects are often called upon to create solutions to problems that are ambiguous. How do they deal with these often-nebulous situations? Join #AzureEnablementShow host David Blank-Edelman for a conversation with our #ArmchairArchitects, Uli and Eric, in which they offer their perspectives on how to avoid pitfalls such as false precision and confirmation bias. Resources • Read Eric's blog post: Architecture and Ambiguity https://techcommunity.microsoft.com/t... • Managing ambiguity – an emergent skillset   / managing-ambiguity-emergent-skillset-steve...   • User Experience Design Principles https://learn.microsoft.com/en-us/dyn... Related Episodes • Armchair Architects: So, you want to be an Architect? https://aka.ms/azenable/83 To watch more episodes in the Well-Architected Series, check out our playlist: https://aka.ms/azenable/yt/wa-playlist To watch more episodes in the Armchair Architects series, check out this playlist! https://aka.ms/armchairarchitects Chapters 0:00 Introduction 1:35 How do architects respond when a customer approaches them with an ambiguous problem? 2:51 Isn’t ambiguity what Agile is supposed to solve? 3:12 You shouldn’t design a solution based on initial assumptions; get feedback and reset expectations along the way 4:06 Two things to keep in mind: how humans deal with ambiguity, and a clearly defined North Star 6:06 Uli uses Visual Studio Team Foundation Server as an example 7:50 Can architects get training to deal with ambiguity? 8:28 A lot of these principles come out of the User Experience discipline 10:33 How can you tell when you’re experiencing false precision or confirmation bias? 12:34 Don’t be an order taker; it’s ok to have an opinion and to challenge assumptions

Follow along using the transcript.

Microsoft Developer

589K subscribers