Back in 2010…
…after that
???
Panning
Architecture
Dev
QA
Prioritization
Ops
Analysis
Dev
Ops
Detailed Ridgid Processes
Rough Flexible Processes
Requirements
Requirements
Dev
QA
Dev incl. QA
Quality as a Department
Quality as Team Objective
not good
Code
Bug
Reports
Code
Ideas for
Improvement
Ops
Ops
Feedback
MORE
CONTROL
LESS
BUGS
VICIOUS CYCLE of CONTROL
MORE
CONTROL
LESS
RESPONSIBILITY
LESS
BUGS
LESS
TRUST
MORE
self
relationship
organization
market
society
Gaining Trust
and the surest way to make them untrustworthy
is to distrust them and show your distrust.
The only way to make a person trustworthy
is to trust them;
–Henry L. Stimson
former US Secretary of State
Intent
Integrity
Capabilities
Results
Competence
Character
MAKE & KEEP
COMMITMENTS
CONFRONT REALITY &
CLARIFY EXPECTATIONS
Demand clear success criteria
Push back on unrealistic expectations
Say "no"
ERROR RATE
DEPLOYMENTS
GET BETTER & DELIVER RESULTS
ERROR RATE
DEPLOYMENTS
GET BETTER & DELIVER RESULTS
MISSION
Finding someone to blame
MISSION
Finding excuses
PRACTICE ACCOUNTABILITY &
TALK STRAIGHT
MISSION
Find out how to prevent this in the future
RESPONSIBILITY
DIFFUSION
STEP UP &
TAKE RESPONSIBILITY
VICIOUS CYCLE of CONTROL
MORE
CONTROL
LESS
RESPONSIBILITY
MORE
BUGS
LESS
TRUST
VIRTUOUS
TRUST
MORE
LESS
MORE
LESS
MORE
Dear Teams,
You can't make them trust you.
But you can remove every reason not to.
Be the team they'd feel foolish not to trust.
Don't fight the symptoms.
The gates, reports, metrics.
Don't wait for trust.
Dear Managers,
Don't remove the control —move it into the team.
Trust without capability isn't trust —it's abandonment.
You hold the trust — so you gofirst. Trust is the input, not the reward.
Going first isn't letting go.
Handover the responsibility and the capability to carry it.
Dear Teams,
You can't make them trust you.
But you can remove every reason not to.
Be the team they'd feel foolish not to trust.
Don't fight the symptoms.
The gates, reports, metrics.
Don't wait for trust.
