Business report system, business report method, and business report program

The business reporting system addresses the challenge of emotional misinterpretation in reports by integrating emotional data and positive feedback, enhancing understanding and motivation through accurate emotional representation.

JP7587379B2Active Publication Date: 2024-11-20MIRAI CONSULTING CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2020157655
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-09-18
Publication Date
2024-11-20
Estimated Expiration
2040-09-18

AI Technical Summary

Technical Problem

Business reports often fail to convey the reporter's emotions, making it difficult for the reportee to accurately judge the reporter's feelings towards the reported matter, leading to potential misinterpretation.

Method used

A business reporting system that integrates emotional data input alongside report data, allowing the reportee to view the reporter's feelings through icons or labels, and receives positive feedback comments, enhancing understanding and motivation.

Benefits of technology

Enables the reportee to accurately read the reporter's feelings, fostering trust and motivation by providing a more accurate understanding of the reporter's emotions and work suitability, while ensuring positive feedback.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007587379000001
    Figure 0007587379000001
  • Figure 0007587379000002
    Figure 0007587379000002
  • Figure 0007587379000003
    Figure 0007587379000003
Patent Text Reader

Abstract

To allow a reportee to read emotions of a reporter on a business from a business report of the reporter.SOLUTION: A first input unit receives input of first report data on the situation of a business and first emotion data indicative of emotions on the situation of the business from a reporter. A first presentation unit presents the first report data and the first emotion data to a reportee associated with the reporter.SELECTED DRAWING: Figure 12
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a business report system, a business report method, and a business report program. [Background technology]

[0002] Patent Document 1 discloses a technique for detecting changes in employee motivation based on daily work reports. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2007-265134 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in business reports, the reporter's emotions may not be apparent, and the matter to be reported may be described matter-of-factly. Therefore, it may be difficult to read the reporter's emotions from the wording of the business report alone. In other words, when reporting on the same matter, it may be unclear whether the reporter has a positive or negative view of the matter. If the reporter's emotions are misread, the person receiving the report may not be able to properly judge the reporter's work.

[0005] An object of the present disclosure is to provide a work reporting system, a work reporting method, and a work reporting program that are capable of reading the reporter's emotions related to the work in the work report. [Means for solving the problem]

[0006] According to one aspect of the present invention, a business reporting system includes a first input unit that accepts input of first report data about a business-related situation and first emotion data indicating emotions about the business-related situation from a reporter, and a first presentation unit that presents the first report data and the first emotion data to a reportee associated with the reporter. Effect of the Invention

[0007] According to the above aspect, the report recipient can read the reporter's feelings regarding the work from the work report of the reporter. [Brief description of the drawings]

[0008] [Figure 1] 1 is a schematic diagram showing a configuration of a business report system according to a first embodiment. [Diagram 2] 1 is a schematic block diagram showing a configuration of a business report server according to a first embodiment. [Diagram 3] 4 is a flowchart showing a method for inputting daily report data according to the first embodiment. [Figure 4] FIG. 4 is a diagram showing an example of a daily report page according to the first embodiment. [Diagram 5] FIG. 13 is a diagram illustrating an example of a man-hour input page according to the first embodiment. [Figure 6] FIG. 4 is a diagram showing an example of a daily report input page according to the first embodiment. [Figure 7] 5 is a flowchart showing a method for inputting weekly report data according to the first embodiment. [Figure 8] FIG. 11 is a diagram showing an example of a weekly report page according to the first embodiment. [Figure 9] FIG. 13 is a diagram showing an example of a weekly report editing page according to the first embodiment. [Figure 10] 5 is a flowchart showing a method for approving weekly report data by a first approver in the first embodiment. [Figure 11] FIG. 13 is a diagram illustrating an example of a waiting for approval list page according to the first embodiment. [Figure 12]FIG. 11 is a diagram showing an example of a weekly report viewing page according to the first embodiment. [Figure 13] 5 is a flowchart showing a method for a manager to receive weekly report data in the first embodiment. [Figure 14] FIG. 13 is a diagram showing an example of a report list page according to the first embodiment. [Figure 15] FIG. 1 is a schematic block diagram illustrating a configuration of a computer according to at least one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] First Embodiment <Configuration of Business Report System 1> Hereinafter, the embodiments will be described in detail with reference to the drawings. FIG. 1 is a schematic diagram showing the configuration of a business report system 1 according to a first embodiment. The business report system 1 accepts business reports from reporters who are employees of a company, etc., and presents the business reports to reportees who are the superiors of the reporters, etc. The business report system 1 according to the first embodiment accepts the reporter's feelings about the business together with the business report, and presents them to the reportee. The business report system 1 also presents feedback comments about the business report by the reportee to the reporter.

[0010] The business report system 1 comprises a business report server 100 and multiple user terminals 200. The business report server 100 manages business reports by reporters and feedback comments by report recipients. The user terminal 200 is a terminal operated by a user of the business report system 1. The business report server 100 and the user terminal 200 are connected to each other via a network. The user terminal 200 is a PC (Personal Computer) and accesses the business report server 100 using a web browser application or the like.

[0011] 2 is a schematic block diagram showing the configuration of the business report server 100 according to the first embodiment. The business report server 100 includes an authentication unit 101, a user memory unit 102, a daily report input unit 103, a weekly report input unit 104, a feedback input unit 105, a daily report memory unit 106, a weekly report memory unit 107, a feedback memory unit 108, and a display control unit 109.

[0012] The authentication unit 101 receives input of authentication information such as an ID and a password from a user terminal 200 connected via a network, and refers to a user storage unit 102 to authenticate the user.

[0013] The user storage unit 102 stores an authentication table and a relationship table. The authentication table holds a user's ID, password, name, and job title in association with each other. The relationship table holds a reporter's ID (reporter ID) and a first approver (reportee ID) who is a report recipient who first accepts (approves) and acknowledges (acknowledges) the report of the reporter in association with each other. The relationship between a reporter and a report recipient is not necessarily limited to one-to-one. A report by one reporter may be approved by one of multiple first approvers, or one reporter may be the first approver for multiple reporters. In addition, when a report is approved by the first approver, the report is presented to a user who belongs to a certain job title or higher. This allows the report to be accepted by multiple users who belong to a certain job title or higher.

[0014] The daily report input unit 103 accepts input of daily report data from the reporter. A daily report is a report on the status of work on a day. The daily report data includes a date, a project name, man-hours expressed in hours, report data expressed in character strings, and emotion data expressed in icons. Man-hours indicate the time spent on the project on a target day. The emotion data in the daily report is selected from "exceeds expectations," "meets expectations," "below expectations," and "significantly less than expectations." Note that the emotion data may be label data expressed in another format, such as a character string, instead of an icon.

[0015] The weekly report input unit 104 accepts input of weekly report data from a reporter. The weekly report is a report on the status of work during the week. The weekly report data includes a period, report data represented by a character string, and emotion data represented by an icon. The emotion data in the weekly report is selected from among "fulfilled," "normal," "busy," and "distressed."

[0016] The feedback input unit 105 accepts input of feedback data for a weekly report from the report recipient. The feedback data includes comment data represented by a character string and acceptance data represented by an icon. One of the acceptance data items is selected from "FANTASTIC", "GREAT", "NICE" and "CHECKED". The options for the acceptance data include only positive content. Note that the acceptance data may be label data represented in another format, such as a character string, instead of an icon.

[0017] The daily report storage unit 106 stores the daily report ID and the daily report data in association with the reporter ID. The weekly report storage unit 107 stores the weekly report ID and the weekly report data in association with the reporter ID. The feedback storage unit 108 stores the report recipient ID and the feedback data in association with the weekly report ID. The display control unit 109 generates a screen to be displayed on the user terminal 200 and outputs it to the user terminal 200 .

[0018] <<Operation of Business Report System 1>> When a user operates the user terminal 200 to access the business report server 100, the display control unit 109 of the business report server 100 generates a login screen including an input form for authentication information and transmits it to the user terminal 200. When the user terminal 200 receives the login screen, it displays the login screen on the display. When the user inputs the authentication information according to the login screen, the user terminal 200 transmits the authentication information to the business report server 100.

[0019] When the authentication unit 101 of the business report server 100 receives authentication information from the user terminal 200, it compares the authentication information with the authentication table in the user storage unit 102 and performs authentication processing for the user. The display control unit 109 generates a portal screen for the authenticated user and transmits it to the user terminal 200. The portal screen includes at least a link to a daily report page and a link to a weekly report page. If the user is a report recipient, it also includes a link to a waiting approval list page. If the user holds a certain position or higher, it also includes a link to a report list page.

[0020] <<Entry of daily reports by reporters>> FIG. 3 is a flowchart showing a method for inputting daily report data according to the first embodiment. FIG. 4 is a diagram showing an example of a daily report page according to the first embodiment. When a user selects a link to a daily report page using the user terminal 200, the user terminal 200 transmits a request for the daily report page to the business report server 100. When the display control unit 109 of the business report server 100 receives the request for the daily report page (step S20), it acquires attendance data related to the user from an attendance database (not shown) (step S21). The display control unit 109 also refers to the daily report storage unit 106 to acquire the daily report data related to the user (step S22). The display control unit 109 generates a daily report page based on the data acquired in steps S21 and S22, and transmits it to the user terminal 200 (step S23). As shown in FIG. 4, the daily report page includes a list in which the most recent date, attendance data related to the date, and a flag indicating whether or not there is a daily report for the date are associated with each other. Each line of the list is provided with a link to a man-hour input page for the date related to the line.

[0021] FIG. 5 is a diagram illustrating an example of a man-hour input page according to the first embodiment. When a user selects a link to a man-hour input page for a certain date from the daily report page using the user terminal 200, the user terminal 200 transmits a request for the man-hour input page to the business report server 100. When the display control unit 109 of the business report server 100 receives the request for the man-hour input page (step S24), it generates a man-hour input page for the selected date and transmits it to the user terminal 200 (step S25). As shown in FIG. 5, the man-hour input page includes an input field for the name of the project, an input field for the man-hours spent on the project, a link icon for the daily report for the project, a time display of the difference between the total man-hours input and the working hours related to the attendance data, and an application button. When daily report data has already been recorded in the daily report storage unit 106, the display control unit 109 displays information indicated by the daily report data in each input field.

[0022] FIG. 6 is a diagram showing an example of a daily report input page according to the first embodiment. When the user inputs the name of the project related to the target date and presses the link icon for daily report, the user terminal 200 transmits a request for a daily report input page to the business report server 100 (step S26: daily report). The display control unit 109 generates a daily report input page for the project related to the selected link icon (step S27). As shown in FIG. 6, the daily report input page includes a display field for the date, a display field for the name of the project, an input field for emotion data for the business related to the project, an input field for report data for the business, a delete button, and a save button. If daily report data has already been recorded in the daily report storage unit 106, the display control unit 109 displays information indicated by the daily report data in each input field. In the emotion data input field, emotion data options are displayed as icons.

[0023] When the user presses the save button using the user terminal 200 (step S28: save), the display control unit 109 of the business report server 100 closes the daily report input page and returns the process to step S25 (step S29). Note that even if the daily report input page is closed, the business report server 100 retains the emotion data and report data inputted to the daily report input page. On the other hand, when the user presses the delete button using the user terminal 200, the display control unit 109 of the business report server 100 closes the daily report input page and returns the process to step S25 (step S30). At this time, the business report server 100 discards the emotion data and report data inputted to the daily report input page.

[0024] When the user inputs the name and man-hours of the project related to the target date and presses the "Apply" button (step S26: Apply), the daily report input unit 103 associates the user ID, date, man-hours, and the emotion data and report data stored in step S29 with each project name, and records them in the daily report storage unit 106 (step S31). Then, the display control unit 109 of the business report server 100 closes the man-hours input page (step S32) and ends the process.

[0025] 《Entry and viewing of weekly reports by reporters》 FIG. 7 is a flowchart showing a method for inputting weekly report data according to the first embodiment. FIG. 8 is a diagram showing an example of a weekly report page according to the first embodiment. When a user selects a link to a weekly report page using the user terminal 200, the user terminal 200 transmits a request for the weekly report page to the business report server 100. When the display control unit 109 of the business report server 100 receives the request for the weekly report page (step S40), the display control unit 109 refers to the weekly report storage unit 107 and acquires weekly report data related to the user (step S41). The display control unit 109 generates a weekly report page based on the weekly report data acquired in step S41 and transmits it to the user terminal 200 (step S42). As shown in FIG. 8, the weekly report page includes a list in which a target month, a target period which is each week in the month, the presence or absence of weekly report data for the week, and an edit button for the weekly report data are associated with each other. In the list, a row for a week for which weekly report data is available includes a snippet of the weekly report for the week and a view button. In the list, a row for a week for which weekly report data is not available includes an edit button for the weekly report for the week. The view button and edit button for weekly report data contain links to a weekly report edit page for that week.

[0026] FIG. 9 is a diagram showing an example of a weekly report editing page according to the first embodiment. When a user selects a view button or an edit button for a week from the weekly report page using the user terminal 200, the user terminal 200 transmits a request for the weekly report edit page to the business report server 100. When the display control unit 109 of the business report server 100 receives the request for the weekly report edit page (step S43), it refers to the daily report storage unit 106 and acquires daily report data for the date belonging to the selected week for the user (step S44). The display control unit 109 also refers to the feedback storage unit 108 and acquires feedback data about the weekly report for the selected week for the user (step S45). The display control unit 109 generates a weekly report edit page for the selected week and transmits it to the user terminal 200 (step S46).

[0027] As shown in FIG. 9, the weekly report editing page displays an input field for report data on the status of work in the selected week, a selection button for emotion data indicating emotions about the status of work, a list of daily report data for dates belonging to the selected week, and a list of feedback data. This allows the user to create weekly report data while looking back on his / her own past work content and emotions at that time when editing the weekly report data. The user can also view comments from report recipients on the weekly report data. When the selection button for emotion data shown in FIG. 9 is clicked, the display control unit 109 presents a plurality of emotion data icons in a selectable manner. The user inputs emotion data by selecting one of the presented icons. The weekly report input unit 104 updates the weekly report data stored in the weekly report storage unit 107 every time the report data or emotion data is edited (step S47).

[0028] 《Viewing of weekly reports by the first approver》 FIG. 10 is a flowchart showing a method for approving weekly report data by the first approver in the first embodiment. FIG. 11 is a diagram showing an example of a waiting for approval list page according to the first embodiment. When the user selects a link to the approval waiting list page using the user terminal 200, the user terminal 200 transmits a request for the approval waiting list page to the business report server 100. When the display control unit 109 of the business report server 100 receives the request for the approval waiting list page (step S60), it refers to the relationship table in the user storage unit 102 and identifies the reporter ID associated with the user ID as the first approver. That is, the display control unit 109 identifies the reporter to be approved by the user (step S61). The display control unit 109 refers to the weekly report storage unit 107 and acquires the weekly report data related to the reporter ID identified in step S61 (step S62). The display control unit 109 generates the approval waiting list page based on the weekly report data acquired in step S62 and transmits it to the user terminal 200 (step S63). The approval waiting list page includes a list in which the target month, the reporter's name, the report date, and the data waiting for approval are associated with each other, as shown in FIG. 11. The list may include data awaiting approval other than the weekly report data, such as travel expense reimbursement, holiday application, etc. In the list, a link to the weekly report viewing page is provided in the row showing the weekly report data awaiting approval.

[0029] FIG. 12 is a diagram showing an example of a weekly report viewing page according to the first embodiment. When a user selects one row related to weekly report data from the approval waiting list page using the user terminal 200, the user terminal 200 transmits a request for a weekly report viewing page to the business report server 100. When the display control unit 109 of the business report server 100 receives the request for the weekly report viewing page (step S64), it refers to the daily report storage unit 106 and acquires the daily report data for the date belonging to the selected week related to the reporter ID identified in step S61 (step S65). The display control unit 109 generates a weekly report viewing page for the selected week and transmits it to the user terminal 200 (step S66).

[0030] As shown in FIG. 12, the weekly report viewing page displays report data and emotion data related to the selected weekly report data, a list of daily report data for dates belonging to the selected week, and an input block for feedback data. The input block for feedback data includes an input field for feedback comments, a selection button for acceptance data indicating the acceptance of the reporter's work, and a registration button. This allows the user to read the reporter's emotion related to the report from the emotion data icon while viewing the report data from the reporter. This allows the user to input feedback comments that are more in line with the reporter's emotion. When the selection button for acceptance data shown in FIG. 9 is clicked, the display control unit 109 presents a plurality of icons of acceptance data in a selectable manner. The user inputs acceptance data by selecting one of the presented plurality of icons. The options for acceptance data consist of only positive content. This makes it possible to prevent the motivation of the reporter from being lowered by the feedback data. Note that, at the time of the first viewing by the first approver, feedback data by other users is not registered in the weekly report viewing page. When the registration button is pressed, the weekly report input unit 104 updates the feedback data stored in the feedback storage unit 108 (step S67).

[0031] 《Viewing of weekly reports by officials》 FIG. 13 is a flowchart showing a method for a manager to receive weekly report data in the first embodiment. FIG. 14 is a diagram showing an example of a report list page according to the first embodiment. When a user selects a link to a report list page using the user terminal 200, the user terminal 200 sends a request for the report list page to the business report server 100. When the display control unit 109 of the business report server 100 receives the request for the report list page (step S80), it refers to the feedback storage unit 108 and the weekly report storage unit 107, and acquires weekly report data to which at least one piece of feedback data has been added (step S81). The fact that at least one piece of feedback data has been added to the weekly report data indicates that the weekly report data has been approved by the first approver. In other words, the business report server 100 presents the weekly report data approved by the first approver to the manager.

[0032] The display control unit 109 generates a report list page based on the weekly report data acquired in step S81, and transmits it to the user terminal 200 (step S82). The report list page includes a list that associates the target month, the reporter's name, the target week of the period, and a snippet of weekly report data for the week, as shown in Fig. 14. Each line of the list has a link to a weekly report viewing page.

[0033] When a user selects one row from the report list page using the user terminal 200, the user terminal 200 transmits a request for a weekly report viewing page to the business report server 100. When the display control unit 109 of the business report server 100 receives the request for the weekly report viewing page (step S83), it refers to the daily report storage unit 106, and retrieves the daily report data for the date belonging to the selected week based on the reporter ID of the selected weekly report data (step S84). The display control unit 109 generates a weekly report viewing page for the selected week as shown in FIG. 12, and transmits it to the user terminal 200 (step S85). The weekly report viewing page presented to the manager includes a list of feedback data by other users. When the registration button is pressed, the weekly report input unit 104 updates the feedback data stored in the feedback storage unit 108 (step S86).

[0034] Actions and Effects In this way, the business report system 1 according to the first embodiment accepts input of report data on a business-related situation and emotion data indicating emotion on the business-related situation from the reporter, and presents the report data and emotion data to the report recipient associated with the reporter. This allows the report recipient to read the reporter's emotion on the business in the business report. Furthermore, by recording a combination of the report data and emotion data in chronological order, the business report system 1 can provide the report recipient with material for grasping the reporter's tendency of thinking and the suitability of the business. Furthermore, the above-mentioned report data and emotion data are presented only to the report recipient. This allows the reporter to be expected to express his / her true feelings without worrying about the eyes of other colleagues.

[0035] Furthermore, the business reporting system 1 according to the first embodiment accepts input of daily report data and weekly report data as report data, and presents the daily report data and the weekly report data to the report recipient. This allows the report recipient to confirm the reporter's overall weekly report indicated by the weekly report data and the report on the individual situation for that week. Note that while the business reporting system 1 according to the first embodiment accepts input of weekly report data, the period is not limited to a week, and may be a period separated by a predetermined cycle of two or more days. Note that since it is preferable for the report to be made while the reporter's memory is still fresh, it is preferable for the period to be shorter than one month.

[0036] In addition, the business report system 1 according to the first embodiment presents the reporter with the daily report data for the week when the reporter inputs the weekly report data. This allows the reporter to create the weekly report data while looking back on the events of the week.

[0037] Furthermore, the business report system 1 according to the first embodiment accepts from the report recipient the input of comment data about the weekly report data and acceptance data selected from options consisting of only positive content, and presents the comment data and acceptance data to the reporter. This can increase the motivation of the report recipient to register the weekly report data, and is expected to foster a relationship of trust between the report recipient and the reporter. This also allows the reporter to receive comments that are in tune with the report recipient's feelings, encouraging the reporter to voluntarily create a report.

[0038] Moreover, the business report server 100 according to the first embodiment presents weekly report data to a first approver associated with the reporter, and after approval by the first approver, presents the weekly report data to a user (managerial person) who belongs to a certain position or higher. That is, in the first embodiment, the first approver and the managerial person are report recipients. By presenting the weekly report data to the managerial person after approval by the first approver, the reporter can have the first approver brush up the weekly report data before presenting it to the managerial person. Note that the business report server 100 according to other embodiments may present weekly report data to a plurality of report recipients without approval by the first approver. Furthermore, in other embodiments, report recipients other than the first approver may also be associated with the reporter in the relationship table of the user storage unit 102.

[0039] Other Embodiments Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes are possible. That is, in other embodiments, the order of the above-mentioned processes may be changed as appropriate. Also, some of the processes may be executed in parallel. The business report system 1 according to the embodiment described above is composed of the business report server 100 and the user terminal 200, but may be composed of a single computer. Also, the functions of the business report server 100 may be realized by a plurality of computers.

[0040] Computer Configuration FIG. 13 is a schematic block diagram illustrating a configuration of a computer according to at least one embodiment. The computer 500 includes a processor 501 , a main memory 502 , a storage 503 , and an interface 504 . The above-mentioned business report server 100 and user terminal 200 are implemented in a computer 500. The operations of each of the above-mentioned processing units are stored in the form of a program in a storage 503. The processor 501 reads the program from the storage 503, loads it in the main memory 502, and executes the above-mentioned processing in accordance with the program. The processor 501 also secures a storage area in the main memory 502 corresponding to each of the above-mentioned storage units in accordance with the program. Examples of the processor 501 include a CPU (Central Processing Unit), a GPU (Graphic Processing Unit), and a microprocessor.

[0041] The program may be for realizing a part of the functions to be performed by the computer 500. For example, the program may be for realizing the functions by combining with other programs already stored in the storage or by combining with other programs implemented in other devices. In another embodiment, the computer 500 may include a custom LSI (Large Scale Integrated Circuit) such as a PLD (Programmable Logic Device) in addition to the above configuration or instead of the above configuration. Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), and FPGA (Field Programmable Gate Array). In this case, some or all of the functions to be realized by the processor 501 may be realized by the integrated circuit. Such an integrated circuit is also included in an example of a processor.

[0042] Examples of storage 503 include a magnetic disk, a magneto-optical disk, an optical disk, a semiconductor memory, etc. Storage 503 may be an internal medium directly connected to the bus of computer 500, or an external medium connected to computer 500 via interface 504 or a communication line. In addition, when this program is distributed to computer 500 via a communication line, computer 500 that receives the program may load the program in main memory 502 and execute the above-mentioned process. In at least one embodiment, storage 503 is a non-transitory tangible storage medium.

[0043] The program may be for realizing part of the above-mentioned functions. Furthermore, the program may be a so-called difference file (difference program) that realizes the above-mentioned functions in combination with another program already stored in the storage 503. [Explanation of symbols]

[0044] 1...Business report system 100...Business report server 101...Authentication unit 102...User memory unit 103...Daily report input unit 104...Weekly report input unit 105...Feedback input unit 106...Daily report memory unit 107...Weekly report memory unit 108...Feedback memory unit 109...Display control unit 200...User terminal 500...Computer 501...Processor 502...Main memory 503...Storage 504...Interface

Claims

1. a first input unit that receives inputs of first report data on a work-related situation during a period that is divided into a predetermined cycle of two days or more and less than one month from a reporter, and first emotion data indicating an emotion regarding the work-related situation; a second input unit that receives an input of second report data on business performance on a day from the reporter and records the second report data in a storage unit in association with the day; a second presentation unit that presents to the reporter, at the time of inputting the first report data and the first emotion data, the second report data associated with a day within the period; a first presentation unit that presents the first report data, the first emotion data, and the second report data associated with days within the period to a plurality of report recipients associated with the reporter; a third input unit that receives, from the plurality of report recipients, input of comment data regarding the first report data to the reporter and acceptance data indicating acceptance of the first report data selected from options consisting of only positive content; a third presentation unit that presents the comment data and the acceptance data to the reporter; Equipped with The first presentation unit presents, to each of the plurality of report recipients, the first report data, the first emotion data, and the second report data, as well as the comment data and the acceptance data by other report recipients. Business reporting system.

2. The second report data includes the number of tasks related to the work on the day. The business report system according to claim 1 .

3. The second report data includes information indicating a type of project and a man-hour related to the project on the date. The business report system according to claim 2 .

4. The period is separated by one-week periods. The business report system according to any one of claims 1 to 3.

5. A plurality of report recipients including a first report recipient are associated with the reporter; The first presentation unit presents the first report data and the first emotion data to the first report recipient, and after approval by the first report recipient, presents the first report data and the first emotion data to another report recipient.

5. A business report system according to claim 1.

6. A step of receiving, from a reporter, first report data on a work-related situation during a period that is divided into a predetermined cycle of two days or more and less than one month, and first emotion data indicating an emotion regarding the work-related situation; a step of the computer receiving an input of second report data on a performance related to the business on a day from the reporter and recording the second report data in a storage unit in association with the day; a step of the computer presenting the second report data associated with a day within the period to the reporter upon input of the first report data and the first emotion data; presenting the first report data and the first emotion data, and the second report data associated with days within the time period to a plurality of reportees associated with the reporter; The computer receives, from the plurality of report recipients, input of comment data about the first report data and acceptance data indicating acceptance of the first report data selected from among options consisting of only positive content; the computer presents the comment data and the acceptance data to the reporter; Equipped with In the step of presenting the first report data, the first emotion data, and the second report data to the plurality of report recipients, the comment data and the acceptance data by the other report recipients are further presented to each of the plurality of report recipients. Business reporting method.

7. A computer comprising: a first input unit that receives inputs of first report data on a work-related situation during a period that is divided into a predetermined cycle of two days or more and less than one month, and first emotion data indicating an emotion regarding the work-related situation, from a reporter; a second input unit that receives input of second report data on business performance on a day from the reporter and records the second report data in a storage unit in association with the day; a second presentation unit that presents to the reporter, at the time of inputting the first report data and the first emotion data, the second report data associated with a day within the period; a first presentation unit that presents the first report data, the first emotion data, and the second report data associated with days within the period to a plurality of report recipients associated with the reporter; a third input unit that receives, from the plurality of report recipients, input of comment data about the first report data to the reporter and acceptance data indicating acceptance of the first report data selected from options consisting of only positive content; a third presentation unit that presents the comment data and the acceptance data to the reporter; Function as a The first presentation unit presents, to each of the plurality of report recipients, the first report data, the first emotion data, and the second report data, as well as the comment data and the acceptance data by other report recipients. Business reporting program.

Citation Information

Patent Citations

  • Task management system

    JP2004287575A

  • Display area of information for developing and introducing human resources

    JP2007072836A

  • Motivation management system

    JP2007265134A

  • Work status management support system, work status management support method, and program

    JP2007272425A

  • Customer service information managing system

    JP2017072903A