When thinking about a product, especially a B-end product involving multiple roles, this means that there is a lot of cross-departmental and cross-team collaboration and communication, which can create the risk of processing loopholes, inefficiencies, and duplication, as well as increasing costs. At this time, the use of various types of diagrams can help solve such problems, such as: information architecture diagrams, swimlane diagrams, flowcharts, etc. 1. Information Architecture Diagram Definition: It refers to the idea of a series of organic processing ideas such as overall planning, planning,
design, and arrangement of information in a specific content. The information architecture diagram is the skeleton of the product, and it can directly see information such as product modules/functions. When drawing an information architecture diagram b2b data for the first time, it will be mistaken for a simple mind map. However, drawing an information architecture is a test of the ability of a product person. Tip1: Drawing information architecture adhering to the methodology MECE principle Take an administrative business as an example: for example,
the travel function can be divided into the role module, which belongs to the category of people, and it can also be divided into the module of work, because it also belongs to the category of affairs. Products that are not clearly classified can cause cognitive ambiguity to users, and every time they look for something, they don’t know where to look. This greatly reduces the operational efficiency. In addition, for a product with unclear classification, subsequent iterations will cost more. If a new function is added, where should it be added? How to add?