Task management system, task management method, and program

Abstract

The present invention makes it possible to increase the motivation of a user who repeatedly performs the same operation.　A task management system comprises: a reception unit 11 that receives completion of one task among a plurality of tasks included in one operation performed by each user; and a scenario advancing unit 12 that advances avatars of a plurality of users according to a scenario assigned to each of the avatars. Each time one task is completed, the scenario advancing unit 12 sequentially advances each of the avatars for a plurality of scenes included in one scenario. The number of scenes included in one scenario is set to be different according to the user.

Description

Task management system, task management method and program

[0001] There have been production line progress information display systems that display production efficiency in an easy-to-understand manner and enable production line management (see, for example, Patent Document 1). The production line progress information display system described in Patent Document 1 calculates the current number of actual processes based on process completion information and outputs it to a monitor.

[0002] The production line progress information display system can display the progress status on the inserting machine monitor installed at each production site. This allows the operator operating the inserting machine to be prompted to speed up the work pace if the progress is behind target.

[0003] JP 2012-174019 A

[0004] However, when workers on a production line are required to repeatedly perform the same tasks, which are often simple, they can easily lose motivation and lose concentration.

[0005] In a production line progress information display system such as that described in Patent Document 1, workers can be encouraged to speed up their work if they are behind schedule, but this has little effect on increasing worker motivation.

[0006] The present invention has been made in view of the above circumstances, and has as its object to provide a task management system, a task management method, and a program that can increase the motivation of a user who repeatedly performs the same task.

[0007] A task management system according to one embodiment of the present invention comprises a reception unit that receives the completion of one of multiple tasks included in a single task performed by each user, and a scenario progression unit that progresses the avatars of multiple users according to a scenario assigned to each avatar, wherein the scenario progression unit progresses each avatar in sequence through multiple scenes included in one scenario each time a task is completed, and the number of scenes included in one scenario is set to a different number depending on the user.

[0008] A task management method according to one aspect of the present invention includes a receiving step of receiving that one of multiple tasks included in one work performed by each user has been completed, and a scenario progression step of causing avatars of multiple users to progress according to a scenario assigned to each avatar, wherein the scenario progression step causes each avatar to progress sequentially through multiple scenes included in one scenario each time a task is completed, and the number of scenes included in one scenario is set to a different number depending on the user.A program according to one aspect of the present invention is a program for causing at least one processor to execute each step of the task management method.

[0009] The task management system, task management method, and program according to the above aspects of the present invention have the advantage of being able to increase the motivation of a user who repeatedly performs the same task.

[0010] 1 is a block diagram of a system including a task management device (task management system) according to an embodiment of the present invention; FIG. 2A is a block diagram of an event generation unit according to an embodiment; FIG. 2B is a block diagram of a calculation unit according to an embodiment; FIG. 3 is a flowchart showing an example of an operation of the task management device according to an embodiment; and FIG. 4 is a flowchart showing an example of an operation of the task management device according to an embodiment.

[0011] <Embodiment> A task management system according to this embodiment will be described in detail below with reference to the accompanying drawings.

[0012] The task management system according to this embodiment is a system that, when a user inputs that one task among the tasks to be performed by the user has been completed, progresses a scenario assigned to the user's avatar, thereby increasing the user's motivation for completing the task. As shown in Fig. 1, the task management system according to this embodiment includes a reception unit 11 that receives information that one task has been completed, and a scenario progression unit 12 that progresses the user's avatar according to the scenario.

[0013] Here, each scenario includes multiple scenes. When one task is completed, the scenario progression unit 12 can progress one scene. The number of scenes included in one scenario is set to a different number depending on the user.

[0014] By completing one task, the user can progress through the scenario with their avatar, scene by scene, which increases their motivation to complete the task. In addition, because the number of scenes included in one scenario is set to be different for each user, the difficulty of completing the scenario can be adjusted by the number of scenes. In other words, the difficulty of completing the scenario can be adjusted by setting fewer scenes than usual for a user performing a highly difficult task, or by setting more scenes than usual for a highly skilled user.

[0015] This can increase motivation and improve concentration on work, even for users who only perform simple repetitive tasks, which can increase the speed of work and improve productivity.

[0016] In this specification, a scenario refers to a story line assigned to each avatar. As described above, a scenario includes multiple scenes. The multiple scenes have content related to each other, and it is preferable that the story unfolds by progressing through the scenes in order. By displaying multiple scenes in order, a single story line is completed as a scenario. One scenario is executed by going through all the scenes, and after one scenario is completed, the scenario is executed again from the first scene.

[0017] Examples of scenarios include the following: That is, an example of a scenario is a hotel work scenario. Hotel work includes, for example, front desk clerk, bellboy, housekeeper, driver, restaurant, etc. In this embodiment, each of the avatars of multiple users is assigned one of these roles.

[0018] The front desk clerk scenario includes (1) a scene in which a customer arrives at the lobby and checks in, and (2) a scene in which a customer checks out.

[0019] The bellboy scenario includes (1) a scene in which the customer's car is carried to the parking lot, (2) a scene in which the customer's luggage is carried to the front desk, and (3) a scene in which the customer's luggage is carried to the guest room. The housekeeper scenario includes (1) a scene in which the guest room is cleaned after checkout, and (2) a scene in which the guest room is made up.

[0020] The driver's scenarios include (1) a scene where a customer is picked up from the station to the hotel, (2) a scene where a customer is taken from the hotel to the station, (3) a scene where sheets and towels (hereinafter referred to as linen) are transported to the laundry, and (4) a scene where linen is transported from the laundry to the hotel.

[0021] The restaurant scenario includes (1) a scene of cooking, (2) a scene of setting up a table, (3) a scene of serving food to customers, and (4) a scene of clearing the table.

[0022] While a scenario is set for each role, an overall scenario (hereinafter sometimes referred to as the "full scenario") can also be set by setting multiple users as a team and assigning each team a scenario. In the above example, the overall scenario is composed of the front desk clerk, bellboy, housekeeper, driver, and restaurant. Other examples of the overall scenario include a pizza restaurant (scenario: phone reception, dough crafter, making, delivery, etc.), a hot spring (scenario: receptionist, hall staff, kitchen chef, etc.), an explorer's deserted island life (scenario: navigator, laundry / props / fishing, cook, hunter, etc.), agriculture (scenario: plowing, sowing / watering, maintenance / fertilizer, harvesting / shipping, etc.), and a restaurant (scenario: receptionist, hall staff, kitchen chef, etc.). Below, hotel operations will be described as an example of an overall scenario.

[0023] In the following embodiment, a task management device 100 in which most of the functions of a task management system are integrated into a single housing will be described. However, it is not essential for a task management system to have multiple functions integrated into a single housing; for example, the components of the task management system may be distributed across multiple housings. Furthermore, some of the functions of the task management system may be realized by the cloud (cloud computing) or the like.

[0024] 1, the entire system including the task management device 100 comprises a data input unit 3, the task management device 100, and a display device 4. The data input unit 3, the task management device 100, and the display device 4 are connected to each other so as to be able to communicate with each other via wire or wirelessly.

[0025] An example of a task performed by a user is a process in a product production line. On a production line, multiple users (workers) each perform different tasks. In addition, multiple users belonging to a single production line can form a single team.

[0026] One operation includes multiple tasks. For example, if one user is a worker who assembles one part, that is, if the worker assembles one part and places it on a conveyor to be sent to the next user, one task is completed when the part is assembled and then placed on the conveyor.

[0027] As another example, if a user is a worker who cuts vegetables such as cabbage, that is, when the user is cutting one vegetable, one task is considered to be completed when the user has finished cutting one vegetable.

[0028] The multiple tasks may involve repeating one task or sequentially performing different tasks. When one task is completed, the data is input into the task management device 100 by the data input unit 3. (Data Input Unit 3)

[0029] The data input unit 3 inputs information indicating that a task has been completed by the user to the task management device 100 for each task. For example, the data input unit 3 detects a deliverable generated by completing one task and inputs the completion number "1" to the task management device 100. In this case, the data input unit 3 may be a sensor attached to a conveyor that moves the deliverables. Examples of the sensor include a non-contact sensor such as a photoelectric sensor installed so as to intersect with the conveyor's transport direction, a contact sensor such as a pressure-sensitive sensor, a camera, an infrared sensor, etc.

[0030] The data input unit 3 is not limited to inputting the completion number "1" when one product is detected by the sensor. For example, if multiple products are produced in one task, the completion number "1" may be input when all of the multiple products are detected. Also, for example, in the case of the task of "cutting vegetables," the cut vegetables are the products, and the completion number "1" may be input when the cut vegetables exceed a predetermined weight.

[0031] The data input unit 3 may also determine the degree of completion of the work product and input a completion number of "1" when it is determined that the product is complete. This makes it possible to avoid inputting defective products as the completion number. The degree of completion may be determined automatically by a system function or by a worker in the next process on the production line.

[0032] The data input unit 3 does not have to automatically detect task completion using a sensor. The data input unit 3 may be, for example, an input device that allows a worker or manager to input that a task has been completed. Examples of input devices include a mouse, keyboard, microphone, and touch panel. For tasks that do not generate deliverables, an input device is preferably used as the data input unit 3. Data indicating that the task has been completed, input by the data input unit 3, is transmitted from the data input unit 3 to the task management device 100. (Task management device 100)

[0033] The task management device 100 can execute graphics and other processing based on information transmitted from the data input unit 3 and display the results on the display device 4. The task management device 100 includes, for example, a personal computer or a server computer. That is, the task management device 100 includes a computer system having one or more processors and memory. At least some of the functions of the task management device 100 are realized when the processor of the computer system executes a program stored in the memory of the computer system. The program may be stored in memory, provided via a telecommunications line such as the Internet, or provided by being recorded on a non-transitory recording medium such as a memory card.

[0034] 1, the task management device 100 includes a processing unit 1 that executes the processes of the task management device 100, and a storage unit 2. The processing unit 1 is realized by a processor that executes various processes in accordance with programs stored in storage. Examples of the processor include a CPU (Central Processing Unit), an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), and a microprocessor.

[0035] The storage unit 2 stores information handled by the task management device 100. The storage unit 2 is realized by, for example, a read-only memory (ROM), a random access memory (RAM), an electrically erasable programmable read-only memory (EEPROM), etc. (Processing Unit 1)

[0036] The processing unit 1 includes a reception unit 11, a scenario progression unit 12, an event generation unit 13, a calculation unit 14, a title determination unit 15, and a display unit 16. The reception unit 11, the scenario progression unit 12, the event generation unit 13, the calculation unit 14, the title determination unit 15, and the display unit 16 merely represent functions realized by the task management device 100 and do not necessarily represent actual configurations. (Reception unit 11)

[0037] The reception unit 11 receives information that one task has been completed, which is sent from the data input unit 3. When the reception unit 11 receives information that one task has been completed from the data input unit 3, it associates the user name with the information that one task has been completed and outputs the information to the scenario progression unit 12. This makes it possible to distinguish which user has completed the input information on task completion. The information received by the reception unit 11 is output to the scenario progression unit 12. (Scenario progression unit 12)

[0038] The scenario progression unit 12 causes the avatars of multiple users to progress scene by scene according to the scenario assigned to each avatar. When information that one task has been completed is input from the reception unit 11, a command is output to the display unit 16 to display the corresponding avatar moving according to one scene.

[0039] After progressing the first scene, the scenario progression unit 12 stores this, and when information indicating the completion of the next task is input, the scenario progression unit 12 progresses the second scene. In this manner, the scenario progression unit 12 progresses multiple scenes in order. Furthermore, when the scenario progression unit 12 has finished progressing the final scene of multiple scenes in a scenario assigned to the user's avatar, and information indicating the completion of the next task is input, the scenario progression unit 12 progresses the first scene of the scenario.

[0040] Scenarios assigned to avatars are stored in advance in the storage unit 2. The assignment of avatars to scenarios is preferably performed, for example, by initial setting. As described above, scenarios contain different numbers of scenes depending on the scenario, so it is preferable to assign scenarios according to the user's work, skill level, etc. This makes it possible to adjust the difficulty of completing a scenario for each user. (Event generation unit 13)

[0041] The event generation unit 13 generates a specific event randomly or when a predetermined condition is satisfied. The event generated by the event generation unit 13 may be executed by interrupting a scene being executed by the scenario progression unit 12, or may be executed after the scene. In other words, the event generation unit 13 can execute a specific effect regardless of the scene executed by the scenario progression unit 12. As shown in FIG. 2A , the event generation unit 13 according to this embodiment includes a point-adding scene generation unit 131 and a point-deducting scene generation unit 132.

[0042] The point-adding scene generating unit 131 generates a scene (point-adding scene) in which a customer gives a point-adding evaluation to the avatar while the scenario is in progress. Examples of scenes generated by the point-adding scene generating unit 131 include a scene in which a customer gives a tip, a scene in which the owner gives a bonus, etc. The point-adding scene generating unit 131 may also generate a scene that displays a score or positive points regardless of the content of the scenario. Hereinafter, point-adding evaluations such as chips, scores, and points will be collectively referred to as "point-adding points."

[0043] The bonus points may be changed randomly for each occurrence, may be a fixed number, or may be linked to the number of defective products in the deliverables (for example, the bonus points may be increased if there are few defective products). The conditions for generating a bonus scene are not particularly limited. For example, the event may be generated when the time required for one task is shorter than a fixed time, or when there are few defective products in the deliverables, or may be generated at a specific rate (for example, once every five tasks are completed), or may be generated randomly. When a scene is generated by the bonus scene generating unit 131, it is preferable that the corresponding user add a bonus evaluation to the evaluation score described below.

[0044] When a problem occurs in a completed task, the deduction scene generation unit 132 generates a scene in the scenario that will result in a deduction (a deduction scene). Examples of scenes generated by the deduction scene generation unit 132 include, for example, a scene in the case of a front desk clerk where a room is double-booked or a scene in which a customer becomes enraged. For example, for a bellboy, examples include a scene in which luggage is delivered to the wrong address or a scene in which the general manager receives a complaint about the bellboy. For housekeeping, examples include a scene in which a large amount of trash is left in a room or a scene in which a customer posts on social media about an insect infestation in the room. For a driver, examples include a scene in which a traffic violation or accident occurs or a scene in which a fine is paid. For a restaurant, examples include a scene in which a dish is dropped and broken or a small fire occurs. Note that the deduction scene generation unit 132 may generate a scene displaying deductions or negative points regardless of the content of the scenario. Hereinafter, deduction evaluations such as trouble, deductions, and negative points will be collectively referred to as "deduction points."

[0045] The "fault" referred to here means, for example, a fault where the deliverable resulting from the completion of a task by a user does not meet a certain level of quality, or where an error occurs later due to insufficient execution of a task. Information about the fault may be input to the reception unit 11 by the user from the data input unit 3, or may be input to the reception unit 11 by the line manager. When a scene is generated by the point-deducting scene generation unit 132, it is preferable that the relevant user add a point-deducting evaluation to the evaluation score described below. (Calculation unit 14)

[0046] The calculation unit 14 calculates the evaluation points of each user and team. As shown in FIG. 2A , the calculation unit 14 includes a user evaluation point calculation unit 141 that calculates the evaluation point of each user, and a team evaluation point calculation unit 142 that calculates the evaluation point of the team.

[0047] The user evaluation point calculation unit 141 calculates the user's evaluation point by tallying the number of completed tasks by each user. The user evaluation point calculation unit 141 can also calculate the number of times a scenario assigned to each user's avatar has been achieved from the number of completed tasks. It is preferable that the user evaluation point calculation unit 141 also adds the number of added points generated by the added point scene generation unit 131. On the other hand, as described above, when a scene generated by the demerit scene generation unit 132 is generated, it is preferable to deduct demerit points from the evaluation point. In this way, it is possible to obtain the evaluation point for each user.

[0048] The team evaluation point calculation unit 142 can calculate the team evaluation points based on the evaluation points of the users belonging to the team. It is preferable that the team evaluation point calculation unit 142 calculates the evaluation points based on the number of times all scenarios have been achieved and the number of times each user has achieved a scenario.

[0049] The number of times all scenarios have been completed is the number of times all scenarios have been completed. Since it is expected that a reward will be received from one customer when all scenarios are completed, the number of times all scenarios have been completed can be evaluated as the hotel's reward. When each of the front desk clerk, bellboy, housekeeping, driver, and restaurant staff completes one scenario, all scenarios are completed once. In other words, the number of times all scenarios have been completed is the same as the number of times the fewest scenarios have been completed among all users belonging to a team. Since it is expected that the evaluation of each role will lead to the team's evaluation, it is preferable that the number of times each user has completed a scenario be added to the team evaluation points. (Title determination unit 15)

[0050] The title determination unit 15 determines a title based on the team evaluation points and assigns the title to the team. The memory unit 2 stores a determination table used when determining a title. The determination table associates required points, which are the threshold for the team evaluation points, with titles. The title determination unit 15 refers to the determination table and determines a title based on the team evaluation points. Examples of titles include "first-class hotel," "second-class hotel," and "third-class hotel," but these are merely examples and are not particularly limited.

[0051] The display unit 16 obtains graphics of each avatar progressing through a scene in accordance with instructions from the scenario progression unit 12, and displays these on the display device 4. The display unit 16 also obtains graphics in accordance with instructions from the calculation unit 14, the event generation unit 13, and the title determination unit 15, and displays these on the display device 4. It is preferable that the graphics are stored in advance in the storage unit 2.

[0052] An avatar is set for each user. Examples of avatars include characters resembling people, animals, or workers, plants, machines, and imaginary characters (e.g., dragons, unicorns, etc.). The avatar displayed by the display unit 16 may be an avatar selected by the user, or the same character may be displayed for all users.

[0053] The display unit 16 preferably displays the progress of the scenario by the avatar in real time while the user is performing the task. In this case, when information for one task is input, the avatar progresses through one scene, but if the avatar moves too quickly, it will stop moving until the signal for the next task is input. To prevent this, it is preferable to set the avatar to move slowly. It is preferable that the avatar's movement can be adjusted as needed.

[0054] It is preferable that the display unit 16 displays the user evaluation and team evaluation obtained by the calculation unit 14, and the title determined by the title determination unit 15, at the end of the day's work.

[0055] Furthermore, it is preferable that the display unit 16 displays the number of times a scenario has been completed without displaying the number of tasks completed. This prevents the user from knowing the number of scenes included in the scenario, making it difficult to compare the actual number of tasks completed with other users. (Display device 4)

[0056] The display screen of the display device 4 is controlled by the display unit 16 of the task management device 100. The display screen of the display device 4 is displayed based on information output from the display unit 16. The display device 4 may be a large display installed in a location where multiple workers can see it at all times, or a small display installed at each worker's work location. Furthermore, a terminal owned by each worker may be used as the display device 4. Examples of the display device 4 include a monitor, a display, a touch display, a projector, a smartphone, a tablet terminal, a laptop PC, VR goggles, and a head-mounted display. (Flowchart) Next, an example of the operation of the task management device 100 according to this embodiment will be described based on a flowchart.

[0057] As shown in FIG. 3, the task management method using the task management device 100 sequentially executes a reception step (ST1, 2), a scenario progression step (ST3, 4), and an evaluation step (ST5 to ST9).

[0058] In the receiving step, after the start of production, the completion of one task by the user is received (ST1, ST2). When the user completes one task, information indicating the completion of one task is input from the data input unit 3 to the receiving unit 11.

[0059] Next, a scenario progression step is executed. In the scenario progression step, based on the information that one task has been completed, the user's avatar progresses through one scene (ST3). At this time, as shown in FIG. 4, when the information that one task has been completed is input to the reception unit 11, the scenario progression unit 12 determines whether all scenes included in one scenario have progressed (ST31), and if not, advances the scene following the previously completed scene (ST32). If all scenes have progressed, advances the scenario from the first scene (ST33). After this, as shown in FIG. 3, it is confirmed whether the user's work is continuing (ST4), and if work is continuing, step 2 is executed again.

[0060] On the other hand, when the work is completed, an evaluation step is executed. In the evaluation step, the number of tasks completed by each user is tallied, and the number of times each user has achieved each scenario is tallied (ST5). Next, the number of times all scenarios have been achieved is calculated from the number of times each user in the team has achieved each scenario (ST6).

[0061] Furthermore, positive evaluation points are added to each user from the added points generated by the point-adding scene generation unit 131, and negative evaluation points are added from the demerit points generated by the demerit scene generation unit 132. Then, a team evaluation point (total evaluation point) is calculated for the team (ST7, 8). After that, a title is determined based on the team evaluation point and displayed on the display device 4 (ST9). <Modification>

[0062] The above embodiment is merely one of various embodiments of the present invention. The embodiment can be modified in various ways depending on the design, etc., as long as the object of the present invention can be achieved. Modifications of the embodiment are listed below. The modifications described below can be applied in appropriate combinations.

[0063] In the above embodiment, one scene was described as, for example, "a scene of welcoming a guest from the station to the hotel." However, one scene may also be a scene of traveling 100 meters from the station to the hotel. The scene may progress by traveling 100 meters each time a task is completed, and the character may arrive at the hotel from the station upon completion of multiple tasks. In other words, "a scene of welcoming a guest from the station to the hotel" may be considered one scenario, and the scenes of traveling 100 meters from the station to the hotel may be considered multiple scenes. This makes it easier to set the number of scenes included in one scenario.

[0064] Multiple teams can be registered, and the teams may compete with each other based on team evaluation points. Match results may be displayed using team evaluation points and the evaluation points of each user. This is expected to strengthen the unity of users on each team.

[0065] The data input unit 3 may evaluate the quality of the deliverable, obtain an evaluation score from the quality, and output data related to the evaluation score to the receiving unit 11. The data input unit 3 may receive a task completion signal when the evaluation score is equal to or greater than a reference score (e.g., 80 points), and may not receive the task completion signal when the evaluation score is less than the reference score. When the evaluation score is 100 points, the data input unit 3 may output a signal to the event generating unit 13, and the score-adding scene generating unit 131 may display a score-adding scene. The data input unit 3 may be a device with a camera or a system with a camera and a control device. The camera-equipped device includes a controller. The control unit of the controller or the control device evaluates the quality of the deliverable by image processing image data of the deliverable captured by the camera. The evaluation of the quality may be performed by AI or image analysis software. Furthermore, the evaluation of the quality may be performed by a worker other than the user.

[0066] In the above embodiment, when the last scene in one scenario ends, the first scene in the same scenario is displayed, but for example, when the last scene in one scenario ends, the first scene of another scenario may be displayed. Also, one scenario may be composed of so many scenes that it is impossible to complete it in one day.

[0067] The task management system according to the above embodiment is used for work on a production line as a task performed by a user. However, the task is not limited to a production line, and can also be applied to training, rehabilitation, and the like. Examples of training tasks include muscle training for athletes and muscle and environmental training for astronauts. Examples of rehabilitation tasks include training in basic movement movements and training for functional recovery. In other words, the term "task" in this specification includes training and training.

[0068] In the above embodiment, the number of times all scenarios have been completed is the number of times the scenarios of the users belonging to the team have been completed the least, but the completion of one scene by one user may trigger the progression of a scene by a second user. For example, the scene in which the front desk clerk checks in may not proceed until the scene in which the driver welcomes the guests from the station to the hotel is completed.

[0069] In the above embodiment, the task management device 100 includes, for example, a personal computer or a server computer, and includes a computer system having one or more processors and memories, but the task management device 100 may also be, for example, a smartphone, a mobile phone, a tablet terminal, a game console, etc.

[0070] As described above, the task management system according to the first aspect includes a receiving unit 11 that receives notification that one of multiple tasks included in one work performed by each user has been completed, and a scenario progression unit 12 that causes avatars of multiple users to progress according to a scenario assigned to each avatar. Each time a task is completed, the scenario progression unit 12 causes each avatar to progress sequentially through multiple scenes included in one scenario. The number of scenes included in one scenario is set to a different number depending on the user.

[0071] According to this aspect, by completing a task, a user can progress through a scenario with an avatar, scene by scene. This not only increases motivation for completing tasks, but also increases the number of scenes included in a scenario, which is set to vary for each user. This allows the level of difficulty of the task to be reflected in the number of scenes, thereby enabling the user to set the difficulty of completing the scenario. As a result, even a user who only performs simple repetitive tasks can be motivated and improve their concentration on the task, thereby increasing the user's work speed and improving productivity. The task management system according to the second aspect, as compared to the first aspect, further includes a calculation unit 14 that tallies the number of completed tasks for each user. According to this aspect, each user and the system administrator can grasp the number of completed tasks for each user.

[0072] In the task management system according to the third aspect, in the second aspect, the calculation unit 14 calculates the number of times a scenario has been completed according to the total number of completed tasks. The task management system further includes a display unit 16 that causes the display device 4 to display the number of times a scenario has been completed obtained by the calculation unit 14, without displaying the number of completed tasks. According to this aspect, the number of scenes included in a scenario is not known to the user, making it difficult to compare the actual number of completed tasks with other users.

[0073] In a task management system according to a fourth aspect, in any one of the first to third aspects, the reception unit 11 is configured to be able to receive information that a problem has occurred in the completed task. The task management system further includes an event generation unit 13 that executes a specific performance regardless of the scene in progress when the reception unit 11 receives information that a problem has occurred. According to this aspect, the occurrence of problems can be suppressed in the task management system.

[0074] In a task management system according to a fifth aspect, in any one of the first to fourth aspects, the receiving unit 11 is configured to be able to receive a notification that a problem has occurred in the completed task. When the receiving unit 11 receives a notification that a problem has occurred, the task management system adds a negative evaluation to the user's evaluation. According to this aspect, the occurrence of problems can be suppressed in the task management system.

[0075] In a task management system according to a sixth aspect, in any one of the first to fifth aspects, a team is made up of multiple users. A calculation unit 14 calculates the number of times a scenario has been completed for each user according to the total number of completed tasks. The number of times a scenario has been completed by the user in the team who has completed that scenario the fewest times is set as the total number of times all scenarios have been completed. The task management system further includes a display unit 16 that displays an evaluation of the team based on the number of times all scenarios have been completed.

[0076] According to this aspect, each team can compete for the highest rating, which is expected to improve the sense of unity among the users included in the team and also to increase the motivation of each user.

[0077] A task management method according to a seventh aspect includes a receiving step of receiving that one of multiple tasks included in one work performed by each user has been completed, and a scenario progression step of causing avatars of multiple users to progress according to a scenario assigned to each avatar. The scenario progression step causes each avatar to progress sequentially through multiple scenes included in one scenario each time a task is completed. The number of scenes included in one scenario is set to a different number depending on the user.

[0078] According to this aspect, even a user who only performs work such as repeating simple tasks can be motivated, improve their concentration on the work, increase the speed of the work, and expect to improve their productivity. A program according to an eighth aspect is a program for causing at least one processor to execute each step of the task management method of the seventh aspect. According to this aspect, the task management method can be realized by executing the program.

[0079] 100 Task management device (task management system) 1 Processing unit 11 Reception unit 12 Scenario progression unit 13 Event generation unit 131 Point-adding scene generation unit 132 Point-deducting scene generation unit 14 Calculation unit 141 User evaluation point calculation unit 142 Team evaluation point calculation unit 15 Title determination unit 16 Display unit 2 Storage unit 3 Data input unit 4 Display device

Claims

1. A task management system comprising: a data input unit for inputting information that a task has been completed by a user performing an operation; a reception unit for receiving from the data input unit information that one of multiple tasks included in one operation performed by each user has been completed; and a scenario progression unit for progressing avatars of multiple users according to a scenario assigned to each avatar, wherein each time a task is completed, the scenario progression unit progresses each avatar in sequence through multiple scenes included in one scenario, and the number of scenes included in one scenario is set to a different number depending on the user.

2. The task management system according to claim 1, further comprising a calculation unit that tallies the number of completed tasks for each user.

3. The task management system according to claim 2, further comprising a display unit that calculates the number of times a scenario has been completed according to the number of completed tasks that has been collected, and that displays the number of times the scenario has been completed obtained by the calculation unit on a display device without displaying the number of completed tasks.

4. A task management system as described in any one of claims 1 to 3, wherein the reception unit is configured to be able to receive information that a problem has occurred in a completed task, and further comprising an event generation unit that, when the reception unit receives information that a problem has occurred, executes a specific performance regardless of the scene in progress.

5. A task management system as described in any one of claims 1 to 3, wherein the reception unit is configured to be able to receive information that a problem has occurred in a completed task, and when the reception unit receives information that a problem has occurred, a negative evaluation is added to the user's evaluation.

6. A task management system as described in claim 2, further comprising: a plurality of users forming a team; the calculation unit calculating the number of times a scenario is completed for each user according to the total number of tasks completed; the number of times a scenario is completed for a user in the team who has completed the scenario the fewest times is regarded as the total number of scenarios completed, which is the number of times the entire scenario is completed; and a display unit displaying an evaluation of the team based on the total number of scenarios completed.

7. A task management method executed by a task management system, comprising: a data input step of inputting information that a task has been completed by a user performing an operation; a reception step of receiving from the data input unit that one of multiple tasks included in one operation performed by each user has been completed; and a scenario progression step of causing avatars of multiple users to progress in accordance with a scenario assigned to each avatar, wherein the scenario progression step causes each avatar to progress in sequence through multiple scenes included in one scenario each time a task is completed, and the number of scenes included in one scenario is set to a different number depending on the user.

8. A program for causing at least one processor to execute each step of the task management method according to claim 7.

Images