Systems and methods to measure and visualize workload for individual users

Abstract

Systems and methods for measuring and visualizing workload for individual users are disclosed. Exemplary implementations may: manage environment state information describing units of work assigned to individual users within the collaboration environment; determine values of a workload parameter for the individual users; effectuate presentation of user interface including individual date panes configured to reflect the values of the workload parameter; and/or perform other operations.

Description

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods to measure and visualize workload for individual users.

BACKGROUND

Collaboration environments, sometimes referred to as integrated collaboration environments, may enable users to assign projects, tasks, or other assignments to assignees (e.g., other users) to complete. A collaboration environment may comprise an environment in which a virtual team of users does its work. A collaboration environment may enable users to work in a more organized and efficient manner. A collaboration environment may integrate features and/or functionality such as customized views of calendars to organize projects, tasks or other assignments, assigned to users.

SUMMARY

One aspect of the present disclosure relates to a system configured to measure and visualize user workload for individual users. One or more implementations described herein may determine values of a parameter by which workload may be determined (herein referred to as a “workload parameter”), which may describe units of work based on one or more quantities of individual units of work having due dates that fall on one or more individual dates, and/or other quantities used to measure workload. Measuring workload in this manner may provide users with useful data to determine if the quantity of units of work assigned to users on any given day can be completed, and/or if one or more units of work should be reassigned.

One or more implementations of a system to measure and visualize workload for individual users may include one or more hardware processors configured by machine-readable instructions. The processor(s) may be configured to manage environment state information maintaining a collaboration environment and/or other information. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may define one or more of work unit records, user records, and/or other records. The user records may include user information for the individual users. The work unit records may include work information comprising values of units of work managed, created, and/or assigned within the collaboration environment. The work unit information for individual units of work may include individual due dates for the expected completion of the individual units of work by the individual users assigned to the individual units of work.

The workload component may be configured to determine values of a workload parameter for the individual users. The values of the workload parameter may specify, for individual dates, individual quantities of units of work having due dates that fall on the individual dates. By way of non-limiting illustration, the values of the workload parameter for a first user may specify that a first quantity of units of work have due dates that fall on a first date. Further, the values of the workload parameter for the first user may specify that a second quantity of units of work may have due dates that fall on a second date.

The user interface component may effectuate presentation of a user interface on computing platforms associated with the users. The user interface may display, for the individual users, individual date panes associated with the individual dates. The individual date panes may be configured to reflect the individual quantities of units of work having due dates that fall on the individual dates. By way of non-limiting illustration, the user interface disposed to the first user may display a first date pane for the first date and a second date pane for the second date. The first date pane may reflect the first quantity of units of work and the second date pane may reflect the second quantity of units of work.

The user input component may be configured to obtain input information conveying user input into the individual date panes displayed in the user interface. In some implementations, the user input component may be configured to effectuate presentation of individual lists of the units of work having the due dates that fall on the individual dates in response to the user input. The individual lists may facilitate access to the individual units of work.

As used herein, any association (or relation, or reflection, or indication, or correspondency) involving servers, processors, client computing platforms, and/or another entity or object that interacts with any part of the system and/or plays a part in the operation of the system, may be a one-to-one association, a one-to-many association, a many-to-one association, and/or a many-to-many association or N-to-M association (note that N and M may be different numbers greater than 1).

These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to measure and visualize workload for individual users, in accordance with one or more implementations.

FIG. 2 illustrates a method to measure and visualize workload for individual users, in accordance with one or more implementations.

FIG. 3 illustrates an exemplary user interface, in accordance with one or more implementations.

FIG. 4 illustrates an exemplary user interface, in accordance with one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to measure and visualize workload for individual users, in accordance with one or more implementations. An accurate measurement of workload for individual users on individual due dates may prove useful for users or teams of users to have confidence in completing units of work on time. One or more implementation of the system 100 may be configured to present a visual via a user interface on a computing platform associated with the users, representative of individual quantities of units of work having due dates that fall on individual dates. Users may have a general idea of their ability to complete the quantities of units of work. Instead of relying on rough estimates of users abilities, risking that units of work may not be completed by their due dates, a comparison of users abilities and measurements of workloads may provide useful. This comparison may allow users and their teams the chance to redistribute assignment of units of work so that quantities of units of work are completed by their intended due date.

In some implementations, system 100 may include one or more of one or more servers 102, one or more client computing platforms 104, external resources 126, and/or other components. Server(s) 102 may be configured to communicate with one or more client computing platforms 104 according to a client/server architecture and/or other architectures. Client computing platform(s) 104 may be configured to communicate with other client computing platforms via server(s) 102 and/or according to a peer-to-peer architecture and/or other architectures. Users may access system 100 via client computing platform(s) 104.

Server(s) 102 may include one or more of non-transitory electronic storage 128, one or more processors 130 configured by machine-readable instructions 106, and/or other components. Machine-readable instructions 106 may include one or more instruction components. The instruction components may include computer program components. Executing the machine-readable instructions 106 may cause server(s) 102 to facilitate measuring and visualizing workload for individual users. The instruction components may include one or more of an environment state component 108, a workload component 110, a user interface component 112, a user input component 114, and/or other instruction components.

Environment state component 108 may be configured to manage environment state information and/or other information used in maintaining a collaboration environment. The environment state information may include one or more of work unit records, user records, and/or other records. The user records may include user information for the individual users. The work unit records may include work unit information for units of work managed, created, and/or assigned within the collaboration environment. The work unit information for individual units of work may include individual due dates for expected completion of the individual units of work by individual users assigned to the individual units of work.

The user information in the user records may include values of user parameters. The values of the user parameters may be organized in user records corresponding to user interacting with and/or viewing the collaboration environment. The values of the user parameters may include information describing the users, their actions within the collaboration environment, their settings, their workload capacity for the individual users on individual dates, and/or other user information. Individual ones of the users may be associated with individual ones of the user records. A user record may define values of the user parameters associated with a given user.

The values of the user parameters may, by way of non-limiting example, specify one or more of: a user name, a group parameter, a user account, a user role information, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, a workload capacity, one or more projects (which may include project parameters defined by one or more work unit records), one or more items of work (which may include one or more unit of work parameters defined by one or more unit of work records), one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, other unit of work order, etc.), one or more authorized applications, one or more interaction parameters (e.g., indicating a user is working on/worked on a given unit of work, a given user viewed a given work unit of work, a given user selected a given unit of work, a timeframe a given user last interacted with and/or worked on a given unit of work, a time period that a given unit of work has been idle, and/or other interaction parameters), a presence parameter (e.g., indicating presence and/or interaction level at an environment level, unit of work level, project level, task level, application level, etc.), one or more notification settings, one or more progress parameters, status information for one or more work units the user is associated with (units of work assigned to the user, assigned to other users by the user, completed by the user, past-due date, and/or other information), one or more performance metrics of a given user (e.g., how many units of work the user has completed, how quickly the user completed the units of work, how quickly the user completes certain types of work units, the efficiency of the user, bandwidth of the user, activity level of the user, etc.), application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, schedule information, other user parameters for the given user.

User role information may specify individual roles of the individual users in the individual units of work. A role may represent a position of an individual user. The position may be specified based on a description of one or more of job title, level, stage, and/or other descriptions of position. The role may be specified with respect to a company as a whole, a particular unit of work, and/or other considerations. By way of non-limiting illustration, a role may include one or more of chief executive officer (or other officer), owner, manager, supervisor, accountant, associate, employee, entry level, midlevel, senior, administrator, director, foreman, engineer, product developer, human resource officer, artist, art director, and/or other description.

Schedule information for the individual users may include one or more calendar entries associated with the individual users. The individual calendar entries may be associated with individual start dates and individual end dates.

In some implementations, schedule information may be stored locally within electronic storage 128 by virtue of features and/or functionality provided within a collaboration environment. By way of non-limiting illustration, a collaboration environment may have the features and/or functionality of calendar application configured to facilitate calendaring entries into a schedule. It is noted that schedule information may be determined through features and/or functionality provided by one or more external resources 126. By way of non-limiting illustration, an external resource may include a calendar application which may be external to a collaboration environment. The collaboration environment may have permissions to access the external calendar application to determine and/or obtain schedule information.

The workload capacity may include a threshold quantity of units of work. The threshold quantity may be specified for individual days and/or other periods of time. In some implementations, if the threshold quantity is specified for multiple dates, a daily quantity for individual days may be determined by dividing the threshold quantity for multiple dates by the quantity of days. In some implementations, workload capacity may be specified by one or more users. In some implementations, workload capacity may be determined automatically over time. By way of non-limiting illustration, a first user record for a first user may specify a first threshold quantity of units of work a given day. Accordingly, first threshold quantity may convey that the first user may only be able to complete that quantity of units of work on the first date and/or the second date.

The work information may include values of one or more work unit parameters. The values of the work unit parameters may be organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. A given work unit may have one or more assignees and/or team members working on the given work unit. Work units may include one or more to-do items, action items, objectives, and/or other units of work one or more users should accomplish and/or plan on accomplishing. Units of work may be created by a given user for the given user and/or created by the given user and assigned to one or more other users. A given unit of work may include one or more projects, tasks, sub-tasks, and/or other units of work possibly assigned to and/or associated with one or more users.

By way of non-limiting illustration, the one or more work unit parameters may include one or more of a workload parameter, a work assignment parameter, a work management parameter, work creation parameter, and/or other parameters. The values of the work assignment parameter may describe units of work assigned to the individual users. The values of the work management parameter may describe units of work managed by the individual users. The values of the work creation parameter may describe units of work created by the individual users.

In some implementations, the units of work may be described based on one or more of a unit of work name, a unit of work description, one or more unit of work dates (e.g., a start date, a due date, a completion date, and/or dates), one or more members associated with a unit of work (e.g., an owner, one or more other project/task members, member access information, and/or other unit of work members and/or member information), a status parameter (e.g., an update, a hardcoded status update, a completed/uncomplete/mark complete, a measured status, a progress indication, quantity of sub-work units remaining for a given unit of work, completed work units in a given project, and/or other status parameter), one or more user comment parameters (e.g., permission for who may comments such as a creator, a recipient, one or more followers, and/or one or more other interested parties; content of the comments; one or more times; presence or absence of the functionality of up-votes; one or more hard-coded responses; and/or other parameters.), one or more interaction parameters (e.g., indicating a given unit of work is being worked on/was worked on, given work unit of work was viewed, a given unit of work was selected, how long the given unit of work has been idle, a last interaction parameter indicating when and what user last interacted with the given unit of work, users that interacted with the given unit of work, and/or other interaction parameters indicating sources of the interactions, context of the interactions, content of the interactions and/or time for the interactions), one or more file attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within a given unit of work (e.g., tasks within a project, subtasks within a task, etc.,), state of a workspace for a given unit of work (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a unit of work), dependencies between one or more work units, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), quantities of work production for the unit of work (e.g., quantity of lines of code, quantity of lines of copy, etc.), other work unit parameters for the given work units, and/or other work unit parameters, and/or user parameters for one or more users and/or work units the given project is associated with.

The values of the work assignment parameter describing units of work assigned to the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign one or more unit of work to themselves and/or an other user. In some implementations, a user may be assigned a unit of work and the user may effectuate a reassignment of the unit of work from the user or one or more other users.

In some implementations, values of the work assignment parameter may indicate that a status parameter of a unit of work has changed from “incomplete” to “marked complete” and/or “complete”. In some implementations, a status of complete for a unit of work may be associated with the passing of an end date associated with the unit of work. In some implementations, a status of “marked complete” may be associated with a user providing input via the collaboration environment at the point in time the user completes the unit of work (which may be before or after an end date). In some implementations, for the purposes of measuring workload, values of the work assignment parameter for a unit of work indicating a status of “marked complete” and/or “complete” may be treated as if the unit of work is no longer assigned to the user for the purpose of measuring a current workload of the user.

By way of non-limiting illustration, environment state information may specify values of the work unit parameters describing a first unit of work currently assigned to the first user. The first unit of work may be associated with a start date, an end date (e.g., due date), and/or other information.

In some implementations, environment state information may be updated as users continue to interact with the collaboration environment over time. The environment state component 108 may store and/or archive the environment state information periodically and/or based on user request to archive. In some implementations, the environment state component 108 may store historical environment state information specifying historical user information, work information, user information, and/or other information. By way of non-limiting illustration, the historical environment state information may specify historical workload capacities of individual users, and/or other information.

The workload component 110 may be configured to determine values of a workload parameter for the individual users. The values of the workload parameter may specify for individual dates, individual quantities of units of work having due dates that fall on the individual dates. By way of non-limiting illustration, the values of the workload parameter for the first user may specify that a first quantity of units of work have due dates that fall on a first date. The values of the workload parameter for the first user may specify a second quantity of units of work that have due dates that fall on a second date.

The workload component 110 may be configured to obtain the schedule information for the individual users. The workload component 110 may be configured to, for individual dates, aggregate individual quantities of the calendar entries on the individual dates with the individual quantities of units of work having due dates that fall on the individual dates to generate individual aggregate quantities of workload for the individual dates. An aggregate quantity of workload for a given date may refer to a quantity of calendar entries for the given date, combined with a quantity of units of work having due dates falling on the given date, and/or other information. In some implementations, the individual aggregate quantities of workload for the individual dates may be stored as values of the workload parameter.

The user interface component 112 may be configured to effectuate presentation of a user interface on computing platforms associated with the users. The user interface may display, for the individual users, individual date panes associated with the individual dates. The individual date panes may be configured to reflect one or more of the individual quantities of units of work having due dates that fall on the individual dates, the individual quantities of calendar entries that fall on the individual dates, the individual aggregate quantities of workload for the individual dates, and/or other information. By way of non-limiting illustration, the user interface may display, for the first user, a first date pane for the first date, a second date pane for the second date, and/or other date panes. The first date pane may reflect one or more of the first quantity of units of works, a quantity of calendar entries on the first date for the first user, a first aggregate quantity of workload on the first date for the first user, and/or other information. The second date pane may reflect one or more of the second quantity of units of works, a quantity of calendar entries on the second date for the first user, a second aggregate quantity of workload on the second date for the first user, and/or other information.

By way of non-limiting illustration, displaying the individual date panes to reflect the individual values of the workload parameter determined for the individual dates may comprise of determining display characteristics of individual user interface elements that make up the individual date panes. The display characteristics may be determined to cause the individual user interface elements to reflect one or more of the values of the workload parameter. In some implementations, a first display characteristic of a first user interface element of the first date pane may be configured based on one or more of the first quantity of units of work, a quantity of calendar entries on the first date for the first user, the first aggregate quantity of workload on the first date for the first user, and/or other information. The first display characteristic of a second user interface element of the second date pane may be configured based on one or more of the second quantity of units of work, the quantity of calendar entries on the second date for the first user, the second aggregate quantity of workload on the second date for the first user, and/or other information. In some implementations, the user interface may display multiple date panes in a calendar grid. In some implementations the quantity of date pages may form one or more of a week-long calendar grid, a month-long calendar grid, and/or other length grids.

In some implementations, the display characteristics of the individual user interface elements may include one or more size, shape, color, a plot line, and/or other features. In some implementations, size may be reflective of the values of the workload parameter. For example, relatively larger quantities may result in relatively larger size user interface elements. As an illustrative example, a user interface element may include a circle that changes in size relative to the values of the workload parameter. In some implementations, certain colors may be associated with certain values of the workload parameter. For example, a given quantity (or range of quantities) may be associated with a given color, while an other given quantity (or range of quantities) may be associated with another color. As an illustrative example, a shading of a date pane may change color relative to the values of the workload parameter. In some implementations, certain shapes may be associated with certain values of the workload parameter. For example, a given quantity (or range of quantities) may be associated with a given shape, while an other given quantity (or range of quantities) may be associated with another shape. As an illustrative example, a graphic displayed within a date pane may change shape relative to the values of the workload parameter.

In some implementations, a date pane may display a workload axis representing quantities of units of work (and/or calendar entries and/or aggregate quantities of workload), and/or other components. A plot line may be plotted with respect to the workload axis. The individual quantities may be shown relative the workload axis. The workload axis may include visual increments of units of work (and/or calendar entries). A height of the plot line may represent a quantity of units of time (and/or calendar entries and/or aggregate quantities). A length of a line may represent the time span over the given date.

In some implementations, the display characteristics of the individual user interface elements may further include a quantity indicator and/or other information. The quantity indicator may display a numerical representation of the individual quantities of units of work (and/or calendar entries and/or aggregate quantities of workload) having due dates that fall on the individual dates.

A user interface may include one or more user interface elements configured to facilitate user interaction with the user interface. By way of non-limiting illustration, user interface elements may include one or more of text input fields, drop down menus, check boxes, display windows, virtual buttons, and/or other elements configured to facilitate user interaction. The user input component 114 may be configured to obtain input information conveying user input into the individual date panes displayed in the user interface.

In some implementations, the user input component 114 may, in response to the user input, effectuate presentation of individual lists of the units of work (and/or calendar entries) having the due dates that fall on the individual dates. The individual lists may facilitate access to the individual units of work (and/or calendar entries) having the due dates that fall on the given date.

The environment state component 108 may be configured to compare, for the individual dates, individual quantities of units of work (and/or calendar entries) having due dates that fall on the individual dates with the threshold quantity of units of work for the individual dates. In some implementations, a determination may be made, based on the comparison, whether to generate notifications for the individual users. If a quantity of units of work exceeds a threshold quantity, a determination to generate a notification may be made. If a quantity of units of work (and/or calendar entries) does not exceed a threshold quantity, a determination not to generate a notification may be made. For example, if a comparison indicates a threshold quantity of a user is 10 units of work on a given day and the first user has 11 units of work to be completed by a given due date, a notification may be generated and delivered to the user and/or other users.

By way of non-limiting illustration, based on a comparison between the first threshold quantity of units of work and the first quantity of units of work for the first date shows the first quantity is greater than the first threshold quantity, a determination may be made to generate a first notification. Based on a comparison between the first threshold quantity of units of work and the second quantity of units of work for the second date shows the second quantity is less than the first threshold quantity, a determination may be made to not generate a notification.

The environment state component 108 may be configured to generate the notifications in response to determination that the notifications should be generated. The notifications may convey the results of the comparison, and/or include other information. In some implementations, other information may include recommendations on how to redistribute units of work (and/or to redate calendar entries). In some implementations, the recommendations may identify one or more other users having quantities of due dates of units of work that do not exceed a threshold of the particular date. The recommendations may be selected to automatically reassign a unit of work to a user that was identified as a quantity of due dates of units of work that do not exceed the threshold of the particular date. By way of non-limiting illustration, the first notification may be generated to include information that the first date is “overloaded” for the first user, e.g., that the first quantity of units of work having due dates on the first date exceeds the threshold. The first notification may identify a second user who may have a quantity of units of work having due dates on the first date that does not exceed a threshold quantity for the second user. The first notification may include a recommendation to reassign one or more units of work to the second user.

In some implementations, the environment state component 108 may be configured to identify one or more user(s) to receive notification(s). In some implementations, a user receiving a notification may include one or more of a given user having the overloaded date, another user having a superior relationship to the given user, another user having a subordinate relations to the given user, and/or other users. In some implementations, the given user having the overloaded date may be sent a notification first. Upon a lapse of time with no response by the given user, another user may be identified to receive the notification and the notification may be delivered.

By way of non-limiting illustration, the first user and/or a third user may be identified to receive the first notification. The third user may be identified based on the third user having a role that is superior and/or subordinate to the first user. By way of non-limiting illustration, the third user may be in a managerial role and may act on the first notification to re-distribute one or more units of work that the first user may not be able to complete by a due date.

In some implementations, the environment state component 108 may be configured to deliver the notifications. By way of non-limiting illustration, the first notification may be delivered to a computing platform of one or more users.

FIG. 3 illustrates an exemplary user interface 300 visualizing a measure of workload for an individual user for a week, in accordance with one or more implementations. By way of non-limiting illustration, the user interface 300 may include a series of date panes representing individual dates in the week. The individual date panes may be configured to reflect the individual quantities of units of work having due dates that fall on the individual dates. The user interface 300 may display a visual representation of values of a workload parameter of individual users throughout the week. The user interface 300 may include one or more of a visual 302 of four units of work on a Monday, a visual of four units of work on a Tuesday, a visual 304 of one unit of work on a Wednesday, a visual 306 of five units of work on a Thursday, a visual 308 of nine units of work on a Friday, and/or other visualizations. As illustrated, the individual date panes include user interface elements in the form of circles. Display characteristics of individual user interface elements, in this case size, may be configured to reflect the individual quantities of units of work.

It is noted that FIG. 3 is for illustrative purposes only and is not to be considered limiting. Instead, it is to be understood that the user interface 300 may be configured in other ways and/or including other elements in accordance with one or more implementations of the system 100 presented herein.

FIG. 4 illustrates a user interface 400, in accordance with one or more implementations. The user interface 400 may include one or more user interface elements configured to facilitate user interaction with the user interface 400. The user interface 400 may be generated in response to input into the individual date panes displayed in the user interface 300 of FIG. 3. In response to the user input, presentation of an individual list of the units of work 402 on an individual date may be displayed in the user interface.

In some implementations, the user interface 400 may include a portion 402 displaying an individual list of the units of work. By way of non-limiting illustration, the units of work listed in portion 402 may facilitate access to the individual units of work for that date. FIG. 4 is for illustrative purposes only and is not to be considered limiting. Instead, it is to be understood that the user interface 400 may be configured in other ways and/or including other elements to facilitate other user interaction in accordance with one or more implementations of the system 100 presented herein.

In FIG. 1, in some implementations, server(s) 102, client computing platform(s) 104, and/or external resources 126 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network 116 such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, client computing platform(s) 104, and/or external resources 126 may be operatively linked via some other communication media.

A given client computing platform may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform to interface with system 100 and/or external resources 126, and/or provide other functionality attributed herein to client computing platform(s) 104. By way of non-limiting example, the given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

External resources 126 may include sources of information outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 126 may be provided by resources included in system 100.

Server(s) 102 may include electronic storage 128, one or more processors 130, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network 116 and/or other computing platforms. Illustration of server(s) 102 in FIG. 1 is not intended to be limiting. Server(s) 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102. For example, server(s) 102 may be implemented by a cloud of computing platforms operating together as server(s) 102.

Electronic storage 128 may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 128 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 128 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 128 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 128 may store software algorithms, information determined by processor(s) 130, information received from server(s) 102, information received from client computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.

Processor(s) 130 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 130 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 130 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 130 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 130 may represent processing functionality of a plurality of devices operating in coordination. Processor(s) 130 may be configured to execute components 108, 110, 112, 114, and/or other components. Processor(s) 130 may be configured to execute components 108, 110, 112, and/or 114, and/or other components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 130. As used herein, the term “component” may refer to any component or set of components that perform the functionality attributed to the component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.

It should be appreciated that although components 108, 110, 112, and/or 114 are illustrated in FIG. 1 as being implemented within a single processing unit, in implementations in which processor(s) 130 includes multiple processing units, one or more of components 108, 110, 112, and/or 114 may be implemented remotely from the other components. The description of the functionality provided by the different components 108, 110, 112, and/or 114 described below is for illustrative purposes, and is not intended to be limiting, as any of components 108, 110, 112, and/or 114 may provide more or less functionality than is described. For example, one or more of components 108, 110, 112, and/or 114 may be eliminated, and some or all of its functionality may be provided by other ones of components 108, 110, 112, and/or 114. As another example, processor(s) 130 may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of components 108, 110, 112, and/or 114.

FIG. 2 illustrates a method 200 to measure and visualize workload for individual users, in accordance with one or more implementations. The operations of method 200 presented below are intended to be illustrative. In some implementations, method 200 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 200 are illustrated in FIG. 2 and described below is not intended to be limiting.

In some implementations, method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.

An operation 202 may manage environment state information maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may include work unit records, user records, and/or other records. The work unit records may include work unit information for units of work managed, created, and/or assigned within the collaboration environment. The work unit information for individual units of work may include individual due dates for expected completion of the individual units of work by individual users assigned to the individual units of work. Operation 202 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component 108, in accordance with one or more implementations.

An operation 204 may determine values of a workload parameter for the individual users. The values of the workload parameter may specify, for individual dates, individual quantities of units of work having due dates that fall on the individual dates. By way of non-limiting illustration, the values of the workload parameter for a first user may specify that a first quantity of units of work have due dates that fall on a first date. A second quantity of units of work may have due dates that fall on a second date. Operation 204 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to workload component 110, in accordance with one or more implementations.

An operation 206 may present, to individual users, a user interface on a computing platform associated with the users. The user interface may display individual date panes associated with the individual dates. The individual date panes may be configured to reflect the individual quantities of units of work having due dates that fall on the individual dates. By way of non-limiting illustration, the user interface may display, for the first user, a first date pane for the first date, and/or a second date pane for the second date. The first date pane may reflect the first quantity of units of work and/or the second date pane may reflect the second quantity of units. Operation 206 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to user interface component 112, in accordance with one or more implementations.

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.

Claims

1. A system configured to measure and visualize workload for individual users, the system comprising: one or more physical processors configured by machine-readable instructions to: manage environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by users with the collaboration environment, the environment state information including work unit records, the work unit records including work unit information for units of work managed, created, and/or assigned within the collaboration environment, wherein the work unit information for individual units of work includes individual due dates for expected completion of the individual units of work by individual users assigned to the individual units of work;determine values of a workload parameter for the individual users, the values of the workload parameter specifying, for individual dates, individual quantities of units of work having due dates that fall on the individual dates, such that the values of the workload parameter for a first user specify that a first quantity of units of work have the due dates that fall on a first date, and a second quantity of units of work have the due dates that fall on a second date;generate, based on the values of the workload parameter, user interface information defining a user interface that reflects the individual quantities of units of work having the due dates that fall on the individual dates, such that the user interface displays, for the individual users, individual date panes associated with the individual dates, wherein the individual date panes are configured to reflect the individual quantities of units of work having the due dates that fall on the individual dates, such that the user interface displays, for the first user, a first date pane for the first date, and a second date pane for the second date, the first date pane reflecting the first quantity of units of work and the second date pane reflecting the second quantity of units of work, and wherein the user interface information is generated based on: identifying display characteristics of individual user interface elements that make up the individual date panes that are to be configured based on the individual quantities of units of work having the due dates that fall on the individual dates, the display characteristics including size, shape, and color; andconfiguring one or more of the display characteristics of the individual user interface elements to reflect the individual quantities of units of work having the due dates that fall on the individual dates, such that a first display characteristic of a first user interface element of the first date pane is configured based on the first quantity of units of work, and the first display characteristic of a second user interface element of the second date pane is configured based on the second quantity of units of work;effectuate communication of the user interface information to computing platforms associated with the users to cause the computing platforms to present the user interface, such that the user interface information is communicated to a first computing platform associated with the first user to cause the first computing platform to present the user interface displaying the first date pane reflecting the first quantity of units of work and the second date pane reflecting the second quantity of units of work;determine updates to the environment state information that impact the values of the workload parameter for the individual users, the updates being caused by continued interaction with the collaboration environment by the users via the computing platforms; andupdate, based on the updates to the environment state information, the values of the workload parameter for the individual users and the user interface information communicated to individual computing platforms so that the user interface presented by the individual computing platforms includes the individual date panes reflecting up-to-date individual quantities of units of work having the due dates that fall on the individual dates.

2. The system of claim 1, wherein the display characteristics of the individual user interface elements further include a quantity indicator, wherein the quantity indicator displays a numerical representation of the individual quantities of units of work having the due dates that fall on the individual dates.

3. The system of claim 1, wherein the user interface displays multiple date panes in a calendar grid.

4. The system of claim 1, wherein the one or more physical processors are further configured by the machine-readable instructions to: obtain schedule information for the individual users, the schedule information including calendar entries for the individual dates;aggregate, for the individual dates, individual quantities of the calendar entries on the individual dates with the individual quantities of units of work having the due dates that fall on the individual dates to generate individual aggregate quantities of workload for the individual dates; andeffectuate presentation of the user interface so that the individual date panes reflect the individual aggregate quantities of workload.

5. The system of claim 1, wherein the one or more physical processors are further configured by the machine-readable instructions to: obtain input information conveying user input into the individual date panes displayed in the user interface; andin response to the user input, effectuate presentation of individual lists of the units of work having the due dates that fall on the individual dates, wherein the individual lists facilitate access to the individual units of work.

6. The system of claim 1, wherein the environment state information further includes user records, the user records including user information for the individual users, the user information including workload capacity for the individual users on individual dates, wherein the workload capacity includes a threshold quantity of units of work, such that a first user record for the first user specifies a first threshold quantity of units of work for the first date and the second date.

7. The system of claim 6, wherein the one or more physical processors are further configured by the machine-readable instructions to: compare, for the individual dates, individual quantities of units of work having the due dates that fall on the individual dates with the threshold quantity of units of work for the individual dates;based on the comparison, determine whether to generate notifications for the individual users, such that based on a comparison between the first threshold quantity of units of work and the first quantity of units of work for the first date, determine that a first notification is to be generated, and based on a comparison between the first threshold quantity of units of work and the second quantity of units of work for the second date, determine no notifications are to be generated; anddeliver the notifications, such that the first notification is delivered.

8. The system of claim 7, wherein the one or more physical processors are further configured by the machine-readable instructions to: identify the users to receive the notifications, including identifying the first user or a second user to receive the first notification.

9. A method configured to measure and visualize workload for individual users, the method comprising: managing environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by users with the collaboration environment, the environment state information including work unit records, the work unit records including work unit information for units of work managed, created, and/or assigned within the collaboration environment, wherein the work unit information for individual units of work includes individual due dates for expected completion of the individual units of work by individual users assigned to the individual units of work;determining values of a workload parameter for the individual users, the values of the workload parameter specifying, for individual dates, individual quantities of units of work having due dates that fall on the individual dates, such that the values of the workload parameter for a first user specify that a first quantity of units of work have the due dates that fall on a first date, and a second quantity of units of work have the due dates that fall on a second date;generating, based on the values of the workload parameter, user interface information defining a user interface that reflects the individual quantities of units of work having the due dates that fall on the individual dates, such that the user interface displays, for the individual users, individual date panes associated with the individual dates, wherein the individual date panes are configured to reflect the individual quantities of units of work having the due dates that fall on the individual dates, such that the user interface displays, for the first user, a first date pane for the first date, and a second date pane for the second date, the first date pane reflecting the first quantity of units of work and the second date pane reflecting the second quantity of units of work, and wherein the generating the user interface information comprises: identifying display characteristics of individual user interface elements that make up the individual date panes that are to be configured based on the individual quantities of units of work having the due dates that fall on the individual dates, the display characteristics including size, shape, and color; andconfiguring one or more of the display characteristics of the individual user interface elements to reflect the individual quantities of units of work having the due dates that fall on the individual dates, such that a first display characteristic of a first user interface element of the first date pane is configured based on the first quantity of units of work, and the first display characteristic of a second user interface element of the second date pane is configured based on the second quantity of units of work;effectuating communication of the user interface information to computing platforms associated with the users to cause the computing platforms to present the user interface, including effectuating communication of the user interface information to a first computing platform associated with the first user to cause the first computing platform to present the user interface displaying the first date pane reflecting the first quantity of units of work and the second date pane reflecting the second quantity of units of work;determining updates to the environment state information that impact the values of the workload parameter for the individual users, the updates being caused by continued interaction with the collaboration environment by the users via the computing platforms; andupdating, based on the updates to the environment state information, the values of the workload parameter for the individual users and the user interface information communicated to individual computing platforms so that the user interface presented by the individual computing platforms includes the individual date panes reflecting up-to-date individual quantities of units of work having the due dates that fall on the individual dates.

10. The method of claim 9, wherein the display characteristics of the individual user interface elements includes a quantity indicator, wherein the quantity indicator displays a numerical representation of the individual quantities of units of work having the due dates that fall on the individual dates.

11. The method of claim 9, wherein the user interface displays multiple date panes in a calendar grid.

12. The method of claim 9, further comprising: obtaining schedule information for the individual users, the schedule information including calendar entries for the individual dates;aggregating, for the individual dates, individual quantities of the calendar entries on the individual dates with the individual quantities of units of work having the due dates that fall on the individual dates to generate individual aggregate quantities of workload for the individual dates; andeffectuating presentation of the user interface so that the individual date panes reflect the individual aggregate quantities of workload.

13. The method of claim 9, further comprising: obtaining input information conveying user input into the individual date panes displayed in the user interface; andin response to the user input, effectuating presentation of individual lists of the units of work having the due dates that fall on the individual dates, wherein the individual lists facilitate access to the individual units of work.

14. The method of claim 9, wherein the environment state information further includes user records, the user records including user information for the individual users, the user information including workload capacity for the individual users on individual dates, wherein the workload capacity includes a threshold quantity of units of work, such that a first user record for the first user specifies a first threshold quantity of units of work for the first date and the second date.

15. The method of claim 14, further comprising: comparing, for the individual dates, individual quantities of units of work having the due dates that fall on the individual dates with the threshold quantity of units of work for the individual dates;based on the comparison, determining whether to generate notifications for the individual users, including based on a comparison between the first threshold quantity of units of work and the first quantity of units of work for the first date, determining that a first notification is to be generated, and based on a comparison between the first threshold quantity of units of work and the second quantity of units of work for the second date, determining no notifications are to be generated; anddelivering the notifications, including delivering the first notification.

16. The method of claim 15, further comprising: identifying the users to receive the notifications, including identifying the first user or a second user to receive the first notification.