The development and changes are fast, not only because the business really did not think clearly, but also because we did not build a system that can flexibly accommodate changes in job function email list the business. So don't blame the business for saying that his needs are changing . We job function email list ourselves have not fully figured out what our products look like. If we just turn making products into meeting needs, then the needs will keep changing.
Then yours Products have been constantly changing, but their goals job function email list and values are basically the same , but when we really set KPIs, we may focus on the precipitation of the product's own capabilities in addition to business value. The embodiment of the goal of the product, so it is probably such a relationship, and then I will give an example first . Take the sales crm of the internal business system as an example. Let me first talk about the sales crm in an internal business system, which is a transactional job function email list platform.
He builds a system for selling crm by himself. Then we w ill look job function email list at his product framework, which is a business link at that time. , where is sales management, and what is his core positioning? Then we based on this positioning, we try to do some dismantling for the field of this product. In fact, the positioning of the business field and the field positioning of the product are basically the job function email list same, as long as other fields are compared with your field. With a clear matching relationship, then you can directly and clearly say that your product field is nothing more than serving this result.