The issue of function retention and deletion is something that I slowly figured out when I was working on a product.
Here I cite the function of "copying" data objects in the product.
The situation was like this:
There is a page in our product that manages a email list certain type of data, but these data objects will be copied and used. (Imagine if you just want to slightly modify the title of an article and send it to another person, you will choose to copy edit or rewrite. I think most people will use copy to deal with it.)
We have put a lot of thought into this: whether to copy the latest version or copy the entire state at the moment of copying the data object (objects have a concept of version); if the data object is copied to the current category, whether to allow copying; whether the data object can be copied across products copy? Wait, a series of questions about replication plagues us.
Ultimately in MVP, I cut this feature for three reasons:
First: The copy function is not a core function, and it can be added later. Not now, the core process of the product can still run through;
Second: The copy function needs to design logic based on user scenarios, it is not a simple operation function;
Third: Even if the copy function is developed, it may not be the copy form that the user wants.
Above, let me decide to focus on the core functions, and in the MVP, I don’t understand everything, and I’m not sure whether users will really need the functions that are cut off.
I think, which features in MVP should stay and which ones can be cut. On the one hand, it depends on whether the core process can still run without this function; on the other hand, it depends on whether it is a necessary function (see KANO for filtering).