Suggestions
Nora Jones
Founder and CEO of Jeli.io (acquired by PagerDuty)
Nora Jones is currently the Senior Director of Product at PagerDuty, leading Jeli.io following its acquisition.1 She is a seasoned technology leader and software engineer with over 10 years of experience in innovative companies.3
Career Highlights
- Founder and CEO of Jeli.io from September 2019 to November 202312
- Senior Director of Product at PagerDuty (current position)13
- Head of Chaos Engineering at Slack (February 2019 - August 2019)4
- Senior Software Engineer at Netflix (March 2017 - February 2019)4
- Team Lead/Senior Software Engineer at Jet.com (September 2015 - March 2017)4
Expertise and Contributions
Nora is known for her focus on the sociotechnical aspects of engineering, exploring the intersection of how people and software work together in distributed systems.3 She is a founding figure in the Chaos Engineering movement and has co-authored a book on the subject.4 Nora is also the founder of the Learning From Incidents community.3
Education
- Master's degree in Human Factors and Systems Safety from Lund University1
- Bachelor's degree in Computer Engineering from Virginia Tech1
Additional Roles
Nora has experience as an angel investor, working with companies such as First Round Capital, Guide, and artillery.io.14 She is also a frequent speaker at technology conferences, having delivered keynotes at events like AWS re::no-wrap[Invent.4]
Nora Jones is recognized for her expertise in incident analysis, reliability engineering, and the human factors involved in software development and operations.34
Highlights
When an incident occurs with a large impact, oftentimes the focus is on two things: stabilizing the situation, and controlling the narrative. Organizations often miss the opportunity incidents also present, learning.
While all organizations will say they support learning, many simply haven’t realized what it takes to both unearth the necessary data points and to disseminate insights after incidents so that employees (and executives) can use them for growth.
Most organizations rely on a small group of people to jump in and start fixing the situation—they are the experts and can often figure out what needs to be done and who they should call on.
And one of the best opportunities you have after an incident? Leveraging the knowledge of these experts to build more experts.
Check out my latest blog for PagerDuty here: https://lnkd.in/gsVrvGsJ
And if you'd like to talk about practical ways to build more expertise after incidents -- shoot me a message, I'd love to hear from you.
If you're investing in building the expertise of your employees, it'll enable you to run a leaner, and more collaborative organization.
A great way to invest in building expertise is through the lens of retrospecting past "uh-ohs", incidents, or unexpected situations.
However, in order to do this, it's important that there aren't just engineers in the room of a post-incident review. You'll need have representatives from various teams related to a contributing factor of the incident both involved AND talking in the incident review.
Invest in facilitation of this, keep this as a habit, and over time you'll notice your culture shifts: from various departments operating on their own agendas ➡️to one organization: understanding each others' worlds a little more deeply, marching in lockstep, and less reliance on individual expertise.
