Enjoyed the article!

I gave up and wrote my own definition for vision:

A vision statement is an inspirational postcard from an aspirational future. It should be brief. It should paint a picture. And it should make you wish you were there.

the.codegardener.com/vision-missi...

Excellent suggestions.

One other challenge: what happens when the OPUR is unavailable or leaves the organization? Is there backup? Would it not make more sense for there to be a team instead of one person?

In other words, as the OPUR, I am empowered but don’t have time. The people on the rotation have time but don’t feel empowered because there is an OPUR. I do not see that as a healthy dynamic.

I’m thinking about changing the run book for the process to make updating the run book part of the process.

“Could you make that change for me so the next person in the rotation can benefit from your learnings?” usually works.

Rather than update the docs or work on the backlog of tickets to further automate the process, they tell the coordinator (me) that changes need to be made. But I am just one person. By making me the OPUR, nothing is happening to improve the system. So I turn it around on them.

We have a gated deployment process that requires a human to push buttons and check dashboards as a build goes through automated end-to-end tests in staging and canary before being promoted to production. We have a rotation of engineers who run the process. They have downtime while tests run.

You know Fito and I will be there!!!

I end up using the right half of my left monitor and the left half of my right monitor.

You’ll need a good window manager. I use magnet on MacOS.