SLIDE 1
AN ARCHITECT’S GUIDING PRINCIPLES FOR LEADERSHIP
Seth Dobbs @sethdtech
SLIDE 2
- 1. Overview
- 2. Three Overarching Principles
- 3. Architect’s Principles
- 4. Wrap up
AGENDA
SLIDE 3 Seth Dobbs | @sethdtech
SLIDE 4 4
Seth Dobbs | @sethdtech
- “Digital” is becoming core to business
- We as architects need leadership skills equal to our technical skills
- Responsibility to guide business and align broad strategy
- Need to effectively communicate to our teams and motivate them
LEADERSHIP IS AN ARCHITECT’S IMPERATIVE
SLIDE 5
Seth Dobbs | @sethdtech
The goal of leadership is to influence individuals, teams, and organizations to effectively deliver durable results
LEADERSHIP
SLIDE 6 6
Seth Dobbs | @sethdtech
- Personal Mastery
- Individual Responsibility
- Self reflection
INTERNAL EXTERNAL
- Interdependence
- Responsibility for Others
- Team Learning
TWO ASPECTS OF LEADERSHIP
SLIDE 7 7
Seth Dobbs | @sethdtech
- Teaching through principles is powerful
- Developers use tech principles all the time (DRY, YAGNI)
- Principles are to guide you, not tell you what to do
WHY PRINCIPLES
SLIDE 8 Seth Dobbs | @sethdtech
- 2. THREE OVERARCHING PRINCIPLES
These form the core of good leadership and good team members
SLIDE 9
Seth Dobbs | @sethdtech
The goal of leadership is to in influ luence individuals, teams, and organizations to effectively deliver durable results
LEADERSHIP
SLIDE 10 Seth Dobbs | @sethdtech
- I. LEADERS PROVIDE VISION
...and can provide a path to realizing the vision
SLIDE 11 11
Seth Dobbs | @sethdtech
Seneca
To the person who does not know where he wants to go there is no favorable wind.
SLIDE 12
Seth Dobbs | @sethdtech
Outcome-focused view of how to solve the problems we’re faced with
WHAT IS VISION?
SLIDE 13
Seth Dobbs | @sethdtech
The goal of leadership is to influence individuals, teams, and organizations to ef effec ectivel ely deliver durable results
LEADERSHIP
SLIDE 14 Seth Dobbs | @sethdtech
- II. LEADERS SOLVE PROBLEMS
…and deal with difficult things, take ownership, focus on outcome
SLIDE 15 15
Seth Dobbs | @sethdtech
Patrick Lencioni
The high point of being a leader in an organization is wrestling with difficult decisions and situations. Truncating those high points just doesn’t make sense.
SLIDE 16
Seth Dobbs | @sethdtech
If all you want to do is say a few good words and hope for the best…you’re not ready to lead
DEALING WITH THE DIFFICULT
SLIDE 17
Seth Dobbs | @sethdtech
The goal of leadership is to influence individuals, teams, and organizations to effectively deliver du durabl ble results
LEADERSHIP
SLIDE 18 Seth Dobbs | @sethdtech
- III. LEADERS CREATE MORE LEADERS
…through continual improvement, through learning organizations, through principles
SLIDE 19 19
Seth Dobbs | @sethdtech
Ralph Nader
I start with the premise that the function of leadership is to produce more leaders, not more followers.
SLIDE 20
Seth Dobbs | @sethdtech
Enabling team members to be better at what they do is a good thing
CREATING MORE LEADERS
SLIDE 21
- 3. ARCHITECT’S PRINCIPLES
SLIDE 22
Seth Dobbs | @sethdtech
“Why aren’t you coding?” “We need to do something, now!”
THE ANTI-PATTERN: BE BUSY!
SLIDE 23
Seth Dobbs | @sethdtech
BIAS TO OUTCOME > BIAS TO ACTION
“We have to achieve something” vs. “We have to do something”
SLIDE 24 Seth Dobbs | @sethdtech
Coding is an action. The goal is creating an interaction between people and/or systems that delivers a useful
PRINCIPLE APPLIED
SLIDE 25
Seth Dobbs | @sethdtech
“I take on everything that comes my way” This is a good way to get buried and fail at everything
THE ANTI-PATTERN: NEVER SAY NO
SLIDE 26
Seth Dobbs | @sethdtech
DON’T JUST SAY “YES”
Some think that success comes from saying ”yes” to everything Simply not true and will actually have the opposite result If everything is important, nothing is important
SLIDE 27
Seth Dobbs | @sethdtech
Defend your ability to succeed Vision for your role should help you prioritize
PRINCIPLE APPLIED
SLIDE 28
Seth Dobbs | @sethdtech
“We need a mobile app” Solutions in search of problems
THE ANTI-PATTERN: LEAD WITH SOLUTIONS
SLIDE 29
Seth Dobbs | @sethdtech
SHAPE THE PROBLEM BEFORE THE SOLUTION
A problem well-stated is a problem half-solved Work to clarify and bound the problem
SLIDE 30 Seth Dobbs | @sethdtech
A problem statement should have a desired
- utcome that isn’t happening or an existing
- utcome that shouldn’t be happening
PRINCIPLE APPLIED
SLIDE 31
Seth Dobbs | @sethdtech
“Because I’m the architect”
THE ANTI-PATTERN: I’M IN CHARGE
SLIDE 32
Seth Dobbs | @sethdtech
LEADERSHIP IS RESPONSIBILITY, NOT AUTHORITY
Leaders have a responsibility to make team members succeed, not an authority to make their ideas hold.
SLIDE 33
Seth Dobbs | @sethdtech
Acknowledge and enlist
PRINCIPLE APPLIED
SLIDE 34 Seth Dobbs | @sethdtech
- 1. I need someone to tell me what to do
- 2. …
- 3. I have all the answers and tell others
what to do
THE ANTI-PATTERN: FALSE STAGES OF MASTERY
SLIDE 35
Seth Dobbs | @sethdtech
GETTING TO RIGHT > BEING RIGHT
People have more ownership in problems that they help solve
SLIDE 36 Seth Dobbs | @sethdtech
- 1. I need to be taught what to do
- 2. I begin to realize how much I don’t know
- 3. I learn to ask the right questions
PRINCIPLE APPLIED
SLIDE 37
Seth Dobbs | @sethdtech
“But what about this (esoteric) detail???” The CEO’s laptop…
THE ANTI-PATTERN: THE ROADBLOCKER
SLIDE 38
Seth Dobbs | @sethdtech
DON’T PRIORITIZE MINUTIAE AT THE EXPENSE OF A GOOD SOLUTION
Not all requirements or scenarios are equal …even though parts of the business may not want to hear this
SLIDE 39
Seth Dobbs | @sethdtech
Do the heavy lifting for high usage cases Get data to understand edge cases
PRINCIPLE APPLIED
SLIDE 40
Seth Dobbs | @sethdtech
“I need to review everything”
THE ANTI-PATTERN: I AM THE CENTER OF ALL THE THINGS
SLIDE 41
Seth Dobbs | @sethdtech
MAKE YOURSELF OBSOLETE
…so that you can tackle the next big problem
SLIDE 42
Seth Dobbs | @sethdtech
Provide architectural principles to enable the dev team to make decisions in your absence
PRINCIPLE APPLIED
SLIDE 43
Seth Dobbs | @sethdtech
“We really need to optimize this query” “The servers can’t support high throughput”
THE ANTI-PATTERN: A PROBLEM IS IN THE EYE OF THE BEHOLDER
SLIDE 44
Seth Dobbs | @sethdtech
IF THE BUSINESS DOESN’T THINK IT’S A PROBLEM, IT’S NOT A PROBLEM
This doesn’t mean we can’t address technology problems We need to state them as business problems
SLIDE 45
Seth Dobbs | @sethdtech
Translate our technical problem statements to business problem statements
PRINCIPLE APPLIED
SLIDE 46
Seth Dobbs | @sethdtech
“That’s a bad requirement because it doesn’t fit our architecture” “That’s not agile!”
THE ANTI-PATTERN: SERVE THE MEANS
SLIDE 47
Seth Dobbs | @sethdtech
DON’T ELEVATE THE MEANS BEYOND THE END
We as an industry have a tendency to do this Sometimes we feel distant from the value of the company and focus on what we can control to make our work interesting Sometimes organizations like their rules
SLIDE 48
Seth Dobbs | @sethdtech
Our business needs don’t serve our architecture, our architectures enable us to achieve something
PRINCIPLE APPLIED
SLIDE 49 Seth Dobbs | @sethdtech
SLIDE 50 50
Seth Dobbs | @sethdtech
- Principles are to guide you, not tell you what to do
- Think about why you make the decisions you make
- This is where principles come from and helps you refine your
understanding of your own approach
PRINCIPLES
SLIDE 51
Thank You!
Twitter: @sethdtech LinkedIn: https://www.linkedin.com/in/seth-dobbs/ Blog: https://www.seth-dobbs.com
Seth Dobbs