Everyone has a different understanding of operations, and a large portion of the operations group accidentally enters this circle. Different projects, businesses, and modules are responsible for, and 360 line operations will generate 360 * N times more operational understanding.

Just write down my personal understanding, the topic is about users, user value, and user operations.

01 What is a user

The explanation on Baidu is:

The so-called user is the person who uses the product

End users refer to people who use computers or network services, usually possessing a user account and identified by their username

This meaningless answer is clearly not what the operator wants.

02 Understanding of Users

A user is an object, and these objects called users have different attributes and methods: attributes refer to labels such as (name, age, height, gender, etc.), and methods refer to the user's behavior (possible and already done behavior).

So what is a user?

This question is essentially asking what defines a user, and at this point, the "user" is defined by attributes and methods as a concrete object that can exist in the objective world. In object-oriented programming, this is an instance object.

The properties and methods of an object are all the data of a user.

But what use does this have for enhancing user value through practical operations?

My favorite "Three Body" novel, the Dark Forest Theory, is also derived from two self-evident axioms combined with human experience.

Operations also have axioms similar to those in mathematical geometry (such as the shortest line segment between two points), namely:

Value=user volume * user value

Combining this formula with my personal understanding of users, I can summarize four points:

Users have different attributes, and the value of different attributes varies

Users have different states, and the value of different states varies

Users have different behaviors, and different behaviors have different values

User value is proportional to usage time