Skip to content

Commit 8b4fab3

Browse files
committed
feat: Add speaker and program files for Ben Rockwood and Heather Osborn
1 parent 4970b3e commit 8b4fab3

File tree

4 files changed

+82
-0
lines changed

4 files changed

+82
-0
lines changed
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
+++
2+
Talk_date = "2025-03-07"
3+
Talk_start_time = "14:00"
4+
Talk_end_time = "14:45"
5+
Title = "How did it come to this? Untangling SA Dev(*)Ops SRE and PE"
6+
Type = "talk"
7+
Speakers = ["ben-rockwood"]
8+
+++
9+
10+
In this talk I'll break down the winding road that got us to a place of so many titles and share experiences, my own and others, on the pro's and con's of so many roles. We'll also step back and look at other industries to seek for some parallels we might draw upon. Finally I'll attempt to provide a working solution to the problem. My hope is for this talk to be interactive and engaging for the entire audience.
11+
12+
<style>
13+
p {
14+
text-align: justify;
15+
}
16+
</style>
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
+++
2+
Talk_date = "2025-03-07"
3+
Talk_start_time = "15:00"
4+
Talk_end_time = "15:15"
5+
Title = "Turning Incidents into Insights, Not Insults"
6+
Type = "talk"
7+
Speakers = ["heather-osborn"]
8+
+++
9+
10+
Let's face it—most incident retrospectives are about as useful as debug logs without timestamps. They're full of finger-pointing, hindsight bias, and theoretical scenarios where everyone acts with perfect foresight. It's time to change the script. In this talk, we'll explore a blame-aware, human-centered approach to incident management, where every incident becomes an opportunity for meaningful growth, not just a checkbox on the postmortem list.
11+
12+
Instead of "who dropped the ball?" this approach asks, "what did we learn, and how can we make things better?" By focusing on quality observability, a useful service catalog, and leveraging a strong customer support team as our first line of defense, we'll transform incident management from a reactive cycle into a proactive practice. We'll dive into designing retrospectives that generate actionable insights without the usual counterfactual time-traveling ("If only we had…") and that bring genuine improvements rather than finger-pointing. We'll look at ways to identify commonality between incidents to identify systemic issues instead of just classing everything as 'code bug'.
13+
14+
With quality observability, we'll demonstrate how teams can identify and resolve issues before they become five-alarm fires, using metrics that actually matter. We'll discuss how to build a service catalog that doesn't make you wish for the simpler days of "Ctrl+F," helping everyone—DevOps, engineering, and support—stay aligned and informed. Finally, we'll look at how to integrate customer support as a critical part of incident management. Far from being an afterthought, support teams offer front-line visibility into issues as they're happening, making them invaluable partners for incident management and retrospectives.
15+
16+
Attendees will walk away equipped with practical strategies to build an incident management culture that emphasizes continuous learning and real improvements. By the end of the session, you'll be ready to lead retros that focus on insights over blame, avoid the "Groundhog Day" of recurring incidents, and leverage every incident as a chance to build stronger systems and stronger teams. Regardless of your role, this session will show you how to turn retrospectives into a powerful tool for continuous improvement and resilience.
17+
18+
<style>
19+
p {
20+
text-align: justify;
21+
}
22+
</style>
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
+++
2+
Title = "Ben Rockwood"
3+
type = "speaker"
4+
image = "ben-rockwood.jpg"
5+
linktitle = "ben-rockwood"
6+
+++
7+
<h3>
8+
VP, Engineering & Operations
9+
Mondoo
10+
</h3>
11+
12+
<p>
13+
Ben Rockwood is the VP of Engineering & Operations at Mondoo
14+
</p>
15+
16+
<style>
17+
p {
18+
text-align: justify;
19+
}
20+
</style>
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
+++
2+
Title = "Heather Osborn"
3+
type = "speaker"
4+
image = "heather-osborn.jpg"
5+
linktitle = "heather-osborn"
6+
+++
7+
<h3>
8+
Engineering Manager, Developer Enablement
9+
Zapier
10+
</h3>
11+
12+
<p>
13+
Heather Osborn has been working in technology as a system and operations engineer and manager for the last 25 years, moving from physical to cloud infrastructure.
14+
15+
Heather is an avid long distance runner who has lots of time to think about these things while pounding the pavement.
16+
17+
https://twitter.com/brokenheather
18+
</p>
19+
20+
<style>
21+
p {
22+
text-align: justify;
23+
}
24+
</style>

0 commit comments

Comments
 (0)