Drawing from the three elements of trust (Motivation, Integrity, and Competence), Randy Shoup discusses how engineering leaders can work and communicate effectively with their product and business counterparts.
In the first section, we discuss
* Outcomes Over Outputs
* Integrity and Transparency
* Continuous Delivery and Estimation
In the second section, we apply these ideas in three common scenarios faced by engineering leaders:
* "We Need to Go Faster"
* Technical Debt
* Site Incident
6. Business Outcomes
• Clear business metrics
o Revenue, profit, market share, etc.
• Clear customer metrics
o Performance of key customer flows
o Failed Customer Interactions
o Availability to Business
@randyshoup
10. Engineering Discipline
• Engineers are trained in
disciplined problem-
solving
o Not everyone is
• It is our job to help
clarify and refine the
problem
@randyshoup
11. “A problem well-stated
is a problem half-solved.”
-- Charles Kettering,
head of research at GM
@randyshoup
12. Engineering is about solving
problems …
@randyshoup
… Sometimes we solve those
problems by writing code.
14. “Tell It Like It Is”
• Share both good news and bad news
o Never hide the situation
• Share engineering context
o Given common context, well-meaning people generally agree
• ”Disagree and Commit”
@randyshoup
15. “The Curse of Knowledge”
• We understand the
options, tradeoffs,
and implications
• It is our job to help
our partners
understand them
@randyshoup
16. Regular Communication
• Regular structured communication
o Up, laterally, down
o Just as important when things are good as when things are bad
• Visibility into status and issues
o Similar to monitoring a service!
@randyshoup
20. Continuous Delivery
• Show a consistent trajectory of incremental value
• Deliver on commitments
• When things don’t go as planned …
o Be Honest
o Provide Options
@randyshoup
24. Estimating Effort
• Honor request
o Planning and resource allocation
o Coordinating resources and dependencies (Marketing, Purchasing, etc.)
• Communicate Uncertainty
o Perfect accuracy is impossible, rarely required
o Ranges, progressively refined over time
o Time-boxed work
@randyshoup
32. Improvement Budget
• Explicit resource investment
o Agree on an up-front investment
(e.g., 25%, 30% of engineering efforts)
• Retain autonomy, Provide transparency
o Making these decisions is exactly why they hired you
@randyshoup
34. During the Incident
• Focus on restoring service
o Everything else is secondary, and should wait
• Shield the team
• Clear, structured communication
o Even when there is nothing to report!
@randyshoup
35. After the Incident
• Blameless postmortem
• Identify and understand the
contributing factors
• Action items and Learnings
• Follow Up!
@randyshoup
37. “Incidents are unplanned
investments, and they are also
opportunities. Your challenge
is to maximize the ROI on the
sunk cost.”
@randyshoup
-- John Allspaw, Adaptive Capacity Labs