Product management system and program

Abstract

Provided are a product management system and a program capable of performing product development and management based on a business strategy with predetermined quality.　This product management system comprises: a strategy information acquisition unit that acquires strategy information that defines a strategy for a product to achieve business success; a required specification generation unit that generates a required specification for the product on the basis of the strategy information acquired by the strategy information acquisition unit; and a code generation unit that generates program code of the product on the basis of the required specification generated by the required specification generation unit.

Description

Product Management Systems and Programs

[0001] The present invention relates to a product management system and program that can carry out the development and operation of products based on business strategies with a predetermined quality.

[0002] Currently, many companies formulate their business strategies using strategic planning methods proposed by universities, business schools, consulting companies, etc. For companies, the creation of an accurate business strategy determines the fate of the company, and the question of how to formulate an accurate business strategy based on an analysis of the current situation or a forecast of the future is a universally important issue.

[0003] In many cases, strategic planning methods require advanced knowledge and skills, and therefore business strategy planning is provided as a service by consultants at consultation companies for a fee, making it difficult for in-house personnel to easily plan business strategies. In light of this situation, the inventors have proposed a business strategy planning support device that enables strategic planners to quickly plan high-quality strategies and enables strategic plan adoption assessors to improve the accuracy of their decisions on whether to implement strategic plans (see Patent Document 1).

[0004] The business strategy planning support device described in Patent Document 1 makes it possible to search for and output parameters and features that are significant in a positioning strategy (highly important for differentiating from competitors) using a trained model obtained by machine learning using a data set that includes input parameters, which are explanatory variables related to the success or failure of multiple business strategies, and a target variable, which indicates the likelihood of success of the business strategy, as training data.

[0005] By reflecting highly important parameters and features identified by the technology described in Patent Document 1, highly competitive products (especially products provided to users via computer systems, such as web services) can be realized.

[0006] Patent No. 7073029

[0007] To realize a product, a requirements specification is created based on the most important parameters and features, and the product is then developed based on the requirements specification. The requirements specification is typically compiled by a person called a product manager (PM). However, individual product managers have different ways of compiling the requirements specification (items to be included, granularity, etc.), and the frequency with which the requirements specification is revised and updated varies. Furthermore, product managers are not necessarily the same people who plan the business strategy. These circumstances often result in the product being developed being inconsistent with the business strategy that was formulated to be highly competitive, or in the product not being properly revised or updated based on the operational results.

[0008] The present invention has been made to solve the above problems, and aims to provide a product management system and program that can carry out product development and operation based on business strategy with a specified quality.

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

[0010] In the present invention, the product management system may further include a log analysis unit that analyzes logs generated when the program code generated by the code generation unit is placed on a server available to the user and the product is operated, derives improvements to the product to achieve higher evaluation indexes, and feeds back the improvements to the requirements specification generation unit.The requirements specification generation unit may then update the requirements specification 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 points along with the improvement points, and feed back only those with a reliability equal to or greater than a predetermined value to the requirements specification generation unit.

[0012] In the present invention, the product management system may further include a questionnaire processing unit that processes a questionnaire for users of the product. The log analysis unit may issue a request to the questionnaire processing unit to conduct a questionnaire for improvement items whose reliability is less than a predetermined value among the derived improvement points. In response to the request from the log analysis unit, the questionnaire processing unit may generate a questionnaire regarding the improvement items related to the request, send it to the users, receive responses from the users, derive an improvement direction for the improvement items based on the received questionnaire responses, and feed the result back to the requirements specification generation unit. The requirements specification generation unit may then update the requirements specification to reflect 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 three aspects: diversity of log data, representativeness of log data, and fairness of log data.

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

[0015] The present invention may further include a causal loop diagram (CLD) generation unit that generates a CLD that shows the logic for product growth (achieving continuous growth). Furthermore, the log analysis unit may evaluate the product's KPIs (Key Performance Indicators) when periodically analyzing the logs, and determine that PMF (Product Market Fit) has been achieved if the KPIs improve dramatically. The CLD generation unit may generate the causal loop diagram when the log analysis unit determines that PMF has been achieved.

[0016] The product management system according to the present invention may further include a DAG generation unit that generates a directed acyclic graph (DAG) that describes the causal relationships between features in the strategic information acquired by the strategic information acquisition unit and items in the requirements specification. The most upstream element in the directed acyclic graph generated by the DAG generation unit may be a feature representing customer insights.

[0017] In the present invention, the requirements specification generation unit uses the acyclic directed graph generated by the DAG generation unit to identify requirements specifications corresponding to the features of important elements in the strategic information acquired by the strategic information acquisition unit, and reflects these in the requirements specification.

[0018] In the present invention, the requirements specification generator may include the acyclic directed graph generated by the DAG generator in the requirements specification.

[0019] A program according to another example of the present invention is characterized by causing a computer to function as any one of the above-described product management systems.

[0020] 1 is a schematic diagram showing a product management system 1 together with devices connected to the product management system 1. FIG. 2 is a schematic diagram showing the hardware configuration of the product management system 1. FIG. 3 is a functional block diagram of the product management system 1. FIG. 4 is a diagram showing an example of a DAG. FIG. 5 is a diagram showing an example of an MRD, which is a type of requirements specification. FIG. 6 is a diagram showing an example of a PRD, which is a type of requirements specification. FIG. 7 is a diagram showing an example of a CLD. FIG. 8 is a flowchart showing a product development and operation process by the product management system 1.

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

[0022] 1 is a schematic diagram showing a product management system 1 according to an embodiment of the present invention, together with a business strategy evaluation device 2, a product publication server 3, and a user terminal 6, which are connected to the product management system 1 via a network NW. The product management system 1 supports the design, implementation, and operation of a product based on information on the market, business environment, etc., and strategic information such as parameters and features that are significant in a positioning strategy.

[0023] The business strategy evaluation device 2 analyzes and formulates business strategies based on various information such as parameters related to the external environment, analysis items in various frameworks used to analyze business strategies such as 3C (Customer (market / customers), Competitor (competitor), Company (one's own company)), 4P (Product (product / service), Price (price), Place (location / distribution / sales channel), Promotion (sales promotion / advertising)), strategic models applied to the business (e.g., types of initial strategy, mid-stage strategy, and scale strategy), and news, and provides the product management system 1 with information on the market, business environment, etc., and strategic information such as parameters and features significant in positioning strategies. The product management system 1 may be, for example, a business strategy formulation support device such as that described in Patent Document 1.

[0024] The product publication server 3 is a server computer for publishing to users and operating the products designed and implemented by the product management system 1. The product publication server 3 is configured as a general computer system, and is equipped with various functions such as a database server and a web server according to the product functions.

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

[0026] The product management system 1 is entirely controlled by a processor 101. The processor 101 may be a multiprocessor. The processor 101 is, for example, a central processing unit (CPU), a micro processing unit (MPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a graphics processing unit (GPU), or a programmable logic device (PLD). The processor 101 may also be a combination of two or more elements selected from the group consisting of a CPU, an MPU, a DSP, an ASIC, and a PLD.

[0027] The RAM 102 (Random Access Memory) is used as the main storage device of the product management system 1. The RAM 102 temporarily stores at least a portion of the OS (Operating System) program and application programs to be executed by the processor 101. The RAM 102 also stores various data necessary for processing by the processor 101.

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

[0029] A display device 104a is connected to the graphics processing unit 104. The graphics processing unit 104 displays an image on the screen of the display device 104a in accordance with an instruction from the processor 101. The display device 104a may be a liquid crystal display, an organic EL (Electro Luminescence) display, or the like.

[0030] An input device 105a is connected to the input interface 105. The input interface 105 transmits a signal output from the input device 105a to the processor 101. The input device 105a may be a keyboard or a pointing device. The pointing device may be a mouse, a touch panel, a tablet, a touch pad, a trackball, or the like.

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

[0032] The product management system 1 can be realized with the above hardware configuration.

[0033] [Functional Blocks of Product Management System 1] Figure 3 shows a functional block diagram of the product management system 1. The product management system 1 includes a strategic information acquisition unit 11, a requirements 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 a processor 101 in the hardware configuration of the product management system 1 described above executing a program stored in a RAM 102 or HDD 103.

[0034] The strategic information acquisition unit 11 acquires strategic information that defines a strategy for achieving business success for a product. In this embodiment, the strategic information acquisition unit 11 acquires, as strategic information, information on the market, business environment, etc., and parameters and feature quantities that are significant in a positioning strategy, from the business strategy evaluation device 2. Note that the strategic information acquisition unit 11 may acquire strategic information from a source other than the business strategy evaluation device 2. For example, the strategic information acquisition unit 11 may acquire strategic information that has been planned and input by a business strategy consultant.

[0035] The DAG generation unit 16 generates a directed acyclic graph (DAG) describing the causal relationships between features included in the strategic information acquired by the strategic information acquisition unit 11 and features fed back from the log analysis unit 14 and the questionnaire processing unit 15 and items in the requirement specifications. FIG. 4 shows an example of a DAG. The DAG generation unit 16 may re-learn the features in the strategic information acquired by the strategic information acquisition unit 11 and generate a DAG based on the strategic information. In this case, the DAG generation unit 16 may be configured to allow the user to set a target variable (i.e., an item of interest, such as "sales" or "customer satisfaction"), and may output a DAG depicting the causal relationships that indicate how the feature affects the set target variable. In addition, the DAG generation unit 16 preferably sets the root cause (the most upstream in the DAG) to a feature representing customer insight in the generated DAG. The DAG generated by the DAG generation unit 16 in this way can visualize and make easier to understand the causal relationships between feature quantities and requirement specifications, which are difficult for humans to intuitively understand, thereby supporting consensus building and agreement among those involved in product development. 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 the DAG externally (for example, by the strategic information acquisition unit 11 together with strategic information) without including the DAG generation unit 16. The DAG generation unit 16 may update the DAG based on feedback from the log analysis unit 14 and the questionnaire processing unit 15.

[0036] The requirements specification generation unit 12 generates a product requirements specification based on the strategic information acquired by the strategic information acquisition unit 11. For example, the requirements specification generation unit 12 may use the DAG generated by the DAG generation unit 16 to identify requirements specifications corresponding to the features of important elements in the strategic information acquired by the strategic information acquisition unit 11 and reflect them in the requirements specification. The requirements specification may include the DAG itself. The generated requirements specification is stored in the HDD 103. The requirements specification consists of a market requirements document (hereinafter abbreviated as MRD) and a product requirements document (hereinafter abbreviated as PRD). The MRD and PRD are documented so that those involved in product development can share assumptions and understanding about the product and communicate with each other. The requirements specification generation unit 12 may generate the MRD and PRD in a predetermined format.

[0037] Figure 5 shows an example of an MRD, a type of requirements specification. The RD focuses on the problem the product is trying to solve (what is the value proposition) and includes information on the target market, needs, competitive information, revenue and cost, etc. The requirements specification generated by the requirements specification generator 12 may include the MRD and PRD described above as well as a business requirements document (hereinafter abbreviated as BRD). A BRD is a document that summarizes project goals, expectations during the project lifecycle, and what is required to achieve the project. The MRD shown in Figure 5 includes the content described in the BRD. In other words, the requirements specification shown in Figure 5 can be considered a combination of a BRD and an MRD.

[0038] Figure 6 shows an example of a PRD, a type of requirements specification. The PRD centrally manages the latest information needed to build solutions to the issues described in the MRD. For example, as shown in Figure 6, the PRD describes the development background of the product to be developed, the product's functions and features, KPIs (Key Performance Indicators) used to measure the product's goal achievement level, and a product mockup.

[0039] The code generation unit 13 automatically generates program code for the product's front end (i.e., screen design, user interface, etc. that are visible to the user) and back end (i.e., data structure, database, etc. that are not directly visible to the user) based on the requirements definition document (mainly the PRD) generated by the requirements specification generation unit 12. The generated program code is stored in the HDD 103. The code generation unit 13 may be realized, for example, by generating program code using a large-scale language model, i.e., so-called code generation. In this case, the code generation unit 13 may generate code using a trained model that has been pre-trained using many other successful products as training data. In addition, the trained model used by the code generation unit 13 may be periodically re-trained by adding new successful products to the training data so that code for a product that is in line with the trends at the time of generation can be output.

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

[0041] The log analysis unit 14 analyzes the logs of the product operated on the product publishing server 3 to obtain insights for improving KPIs (e.g., improving user benefits). That is, by analyzing the logs, the log analysis unit 14 derives improvements to the product in order to achieve higher KPIs. For example, the log analysis unit 14 may output items to be changed in the product, the direction of the changes, and the reliability of the judgment regarding these improvements. As a specific example, the log analysis unit 14 may derive, as an improvement to the product, that the display size of an image on a certain screen of the product (item to be changed) should be made larger (direction of change), and may also calculate the reliability (which can also be rephrased as "certainty" or "confidence") that an improvement effect will be achieved if the change is made in this way, such as "90%."

[0042] The log analysis unit 14 feeds back the derived improvements to the requirements specification generation unit 12 and the DAG generation unit 16. At this time, the log analysis unit 14 may feed back only improvements whose reliability is equal to or greater than a predetermined value to the requirements specification generation unit 12 and the DAG generation unit 16. The log analysis unit 14 may also feed back various information obtained by analyzing the log (e.g., customer persona) to the requirements specification generation unit 12 and the DAG generation unit 16 in addition to the improvements. Furthermore, the log analysis unit 14 may issue a request to the survey processing unit 15 to conduct a survey for improvements whose reliability is less than a predetermined value.

[0043] In response to a request from the log analysis unit 14 for a questionnaire about an improvement item with low reliability, the questionnaire processing unit 15 generates and sends a questionnaire about the improvement item to the user of the product and receives responses from the user. The questionnaire processing unit 15 then determines the direction of improvement based on the questionnaire responses and provides feedback to the requirements specification generation unit 12 and the DAG generation unit 16. The questionnaire sent to the user by the questionnaire processing unit 15 may, for example, ask about the direction and degree of change for the improvement item. As a specific example, the questionnaire processing unit 15 may ask the user whether they prefer to increase, decrease, or maintain the current display size of an image on a screen of the product. This enables accurate feedback based on user opinions for improvement items with low reliability (i.e., improvement items that are thought to have an impact on KPIs but for which it is unclear how to change them). Based on feedback from the log analysis unit 14 and the questionnaire processing unit 15, the requirements specification generation unit 12 updates the MRD and PRD. Similarly, the DAG generation unit 16 updates the DAG based on feedback from the log analysis unit 14 and the questionnaire processing unit 15 .

[0044] The log data acquired while the product is operating on the product publishing server 3 and analyzed by the log analysis unit 14 may include a variety of items, but it is preferable that the data ensures three aspects: diversity of the log data, representativeness of the log data, and fairness of the log data. Diversity of the log data means that the data reflects people and events with a variety of attributes and characteristics. Representativeness of the log data means that the data is representative of the target group. Fairness of the log data means that the data is not biased by attributes such as gender, race, ethnicity, religion, or disability.

[0045] The log analysis unit 14 generates a customer journey diagram by performing user story mapping based on journey data recording user behavior in the product. The journey data may be multimodal data, including a mixture of different data formats, regardless of the data type (format), such as images, text, tables, videos, and cursor operations. The log analysis unit 14 detects areas for improvement in the product, such as unreasonableness, waste, inconsistencies, omissions, and mistakes, from the journey data, extracts measures and insights for modifying the journey to further improve it, and provides these as feedback to the requirements specification generation unit 12 and the DAG generation unit 16. Specifically, the improvements provided to the requirements specification generation unit 12 and the DAG generation unit 16 may include, for example, the time spent in the product at regular intervals, the number of actions, engagement, thresholds and qualitative factors that result in behavioral change, and measures and insights for modifying the journey to increase user adherence to the product relative to competing services.

[0046] The product management system 1 according to the present invention provides a mechanism for continuously improving the above-described logs by providing feedback for more accurate strategy formulation and further improving the initial TOBE (i.e., the MRD and PRD generated by the requirements specification generator 12 based on the strategic information initially acquired by the strategic information acquisition unit 11). This continuous improvement involves, in some cases, pivoting (business transformation, change of direction) or adding features to modify and improve the causal chain (i.e., DAG) for the product to achieve higher KPIs. Furthermore, the requirements specification generator 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. Furthermore, by updating the DAG each time the requirements specifications of the product are repeatedly changed (improved), the DAG generator 16 can visualize and present the causal relationship of the UX improvement resulting from the change in the DAG in an easily understandable manner.

[0047] The product management system 1 according to the present invention achieves PMF (Product Market Fit; a state in which a product or service satisfies customers and is suited to a specific market) through repeated improvements as described above. After PMF is achieved, the CLD generator 17 generates a causal loop diagram (CLD) for achieving growth targets (continuing product discovery). Figure 7 shows an example of a CLD. While a DAG shows upstream-to-downstream (i.e., one-way) causal relationships between features contained in strategic information and feedback and items in the requirements specification, a CLD represents a loop connected by a causal chain. The CLD generated by the CLD generator 17 visualizes and makes easy to understand the logic for growth (achieving continuous growth while operating the product) with PMF achieved, thereby supporting consensus building and consensus building among those involved in product development. The CLD generator 17 may output the generated CLD as an image. The CLD generated by the CLD generating unit 17 may be included in the requirements specification.

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

[0049] Next, a description will be given of the operation of the product management system 1. Fig. 8 is a flowchart showing the product development and operation process performed by the product management system 1.

[0050] As the first step in the business development and operation process, the strategic information acquisition unit 11 acquires strategic information from the business strategy evaluation device 2, such as information on the market, business environment, and parameters and features that are significant in the positioning strategy (step S01).

[0051] Next, based on the strategic information acquired by the strategic information acquisition unit 11 (and feedback from the log analysis unit 14), the DAG generation unit 16 generates a DAG (step S02), and the requirements specification generation unit 12 generates an MRD and a PRD (step S03). Furthermore, the code generation unit 13 generates product code based on the MRD and PRD (step S04), and deploys the generated code on the product publication server 3 (step S05), making the product available to users.

[0052] The log analysis unit 14 periodically (e.g., weekly) analyzes the product logs stored on the product publishing server 3, identifies improvements to the product to achieve higher KPIs, and provides feedback to the requirements specification generation unit 12, along with other information such as customer personas, as needed (step S06). For improvements with reliability levels below a predetermined value, the survey processing unit 15 sends a survey to users, identifies directions for improvement based on the survey responses, and provides feedback to the requirements specification generation unit 12 (step S07). Furthermore, the log analysis unit 14 determines whether the product has achieved its PMF, for example, based on KPI evaluation (step S08). If it determines that the PMF has not been achieved (step S08; No), the process returns to step S02. On the other hand, if it determines that the PMF has been achieved (step S08; Yes), the CLD generation unit 17 generates a CLD representing the business logic for the product's growth (step S09). The process then returns to step S02.

[0053] After generating the MRD and PRD based on the initial strategic information as described above, the product management system 1 periodically repeats the processes of steps S02 to S07, enabling the automatic repetition of so-called Scrum sprints, which develop and update the product in a short period of time, and also enables the execution of Kaizen (improvement) sprints while recalculating the success rate of the business realized by the product in each sprint. Furthermore, if the product achieves PMF, a CLD representing the business logic for the product's growth can be generated, making it possible to visualize the business logic that leads to the product's success (achievement of growth).

[0054] Although the present embodiment has been described above, the present invention is not limited to these examples. Furthermore, any embodiment in which a person skilled in the art appropriately adds or deletes components or modifies the design of the above embodiment, or any embodiment in which the features of each embodiment are appropriately combined, is also included within the scope of the present invention as long as it includes the gist of the present invention.

[0055] REFERENCE SIGNS LIST 1 Product management system 11 Strategy 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 product management system comprising: a strategic information acquisition unit that acquires strategic information that defines a strategy for a product to achieve business success; a requirements specification generation unit that generates a requirements specification for the product based on the strategic information acquired by the strategic information acquisition unit; and a code generation unit that generates program code for the product based on the requirements specification generated by the requirements specification generation unit.

2. The product management system described in claim 1 further comprises a log analysis unit that analyzes logs when the program code generated by the code generation unit is placed on a server available to the user and the product is operated, derives improvements to the product to achieve higher evaluation indicators, and feeds back the improvements to the requirements specification generation unit, and the requirements specification generation unit updates the requirements specification to reflect the feedback from the log analysis unit.

3. The product management system described in claim 2, characterized in that the log analysis unit determines the improvement points along with the reliability of the judgment regarding the improvement points, and only those with a reliability above a predetermined value are fed back to the requirements specification generation unit.

4. The product management system described in claim 3 further comprises a questionnaire processing unit that processes questionnaires for users of the product, wherein the log analysis unit issues a request to the questionnaire processing unit to conduct a questionnaire for improvement items among the derived improvement points whose reliability is less than a predetermined value, wherein 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 and sends it to the user, receives responses from the user, derives an improvement direction for the improvement items based on the received questionnaire responses and feeds this back to the requirements specification generation unit, and wherein the requirements specification generation unit updates the requirements specification to reflect the feedback from the questionnaire processing unit.

5. The product management system described in claim 2, 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.

6. The product management system described in claim 2, characterized in that the log analysis unit performs user story mapping based on multimodal journey data that records user behavior to generate a customer journey diagram, detects areas that need improvement in the product from the journey data, extracts measures and insights to change the journey to one that will result in further improvement, and feeds these back to the requirements specification generation unit as areas for improvement.

7. The product management system according to claim 2, wherein the log analysis unit periodically analyzes the log.

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

9. The product management system described in claim 8, characterized in that the log analysis unit, when periodically analyzing logs, evaluates the product's KPIs (Key Performance Indicators) and determines that PMF (Product Market Fit) has been achieved if the KPIs improve dramatically, and the CLD generation unit generates the causal loop diagram when the log analysis unit determines that PMF has been achieved.

10. The product management system described in claim 1, further comprising a DAG generation unit that generates an acyclic directed graph that describes the causal relationship between the features in the strategic information acquired by the strategic information acquisition unit and the items in the requirements specification.

11. A product management system as described in claim 10, characterized in that the most upstream in the acyclic directed graph generated by the DAG generation unit is a feature representing customer insight.

12. The product management system described in claim 10, 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 features of important elements in the strategic information acquired by the strategic information acquisition unit, and reflects these in the requirements specification.

13. The product management system according to claim 10, wherein the requirements specification generation unit includes the acyclic directed graph generated by the DAG generation unit in the requirements specification.

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

Images