[Internet Week 2018 What is valuable operation?] I participated in the seminar.

Hello.
This is Miyazaki from the SS Team, Operations Management Division.
The operations management department's main responsibility is daily operation and maintenance.

I recently attended InternetWeek2018.
InternetWeek2018

What is Internet Week?

where people involved in the research, development, construction, operation, and services of Internet-related technologies gather together to
learn and discuss basic knowledge and the latest trends in Internet-related technology, and to deepen understanding and exchange.

There are various programs, but this time I
participated in the seminar "S11 What is valuable management? Learn the essence of management without being fooled by trends!" which was held on November 29, 2018.

At this seminar, we heard the following stories:

・Operation Value and Role Model
Operation Design Lab LLC
Senior Architect Yuichi Hatano

・Recent trends affecting the value of management

Mr. Masanori Fujisaki, Heartbeats Co., Ltd.

・What is valuable management? - Let's learn from concrete examples - (Talk format)
Operation Design Lab LLC Yuichi Hatano
Heartbeats Co., Ltd. Masanori Fujisaki Yayoi Co., Ltd. Satoshi Matsumoto
Wantedly Co., Ltd.
Kodai Sakabe Co.,
Ltd. Clara Online Motofumi Uno

It was very fulfilling as there were many stories that made me think about what valuable management is.

First of all, before taking this seminar, I thought about what ``valuable operations'' meant, and
personally, I thought it meant ensuring that the customer's services were in a stable state of operation.

What is “operation”?

This seminar began with a discussion of the definition of "operation."
Mr. Hatano defined "operation" as "continuous delivery of services."
For tomorrow's operational sites - from the perspective of an operational framework

Viewing it as service delivery
has the advantage of being able to view the quality of "operation" from a "service" perspective and a "delivery" perspective.
As an operator, I thought it would be easier to provide value if I looked at ``operation'' from this perspective.

A story about the engineering capabilities that support operations

The following three aspects of engineering ability are important.
1. Logical ability
2. Abstraction ability
3. Concrete ability

Among these, the most important one is logical ability, and
whether or not it is logically correct seems to be a major premise and is connected to the ability to abstract and concrete.

This is also mentioned in Google's SRE book, which was discussed in every session.

While implementation is ephemeral, documented theory
is invaluable.

At our company, we are currently working on creating a manual, but
it is very important that the document is logical.If it is not logical,
there will be many exceptions to this, and exceptions to that. I think it will happen that there is no such thing.

I thought this was a particularly important issue for me as I am working on creating manuals.

The story of “operation” and “individualization”

In the past, it has been pointed out that the response to alerts is sometimes individualized.

There are some jobs that only one person can do, but responding to alerts is a job that should not be left to the individual.
If anyone can do this, I think we can get closer to continuing to provide stable services.

To do that, you need the logical documentation (manual) that I mentioned earlier.
Logical documents (manuals) are becoming increasingly important.

A person who can create a manual logically and correctly is a person who can turn something that is personal into a non-personal.
I think that in many cases, things that are individualized are technically individualized, but in order to understand it logically and correctly and incorporate it into a manual, you
need the three engineering abilities mentioned earlier. It becomes.

I know it's difficult, but I want to work towards this level.

Conclusion

As the title of this program suggests, it made me think deeply about the value of "operation."

I used to think that "operation" meant running a customer's service in a stable manner, but when I think back to my day-to-day work, I realize that it is
only when we solve the problems that our customers are having that the customer is able to realize that the cost is worth it. I think you can feel it.

Regarding the logical part of engineering ability,
I have only read English documents such as Apache's config, and
I am almost an amateur when it comes to technology, but I have to continue studying every day to be logically correct. I thought.

It's only my second year here, but I'm really glad I was able to attend the seminar and listen to the speakers.
Also, listening to everyone's stories made me want to read the SRE books I haven't read yet.

That's all.