Restarting my reliability capability project

About 3 years ago, I started working on a visual framework for breaking down the what of reliability work in software.

My goal was to give a comprehensive view to all concerned, whether they are SREs, consultants, DevOps people, or anyone else.

It would enable you to analyze what you are doing right now, what you could be doing, and what you need to get there.

Here’s a screenshot of part of that first version:

It’s not bad at all. A lot of people messaged me and told me it was very useful.

But then someone put this fear in my mind that I am just enabling certain groups to get richer from my insights by offering this as part of their consulting…

… and I would make myself just poorer in terms of time.

I took the map down promising to bring it up when I had a more protected position to benefit in some way from it myself.

I then distracted myself with more subtle ways of getting this framework out there. But I’ve learned that subtlety doesn’t get you anywhere.

I’ve also learned one more thing: through my podcasting efforts, I have learned a lot more about the reliability space from other people.

It’s time I overcame that strange concern that I’m enriching others without enriching myself and moving forward with this.

Because sometimes you just gotta do what you gotta do. And for me, building a capability framework for reliability of one of those things.