The pancake-style revision can be simply understood as - everything you want to change, everything you want to do, and the final product is fancy and bulk sms service messy. So how do we try to avoid it in our product work? The author will answer for you. The so-called pancake-style revision is usually a product-level change, and the version is beautiful but daunting. Either you want to create a perfect and sound product right from the start, which is only a data loss compared to competing products; or the product needs to iterate on new functions, experience optimization, and a new UI bulk sms service revision. I want to change everywhere. A case of revision The first one is the social product for strangers. It does not grasp that the core of products is to connect people.
Without understanding the social tools, the content community function is built in a large and comprehensive way - the content bulk sms service production (publishing system) ), content organization (topics, topic squares), content consumption (square feed flow), user attention system (follow user feed flow, follow circle feed flow), private message chat and message system, etc., all in one go. The result can be imagined, because the user’s needs were not well met and the user’s pain points were not solved, the project was finally dismissed. The other is a content community bulk sms service product, which has been in operation for a while, users are more active, and the community atmosphere is also good. The latest iteration is to upgrade the product container side around content production.
However, with the intervention of the bosses, the final version became bigger and bigger, and it became a major revision of the product level, which required bulk sms service both new functions, system-level optimization, and a whole-body UI revision. … This kind of thing is especially true in the early stages of a product. It stands to reason that the early stage of the product should not pay more attention to ? In reality, this is often not the case. There is a lot of infrastructure work to be done at this stage, but often everyone wants to do it (both... and...), and every time I want to do a lot, it lacks planning thinking and rapid iteration awareness, and it lacks rhythm. Control ability. In addition, the bosses were bulk sms service waving big sticks in the back. In order to give the boss a reassurance, he had to make a fat man in one bite. This kind of revision, because the plan is so beautiful, there is no problem in thinking about it,