While there are no *perfect* decisions, we can all learn to be *better* at deciding. This talk covers the intellectual and emotional aspects of making technical decisions effectively within in our complex sociotechnical environments.
Since writing a book about the importance of decisions in the
More like this
practice of software architecture I get one question more than any other: “so, how do you make the perfect decision?”
Deciding is hard at the best of times and so this talk will consider what a “perfect” decision might be in the world of software architecture. I’ll consider the importance of awareness (right context), participation (right people), timing (right moment), execution (right implementation), of flow (right delivery), of autonomy (right coupling), of alignment, of feedback, of transparency, and of outcome.
This will all be illustrated with examples and you will leave with a new awareness of who your decisions are “perfect” for, and how instead there might be better goals to have in mind.
Key Takeaways
Attendees will learn:
- how a rapidly made bad decision can be better than a slowly made great one
- How involving people who will be affected by your decision, in he decision process yields benefits for everyone
- How including those who disagree with us, even very strongly, can make our decisions better.
