Method, System, Electronic Device and Medium for Generating OKR Management Solution

Abstract

The present invention discloses a method, system, electronic device and medium for generating an OKR management solution. The OKR management solution involves multiple configuration items, each configuration item includes multiple options, and different combinations of options are used to generate different OKR management solutions. The method for generating the OKR management solution includes: configuring member information; for each configuration item, respectively configuring the matching relationship between the feature combination and the option; for each member, obtaining multiple target features corresponding to the member; respectively determining multiple target options matching the target features according to the matching relationship; and combining the target options to generate an OKR management solution corresponding to the member. The present invention dynamically generates multiple OKR management solutions through one deployment, solves the problem of difficulty in developing different OKR management solutions, and greatly reduces the development cost of different OKR management solutions.

Description

Technical Field

[0001] The present invention relates to the technical field of target management, and particularly relates to a method, system, electronic device, and medium for generating an OKR management solution. Background Art

[0002] OKR (Objectives and Key Results) is a set of management tools and methods for clarifying and tracking objectives and their completion status. Currently, in the Internet industry and the public market, many related software products have emerged based on OKR. However, after the conventional OKR management software is deployed, it can only be executed according to the process set by the software itself, that is, the same set of management methods is deployed for multiple teams to use, and the way the teams use it is fixed. However, in actual use, it is found that each team has its own unique usage method and habit, which leads to the need to develop the OKR management solutions for each scenario when developing the corresponding OKR management software, and it is necessary to maintain them according to the user requirements for each scenario. As the number of using teams increases, this kind of unique scenario will become more and more frequent, and the development and maintenance costs will increase exponentially. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to overcome the defects of difficult development and high cost of different OKR management solutions in the prior art, and to provide a method, system, electronic device, and medium for generating an OKR management solution.

[0004] The present invention solves the above technical problem through the following technical solutions:

[0005] According to a first aspect of the present invention, there is provided a method for generating an OKR management solution. The OKR management solution involves multiple configuration items, and each configuration item includes multiple options. Among them, different combinations of options are used to generate different OKR management solutions. The method for generating the OKR management solution includes the following steps:

[0006] Configure member information, where the member information includes members and multiple characteristics corresponding to the members;

[0007] For each configuration item, respectively configure the matching relationship between the characteristic combination and the option, where the characteristic combination includes at least one of the characteristics;

[0008] For each member, respectively obtain multiple target characteristics corresponding to the member;

[0009] According to the matching relationship, respectively determine multiple target options that match the target characteristics;

[0010] Combine the target options to generate an OKR management solution corresponding to the member.

[0011] Preferably, the step of respectively configuring the matching relationship between the feature combination and the options includes:

[0012] For any configuration item, a matching relationship between a feature combination and the option is configured using a configuration process, wherein the configuration process includes:

[0013] Determine whether the option to be matched has received a matching instruction, wherein the option to be matched is used to represent any option under the configuration item. If a matching instruction is received, obtain a feature combination to be matched from the matching instruction, and then determine whether all options under the configuration item have the feature combination to be matched that has an existing matching relationship;

[0014] If the feature combination to be matched exists, the matching relationship is cancelled, and then it is determined whether the option to be matched has a second feature combination with a second matching relationship; if the feature combination to be matched does not exist, it is directly determined whether the option to be matched has a second feature combination with a second matching relationship;

[0015] If the second feature combination exists, the second matching relationship is cancelled, and then the feature combination to be matched is matched with the option to be matched; if the second feature combination does not exist, the feature combination to be matched is directly matched with the option to be matched.

[0016] Preferably, the step of respectively determining a plurality of target options matching the target feature according to the matching relationship comprises:

[0017] For any configuration item, a target option matching the target feature is determined using a determination process, the determination process comprising:

[0018] Acquire feature combination information under the configuration item, wherein the feature combination information includes a feature combination, an option corresponding to the feature combination, and a configuration time corresponding to the feature combination;

[0019] sorting the feature combinations based on the configuration time;

[0020] The first feature combination is set as the feature combination to be determined, and whether the feature combination to be determined satisfies the constraint condition is determined. If the constraint condition is satisfied, the option corresponding to the feature combination to be determined is used as the target option;

[0021] The constraint condition is used to characterize that all features under the feature combination have corresponding target features;

[0022] If the constraint condition is not satisfied, it is determined whether the to-be-determined feature combination is the last feature combination under the configuration item. If it is not the last feature combination, the next feature combination of the to-be-determined feature combination is set as the to-be-determined feature combination, and then it is determined whether the to-be-determined feature combination satisfies the constraint condition;

[0023] If it is the last feature combination, the preset default option is used as the target option.

[0024] Preferably, after the step of combining the target options to generate an OKR management plan corresponding to the member, the following is further included:

[0025] For any OKR management plan, obtain the evaluation parameters corresponding to the OKR management plan;

[0026] Determine whether the evaluation parameters satisfy the recommendation condition. If the recommendation condition is satisfied, the option corresponding to the OKR management plan is set as the recommended option;

[0027] Wherein, the recommendation condition is that the number of members corresponding to the OKR management plan is greater than the first threshold and the score is greater than the second threshold.

[0028] According to the second aspect of the present invention, there is provided a generation system for an OKR management plan. The OKR management plan involves multiple configuration items, and each configuration item includes multiple options. Among them, different combinations of options are used to generate different OKR management plans. The generation system for the OKR management plan includes a first configuration module, a second configuration module, a first acquisition module, a determination module, and a combination module:

[0029] The first configuration module is used to configure member information, and the member information includes members and multiple features corresponding to the members;

[0030] The second configuration module is used to configure the matching relationship between the feature combination and the option for each configuration item, wherein the feature combination includes at least one of the features;

[0031] The first acquisition module is used to respectively obtain multiple target features corresponding to each member;

[0032] The determination module is used to respectively determine multiple target options matching the target features according to the matching relationship;

[0033] The combination module is used to combine the target options to generate an OKR management plan corresponding to the member.

[0034] Preferably, the second configuration module is used to configure the matching relationship between the feature combination and the option for any configuration item by using a configuration process. The second configuration module includes a first judgment unit, a first acquisition unit, a second judgment unit, a release unit, and a matching unit:

[0035] The first judgment unit is used to judge whether a matching instruction is received for the option to be matched, where the option to be matched is used to represent any option under the configuration item. If a matching instruction is received, the first acquisition unit is called, and then the second judgment unit is called;

[0036] The first acquisition unit is used to acquire the feature combination to be matched from the matching instruction;

[0037] The second judgment unit is used to judge whether there is a feature combination with an existing matching relationship among all options under the configuration item. If there is the feature combination to be matched, the release unit is called, and then the matching unit is called; if there is no such feature combination to be matched, the matching unit is directly called;

[0038] The release unit is used to release the matching relationship;

[0039] The matching unit is used to match the feature combination to be matched with the option to be matched.

[0040] Preferably, the determination module is used to determine the target option matching the target feature for any configuration item by using a determination process. The determination module includes a second acquisition unit, a sorting unit, a first setting unit, a third judgment unit, a first determination unit, a fourth judgment unit, a second setting unit, and a second determination unit:

[0041] The second acquisition unit is used to acquire the feature combination information under the configuration item, where the feature combination information includes a feature combination, an option corresponding to the feature combination, and a configuration time corresponding to the feature combination;

[0042] The sorting unit is used to sort the feature combinations based on the configuration time;

[0043] The first setting unit is used to set the first feature combination as the feature combination to be determined, and then call the third judgment unit;

[0044] The third judgment unit is used to judge whether the feature combination to be determined meets the constraint conditions, where the constraint conditions are used to represent that all features under the feature combination all have corresponding target features. If the constraint conditions are met, the first determination unit is called; if the constraint conditions are not met, the fourth judgment unit is called;

[0045] The first determination unit is configured to use the option corresponding to the to-be-determined feature combination as the target option;

[0046] The fourth judgment unit is configured to judge whether the to-be-determined feature combination is the last feature combination under the configuration item. If it is not the last feature combination, the second setting unit is called; if it is the last feature combination, the second determination unit is called;

[0047] The second setting unit is configured to set the next feature combination of the to-be-determined feature combination as the to-be-determined feature combination, and then call the third judgment unit;

[0048] The second determination unit uses a preset default option as the target option.

[0049] Preferably, the OKR management solution generation system further includes a second acquisition module, a judgment module, and a recommendation module:

[0050] The second acquisition module is configured to, for any OKR management solution, acquire evaluation parameters corresponding to the OKR management solution;

[0051] The judgment module is configured to judge whether the evaluation parameters meet the recommendation conditions, where the recommendation conditions are that the number of members corresponding to the OKR management solution is greater than a first threshold and the score is greater than a second threshold. If the recommendation conditions are met, the configuration module is called;

[0052] The recommendation module is configured to set the option corresponding to the OKR management solution as the recommended option.

[0053] According to a third aspect of the present invention, there is provided an electronic device, including a memory and a processor connected to the memory. When the processor executes a computer program stored on the memory, the OKR management solution generation method of the present invention is implemented.

[0054] According to a fourth aspect of the present invention, there is provided a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the OKR management solution generation method of the present invention is implemented.

[0055] The positive and progressive effects of the present invention are as follows:

[0056] By pre-splitting the OKR management solution into different configurable items, each configuration item includes multiple options, and different combinations of options are used to generate different OKR management solutions. The present invention dynamically generates multiple OKR management solutions through a single deployment, solves the problem of difficulty in developing different OKR management solutions, and greatly reduces the development cost of different OKR management solutions. At the same time, as various OKR management solutions accumulate, more excellent OKR management solutions are recommended. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 It is a schematic flowchart of the method for generating the OKR management solution of Embodiment 1 of the present invention.

[0058] Figure 2 It is a schematic flowchart of the configuration process of step S12 of the method for generating the OKR management solution of Embodiment 1 of the present invention.

[0059] Figure 3 It is a schematic flowchart of the determination process of step S14 of the method for generating the OKR management solution of Embodiment 1 of the present invention.

[0060] Figure 4 It is a schematic diagram of an OKR management solution of the method for generating the OKR management solution of Embodiment 1 of the present invention.

[0061] Figure 5 It is a schematic diagram of another OKR management solution of the method for generating the OKR management solution of Embodiment 1 of the present invention.

[0062] Figure 6 It is a schematic diagram of yet another OKR management solution of the method for generating the OKR management solution of Embodiment 1 of the present invention.

[0063] Figure 7 It is a schematic flowchart of the process of recommending an OKR management solution in the method for generating the OKR management solution of Embodiment 1 of the present invention.

[0064] Figure 8 It is a schematic diagram of the structure of the OKR management solution generation system of Embodiment 2 of the present invention.

[0065] Figure 9 It is a schematic diagram of the structure of the second configuration module 22 of the OKR management solution generation system of Embodiment 2 of the present invention.

[0066] Figure 10 It is a schematic diagram of the structure of the determination module 24 of the OKR management solution generation system of Embodiment 2 of the present invention.

[0067] Figure 11 It is a schematic diagram of the structure of the electronic device of Embodiment 3 of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0068] The present invention will be further described below by way of examples, but the present invention is not limited to the scope of the described examples for this reason.

[0069] Example 1

[0070] This example provides a method for generating an OKR management solution. The method for generating the OKR management solution pre-sets multiple configuration items involved in the OKR management solution based on user habits. Each configuration item includes multiple options. Among them, different combinations of options are used to generate different OKR management solutions. For example, the display methods of OKR data are different. Team A hopes to intuitively see its own OKR data list through a list, while Team B hopes to split the OKR data and can sequentially see the OKR data of its subordinates through a hierarchical tree, etc.; Another example is that the control methods of OKR are different. Team A hopes that after the OKR of the leader is drawn up, subordinates can actively claim the OKR of the superior and associate it when formulating their own OKR, while Team B hopes that the superior can forcibly assign the OKR to the subordinates to follow up when formulating the OKR, etc.; Another example is that the member management methods are different. Team A hopes that the participants in a certain OKR are fixed, Team B hopes to be automatically associated according to job functions, and Team C hopes to be divided according to work content, etc. Of course, this example is not limited to the above configuration items and options.

[0071] As Figure 1 shown, the method for generating the OKR management solution includes the following steps:

[0072] S11. Configure member information, where the member information includes members and multiple characteristics corresponding to the members.

[0073] In this example, the characteristics are used to represent useful information for identifying different members. The characteristics may include information such as the unique identity ID (unique identification number), name, age, department, position, working years, and direct superior of the member, etc. As an optional implementation method, a form and various different optional characteristics are provided. First, the members are imported, then the optional characteristic items are selected and combined, and then the corresponding characteristic data is automatically imported. Of course, custom characteristics can also be added; As another optional implementation method, a file in a fixed format with pre-filled member information can be imported (such as filling multiple members and corresponding characteristics into an excel table, etc.), and finally the file format is adjusted to a relational database form and automatically saved.

[0074] The member information involves the superior-subordinate member relationship, and may also involve the docking relationship with a third-party organization, etc. As an optional implementation method, the organizational relationship is automatically maintained, and third-party data import is reserved. For example, when importing member information, the superior and subordination relationships are automatically reorganized, etc.

[0075] S12. For each configuration item, configure the matching relationship between the feature combination and the option respectively, where the feature combination includes at least one feature.

[0076] As an optional implementation, the features in the feature combination include positive features and negative features. A positive feature indicates that the feature must exist, while a negative feature indicates that the feature must not exist. The matching relationship between the feature combination and the option is used to represent that the members meeting the feature combination adopt the option. For example, taking the display method of OKR data as a configuration item, the options include list and hierarchical tree. Assuming that the hierarchical tree option is matched with the feature combination of "Sales Department + Female - Intern", then all members who belong to the Sales Department, are female and not interns will adopt the hierarchical tree method to display OKR data. In step S12, for any configuration item, use the configuration process to configure the matching relationship between the feature combination and the option. As Figure 2 shown, the configuration process in step S12 includes the following steps:

[0077] S121. Determine whether the option to be matched receives a matching instruction. If a matching instruction is received, then execute step S122, and then execute step S123.

[0078] Among them, the option to be matched is used to represent any option under the configuration item. A matching instruction only matches one option with one feature combination, and the matching instruction includes the configurator information, the feature combination to be matched, and the option to be matched. Specifically, sequentially determine whether the option is consistent with the option to be matched in the matching instruction. If there is an option that is consistent with the option to be matched in the matching instruction, it means that the option needs to match the feature combination.

[0079] S122. Obtain the feature combination to be matched from the matching instruction.

[0080] Among them, the feature combination to be matched is used to represent the feature combination that will be matched with the option to be matched, and obtain the feature combination to be matched (i.e., the feature combination to be matched) from the matching instruction.

[0081] S123. Determine whether there is a feature combination to be matched with an existing matching relationship among all the options under the configuration item. If there is a feature combination to be matched, then execute step S124, and then execute step S125; if there is no feature combination to be matched, then directly execute step S125.

[0082] Judge separately whether all options under the configuration item have matching feature combinations. If there are, further judge whether each feature combination under the option is consistent with the feature combination to be matched. If the feature combination to be matched exists under the configuration item, the original matching relationship needs to be removed first, and then the feature combination to be matched in the matching instruction is matched with the option to be matched. If the feature combination to be matched does not exist under the configuration item, directly match the feature combination to be matched in the matching instruction with the option to be matched. It should be noted that this step is mainly to avoid the situation where different options under a configuration item match the same feature combination. As an optional implementation method, when the feature combination to be matched already exists under the configuration item, output the option corresponding to the current feature combination to be matched. If this option happens to be the option to be matched, you can choose to exit the configuration process. At this time, the configuration time of this option remains unchanged. Of course, you can also choose to continue the configuration process. After the configuration is completed, the configuration time of this option can be updated.

[0083] S124. Remove the matching relationship.

[0084] Among them, removing the matching relationship is used to represent deleting the original feature combination to be matched. As an optional implementation method, before removing the matching relationship, it is necessary to obtain the configuration record when the feature combination to be matched is configured. The configuration record includes the configurator information and the configuration time. The configurator information includes the management authority of the configurator, and the matching instruction also includes the configurator information. Compare the management authority in the configuration record with the management authority in the matching instruction. If the management authority in the matching instruction is higher than the management authority in the configuration record, directly remove the matching relationship; otherwise, send a prompt message indicating that there is no permission to delete the current information to the configurator in the matching instruction, prompting the configurator to obtain a higher management authority.

[0085] As an optional implementation method, the management authority is default determined by the identity of the configurator. For example, by default, the management authority of the boss is higher than that of the department manager, and the management authority of the department manager is higher than that of the subordinates in the department. At the same time, it supports the configurator with a higher management authority to assign their own management authority to the configurator with a lower management authority. For example, the management authority of Zhang San is higher than that of Li Si, and the management authority of Li Si is higher than that of Wang Wu. When Zhang San assigns his own management authority to Wang Wu, the management authority of Wang Wu will be higher than that of Li Si.

[0086] S125. Match the feature combination to be matched with the option to be matched.

[0087] As an optional implementation method, after successful matching, generate relevant configuration records. The configuration records include configurator information, configuration time, and the configured options and feature combinations, and then save the configuration records in the form of files to the server.

[0088] S13. For each member, obtain multiple target features corresponding to the member respectively.

[0089] Specifically, obtain each member and the features corresponding to the member (i.e., target features) from the pre-configured member information. For example, the features of member Zhang San include that his name is Zhang San, gender is male, department is the Sales Department, position is supervisor, and working years is 5 years, etc.

[0090] S14. Determine multiple target options that match the target features respectively according to the matching relationship.

[0091] In step S14, for any one configuration item, use the determination process to determine the target option that matches the target feature. As Figure 3 shown, the determination process of step S14 includes the following steps:

[0092] S141. Obtain the feature combination information under the configuration item. Among them, the feature combination information includes feature combinations, options corresponding to the feature combinations, and configuration times corresponding to the feature combinations.

[0093] As an optional implementation manner, query whether there are feature combinations with existing matching relationships for each option of the configuration item respectively. If so, obtain the feature combinations from each option respectively. One option may match one or more feature combinations, and then obtain the configuration time from the configuration records of each configuration combination respectively. In this embodiment, the configuration time is accurate to minutes, that is, accurate to a certain year, month, day, hour, and minute.

[0094] For the convenience of explanation, take the OKR management method as an example of the configuration item. The options include "Subscribe to OKR", "Align with OKR", and "Split OKR". Assume that the feature combinations matched by the option "Subscribe to OKR" include "Sales Department + Supervisor" configured at 10:00 on February 1, 2022, the feature combinations matched by the option "Align with OKR" include "Sales Department" configured at 8:00 on February 1, 2022, and "Design Department + Supervisor - Working for more than four years" configured at 9:00 on February 3, 2022. The option "Split OKR" does not match any feature combinations. Then the feature combination information obtained under this configuration item includes [Sales Department + Supervisor, Subscribe to OKR, February 1, 2022, 10:00], [Sales Department, Align with OKR, February 1, 2022, 8:00], and [Design Department + Supervisor - Working for more than four years, Align with OKR, February 3, 2022, 9:00].

[0095] S142. Sort the feature combinations based on the configuration time.

[0096] As an optional implementation, sort the feature combinations in the order of configuration time. Specifically, place the configuration options with a newer configuration time in the front and those with an older configuration time in the back. For example, after sorting [Sales Department, Subscribe to OKR, February 1, 2022, 8:00], [Sales Department + Supervisor, Align OKR, February 1, 2022, 10:00], and [Design Department + Supervisor - with more than four years of work experience, Align OKR, February 3, 2022, 9:00], the resulting feature combinations and order are "Design Department + Supervisor - with more than four years of work experience", "Sales Department + Supervisor", and "Sales Department".

[0097] S143. Set the first feature combination as the feature combination to be determined, and then execute step S144.

[0098] As an optional implementation, by default, start reading from the first feature combination under the configuration item, set the first feature combination as the feature combination to be determined, and then determine whether the feature combination to be determined meets the constraint conditions. For example, among "Design Department + Supervisor - with more than four years of work experience", "Sales Department + Supervisor", and "Sales Department", set the feature combination "Design Department + Supervisor - with more than four years of work experience" as the feature combination to be determined.

[0099] S144. Determine whether the feature combination to be determined meets the constraint conditions. If it meets the constraint conditions, execute step S145; if it does not meet the constraint conditions, execute step S146.

[0100] Among them, the constraint condition is used to represent that all features under the feature combination have corresponding target features.

[0101] As an optional implementation, split the feature combination to be determined into multiple features. Specifically, split it in the same way as the original combined features, and then compare the features of the feature combination with the features of the member information (i.e., the target features) respectively to determine whether they exactly correspond. If the features of the feature combination exactly correspond to the target features, take the option corresponding to this feature combination as the target option. If there is a non - corresponding situation, it is still necessary to continue to judge the feature combination. The ways of combined features include two ways: forward and reverse. The forward way means that this feature must exist, while the reverse way means that this feature must not exist. For example, if the feature combination to be determined is "Design Department + Supervisor - with more than four years of work experience", the split features include "Design Department", "Supervisor", and "not with more than four years of work experience".

[0102] Taking member Zhang San as an example, assume that Zhang San's characteristics include his name being Zhang San, gender being male, department being the Sales Department, position being supervisor, and working years being 5 years. Among them, Zhang San's characteristics do not meet the two characteristics of "Design Department" and "not more than four years of work experience". Therefore, for Zhang San, the characteristic combination of "Design Department + Supervisor - more than four years of work experience" does not meet the constraint conditions. Taking member Li Si as another example, assume that member Li Si's characteristics include his name being Li Si, gender being female, department being the Design Department, position being supervisor, and working years being 3 years. Li Si's characteristics meet "Design Department", "Supervisor", and "not more than four years of work experience". Therefore, for Li Si, this characteristic combination meets the constraint conditions.

[0103] S145. Take the option corresponding to the feature combination to be determined as the target option.

[0104] Among them, the target option is used to represent the option required for generating the OKR management plan. If the feature combination to be determined meets the constraint conditions, it means that the option corresponding to the feature combination to be determined is the required option (i.e., the target option). It should be noted that only one option can be selected for a configuration item. As an optional implementation method, after the target option is selected under this configuration item, the determination process for this configuration item ends, and then the next configuration item is read and the corresponding determination process is executed.

[0105] S146. Determine whether the feature combination to be determined is the last feature combination under the configuration item. If it is not the last feature combination, execute step S147; if it is the last feature combination, execute step S148.

[0106] When the feature combination to be determined meets the constraint conditions, further determine whether there are other feature combinations after the feature combination to be determined, so as to determine whether the feature combination to be determined is the last feature combination under the configuration item. If it is determined that the feature combination to be determined is not the last feature combination, set the next feature combination of the current feature combination to be determined as the feature combination to be determined. If it is determined that the feature combination to be determined is the last feature combination, it means that all the feature combinations under this configuration item do not meet the constraint conditions, and the preset default option is taken as the target option.

[0107] S147. Set the next feature combination of the feature combination to be determined as the feature combination to be determined, and then return to execute step S144.

[0108] For example, among "Design Department + Supervisor - Working for more than four years", "Sales Department + Supervisor" and "Sales Department", the next feature combination of the feature combination of "Design Department + Supervisor - Working for more than four years", that is, "Sales Department + Supervisor", is set as the feature combination to be determined, and then the process returns to step S144 again. For example, for the member Zhang San in the above example, Zhang San's features include his name Zhang San, gender male, department he belongs to, position supervisor and years of work experience 5 years, and the features of the feature combination to be determined include "Sales Department" and "Supervisor". For each feature combination to be determined, consistent features can be found in Zhang San's features, then step S145 is executed, and the option "Align OKR" corresponding to "Sales Department + Supervisor" is set as the target option, and then the determination process is exited.

[0109] In this embodiment, if it is determined in step S144 that the feature combination to be determined does not satisfy the constraint condition, step S146 is further executed until it is determined in step S146 that the feature combination to be determined is the last feature combination under the configuration item.

[0110] S148. Use the preset default option as the target option.

[0111] Among them, the preset default option can be the option set by the system by default, or the option set in advance by the user. The options that match the feature combination are prioritized. If all feature combinations do not meet the constraints, the preset default option is used as the target option, and then the determination process ends.

[0112] S15. Combine the target options to generate an OKR management plan corresponding to the members.

[0113] Through step S14, one option corresponding to a member (i.e., target option) is selected from each configuration item respectively, and then the OKR management plan corresponding to each member is loaded according to the function control corresponding to each target option, thereby realizing dynamic generation of multiple OKR management plans under one configuration, wherein members with the same characteristics can be represented as a team, and each team can have its own unique OKR management plan.

[0114] As an optional implementation method, each OKR management plan will be stored in the server in the form of a file, and each registered user has the authority to customize or directly adopt other people's OKR management plans. The interfaces of each plan do not interfere with each other, but the data can be the same. Users can perform corresponding goal management operations according to their own OKR management plans.

[0115] Figure 4 , Figure 5 and Figure 6OKR management solutions in several different scenarios are respectively shown.

[0116] As Figure 4 shown, the OKR management solution is applicable to the situation where the highest-level leader enters the OKR goal, and the subordinates only need to supplement the specific implementation methods of the OKR indicators. Specifically, the Master (the person with the highest authority in the organization) is responsible for creating the OKR indicators and designating relevant members. The relevant members can subscribe to the OKR indicators, while other irrelevant members can only view the goals. Then, the completion status of the OKR indicators is associated with a third-party platform. At this time, the background will automatically synchronize the data of the third-party platform to ensure that all data is up-to-date. Among them, the data of the third-party platform may include various indicators or measurable data such as actual performance, which is used to predict the trend of the OKR indicators and prevent the goals from deviating too much from the center.

[0117] As Figure 5 shown, the OKR management solution is applicable to personalized teams. Team members can define OKR indicators for each other or claim the OKR indicators of their superiors. Specifically, the Master creates his own OKR indicators and designates other members. Then, other members can create their own OKR indicators according to the OKR indicators of their superiors. At the same time, the OKRs among the members also form a linkage relationship. For example, when the direction of an OKR indicator deviates, the platform will automatically respond upward to the associated OKR data and remind the corresponding person in charge to correct the direction of the OKR indicator.

[0118] As Figure 6 shown, the OKR management solution is applicable to teams with complex interactions between the organization's superior and subordinate relationships to maintain unified OKR indicators. Specifically, after the Master creates the OKR indicators, all subsequent OKR indicators are only allowed to be broken down downward. As the organizational relationship increases downward in levels, the OKR indicators will be broken down more finely.

[0119] In order to accumulate efficient and high-quality OKR management solutions, it is necessary to determine whether the OKR management solutions predefined by users are worthy of recommendation. By recording the usage frequency and scores of different OKR management solutions predefined by users, efficient and high-quality OKR management solutions are evaluated and promoted to more teams. As Figure 7 shown, the steps for recommending OKR management solutions are as follows:

[0120] S16. For any OKR management solution, obtain the evaluation parameters corresponding to the OKR management solution.

[0121] Among them, the evaluation parameters mainly include the usage frequency and score of the OKR management plan. As an optional implementation method, the usage effect of the OKR management plan is automatically recorded. For example, at the end of the target period, each key result of each target is evaluated, and the OKR index completion degree is analyzed, so as to be converted into the corresponding score. As another optional method, after a preset period of time, such as one month, a scoring window pops up, and the corresponding user scores, and then the average score is calculated by integrating each score segment. Of course, in this embodiment, the final score can also be calculated by integrating the two methods.

[0122] S17. Determine whether the evaluation parameters meet the recommendation conditions. If they meet the recommendation conditions, execute step S18. Among them, the recommendation conditions are that the number of members corresponding to the OKR management plan is greater than the first threshold and the score is greater than the second threshold.

[0123] As an optional implementation method, the members corresponding to the OKR management plan refer to users who have used the OKR management plan beyond the probation period. For example, if the probation period is set to three days, if it is less than three days, it will not be included in the number of members.

[0124] As an optional implementation method, when the number of members exceeds the first threshold, the recommendation mechanism is automatically triggered, and then it is further determined whether the score is greater than the second threshold. If the score is greater than the second threshold, it means that the OKR management plan is a high-quality plan worthy of recommendation.

[0125] S18. Set the option corresponding to the OKR management plan as the recommended option.

[0126] When the evaluation parameters meet the recommendation conditions, the corresponding OKR management plan is recommended to other teams. As an optional implementation method, if there are multiple OKR management plans that meet the recommendation conditions during the same period, the optimal OKR management plan is selected for recommendation, and the option corresponding to the OKR management plan is set as the recommended option, that is, it is displayed in the front row of each configuration item and marked with the word "recommended". Other teams can directly use the recommended OKR management plan or draw on some options in the OKR management plan.

[0127] It should be noted that the recommended option is only set for a period of time, such as three months. After three months, the label on the original recommended option is removed, and then the plan with the optimal evaluation parameters is re-screened from the OKR management plans saved in the service for recommendation.

[0128] In this embodiment, the OKR management solution is pre-split into different configurable items, each configurable item includes multiple options, and different combinations of options are used to generate different OKR management solutions. This embodiment dynamically generates multiple OKR management solutions through one deployment, solves the problem of difficulty in developing different OKR management solutions, and greatly reduces the development cost of different OKR management solutions. At the same time, as various OKR management solutions accumulate, more excellent OKR management solutions are recommended.

[0129] Embodiment 2

[0130] This embodiment provides a generation system for an OKR management solution. The generation system for the OKR management solution pre-sets multiple configurable items related to the OKR management solution based on user habits. Each configurable item includes multiple options. Among them, different combinations of options are used to generate different OKR management solutions. For example, the display methods of OKR data are different. Team A hopes to intuitively see its own OKR data list through a list, while Team B hopes to split the OKR data and can sequentially see the OKR data of its subordinates through a hierarchical tree, etc.; another example is that the control methods of OKRs are different. Team A hopes that after the leader's OKR is drawn up, subordinates can actively claim the superior's OKR and associate it when formulating their own OKRs, while Team B hopes that the superior can forcibly assign an OKR to a subordinate to follow up when formulating the OKR, etc.; still another example is that the member management methods are different. Team A hopes that the participants in a certain OKR are fixed, Team B hopes to be automatically associated according to job functions, and Team C hopes to be divided according to work content, etc. Of course, this embodiment is not limited to the above configurable items and options.

[0131] As Figure 8 shown, the generation system for the OKR management solution includes a first configuration module 21, a second configuration module 22, a first acquisition module 23, a determination module 24, and a combination module 25:

[0132] The first configuration module 21 is used to configure member information, and the member information includes members and multiple characteristics corresponding to the members. In this embodiment, the characteristics are used to represent useful information for identifying different members. The characteristics may include information such as the unique identity ID (unique identification number), name, age, department, position, working years, and direct superior of the member, etc. As an optional implementation method, the first configuration module 21 provides a form and various different optional characteristics, first imports the members, then selects and combines the optional characteristic items, and then automatically imports the corresponding characteristic data. Of course, custom characteristics can also be added; as another optional implementation method, a file in a fixed format with pre-filled member information can be imported (such as filling in multiple members and corresponding characteristics as an excel table, etc.), and finally the first configuration module 21 adjusts the file format to a relational database form and automatically saves it.

[0133] The member information involves the superior-subordinate member relationship and may involve the docking relationship with third-party organizations. As an optional implementation manner, the first configuration module 21 automatically maintains the organizational relationship and reserves the import of third-party data. For example, when importing member information, the superior and subordination relationships are automatically reorganized, etc.

[0134] The second configuration module 22 is used to configure the matching relationship between the feature combination and the option for each configuration item. Among them, the feature combination includes at least one feature. As an optional implementation manner, the features in the feature combination include positive features and negative features. A positive feature indicates that the feature must exist, while a negative feature indicates that the feature must not exist. The matching relationship between the feature combination and the option is used to represent that members meeting the feature combination adopt the option. For example, taking the display method of OKR data as a configuration item, the options include a list and a hierarchical tree. Assuming that the hierarchical tree option is matched with the feature combination of "Sales Department + Female - Intern", then all members who belong to the Sales Department, are female, and are not interns will finally adopt the hierarchical tree method to display OKR data.

[0135] The second configuration module 22 is used to configure the matching relationship between the feature combination and the option for any configuration item by using a configuration process. As Figure 9 shown, the second configuration module 22 includes a first judgment unit 221, a first acquisition unit 222, a second judgment unit 223, a release unit 224, and a matching unit 225:

[0136] The first judgment unit 221 is used to judge whether the option to be matched receives a matching instruction. If a matching instruction is received, the first acquisition unit 222 is called, and then the second judgment unit 223 is called. Among them, the option to be matched is used to represent any option under the configuration item. A matching instruction only matches one option with one feature combination. The matching instruction includes the configurator information, the feature combination to be matched, and the option to be matched. Specifically, the first judgment unit 221 sequentially judges whether the option is consistent with the option to be matched in the matching instruction. If there is an option that is consistent with the option to be matched in the matching instruction, it means that this option needs to match the feature combination.

[0137] The first acquisition unit 222 is used to acquire the feature combination to be matched from the matching instruction. Among them, the feature combination to be matched is used to represent the feature combination that will be matched with the option to be matched. The first acquisition unit 222 acquires the feature combination to be matched (i.e., the feature combination to be matched) from the matching instruction.

[0138] The second judgment unit 223 is used to judge whether there is a feature combination to be matched with a matching relationship in all options under the configuration item. If there is a feature combination to be matched, the release unit 224 is called, and then the matching unit 225 is called; if there is no feature combination to be matched, the matching unit 225 is directly called. The second judgment unit 223 judges whether there is a matching feature combination in all options under the configuration item. If so, it further judges whether each feature combination under the option is consistent with the feature combination to be matched. If there is a feature combination to be matched under the configuration item, it is necessary to first call the release unit 224 to cancel the original matching relationship, and then call the matching unit 225 to match the feature combination to be matched in the matching instruction with the option to be matched; if there is no feature combination to be matched under the configuration item, the matching unit 225 is directly called to match the feature combination to be matched in the matching instruction with the option to be matched.

[0139] It should be noted that this step is mainly to avoid the situation where different options under a configuration item match the same feature combination. As an optional implementation method, when a feature combination to be matched already exists under the configuration item, the option corresponding to the current feature combination to be matched is output. If this option happens to be the option to be matched, you can choose to exit the configuration process. At this time, the configuration time of the option remains unchanged. Of course, you can also choose to continue the configuration process. After the configuration is completed, you can update the configuration time of the option.

[0140] The release unit 224 is used to release the matching relationship. Among them, the release of the matching relationship is used to represent the deletion of the original feature combination to be matched. Specifically, before releasing the matching relationship, it is necessary to obtain the configuration record when the feature combination to be matched is configured. The configuration record includes the configuration person information and the configuration time. The configuration person information includes the configuration person's management authority, and the matching instruction also includes the configuration person information. The release unit 224 compares the management authority in the configuration record with the management authority in the matching instruction. If the management authority in the matching instruction is higher than the management authority in the configuration record, the release unit 224 directly releases the matching relationship; otherwise, the release unit 224 sends a prompt message to the configuration person in the matching instruction that there is no authority to delete the current information, prompting the configuration person to obtain a higher management authority.

[0141] As an optional implementation method, the management authority is determined by the identity of the configurator by default. For example, the management authority of the boss is higher than that of the department manager, and the management authority of the department manager is higher than that of the employees under the department. At the same time, it supports the configurator with high management authority to assign his or her management authority to the configurator with low management authority. For example, Zhang San's management authority is higher than that of Li Si, and Li Si's management authority is higher than that of Wang Wu. When Zhang San assigns his or her management authority to Wang Wu, Wang Wu's management authority will be higher than that of Li Si.

[0142] The matching unit 225 is used to match the feature combination to be matched with the option to be matched. As an optional implementation manner, after the matching unit 225 succeeds in matching, it generates a relevant configuration record, which includes the configurator information, the configuration time, and the configured option and feature combination, and then saves the configuration record in the form of a file to the server.

[0143] The first acquisition module 23 is used to respectively acquire a plurality of target features corresponding to each member. Specifically, the first acquisition module 23 acquires each member and the features corresponding to the member (i.e., target features) from the pre-configured member information. For example, the features of member Zhang San include that the name is Zhang San, the gender is male, the department belongs to the sales department, the position is the supervisor, and the working years are 5 years, etc.

[0144] The determination module 24 is used to respectively determine a plurality of target options that match the target features according to the matching relationship. The determination module 24 is used for any one configuration item, and uses the determination process to determine the target option that matches the target feature, such as Figure 10 shown, the determination module 24 includes a second acquisition unit 241, a sorting unit 242, a first setting unit 243, a third judgment unit 244, a first determination unit 245, a fourth judgment unit 246, a second setting unit 247, and a second determination unit 248:

[0145] The second acquisition unit 241 is used to acquire the feature combination information under the configuration item. Among them, the feature combination information includes the feature combination, the option corresponding to the feature combination, and the configuration time corresponding to the feature combination. As an optional implementation manner, the second acquisition unit 241 respectively queries whether there are feature combinations with existing matching relationships for each option of the configuration item. If so, the second acquisition unit 241 respectively acquires the feature combinations from each option. One option may match one or more feature combinations, and then the second acquisition unit 241 respectively acquires the configuration time from the configuration records of each configuration combination. In this embodiment, the configuration time is accurate to minutes, that is, accurate to a certain year, month, day, hour, and minute.

[0146] For ease of explanation, taking the control method of OKR as an example of the configuration item, the options include "Subscribe to OKR", "Align with OKR", and "Split OKR". Assume that the feature combination matched by the option "Subscribe to OKR" includes "Sales Department + Supervisor" configured at 10:00 on February 1, 2022, the feature combination matched by the option "Align with OKR" includes "Sales Department" configured at 8:00 on February 1, 2022, and "Design Department + Supervisor - with more than four years of work experience" configured at 9:00 on February 3, 2022. The option "Split OKR" does not match any feature combinations. Then, the feature combination information obtained under this configuration item includes [Sales Department + Supervisor, Subscribe to OKR, February 1, 2022, 10:00], [Sales Department, Align with OKR, February 1, 2022, 8:00], and [Design Department + Supervisor - with more than four years of work experience, Align with OKR, February 3, 2022, 9:00].

[0147] The sorting unit 242 is used to sort the feature combinations based on the configuration time. As an optional implementation manner, the sorting unit 242 sorts the feature combinations in the order of the configuration time. Specifically, the configuration option with a newer configuration time is placed in the front, and the configuration option with an older configuration time is placed in the back. For example, after sorting [Sales Department, Subscribe to OKR, February 1, 2022, 8:00], [Sales Department + Supervisor, Align with OKR, February 1, 2022, 10:00], and [Design Department + Supervisor - with more than four years of work experience, Align with OKR, February 3, 2022, 9:00], the obtained feature combinations and order are "Design Department + Supervisor - with more than four years of work experience", "Sales Department + Supervisor", and "Sales Department".

[0148] The first setting unit 243 is used to set the first feature combination as the to-be-determined feature combination, and then call the third judgment unit 244. As an optional implementation manner, the first setting unit 243 defaults to read from the first feature combination under the configuration item, and sets the first feature combination as the to-be-determined feature combination, and then calls the third judgment unit 244 to judge whether the to-be-determined feature combination meets the constraint conditions. For example, among "Design Department + Supervisor - with more than four years of work experience", "Sales Department + Supervisor", and "Sales Department", the first setting unit 243 sets the feature combination "Design Department + Supervisor - with more than four years of work experience" as the to-be-determined feature combination.

[0149] The third judgment unit 244 judges whether the to-be-determined feature combination meets the constraint conditions. If it meets the constraint conditions, it calls the first determination unit 245; if it does not meet the constraint conditions, it calls the fourth judgment unit 246. Among them, the constraint conditions are used to represent that all features under the feature combination have corresponding target features.

[0150] As an optional implementation, the third determination unit 244 splits the feature combination to be determined into multiple features. Specifically, the third determination unit 244 splits it in the way of the original combined features, and then separately compares the features of the feature combination with the features of the member information (i.e., the target features) to determine whether they exactly correspond. If the features of the feature combination exactly correspond to the target features, the first determination unit 245 is called to use the option corresponding to the feature combination as the target option. If there is a non-corresponding situation, the feature combination still needs to be further determined. Among them, the ways of combining features include two ways: forward and reverse. The forward way means that the feature must exist, while the reverse way means that the feature must not exist. For example, if the feature combination to be determined is "Design Department + Supervisor - More than four years of work experience", the split features include "Design Department", "Supervisor", and "Not more than four years of work experience".

[0151] Taking member Zhang San as an example, assume that Zhang San's features include name Zhang San, gender male, department sales department, position supervisor, and work years 5 years. Among them, Zhang San's features do not conform to the two features of "Design Department" and "Not more than four years of work experience". Therefore, for Zhang San, the feature combination of "Design Department + Supervisor - More than four years of work experience" does not meet the constraint conditions. Taking member Li Si as another example, assume that member Li Si's features include name Li Si, gender female, department design department, position supervisor, and work years 3 years. Li Si's features meet "Design Department", "Supervisor", and "Not more than four years of work experience". Therefore, for Li Si, this feature combination meets the constraint conditions.

[0152] The first determination unit 245 is used to use the option corresponding to the feature combination to be determined as the target option. Among them, the target option is used to represent the option required for generating the OKR management plan. If the feature combination to be determined meets the constraint conditions, it means that the option corresponding to the feature combination to be determined is the required option (i.e., the target option). It should be noted that only one option can be selected for one configuration item. As an optional implementation, after the first determination unit 245 selects the target option under this configuration item, it ends the determination process for this configuration item, and then reads the next configuration item and executes the corresponding determination process.

[0153] The fourth determination unit 246 is used to determine whether the feature combination to be determined is the last feature combination under the configuration item. If it is not the last feature combination, the second setting unit 247 is called; if it is the last feature combination, the second determination unit 248 is called.

[0154] When the feature combination to be determined meets the constraint condition, the fourth judgment unit 246 further determines whether there are any other feature combinations after the feature combination to be determined, so as to determine whether the feature combination to be determined is the last feature combination under the configuration item. If the fourth judgment unit 246 determines that the feature combination to be determined is not the last feature combination, it calls the second setting unit 247 to set the next feature combination of the current feature combination to be determined as the feature combination to be determined. If the fourth judgment unit 246 determines that the feature combination to be determined is the last feature combination, it means that all the feature combinations under the configuration item do not meet the constraint condition, and it calls the second determination unit 248 to use the preset default option as the target option.

[0155] The second setting unit 247 is used to set the next feature combination of the feature combination to be determined as the feature combination to be determined, and then call the third judgment unit 244.

[0156] For example, among "Design Department + Supervisor - with more than four years of work experience", "Sales Department + Supervisor", and "Sales Department", the second setting unit 247 sets the next feature combination of the feature combination "Design Department + Supervisor - with more than four years of work experience", that is, "Sales Department + Supervisor", as the feature combination to be determined, and then calls the third judgment unit 244 again. For example, for member Zhang San in the above example, Zhang San's features include name Zhang San, gender male, department Sales Department, position Supervisor, and work years 5 years, and the features of the feature combination to be determined include "Sales Department" and "Supervisor". For each feature of the feature combination to be determined, a consistent feature can be found in Zhang San's features, then the first determination unit 245 is called. The first determination unit 245 uses the option "Align OKR" corresponding to "Sales Department + Supervisor" as the target option, and then exits the determination process.

[0157] In this embodiment, if it is determined in the third judgment unit 244 that the feature combination to be determined does not meet the constraint condition, the fourth judgment unit 246 is continuously called until the fourth judgment unit 246 determines that the feature combination to be determined is the last feature combination under the configuration item.

[0158] The second determination unit 248 is used to use the preset default option as the target option. Among them, the preset default option can be an option defaulted by the system or an option preset by the user. The option with a feature combination is preferentially judged and matched. If all the feature combinations do not meet the constraint condition, the second determination unit 248 uses the preset default option as the target option, and then ends the determination process.

[0159] The combination module 25 is used to combine target options to generate an OKR management plan corresponding to members. Through the determination module 24, one option corresponding to a member (i.e., the target option) is selected from each configuration item respectively, and then the combination module 25 loads the OKR management plan corresponding to each member according to the function control corresponding to each target option, so as to dynamically generate multiple OKR management plans under one configuration. Among them, members with the same characteristics can be characterized as a team, that is, each team can have its own unique OKR management plan.

[0160] As an optional implementation method, each set of OKR management plans will be stored in the server in the form of files, and each registered user has the right to customize or directly adopt other people's OKR management plans. The interfaces of each set of plans do not interfere with each other, but the data can be the same. Users can perform corresponding target management operations according to their own OKR management plans.

[0161] In order to accumulate efficient and high-quality OKR management plans, it is necessary to judge whether the OKR management plan predefined by the user is worthy of recommendation. By recording the usage frequency and score of different OKR management plans predefined by the user, efficient and high-quality OKR management plans are evaluated and promoted to more teams. As Figure 9 shown, the OKR management plan generation system further includes a second acquisition module 26, a judgment module 27 and a recommendation module 28:

[0162] The second acquisition module 26 is used to obtain the evaluation parameters corresponding to an OKR management plan for any OKR management plan. Among them, the evaluation parameters mainly include the usage frequency and score of the OKR management plan. As an optional implementation method, the second acquisition module 26 automatically records the usage effect of the OKR management plan. For example, at the end of the target period, the second acquisition module 26 evaluates each key result of each target, analyzes the completion degree of the OKR index, and thus converts it into a corresponding score; As another optional method, after a preset period of time, such as one month, the second acquisition module 26 pops up a scoring window for the corresponding user to score, and then calculates the average score by integrating each score segment. Of course, in this embodiment, the final score can also be calculated by combining the two methods.

[0163] The judgment module 27 is used to judge whether the evaluation parameters meet the recommendation conditions. If the recommendation conditions are met, the recommendation module 28 is called. Among them, the recommendation conditions are that the number of members corresponding to the OKR management plan is greater than the first threshold and the score is greater than the second threshold. As an optional implementation method, the members corresponding to the OKR management plan refer to users who have used the OKR management plan for more than the probation period. For example, if the probation period is set to three days, if it is less than three days, it will not be included in the number of members.

[0164] As an optional implementation, when the number of members exceeds the first threshold, the judgment module 27 automatically triggers the recommendation mechanism, and then further determines whether the score is greater than the second threshold. If the score is greater than the second threshold, it indicates that the OKR management solution is a high-quality solution worthy of recommendation.

[0165] The recommendation module 28 is used to set the option corresponding to the OKR management solution as the recommended option. When the evaluation parameter meets the recommendation condition, the recommendation module 28 recommends the corresponding OKR management solution to other teams. As an optional implementation, if there are multiple OKR management solutions that meet the recommendation condition during the same period, the recommendation module 28 selects the optimal OKR management solution for recommendation. Specifically, the recommendation module 28 sets the option corresponding to the OKR management solution as the recommended option, that is, displays the recommended option in the front row of each configuration item and marks the word "recommended". Other teams can directly use the recommended OKR management solution or borrow some options in the OKR management solution.

[0166] It should be noted that the recommended option is only set for a period of time, such as three months. After three months, the recommendation module 28 removes the label on the original recommended option, and then recommends the solution with the optimal evaluation parameter from the OKR management solutions saved in the service.

[0167] Embodiment 3

[0168] This embodiment provides an electronic device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the generation method of the OKR management solution in Embodiment 1.

[0169] As Figure 11 shown, the electronic device 30 is only an example and should not bring any restrictions to the functions and usage scope of the embodiments of the present invention.

[0170] The electronic device 30 can be presented in the form of a general computing device. For example, it can be a server device. The components of the electronic device 30 may include, but are not limited to: at least one of the above processors 31, at least one of the above memories 32, and a bus 33 connecting different system components (including the memory 32 and the processor 31).

[0171] The bus 33 includes a data bus, an address bus, and a control bus.

[0172] The memory 32 may include a volatile memory, such as a random access memory (RAM) 321 and a cache memory 322, and may further include a read-only memory (ROM) 323.

[0173] The memory 32 may also include a program tool 325 having a set (at least one) of program modules 324. Such program modules 324 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment.

[0174] The processor 31 executes various functional applications and data processing by running computer programs stored in the memory 32, such as the method for generating the OKR management scheme in Embodiment 1 of the present invention.

[0175] The electronic device 30 can also communicate with one or more external devices 34. Such communication can be carried out through the input / output (I / O) interface 35. Moreover, the device 30 for model generation can also communicate with one or more networks through the network adapter 36. As Figure 11 shown, the network adapter 36 communicates with other modules of the device 30 for model generation through the bus 33. It should be understood that although Figure 11 not labeled, other hardware and / or software modules can be used in combination with the device 30 for model generation, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (Redundant Array of Independent Disks) systems, tape drives, and data backup storage systems, etc.

[0176] It should be noted that although several units / modules or sub-units / modules of the electronic device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present invention, the features and functions of two or more of the above-described units / modules can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0177] Embodiment 4

[0178] This embodiment provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the method for generating the OKR management scheme in Embodiment 1.

[0179] Among them, the more specific forms that the readable storage medium can adopt include, but are not limited to: portable disks, hard disks, random access memories, read-only memories, erasable programmable read-only memories, optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0180] In an optional embodiment, the present invention can also be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to cause the terminal device to execute the method for generating the OKR management scheme in Embodiment 1.

[0181] Among them, the program code for implementing the present invention can be written in any combination of one or more programming languages, and the program code can be executed entirely on the user device, partially on the user device, executed as an independent software package, partially on the user device and partially on a remote device, or entirely on a remote device.

[0182] Although the specific embodiments of the present invention have been described above, those skilled in the art should understand that this is only an example, and the protection scope of the present invention is defined by the appended claims. Without departing from the principles and essence of the present invention, those skilled in the art can make various changes or modifications to these embodiments, but these changes and modifications all fall within the protection scope of the present invention.

Claims

1. A method for generating an OKR management solution, characterized in that, The OKR management scheme involves multiple configuration items, each of which includes multiple options, wherein different combinations of options are used to generate different OKR management schemes. The method for generating the OKR management scheme includes the following steps: Configuring member information, the member information including members and a plurality of features corresponding to the members; For each configuration item, respectively configure a matching relationship between a feature combination and the option, wherein the feature combination includes at least one of the features; For each member, respectively obtain a plurality of target features corresponding to the member; Determine a plurality of target options that match the target feature according to the matching relationship; Combining the target options to generate an OKR management plan corresponding to the member; The step of respectively determining a plurality of target options matching the target feature according to the matching relationship comprises: For any configuration item, a target option matching the target feature is determined using a determination process, the determination process comprising: Acquire feature combination information under the configuration item, wherein the feature combination information includes a feature combination, an option corresponding to the feature combination, and a configuration time corresponding to the feature combination; sorting the feature combinations based on the configuration time; The first feature combination is set as the feature combination to be determined, and whether the feature combination to be determined satisfies the constraint condition is determined. If the constraint condition is satisfied, the option corresponding to the feature combination to be determined is used as the target option; The constraint condition is used to characterize that all features under the feature combination have corresponding target features; If the constraint condition is not satisfied, determining whether the feature combination to be determined is the last feature combination under the configuration item; if it is not the last feature combination, setting the next feature combination of the feature combination to be determined as the feature combination to be determined, and then determining whether the feature combination to be determined satisfies the constraint condition; If it is the last feature combination, the preset default option is used as the target option.

2. The method for generating the OKR management solution according to claim 1, wherein The step of respectively configuring the matching relationship between the feature combination and the options comprises: For any configuration item, a matching relationship between a feature combination and the option is configured using a configuration process, wherein the configuration process includes: Determine whether the option to be matched has received a matching instruction, wherein the option to be matched is used to represent any option under the configuration item. If a matching instruction is received, obtain a feature combination to be matched from the matching instruction, and then determine whether all options under the configuration item have the feature combination to be matched that has an existing matching relationship; If the feature combination to be matched exists, the matching relationship is cancelled, and then the feature combination to be matched is matched with the option to be matched; if the feature combination to be matched does not exist, the feature combination to be matched is directly matched with the option to be matched.

3. The method for generating the OKR management solution according to claim 1, characterized in that, After the step of combining the target options to generate an OKR management plan corresponding to the member, the step further includes: For any OKR management plan, obtain the evaluation parameters corresponding to the OKR management plan; Determine whether the evaluation parameter meets the recommendation condition. If it meets the recommendation condition, set the option corresponding to the OKR management solution as the recommended option; Among them, the recommendation condition is that the number of members corresponding to the OKR management solution is greater than the first threshold and the score is greater than the second threshold.

4. A generation system for an OKR management solution, characterized in that, The OKR management solution involves multiple configuration items, and each configuration item includes multiple options. Among them, different combinations of options are used to generate different OKR management solutions. The generation system of the OKR management solution includes a first configuration module, a second configuration module, a first acquisition module, a determination module, and a combination module: The first configuration module is used to configure member information, and the member information includes members and multiple characteristics corresponding to the members; The second configuration module is used to configure the matching relationship between the feature combination and the option for each configuration item. Among them, the feature combination includes at least one of the characteristics; The first acquisition module is used to acquire multiple target characteristics corresponding to each member respectively; The determination module is used to determine multiple target options matching the target characteristics respectively according to the matching relationship; The combination module is used to combine the target options to generate an OKR management solution corresponding to the member; The determination module is used to determine the target option matching the target characteristic by using a determination process for any one configuration item. The determination module includes a second acquisition unit, a sorting unit, a first setting unit, a third judgment unit, a first determination unit, a fourth judgment unit, a second setting unit, and a second determination unit: The second acquisition unit is used to acquire the feature combination information under the configuration item. Among them, the feature combination information includes a feature combination, an option corresponding to the feature combination, and a configuration time corresponding to the feature combination; The sorting unit is used to sort the feature combinations based on the configuration time; The first setting unit is used to set the first feature combination as the to-be-determined feature combination, and then call the third judgment unit; The third judgment unit is used to judge whether the to-be-determined feature combination meets the constraint condition. Among them, the constraint condition is used to represent that all the characteristics under the feature combination have corresponding target characteristics. If it meets the constraint condition, call the first determination unit; if it does not meet the constraint condition, call the fourth judgment unit; The first determination unit is used to take the option corresponding to the to-be-determined feature combination as the target option; The fourth judgment unit is used to judge whether the to-be-determined feature combination is the last feature combination under the configuration item. If it is not the last feature combination, call the second setting unit; if it is the last feature combination, call the second determination unit; The second setting unit is used to set the next feature combination of the to-be-determined feature combination as the to-be-determined feature combination, and then call the third judgment unit; The second determination unit takes the preset default option as the target option.

5. The generation system of the OKR management solution according to claim 4, wherein, The second configuration module is used to configure the matching relationship between the feature combination and the option using the configuration process for any configuration item, and the second configuration module includes a first judgment unit, a first acquisition unit, a second judgment unit, a release unit and a matching unit: The first judgment unit is used to judge whether the to-be-matched option has received a matching instruction, wherein the to-be-matched option is used to represent any option under the configuration item, and if a matching instruction is received, the first acquisition unit is called, and then the second judgment unit is called; The first acquisition unit is used to acquire a feature combination to be matched from the matching instruction; The second judgment unit is used to judge whether there is a matching feature combination to be matched among all the options under the configuration item, and if so, call the release unit and then call the matching unit; if not, call the matching unit directly; The releasing unit is used to release the matching relationship; The matching unit is used to match the feature combination to be matched with the option to be matched.

6. The generation system of the OKR management solution according to claim 4, wherein The OKR management solution generation system further includes a second acquisition module, a judgment module and a recommendation module: The second acquisition module is used to acquire, for any OKR management plan, an evaluation parameter corresponding to the OKR management plan; The judgment module is used to judge whether the evaluation parameters meet the recommendation condition, wherein the recommendation condition is that the number of members corresponding to the OKR management plan is greater than a first threshold and the score is greater than a second threshold. If the recommendation condition is met, the configuration module is called; The recommendation module is used to set the options corresponding to the OKR management plan as recommended options.

7. An electronic device, characterized in that, It includes a memory and a processor connected to the memory, and when the processor executes a computer program stored in the memory, it implements the method for generating an OKR management plan according to any one of claims 1 to 3.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, the method for generating an OKR management plan according to any one of claims 1 to 3 is implemented.

Images