Patent Publication Number: US-2022215315-A1

Title: Systems and methods for generating prioritization models and predicting workflow prioritizations

Description:
FIELD OF THE DISCLOSURE 
     The present disclosure relates to systems and methods for generating prioritization models and predicting workflow prioritizations. 
     BACKGROUND 
     Collaboration environments enable users to assign projects, tasks, or other assignments to assignees to complete. Such collaboration environments enable users to work in a more organized and efficient manner. However, determining how to prioritize units of work is one common area where efficiency may be lost. 
     SUMMARY 
     Users utilizing the work management platform often have several units of work they are associated with or responsible for at any given time. Deciding which units of work to prioritize can be difficult and/or cause user to lose efficiency. Some users may choose to prioritize the wrong units of work. Determining what users should prioritize based on prioritization models generated based on their answers to a series of questions may solve these problems. In some implementations, machine learning may be used to automatically determine the prioritization of tasks. 
     One aspect of the present disclosure relates to a system configured for generating prioritization models and predicting workflow prioritizations. The system 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. The environment state information may include values of user parameters and values of work unit parameters. The values of the user parameters may be organized in user records corresponding to users interacting with and viewing the collaboration environment and the values of the work unit parameters are organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. The units of work may include a first set of units of work associated with a first user. 
     The processor(s) may be configured to effectuate presentation of a series of questions via a first client computing platform associated with the first user. The processor(s) may be configured to receive user input from the first client computing platform. The user input may include response information in response to the series of questions. The processor(s) may be configured to generate a first prioritization model based on the response information. The processor(s) may be configured to determine one or more priorities for the first user based on the first prioritization model such that a primary first unit of work within the first set of units of work is determined to be a higher priority than a secondary first unit of work within the first set of units of work. Effectuate presentation of a graphical user interface may display an indication of the one or more priorities determined for the first user. The graphical user interface may include an indication that the primary first unit of work is a higher priority than the secondary first unit of work. 
     In some implementations, a system configured for generating prioritization models and predicting workflow prioritizations, may include one or more of: one or more servers, one or more client computing platforms, and/or other components. The one or more servers may be configured to communicate with one or more client computing platforms according to a client/server architecture and/or other architecture. The one or more servers and/or client computing platforms may include one or more physical processors configured to execute one or more computer program components. The computer program components may include one or more of an environment state component, a question component, a user input component, a prioritization model component, a priority component, a graphical user interface component, and/or other components. 
     The environment state component may be configured to manage environment state information. The environment state information may maintain a collaboration environment. The environment state information may include values of user parameters, values of work unit parameters, and/or values of other parameters. The values of the user parameters may be organized in user records corresponding to users interacting with and viewing the collaboration environment. 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. The units of work may include a first set of units of work associated with a first user. 
     The question component may be configured to effectuate presentation of a series of questions. The series of questions may be presented to the first user via a first client computing platform associated with the first user. In some implementations, the series of questions may include one or more predetermined questions, comparisons of units of work associated with the given user, and/or other questions. The user input component may be configured to receive user input from the first client computing platform. The user input may include response information in response to the series of questions. By way of non-limiting example, if the series of questions includes one or more comparisons of units of work, the user may select the higher priority unit of work from the two or more units of work compared. As such, the user input received from the first client computing platform may include one or more selections of individual ones of the units of work associated with the first user from the one or more comparisons. 
     The prioritization model component may be configured to generate a first prioritization model based on the response information. The first prioritization model may be used to determine one or more priorities for the first user. In some implementations, the prioritization model component may be configured to obtain values for the user parameters associated with the first user, values for the work unit parameters associated with one or more of the units of work associated with the first user, and/or other information. The prioritization model may be determined based on the response information, the values for the user parameters associated with the first user, the values for the work unit parameters associated with one or more of the units of work associated with the first user, and/or other information. 
     In some implementations, the prioritization component may use neural networks to determine the prioritization models corresponding to individual users. The first prioritization model may be generated using a neural network based on the response information, the values for the user parameters associated with the first user, the values for the work unit parameters associated with one or more of the units of work associated with the first user, and/or other information. In some implementations, the values for the user parameters associated with the first user and/or the values for the work unit parameters associated with one or more of the units of work associated with the first user indicate previous actions of the first user within the collaboration environment. 
     In some implementations, the first prioritization model may be determined at least partially based on the prioritization information. The prioritization component may be configured to receive secondary user input including the prioritization information. The prioritization information may characterize units of work that should be prioritized by a given user (e.g., the first user for the first prioritization model). By way of example, a manager, boss, and/or other superior may provide the secondary input. 
     In some implementations, the prioritization model component may be configured to export the first prioritization model. The first prioritization model may be exported responsive to the prioritization model component receiving a request to export the first prioritization model. 
     The priority component may be configured to determine one or more priorities for the first user. The one or more priorities for the first user may be determined based on the first prioritization model. As such, a primary first unit of work within the first set of units of work may be determined to be a higher priority than a secondary first unit of work within the first set of units of work. A given unit of work having a high priority than another unit of work may indicate the given unit of work should be completed prior to the other unit of work. Such a determination may be based on other units of work dependent on and/or associated with the given unit of work, the assigning or managing user associated with the given unit of work, the length of the given unit of work, the level of involvement of the given unit of work, the followers for a given unit of work, the due date and/or start date information for a given unit of work, and/or other information. 
     The graphical user interface component may be configured to effectuate presentation of a graphical user interface displaying an indication of the one or more priorities determined for the first user. For example, the graphical user interface may include an indication that the primary first unit of work is a higher priority than the secondary first unit of work. In some implementations, the indication of the one or more priorities may include a recommendation of an individual unit of work for the first user to prioritize, a list of the first units of work in the first set of tasks ranked according to the priorities determined, a visual indication that the primary first unit of work is a higher priority than a secondary first unit of work, an auditory indication that the primary first unit of work is a higher priority than a secondary first unit of work, and/or other indications. 
     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  shows a system configured for generating prioritization models and predicting workflow prioritizations, in accordance with one or more implementations. 
         FIG. 2  illustrates a graphical user interface for presenting a series of questions to a user, in accordance with one or more implementations. 
         FIG. 3  illustrated a graphical user interface for displaying one or more priorities for a user, in accordance with one or more implementations. 
         FIG. 4  includes a flow chart of a method for generating prioritization models and predicting workflow prioritizations, in accordance with one or more implementations. 
     
    
    
     DETAILED DESCRIPTION 
       FIG. 1  illustrates a system  100  configured for generating prioritization models and predicting workflow prioritizations, in accordance with one or more implementations. In some implementations, system  100  may include one or more servers  102 . 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 be configured by machine-readable instructions  106 . Machine-readable instructions  106  may include one or more instruction components. The instruction components may include computer program components. The instruction components may include one or more of an environment state component  108 , a question component  110 , a user input component  112 , a prioritization model component  114 , a priority component  116 , a graphical user interface component  118 , and/or other instruction components. 
     Environment state component  108  may be configured to manage environment state information maintaining a collaboration environment. The environment state information may include values of user parameters and values of work unit parameters. By way of non-limiting example, the values of the user parameters may be organized in user records corresponding to users interacting with and viewing the collaboration environment and the values of the work unit parameters are organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. The units of work may include a first set of units of work associated with a first user. 
     The work unit parameters for work units managed, created, and/or assigned within the collaboration environment may include parameters describing one or more work units managed, created, and/or assigned within the collaboration environment and/or via the collaboration work management platform, and/or the metadata associated with the one or more work units. Individual ones of the work units may be associated with individual ones of the work unit records. A work unit record may define values of the work unit parameters associated with a given work unit managed, created, and/or assigned within the collaboration environment and/or via the collaboration work management platform. A given work unit may have one or more owners and/or one or more 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 work unit 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. 
     The work unit parameters may, by way of non-limiting example, include one or more of: one or more units of work, one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, up-votes, other hard-coded responses, etc.), a work unit name, a work unit description, one or more work unit dates (e.g., a start date, a due date, a completion date, and/or other work unit 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 work unit members and/or member information), a status and/or progress (e.g., an update, a hardcoded status update, a measured status, quantity of work units remaining in a given project, completed work units in a given project, and/or other status parameter), one or more 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, sub-tasks 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), 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 user parameters associated with the users interacting with and/or viewing the collaboration environment may include parameters describing the users, their actions within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their actions within the environment, their settings, 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 interacting with and/or viewing the collaboration environment. 
     The user parameters may, by way of non-limiting example, include one or more of: a user name, a group parameter, a subset parameter, a user account, a user role, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, 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 work unit order, etc.), one or more authorized applications, one or more presence/interaction parameters (e.g., indicating presence and/or interaction level at an environment level, work unit 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, one or more statistics related to 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, workload information, schedule information, historical information, other user parameters for the given user, and/or other user parameters and/or work unit parameters, for one or more work units the given user is associated with. 
     Question component  110  may be configured to effectuate presentation of a series of questions from which the prioritization models are determined. Question component  110  may be configured to effectuate presentation of a series of questions via a first client computing platform associated with the first user. The series of questions may include one or more predetermined questions. For example, the series of questions may include questions related to how the user typically completes units of work, how the user selects units of work to work on, when the user prefers to work, what types of units of work the user prefers to work on, the user&#39;s experience, the user&#39;s qualifications, the user&#39;s expertise, the user&#39;s supervisor or superior, the importance of a given unit of work (e.g., task, project, sub-task, and/or other units of work), and/or anything related to a user and/or how the user works or prioritizes work. 
     In some implementations, the series of questions may include one or more comparisons of units of work associated with the first user. The comparisons may include a comparison of two or more units of work, wherein the series of questions asks the user to select the highest priority unit of work and/or the lowest priority unit of work, and/or to rank the priority of the units of work presented. The user&#39;s selections of the units of work from the comparisons may be used to train the prioritization model for a given user. 
     User input component  112  may be configured to receive user input from the first client computing platform. The user input may include response information in response to the series of questions. The user input may include one or more selections, text input (e.g., answers), rankings, and/or other user input indicating answers to the individual questions in the series of questions. For example, the user input received from the first client computing platform may include one or more selections of individual ones of the units of work associated with the first user from the one or more comparisons. 
     In some implementations, user input component  112  may be configured to receive secondary user input including prioritization information. The prioritization information may characterize units of work that should be prioritized. By way of non-limiting example, the secondary user input may be input by a manager supervisor, team leader, project lead, a superior, and/or other manging users of the given user. By way of example, the prioritization information may indicate types, assigning users, and/or other characteristics of units of work the given user should prioritize. 
       FIG. 2  illustrates a graphical user interface for presenting a series of questions to a user, in accordance with one or more implementations. Graphical user interface  200  may include a series of questions 201. Series of questions 201 may include questions 204,206, 208 including one or more user selectable options, comparison  210 , and/or other questions. In some implementations, one or more questions in series of questions 201 may be predetermined. User  1   202  may provide user input in response to the series of questions 201. The user input may include the response information for questions 1-3 204, 206, 208 and comparison  4   210 , and/or other user input and/or response information. In some implementations, graphical user interface  200  may be presented via a first client computing platform associated with User  1   202 . 
     Returning to  FIG. 1 , prioritization model component  114  may be configured to generate a first prioritization model based on the response information. The response information may be used to train a prioritization model for determining one or more priorities for a given user. In some implementations, other information such as the prioritization information, values for the user parameters, values for the work unit parameters, and/or other information may be used at least partially as a basis for determining the first prioritization model. In some implementations, prioritization model component  114  may be configured to obtain values for the user parameters associated with the first user, values for the work unit parameters associated with one or more of the units of work associated with the first user, and/or other information. The units of work associated with the first user may include units of work assigned to the first user, units of work assigned by the first user, units of work associated with units of work assigned to and/or by the first user (e.g., an overarching unit of work, a unit of work under the same overarching unit of work, one or more sub units of work, and/or other associated units of work), and/or other units of work. The values for the user parameters the values for the user parameters associated with the first user and/or the values for the work unit parameters associated with one or more of the units of work associated with the first user may indicate previous actions of the first user within the collaboration environment. By way of non-limiting example, the prioritization model may be determined based on the response information, the values for the user parameters associated with the first user, and the values for the work unit parameters associated with one or more of the units of work associated with the first user. 
     By way of non-limiting example, the first prioritization model may be generated using a neural network based on the response information, the values for the user parameters associated with the first user, the values for the work unit parameters associated with one or more of the units of work associated with the first user, and/or other information. 
     In some implementations, prioritization model component  114  may be configured to receive a request to export the first prioritization model. Prioritization model component  114  may be configured to export the first prioritization model. The first prioritization model my be used for one or more other users besides the first user. For example, if the first user is a very productive user, the first prioritization model may be used as a prioritization model and/or as part of the basis of a prioritization model for one or more other users. 
     Priority component  116  may be configured to determine one or more priorities for the first user based on the first prioritization model. The one or more priorities may indicate which units of work the first user should prioritize, work on next, focus on, and/or put their attention towards. In some implementations, the priorities may or may not indicate importance of the one or more units of work indicated by the priorities. As such, for example, a primary first unit of work within the first set of units of work may be determined to be a higher priority than a secondary first unit of work within the first set of units of work by priority component  116 . 
     Graphical user interface component  118  may be configured to effectuate presentation of a graphical user interface including the one or more priorities determined. The graphical user interface presented to the first user may display an indication of the one or more priorities determined for the first user. The graphical user interface may include an indication that the primary first unit of work is a higher priority than the secondary first unit of work. By way of non-limiting example, the indication of the one or more priorities may include a recommendation of an individual unit of work for the first user to prioritize, a list of the first units of work in the first set of tasks ranked according to the priorities determined, a visual indication (e.g., highlighting, value ranking, recommendation field, and/or other visual indication) that the primary first unit of work is a higher priority than a secondary first unit of work, an auditory indication, and/or other indication that the primary first unit of work is a higher priority than a secondary first unit of work. 
       FIG. 3  illustrated a graphical user interface for displaying one or more priorities for a user, in accordance with one or more implementations. Graphical user interface  300  may include one or more indications of priorities for User  1   302 . Recommendation  304  may indicate a Primary First Unit of Work is a priority for User  1   302 . Ranked listing  308  may indicate the priorities of the Primary First Unit of Work, the Secondary First Unit of Work, X First Unit of Work, Y First Unit of Work, and Z First Unit of Work for User  1   302 . Ranked listing  308  may indicate that the Primary First Unit of Work is a higher priority than the Secondary First Unit of Work for User  1   302 , the Secondary First Unit of Work is higher priority than the X First Unit of Work for User  1   302 , and/or the Y First Unit of Work is higher priority than the Z First Unit of Work for User  1   302 . 
     Returning to  FIG. 1 , in some implementations, server(s)  102 , client computing platform(s)  104 , and/or external resources  124  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 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  124  may be operatively linked via some other communication media. 
     A given client computing platform  104  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  104  to interface with system  100  and/or external resources  124 , 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  124  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  124  may be provided by resources included in system  100 . 
     Server(s)  102  may include electronic storage  120 , one or more processors  122 , and/or other components. Server(s)  102  may include communication lines, or ports to enable the exchange of information with a network 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  120  may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage  120  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  120  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  120  may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage  120  may store software algorithms, information determined by processor(s)  122 , 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)  122  may be configured to provide information processing capabilities in server(s)  102 . As such, processor(s)  122  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)  122  is shown in  FIG. 1  as a single entity, this is for illustrative purposes only. In some implementations, processor(s)  122  may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s)  122  may represent processing functionality of a plurality of devices operating in coordination. Processor(s)  122  may be configured to execute components  108 ,  110 ,  112 ,  114 ,  116 , and/or  118 , and/or other components. Processor(s)  122  may be configured to execute components  108 ,  110 ,  112 ,  114 ,  116 , and/or  118  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)  122 . 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 ,  114 ,  116 , and/or  118  are illustrated in  FIG. 1  as being implemented within a single processing unit, in implementations in which processor(s)  122  includes multiple processing units, one or more of components  108 ,  110 ,  112 ,  114 ,  116 , and/or  118  may be implemented remotely from the other components. The description of the functionality provided by the different components  108 ,  110 ,  112 ,  114 ,  116 , and/or  118  described below is for illustrative purposes, and is not intended to be limiting, as any of components  108 ,  110 ,  112 ,  114 ,  116 , and/or  118  may provide more or less functionality than is described. For example, one or more of components  108 ,  110 ,  112 ,  114 ,  116 , and/or  118  may be eliminated, and some or all of its functionality may be provided by other ones of components  108 ,  110 ,  112 ,  114 ,  116 , and/or  118 . As another example, processor(s)  122  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 ,  114 ,  116 , and/or  118 . 
       FIG. 4  illustrates a method  400  for generating prioritization models and predicting workflow prioritizations, in accordance with one or more implementations. The operations of method  400  presented below are intended to be illustrative. In some implementations, method  400  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  400  are illustrated in  FIG. 4  and described below is not intended to be limiting. 
     In some implementations, method  400  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  400  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  400 . 
     An operation  402  may include managing environment state information maintaining a collaboration environment. The environment state information may include values of user parameters and values of work unit parameters. The values of the user parameters may be organized in user records corresponding to users interacting with and viewing the collaboration environment and the values of the work unit parameters are organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. The units of work may include a first set of units of work associated with a first user. Operation  402  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  404  may include effectuating presentation of a series of questions via a first client computing platform associated with the first user. Operation  404  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 presentation effectuation component  110 , in accordance with one or more implementations. 
     An operation  406  may include receiving user input from the first client computing platform. The user input may include response information in response to the series of questions. Operation  406  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 input component  112 , in accordance with one or more implementations. 
     An operation  408  may include generating a first prioritization model based on the response information. Operation  408  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 prioritization model generating component  114 , in accordance with one or more implementations. 
     An operation  410  may include determining one or more priorities for the first user based on the first prioritization model. As such, a primary first unit of work within the first set of units of work may be determined to be a higher priority than a secondary first unit of work within the first set of units of work. The graphical user interface may display an indication of the one or more priorities determined for the first user. The graphical user interface may include an indication that the primary first unit of work is a higher priority than the secondary first unit of work. Operation  410  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 priority component  116 , 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.