Product Management System and Program

Abstract

Provide a product management system and program that can perform the development and operation of products based on the business strategy with a predetermined quality. The product management system includes a strategic information acquisition unit that acquires strategic information defining a strategy for the product to achieve business success, a requirements specification generation unit that generates a product requirements specification based on the strategic information acquired by the strategic information acquisition unit, and a code generation unit that generates product program code based on the requirements specification generated by the requirements specification generation unit.

Description

Technical Field

[0001] The present invention relates to a product management system and a program capable of developing and operating products based on a business strategy with a predetermined quality.

Background Art

[0002] Currently, many companies are formulating business strategies using strategic planning methods proposed by universities, business schools, consulting companies, etc. In a company, constructing an accurate business strategy is crucial for the company's fate, and how to formulate an accurate business strategy based on a current situation analysis or future prediction is a common important issue.

[0003] In many cases, since strategic planning methods require advanced knowledge and technology, the formulation of business strategies is provided as a service by consultants of consulting companies, etc., while collecting fees, and it is not easy for the persons in charge within the company to easily formulate business strategies. In view of such a situation, the inventors, etc. have proposed a business strategy formulation support device that enables a strategy formulator to quickly formulate a high-quality strategy and enables a strategy proposal acceptance / rejection decision maker to improve the accuracy of judging whether to execute a strategy proposal (see Patent Document 1).

[0004] In the business strategy formulation support device described in Patent Document 1, using a learned model obtained by performing machine learning with a data set including input parameters, which are explanatory variables regarding the success or failure of a plurality of business strategies, and an objective variable indicating the likelihood of success of a business strategy as teacher data, it is possible to search for and output parameters and features that are significant (highly important for differentiation from competing companies) in a positioning strategy.

[0005] By reflecting parameters and features with high importance as specified by the technology described in Patent Document 1, etc., a highly competitive product (especially a product provided to users via a computer system such as a web service) is realized.

Prior Art Documents

Patent Document

[0006]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] In realizing a product, a requirement specification is created based on important parameters and feature quantities, and further, the product is developed based on the requirement specification. The compilation of the requirement specification is usually performed by a person in a position called a product manager (PM), but the way of compiling the requirement specification (description items, granularity of description, etc.) varies depending on each product manager, and the frequency of modification / updating of the requirement specification also varies. In addition, the product manager does not necessarily coincide with the formulator of the business strategy. Due to these circumstances, situations frequently occur where the developed product does not match the business strategy formulated as a highly competitive one, or the modification / updating based on the operation results of the product is not appropriately performed.

[0008] The present invention has been made to solve the above problems, and an object thereof is to provide a product management system and a program capable of performing product development and operation based on a business strategy with a predetermined quality.

Means for Solving the Problems

[0009] In order to solve the above problems, the product management system according to the present invention includes a strategy information acquisition unit that acquires strategy information that defines a strategy for a product to achieve business success, a requirement specification generation unit that generates a requirement specification for the product based on the strategy information acquired by the strategy information acquisition unit, and a code generation unit that generates a program code for the product based on the requirement specification generated by the requirement specification generation unit.

[0010] In the present invention, the product management system may further include a log analysis unit that analyzes the log when the user operates the product by placing the program code generated by the code generation unit on a server available to the user, derives improvement points of the product for realizing higher evaluation indicators, and feeds back the improvement points to the requirement specification generation unit. Then, the requirement specification generation unit may update the requirement specification by reflecting the feedback from the log analysis unit.

[0011] In the present invention, the log analysis unit may obtain the reliability of the judgment regarding the improvement point together with the improvement point, and feed back only those with a reliability equal to or higher than a predetermined value to the requirement specification generation unit.

[0012] In the present invention, the product management system may further include a questionnaire processing unit that processes a questionnaire for the users of the product. Then, the log analysis unit issues a request to the questionnaire processing unit to conduct a questionnaire on improvement items with a reliability lower than a predetermined value among the derived improvement points. The questionnaire processing unit generates a questionnaire regarding the improvement items related to the request in response to the request from the log analysis unit, transmits it to the user, receives the response from the user, derives the direction of improvement for the improvement items based on the received response to the questionnaire, and feeds back to the requirement specification generation unit. Then, the requirement specification generation unit may update the requirement specification by reflecting the feedback from the questionnaire processing unit.

[0013] In the present invention, it is preferable that the log data analyzed by the log analysis unit ensures the three viewpoints of the diversity of the log data, the representativeness of the log data, and the fairness of the log data.

[0014] In the present invention, the log analysis unit may analyze the log regularly.

[0015] In the present invention, it is preferable to further include a CLD generation unit that generates a causal loop diagram (CLD) indicating the logic for the product to grow (achieve continuous growth). Further, when periodically analyzing the log, the log analysis unit may evaluate the KPI (Key Performance Indicator) of the product and determine that the PMF (Product Market Fit) has been achieved when the KPI improves rapidly. When the log analysis unit determines that the PMF has been achieved, the CLD generation unit may generate a causal loop diagram.

[0016] The product management system according to the present invention may further include a DAG generation unit that generates a directed acyclic graph (DAG) describing the causal relationship between the feature amount in the strategic information acquired by the strategic information acquisition unit and the items in the requirement specification. The uppermost stream in the directed acyclic graph generated by the DAG generation unit may be a feature amount representing customer insight.

[0017] In the present invention, the requirement specification generation unit may use the directed acyclic graph generated by the DAG generation unit to identify the requirement specifications corresponding to the feature amounts of important elements in the strategic information acquired by the strategic information acquisition unit and reflect them in the requirement specification.

[0018] In the present invention, the requirement specification generation unit may include the directed acyclic graph generated by the DAG generation unit in the requirement specification.

[0019] A program according to another example of the present invention causes a computer to function as any one of the above product management systems.

Brief Description of the Drawings

[0020]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Mode for Carrying Out the Invention

[0021] Hereinafter, the product management system 1 according to the embodiment of the present invention will be described with reference to the drawings.

[0022] 〔Configuration of the System〕 FIG. 1 is a schematic diagram showing the product management system 1 according to the embodiment of the present invention together with a business strategy evaluation device 2, a product disclosure server 3, and a user terminal 6 connected to the product management system 1 via a network NW. The product management system 1 supports designing, implementing, and operating a product based on information such as the market, business environment, etc., and strategic information such as significant parameters and feature quantities in the positioning strategy.

[0023] The business strategy evaluation device 2 analyzes and formulates business strategies based on parameters related to the external environment, various analysis items in various frameworks used for analyzing business strategies such as 3C (Customer (market / customer), Competitor (competition), Company (itself)), 4P (Product (product / service), Price (price), Place (location / distribution / channel), Promotion (sales promotion / advertising)), strategic models applied to the business (for example, types of initial strategies, mid-term strategies, scale strategies), and various information such as news, and provides strategic information such as information on the market, business environment, etc., and significant parameters and feature quantities in the positioning strategy to the product management system 1. The product management system 1 may be, for example, a business strategy formulation support device as described in Patent Document 1.

[0024] The product publishing server 3 is a server computer for publicly providing and operating the products designed and implemented by the product management system 1 to users. The product publishing server 3 is composed of a general computer system, and various functions such as a database server and a web server are implemented according to the functions of the product.

[0025] 〔Hardware Configuration of Product Management System〕 Figure 2 is a schematic diagram showing the hardware configuration of the product management system 1. The product management system 1 is realized, for example, as a computer. That is, the product management system 1 includes a processor 101, a RAM 102, an HDD 103, a graphic processing unit 104, an input interface 105, and a network interface 106. Note that Figure 2 shows an example in which the product management system 1 is realized as a so-called stand-alone type by one computer, but the product management system 1 can also be realized in a mode in which a plurality of computers (for example, one server computer connected by LAN and a plurality of client computers) connected to each other via a network line such as LAN cooperate.

[0026] The product management system 1 is controlled by the processor 101 throughout the device. The processor 101 may be a multi-processor. The processor 101 is, for example, a CPU (Central Processing Unit), MPU (Micro Processing Unit), DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), GPU (Graphics Processing Unit), or PLD (Programmable Logic Device). Further, the processor 101 may be a combination of two or more elements among the CPU, MPU, DSP, ASIC, and PLD.

[0027] RAM 102 (Random Access Memory) is used as the main memory device of the product management system 1. At least a part of the OS (Operating System) program and application programs to be executed by the processor 101 are temporarily stored in the RAM 102. Also, various data necessary for the processing by the processor 101 are stored in the RAM 102.

[0028] HDD 103 (Hard Disk Drive) is used as the auxiliary storage device of the product management system 1. The OS program, application programs, and various data are stored in the HDD 103. Note that as the auxiliary storage device, other types of non-volatile storage devices such as SSD (Solid State Drive) can also be used.

[0029] A display device 104a is connected to the graphic processing unit 104. The graphic processing unit 104 displays an image on the screen of the display device 104a according to an instruction from the processor 101. As the display device 104a, a liquid crystal display, an organic EL (Electro Luminescence) display, or the like is used.

[0030] An input device 105a is connected to the input interface 105. The input interface 105 transmits the signal output from the input device 105a to the processor 101. Examples of the input device 105a include a keyboard and a pointing device. Examples of the pointing device include a mouse, a touch panel, a tablet, a touch pad, and a track ball.

[0031] The network interface 106 enables communication with external devices via the network NW. The communication via the network NW by the network interface 106 may be wired communication or wireless communication. As shown in FIG. 1, devices such as a business strategy evaluation device 2 and a product disclosure server 3 are connected to the network NW, and the product management system 1 can communicate with them via the network NW. The product management system 1 may receive operations and information inputs from a user terminal instead of the inputs using the input interface 105.

[0032] With the above hardware configuration, the product management system 1 can be realized.

[0033] [Functional Blocks of the Product Management System 1] FIG. 3 shows a functional block diagram of the product management system 1. The product management system 1 includes a strategy information acquisition unit 11, a requirement specification generation unit 12, a code generation unit 13, a log analysis unit 14, a questionnaire processing unit 15, a DAG generation unit 16, and a CLD generation unit 17. Each of these functional blocks is realized by the processor 101 in the hardware configuration of the product management system 1 described above executing a program stored in the RAM 102 or the HDD 103.

[0034] The strategic information acquisition unit 11 acquires strategic information that defines the strategy for the product to achieve business success. In this embodiment, the strategic information acquisition unit 11 acquires, as strategic information from the business strategy evaluation device 2, information such as the market and business environment, and parameters and feature quantities significant in the positioning strategy. Note that the strategic information acquisition unit 11 may acquire strategic information from sources other than the business strategy evaluation device 2. For example, the strategic information acquisition unit 11 may acquire strategic information formulated and input by a business strategy consultant.

[0035] The DAG generation unit 16 generates a directed acyclic graph (Directed Acyclic Graph; DAG. Hereinafter referred to as DAG) that describes the causal relationship between the feature quantities included in the strategic information acquired by the strategic information acquisition unit 11, the feature quantities fed back from the log analysis unit 14 and the questionnaire processing unit 15, and the items in the requirement specifications. FIG. 4 shows an example of a DAG. The DAG generation unit 16 may re-learn the feature quantities in the strategic information acquired by the strategic information acquisition unit 11 and generate a DAG based on the strategic information. At that time, the DAG generation unit 16 may be configured to enable the user to set the target variable (that is, the item of interest. For example, "sales", "customer satisfaction", etc.), and output a DAG depicting the causal relationship indicating that the feature quantity affects the set target variable. Further, in the DAG generated by the DAG generation unit 16, it is preferable that the Root Cause (root cause; the most upstream in the DAG) is a feature quantity representing customer insight. Thus, the DAG generated by the DAG generation unit 16 can visualize the causal relationship between the feature quantity, which is difficult for humans to intuitively understand, and the requirement specifications, making it easier to understand, and can support the unification of opinions and consensus formation among the product development personnel. The DAG generation unit 16 may output the generated DAG as an image. Note that the product management system 1 may be configured to acquire a DAG from the outside (for example, together with the strategic information by the strategic information acquisition unit 11) without including the DAG generation unit 16. The DAG generation unit 16 may update the DAG based on the feedback from the log analysis unit 14 or the questionnaire processing unit 15.

[0036] Based on the strategic information acquired by the requirement specification generation unit 12, the requirement specification generation unit 12 generates the requirement specification of the product. For example, the requirement specification generation unit 12 may identify the requirement specifications corresponding to the feature quantities of important elements in the strategic information acquired by the strategic information acquisition unit 11 using the DAG generated by the DAG generation unit 16 and reflect them in the requirement specification. The requirement specification may include the DAG itself. The generated requirement specification is stored in the HDD 103. The requirement specification is composed of a market requirement specification (Market Requirements Document, hereinafter abbreviated as MRD) and a product requirement specification (Product Requirements Document, hereinafter abbreviated as PRD). The MRD and PRD are documented for product developers to share their premises and understandings regarding the product and facilitate communication. The requirement specification generation unit 12 may generate the MRD and PRD in a predetermined format.

[0037] Figure 5 shows an example of an MRD, which is a type of requirement specification. The RD is a requirement specification focused on the issues that the product aims to solve (what is the value proposition), and it describes information such as the target market, needs, competitive information, and information regarding revenue and cost. The requirement specification generated by the requirement specification generation unit 12 may include, in addition to the above-mentioned MRD and PRD, a business requirement specification (Business Requirements Document, hereinafter abbreviated as BRD). The BRD is a document that summarizes project goals, expectations during the project life cycle, and what is required to achieve the project, etc. The MRD shown in Figure 5 includes the content described in the BRD. That is, it can also be said that the requirement specification shown in Figure 5 combines the BRD and the MRD.

[0038] FIG. 6 shows an example of a PRD, which is a type of requirement specification document. The PRD centrally manages the latest information for constructing solutions to the issues described in the MRD. For example, as shown in FIG. 6, the PRD describes the development background of the product to be developed, the functions and features of the product, functions, KPIs (Key Performance Indicators; important performance evaluation indicators) used to measure the product's goal achievement level, mock-ups of the product, and so on.

[0039] Based on the requirement definition document (mainly the PRD) generated by the requirement specification document generation unit 12, the code generation unit 13 automatically generates program codes for the front-end of the product (i.e., the screen design and user interface that the user can see) and the back-end (i.e., the data structure and database that the user cannot directly see). The generated program codes are stored in the HDD 103. The code generation unit 13 may be realized, for example, by so-called code generation that uses a large language model to generate program codes. At this time, the code generation unit 13 may generate codes using a learned model that has been pre-trained using a large number of other products that have been successfully implemented in reality as teacher data. Also, the learned model used by the code generation unit 13 should be re-trained by periodically adding new successful products to the teacher data so that it can output the codes of products that keep up with the trends at the generation timing.

[0040] The code generation unit 13 deploys the generated code to the product publication server 3 to start the operation of the product. The product realized by the code generated by the code generation unit 13 is configured to record the history (log) of the product's use by the user.

[0041] The log analysis unit 14 analyzes the logs of the products operated on the product publication server 3 to obtain insights (e.g., improved user benefits) for improving KPIs. That is, by analyzing the logs, the log analysis unit 14 derives improvement points of the product to achieve higher KPIs. For example, the log analysis unit 14 may output the items to be changed in the product, the direction of change, and the reliability of the judgment regarding these improvement points. As a specific example, the log analysis unit 14 may derive, as an improvement point of the product, that on a certain screen of the product, the display size of an image (the item to be changed) should be made larger (the direction of change), and also obtain the reliability (or it can also be rephrased as "accuracy" or "confidence") that an improvement effect can be obtained when changed accordingly, such as "90%".

[0042] The log analysis unit 14 feeds back the derived improvement points to the requirement specification generation unit 12 and the DAG generation unit 16. At this time, the log analysis unit 14 may feed back only the improvement points with a reliability equal to or higher than a predetermined value to the requirement specification generation unit 12 and the DAG generation unit 16. In addition to the improvement points, the log analysis unit 14 may also feed back various information (e.g., customer personas) obtained by analyzing the logs to the requirement specification generation unit 12 and the DAG generation unit 16. Further, for the improvement points with a reliability less than the predetermined value, the log analysis unit 14 may issue a request to the questionnaire processing unit 15 to conduct a questionnaire.

[0043] In response to a questionnaire request for improvement items with low reliability from the log analysis unit 14, the questionnaire processing unit 15 generates and sends a questionnaire regarding the improvement items to the users of the product, and receives answers from the users. Then, based on the answers to the questionnaire, the questionnaire processing unit 15 derives the direction of improvement and provides feedback to the requirement specification generation unit 12 and the DAG generation unit 16. The questionnaire sent by the questionnaire processing unit 15 to the users may, for example, ask about the direction and degree of change regarding the improvement items. As a specific example, the questionnaire processing unit 15 may ask the user which of the following is preferable for the display size of an image on a certain screen of the product: make it larger than the current size, make it smaller, or maintain the current size. In this way, it becomes possible to provide highly accurate feedback based on the opinions of the users for improvement items with low reliability (i.e., improvement items that are considered to have an impact on the KPI but for which it is not clear how to make changes). Based on the feedback from the log analysis unit 14 and the questionnaire processing unit 15, the requirement specification generation unit 12 updates the MRD and PRD. Similarly, based on the feedback from the log analysis unit 14 and the questionnaire processing unit 15, the DAG generation unit 16 updates the DAG.

[0044] The log data obtained while operating the product on the product publishing server 3 and analyzed by the log analysis unit 14 may include various items, but it is preferable to ensure the three aspects of the diversity of log data, the representativeness of log data, and the fairness of log data. The diversity of log data means that "the data reflects people and events with various attributes and characteristics". The representativeness of log data means that "the data represents the target population". The fairness of log data means that "the data is unbiased by attributes such as gender, race, ethnicity, religion, and disability".

[0045] The log analysis unit 14 performs user story mapping based on, for example, journey data that records the actions of users in a product, and generates a customer journey map. The journey data may be multimodal data that includes various types (formats) of data such as images, text, tables, videos, and cursor operations, and may include a mixture of different types of data and formats. The log analysis unit 14 detects points in the product that need to be improved, such as unreasonableness, wastefulness, unevenness, leakage, and mistakes, from this journey data, extracts measures and insights for changing to a more improved journey, and feeds them back as improvement points to the requirement specification generation unit 12 and the DAG generation unit 16. Specifically, the improvement points fed back to the requirement specification generation unit 12 and the DAG generation unit 16 may be the residence time, number of actions, engagement, and threshold values at which action variations occur at regular intervals in the product, as well as qualitative matters and measures and insights for changing to a journey in which the user's stickiness to the product is relatively increased compared to competing services.

[0046] In the product management system 1 according to the present invention, by continuously improving the above-described logs in a natural state, it feeds back to more accurate strategy formulation, improves the initial TO BE (that is, the MRD and PRD generated by the requirement specification generation unit 12 based on the strategic information initially acquired by the strategic information acquisition unit 11), and provides a mechanism for continuously ensuring high data quality. In this continuous improvement, in some cases, pivots (business transformation, route change), function addition, etc. are performed to change and improve the causal chain (that is, DAG) for the product to achieve higher KPIs. In addition, the requirement specification generation unit 12 can optimize the policy gradient by performing reinforcement learning while repeating such improvements. As a result, the UX (User Experience) of the product can be continuously improved to be better. Also, each time the requirement specifications in the product are changed (improved), the DAG generation unit 16 updates the DAG, so that the causal relationship between the improvement of the UX accompanying the change can be presented in a visually understandable form.

[0047] The product management system 1 according to the present invention repeats the above-described improvements to achieve PMF (Product Market Fit; the state where a product or service satisfies customers and fits a specific market). After PMF is achieved, the CLD generation unit 17 generates a Causal Loop Diagram (CLD) for achieving the growth target (continuing product discovery). FIG. 7 shows an example of the CLD. While the DAG shows the upstream-to-downstream (so-called one-way) causal relationship that the feature quantities included in the strategic information and feedback have on the items in the requirements specification, the CLD is a loop connected by a chain of causation. The CLD generated by the CLD generation unit 17 can visualize and make it easier to understand the logic for growth (realizing continuous growth while operating the product) in the state where PMF is achieved, and can assist in unifying the opinions and forming agreements among product developers. The CLD generation unit 17 may generate and output the generated CLD as an image. The CLD generated by the CLD generation unit 17 may be included in the requirements specification document.

[0048] The timing for causing the CLD generation unit 17 to generate the CLD (that is, the timing when PMF is considered to be achieved) may be determined by the user of the product management system 1, but it is preferably automatically determined by the product management system 1. For example, when the log analysis unit 14 periodically analyzes the log, it may evaluate the product's KPI and determine that PMF (Product Market Fit) has been achieved when the KPI improves rapidly. The log analysis unit 14 may detect that the KPI has improved rapidly based on the absolute value of the KPI, the amount of improvement from the previous analysis, the change rate, etc. Then, when the log analysis unit 14 determines that PMF has been achieved, the CLD generation unit 17 may generate the CLD.

[0049] Subsequently, the operation of the product management system 1 will be described. FIG. 8 is a flowchart showing the product development and operation process by the product management system 1.

[0050] As the first step of the operation development and operation process, the strategic information acquisition unit 11 acquires, as strategic information, information such as the market and business environment, and parameters and feature quantities significant in the positioning strategy, etc. by the business strategy evaluation device 2 (step S01).

[0051] Subsequently, based on the strategic information acquired by the strategic information acquisition unit 11 (and the feedback from the log analysis unit 14), the DAG generation unit 16 generates a DAG (step S02), and the requirement specification generation unit 12 generates an MRD and a PRD (step S03). Further, the code generation unit 13 generates the code of the product based on the MRD and the PRD (step S04), arranges (deploys) the generated code in the product publication server 3 (step S05), and makes the product available for use by the user.

[0052] The log analysis unit 14 periodically (for example, every week) analyzes the log of the product arranged in the product publication server 3, derives improvement points of the product to achieve higher KPIs, and feeds back to the requirement specification generation unit 12 together with other information such as customer personas as necessary (step S06). For improvement points with a reliability less than a predetermined value, the questionnaire processing unit 15 sends a questionnaire to the user, derives the direction of improvement based on the answers to the questionnaire, and feeds back to the requirement specification generation unit 12 (step S07). Further, the log analysis unit 14 determines whether the product has achieved PMF based on, for example, the evaluation of KPIs (step S08). If it is determined that PMF has not been achieved (step S08; No), the process returns to step S02. On the other hand, if it is determined that PMF has been achieved (step S08; Yes), the CLD generation unit 17 generates a CLD representing the business logic for the product to grow (step S09). And then the process returns to step S02.

[0053] After the product management system 1 generates the MRD and PRD based on the initial strategic information as described above, it can automatically repeat the so-called Scrum sprints that perform product development and updates in a short period by periodically repeating the processes from step S02 to step S07. While recalculating the winning rate of the business realized by the product in each sprint, it is also possible to conduct Kaizen (improvement) sprints. Furthermore, when the product achieves PMF, it can generate a CLD representing the business logic for the product to grow and visualize the business logic that leads the product to success (achievement of growth).

[0054] Although the above has described this embodiment, the present invention is not limited to these examples. Also, for the foregoing embodiments, those in which those skilled in the art appropriately add, delete, or change the design of components, or those in which the features of each embodiment are appropriately combined, are included in the scope of the present invention as long as they have the gist of the present invention.

Explanation of Reference Numerals

[0055] 1 Product management system 11 Strategic information acquisition unit 12 Requirement specification generation unit 13 Code generation unit 14 Log analysis unit 15 Questionnaire processing unit 16 DAG generation unit 17 CLD generation unit 2 Business strategy evaluation device 3 Product publication server

Claims

1. A strategic information acquisition unit that acquires strategic information that defines the strategy for the product to achieve business success, A requirements specification generation unit generates a requirements specification for the product based on the strategic information acquired by the strategic information acquisition unit, A code generation unit generates program code for the product based on the requirements specification generated by the requirements specification generation unit, A log analysis unit analyzes the logs generated when the program code generated by the code generation unit is deployed to a server accessible to the user and the product is operated, identifies areas for improvement in the product to achieve higher evaluation metrics, and feeds these improvements back to the requirements specification generation unit. Equipped with, The product management system is characterized in that the requirements specification generation unit updates the requirements specification by reflecting feedback from the log analysis unit.

2. The product management system according to claim 1, characterized in that the log analysis unit obtains the reliability of the judgment regarding the improvement points, and feeds back only those with a reliability of a predetermined value or higher to the requirements specification generation unit.

3. The system further includes a survey processing unit for processing surveys for users of the aforementioned product. The log analysis unit issues a request to the survey processing unit to conduct a survey on improvement items whose reliability is below a predetermined value among the identified improvement points. The aforementioned survey processing unit, in response to a request from the log analysis unit, generates a survey regarding the improvement items related to the request and sends it to the user, receives responses from the user, derives directions for improvement regarding the improvement items based on the received survey responses, and feeds this back to the requirements specification generation unit. The product management system according to claim 2, characterized in that the requirements specification generation unit updates the requirements specification by reflecting feedback from the questionnaire processing unit.

4. The product management system according to claim 1, characterized in that the log data analyzed by the log analysis unit ensures three aspects: diversity of log data, representativeness of log data, and fairness of log data.

5. The product management system according to claim 1, characterized in that the log analysis unit generates a customer journey diagram by performing user story mapping based on multimodal journey data recording user behavior, detects areas for improvement in the product from the journey data, extracts strategies and insights for changing the journey to one that is more improved, and feeds these improvements back to the requirements specification generation unit.

6. The product management system according to claim 1, characterized in that the log analysis unit periodically analyzes logs.

7. The product management system according to claim 6, further comprising a CLD generation unit that generates a causal loop diagram showing the logic for achieving continuous growth of the product.

8. The log analysis unit periodically analyzes the logs and evaluates the product's KPIs (Key Performance Indicators). If the KPIs show a rapid improvement, it determines that Product Market Fit (PMF) has been achieved. The product management system according to claim 7, characterized in that the CLD generation unit generates the causal loop diagram when the log analysis unit determines that PMF has been achieved.

9. The product management system according to claim 1, further comprising a DAG generation unit that generates a DAG generation unit that generates a noncyclic directed graph describing the causal relationship between the feature quantities in the strategic information acquired by the strategic information acquisition unit and the items in the requirements specification.

10. The product management system according to claim 9, characterized in that the uppermost element in the acyclic directed graph generated by the DAG generation unit is a feature quantity representing customer insights.

11. The product management system according to claim 9, characterized in that the requirements specification generation unit uses the acyclic directed graph generated by the DAG generation unit to identify requirements specifications corresponding to the feature quantities of important elements in the strategic information acquired by the strategic information acquisition unit, and reflects them in the requirements specification document.

12. The product management system according to claim 9, characterized in that the requirements specification generation unit includes the acyclic directed graph generated by the DAG generation unit in the requirements specification.

13. A program that causes a computer to function as a product management system according to any one of claims 1 to 12.

Images