Systems and methods to facilitate user engagement with units of work assigned within a collaboration environment

Information

  • Patent Grant
  • 11720858
  • Patent Number
    11,720,858
  • Date Filed
    Tuesday, July 12, 2022
    2 years ago
  • Date Issued
    Tuesday, August 8, 2023
    a year ago
Abstract
Systems and methods for facilitating user engagement with units of work assigned within a collaboration environment are presented herein. Implementations may: manage environment state information maintaining a collaboration environment, the environment state information the work unit records including values of an approval state parameter; effectuate presentation of a user interface of the collaboration environment, the user interface displaying individual work unit pages for individual units of work that include a set of user interface elements available for selection by the users, individual user interface elements in the set corresponding to different ones of the values of the approval state parameter; obtain user input information conveying user input characterizing the selection of the individual user interface elements; update the work unit records based on the user input information; and/or other perform other operations.
Description
FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods to facilitate user engagement with units of work assigned within a collaboration environment.


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 web-based conferencing and collaboration, desktop videoconferencing, and/or instant message into a single easy-to-use, intuitive interface.


SUMMARY

One aspect of the present disclosure relates to a system configured to facilitate user engagement with units of work assigned within a collaboration environment. Upon completion of a unit of work, a status of the unit of work may be set as “complete” by a user. However, satisfaction of the completion of the unit of work may not be characterized with merely setting the status of the unit of work as “complete” or “incomplete”. In some implementations, the user may specify an approval state of the unit of work by marking the unit of work as one or more of approved, revise, rejected, pending approval, and/or other states. In some implementations, “revise” may be accompanied by and/or may refer to a request to make changes, e.g., “changes requested,” “request changes,” and/or other instructions. In some implementations, upon the unit of work being marked as approved, the status of the unit of work may be set as “complete”. In some implementations, upon the unit of work being marked with revise, one or more new units of work may be generated. The one or more new units of work may be based on necessary revisions as indicated by the user. The one or more new units of work may be assigned to an assignor of the unit of work to address the revisions. In some implementations, upon the unit of work being marked as rejected, the status of a preexisting unit of work may be reset from “complete” to “incomplete”. These and/or other approval states may promote clarity and/or organization within review cycles as well as progress recordation for users and/or units of work.


One or more implementations of a system to facilitate user engagement with units of work assigned within a collaboration environment may include one or more hardware processors configured by machine-readable instructions. Executing the machine-readable instructions may cause the one or more hardware processors to facilitate user engagement with units of work. The machine-readable instructions may include computer program components. The computer program components may include one or more of an environment state component, a user interface component, a work unit component, and/or other components.


The environment state component 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 include work unit records describing units of work assigned to the users within the collaboration environment. The work unit records may include values of an approval state parameter and/or other values of other parameters. The approval state parameter may characterize approval of the units of work by the users assigned to the units of work. The values of the approval state parameter may include one or more of an approve value, a revise value, a reject value, a pending approval value, and/or other values. By way of non-limiting illustration, the work unit records may include a first work unit record for a first unit of work and/or other work unit records.


The user interface component may be configured to effectuate presentation of a user interface of the collaboration environment. The user interface may display individual work unit pages for individual units of work. Individual work unit pages may include a set of user interface elements available for selection by the users. Individual user interface elements in the set may correspond to different ones of the values of the approval state parameter.


The work unit component may be configured to obtain user input information conveying user input characterizing the selection of the individual user interface elements in the individual work unit pages. The selection of an individual user interface element in an individual work unit page of an individual unit of work may cause a corresponding value of the approval state parameter to be specified for the individual unit of work.


The work unit component may be configured to update the work unit records based on the user input information and/or other information. In some implementations, responsive to obtaining first user input characterizing the selection of a first user interface element on a first work unit page of the first unit of work, the work unit component may be configured to update the first work unit record by specifying the approve value for the approval state parameter of the first unit of work.


In some implementations, responsive to obtaining second user input characterizing the selection of a second user interface element on the first work unit page of the first unit of work, the work unit component may be configured to update the first work unit record by specifying the revise value for the approval state parameter of the first unit of work.


In some implementations, responsive to obtaining third user input characterizing the selection of a third user interface element on the first work unit page of the first unit of work, the work unit component may be configured to update the first work unit record by specifying the reject value for the approval state parameter of the first unit 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).


As used herein, the term “manage” (and derivatives thereof) may include active and/or passive direction, recommendation, suggestion, approval, rejection to users within a collaboration environment and/or any combination thereof. As used herein, the term “effectuate” (and derivatives thereof) may include active and/or passive causation of any effect. As used herein, the term “obtain” (and derivatives thereof) may include active and/or passive retrieval, determination, derivation, transfer, upload, download, submission, and/or exchange of information, and/or any combination thereof. As used herein, the term “update” (and derivatives thereof) may include adding, removing, changing units of work value to an individual work unit page and/or any combination thereof.


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 facilitate user engagement with units of work assigned within a collaboration environment, in accordance with one or more implementations.



FIG. 2 illustrates a method to facilitate user engagement with units of work assigned within a collaboration environment, in accordance with one or more implementations.



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



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



FIG. 5 illustrates user interfaces, in accordance with one or more implementations.





DETAILED DESCRIPTION


FIG. 1 illustrates a system 100 configured to facilitate user engagement with units of work within a collaboration environment, in accordance with one or more implementations. In some implementations, the user may specify an approval state of a unit of work by marking the unit of work as one or more of approved, revise, rejected, pending approval, and/or other states. Upon the unit of work being specified as approved, a status of the unit of work may be set as “complete”. Upon the unit of work being specified as revise, one or more new units of work may be generated. The one or more new units of work may be based on necessary revisions as indicated by the user. The one or more new units of work may be assigned to an assignor of the unit of work to address the revisions. Upon the unit of work being specified as rejected, the status of a preexisting unit of work may be reset from “complete” to “incomplete”. The unit of work may be subordinate to the preexisting unit of work. These and/or other approval states may promote clarity and/or organization within review cycles as well as progress recordation for users and/or units of work.


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 user engagement with units of work within a collaboration environment. The computer program components may include one or more of an environment state component 108, a user interface component 110, a work unit component 112, 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 collaboration environment may be configured to facilitate interaction by users within the collaboration environment. The environment state information may include one or more of user information, work information, and/or other information used to define, support, and/or otherwise maintain a collaboration environment.


The user information may include values of user parameters. The values of the user parameters may be organized in user records corresponding to users 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, 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.


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, 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, role information, and/or other information.


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, a set of units 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.


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 (also referred to as work units) 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. Individual units of work may include one or more of an individual project, an individual task, an individual sub-task, and/or other units of work assigned to and/or associated with one or more users. Individual units of work may include one or more digital content items. An individual unit of work may include an individual digital content item by virtue of the individual digital content item (and/or a copy or instance thereof) being attached and/or appended thereto. An individual unit of work may include an individual digital content item by virtue of the individual digital content item (and/or a copy or instance thereof) being accessible via the individual unit of work (e.g., via link, URL, a pointer, and/or other techniques to provide access). A digital content item may include one or more of an image, a video, an audio file, a PDF, a word document, and/or other digital content items.


Individual sets of work unit records may be defined by a record hierarchy. A record hierarchy may convey individual positions of work unit records (and their corresponding units of work) in the record hierarchy. By way of non-limiting illustration, a position may specify one or more of a work unit record being superior to another work unit record, a work unit record being subordinate to another work unit record, and/or other information. As a result, individual work unit records in the individual sets of work unit records may be subordinate to other individual work unit records in the individual sets of work unit records. For example, a work unit record may define a unit of work comprising a task, and a subordinate work unit record may define unit of work comprising a sub-task to the task. A record hierarchy may define a relationship between work unit records. A work unit record may have some restrictions placed on it by virtue of having a subordinate work unit record. By way of non-limiting illustration, a work unit record may be restricted from access by one or more users unless and/or until a subordinate work unit record is completed and/or started.


Individual work unit records may include values of an approval state parameter and/or other parameters. The approval state parameter may characterize approval of the units of work by the users assigned to the units of work. The values of the approval state parameter may include one or more of an approve value, a revise value, a reject value, a pending approval value, and/or other approval state values. In some implementations, the work unit records may include a first work unit record describing a first unit of work assigned to a first user and/or other work unit records. The first unit of work may include a first digital content item and/or other information.


Individual work units records may include hierarchical information defining a record hierarchy of the individual work unit records. The hierarchical information of a work unit record may include one or more of information identifying other work unit records associated in a record hierarchy the work unit record belongs to, a specification of the position of the work unit record in the hierarchy, restrictions and/or other relationships placed on the work unit record by virtue of its position, and/or other information.


In some implementations, as a consequence of the record hierarchies, the individual units of work described in the individual work unit records that are subordinate to the other individual work unit records may be subordinate to the individual units of work in the other individual work unit records.


In some implementations, the one or more work unit parameters may include one or more of 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/incomplete/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 make comments such as an assignee, an assignor, 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 digital content item 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), hierarchical information, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other information.


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 another 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).


User interface component 110 may be configured to effectuate presentation of a user interface of the collaboration environment. In some implementations, user interface component 110 may be configured to effectuate presentation of individual user interfaces on individual client computing platforms of one or more client computing platforms 104. The user interface component 110 may be configured to effectuate presentation of a user interface displaying the units of work. In some implementations, the user interface may display representations of the units of work in a timeline based on individual start dates and individual end dates of the individual units of work. In some implementations, the user interface may display representations of the units of work in an ordered list based on individual start dates of the individual units of work. In some implementations, representations of the units of work may include icons, graphics, and/or other elements. Selection of a representation of the units of work may facilitate generating views displaying the units of work.


The user interface may display individual work unit pages for individual units of work. The individual work unit pages may include a set of user interface elements available for selection by the users. The individual user interface elements in the set may correspond to different ones of the values of the approval state parameter.


The user interface elements may be configured to facilitate user interaction with the user interface, user entry, and/or selection. By way of non-limiting illustration, the user interface elements may include one or more of text input fields, drop down menus, check boxes, display windows, virtual buttons, and/or other user interface elements.


In some implementations, the user interface elements may include one or more visual representations. The visual representations may include icons, graphics, colors, text, and/or other elements. By way of non-limiting example, the user interface element corresponding to the approve value may be an outlined box and with a check mark icon and/or other graphics. The user interface element corresponding to the revise value may be an outlined box with an arrow icon and/or other graphics. The user interface element corresponding to the reject value may be a outlined box with an “X” icon and/or other icons. The individual user interface elements may be colored. By way of non-limiting illustration, the user interface element corresponding to the approve value may be green; the user interface element corresponding to the revise value may be yellow; and/or the user interface element corresponding to the reject value may be red.


In some implementations, the visual representations for the individual user interface elements that correspond to the different ones of the values of the approval state parameters may be set and/or modified by an administrative user and/or other users. In some implementations, the visual representations for the individual user interface elements that correspond to the different ones of the values of the approval state parameters may be fixed and unmodifiable.


Work unit component 112 may be configured to obtain user input information and/or other information. The user input information may convey user input characterizing the selection of the individual user interface elements in the individual work unit pages. The selection of an individual user interface element in an individual work unit page of an individual unit of work may cause a corresponding value of the approval state parameter to be specified for the individual unit of work.


In some implementations, the user input may further comprise user entry of input content and/or other information in the individual units of work. The input content may include, for example, the text of the comment input by a user. By way of non-limiting example, user input by the first user on, or relating to, the first digital content item may include first input content.


The work unit component 112 may be configured to update the work unit records based on the user input information and/or other information. In particular, work unit component 112 may be configured to update the work unit records based on the selection of the individual user interface elements in an individual work unit page of the individual unit of work.


In some implementations, a first work unit page of the first unit of work may include one or more of a first user interface element, a second user interface element, a third user interface element, and/or other user interface elements. The first user interface element may correspond to the approve value; the second user interface element may correspond to the revise value; and/or the third user interface element may correspond to the reject value.


In some implementations, work unit component 112 may be configured to update the first work unit record by specifying the approve value for the approval state parameter of the first unit of work. Such update may be responsive to obtaining first user input characterizing the selection of the first user interface element on the first work unit page of the first unit of work. In some implementations, updating the first work unit record to specify the approve value for the approval state parameter may cause a value of a status parameter of the first work unit record to be specified with a value of complete.


In some implementations, specifying the approve value for the approval state parameter of a unit of work may cause one or more automated actions to be carried out. Specifying the approve value for the approval state parameter of a unit of work may act as a trigger event to carry out one or more automated actions. In some implementations, an individual automated action may include effectuating one or more of creation of, change in, and/or specification of, one or more values of one or more of the parameters. In some implementations, the creation of, change in, and/or specification of values of parameters may be accomplished by accessing a corresponding record (e.g., user record, work unit record, and/or other records). In some implementations, creation of, change in, and/or specification of an individual value may be reflected in views of the collaboration environment accessed by users. In some implementations, an individual automated action may include effectuating an action outside of the collaboration environment (e.g., in an external resource).


In some implementations, individual sets of automated actions and associated individual trigger events may be stored in individual automation records. An automation record may define one or more of individual actions, individual trigger events, and/or other information. Individual actions may be defined by a target component, an action component, and/or other information. The target component of an automation record may include a parameter (or parameters) to which an action is to be carried out on. The action component of an automation record may define what change is to be made on the parameter (or parameters) defined by the target component. Individual trigger events may be defined by a source component, an event component, and/or other information. The source component of an automation record may include the approval state parameter of a unit of work. The event component may include the approval state parameter being defined by the approval state. Automation records may be specified by individual users. Automation records may reflect common repeated steps a user may take responsive to an approval of a unit of work. This automation may improve user efficiency and workflow since manual intervention may not be required following the approval of a unit of work.


In some implementations, user interface component 110 may be configured to update the user interface based on the update of the work unit records and/or other information. In some implementations, user interface component 110 may be configured to update the first work unit page to include indicia showing that the first unit of work has been approved. Such update may be responsive to the first work unit record specifying with the approve value for the approval state parameter of the first unit of work. Indicia showing that values of the approval state of individual units of work may include one or more of the visual representations. For example, the indicia showing that the first unit of work has been approved may include the first user interface element that corresponds to the approve value having a visual change in its appearance, e.g., change to a solid color. For example, the indicia showing that the first unit of work has been approved may include a green check icon and/or text specifying the user who approval the unit of work.


In some implementations, the work unit component 112 may be configured to update the first work unit record by specifying the revise value for the approval state parameter of the first unit of work. Such update may be responsive to obtaining second user input characterizing the selection of the second user interface element on the first work unit page of the first unit of work. In some implementations, user interface component 110 may be configured to update the first work unit page to include indicia showing that the first unit of work has been revised. Such update may be responsive to the first work unit record specifying the revise value for the approval state parameter of the first unit of work. For example, the indicia showing that the first unit of work has been revised may include the second user interface element that corresponds to the revise value having a visual change. For example, the indicia showing that the first unit of work has been revised may include a yellow arrow icon and/or text specifying the user who revised the unit of work.


In some implementations, the work unit component 112 may be configured to update the first work unit record by specifying the reject value for the approval state parameter of the first unit of work. Such update may be responsive to obtaining third user input characterizing the selection of the third user interface element on the first work unit page of the first unit of work. In some implementations, user interface component 110 may be configured to update the first work unit page to include indicia showing that the first unit of work has been rejected. Such update may be responsive to the first work unit record specifying the reject value for the approval state parameter of the first unit of work. For example, the indicia showing that the first unit of work has been rejected may include the second user interface element that corresponds to the revise value to have a visual change. For example, the indicia showing that the first unit of work has been reject may include a red arrow icon and/or text specifying the user who rejected the unit of work.


In some implementations, work unit component 112 may be configured to generate one or more work unit records based on the user input information and/or other information. Further, work unit component 112 may be configured to automatically assign individual ones of the individual units of work included in the one or more work unit records generated based on the user input information to individual users who are assignors of the individual units of work which are under approval.


In some implementations, updating the first work unit record to specify the revise value for the approval state parameter for the first unit of work may cause a second work unit record for a second unit of work to be generated. Work unit component 112 may be configured to generate the second work unit record for the second unit of work. In some implementations, the second work unit record may be subordinate to the first work unit record within a record hierarchy. In some implementations, the second work unit record may be at the position in the record hierarchy as the first work unit record. The second unit of work may describe revisions to be completed with respect to the first unit of work. The revisions may be input by the assignee of the first unit of work. The revisions may be input prior to or subsequently to the selection of the second user input element (corresponding to the revise value) on the first work unit page of the first unit of work. The revisions may be included in the unit of work description for the second unit of work and/or in the content of the comments. In some implementations, the second work unit record may automatically include a due date value. The due date value may be an amount of time prespecified by the administrative user and/or other users added to the due date and/or completion date of the first unit of work, and/or a current date. In some implementations, the second work unit record may not automatically include a due date value (i.e., the due date value requires user input).


In some implementations, responsive to obtaining the second user input characterizing the selection of the second user interface element on the first work unit page of the first unit of work, user interface component 110 may be configured to effectuation presentation of a set of recommended revision instructions on the first work unit page. By way of non-limiting example, the recommended revisions instructions included in the set may include one or more of an instruction to revise a title, an instruction to revise content of a digital content item, an instruction to revise a deadline or timeframe for the first unit of work, an instruction to revise users on a team related to the first unit of work, and/or other instructions. The set of recommended revision instructions presented may be modified and/or created by an administrative user and/or other users to adapt to use of the collaborative environment.


Work unit component 112 may be configured to obtain further user input including selection of one or more recommended revision instructions from the set of recommended revision instructions. The revisions to be completed as described in the second unit of work may include the one or more recommended revision instructions.


The second unit of work may be assigned to an assignor of the first unit of work. In some implementations, work unit component 112 may be configured to automatically assign individual ones of the individual units of work included in the one or more work unit records generated based on the user input information to individual users of a particular role. In some implementations, assignment may be dictated (e.g., changed from the automatic assignment, initially specified, etc.) by an assignee to other users as needed. By way of non-limiting illustration, the first user may assign the second unit of work to one or more other users as desired.


In some implementations, updating a work unit record to specify the revise value for the approval state parameter for a unit of work may cause the unit of work to be reassigned back to the assignor of the unit of work (alternatively and/or in addition to a new unit of work being generated and assigned to the original assignor). The revise value may be displayed within the work unit page for the unit of work by specifying, among other things, “changes requested.” The assignee may provide specific instructions in a comment section. The assignor may be notified that the unit of work was not approved, but instead that changes were requested. The assignor may then make the changes. Upon completion, the assignor may specify a value of the approval state as “pending approval” and/or other values. The value of pending approval may refer to a request for approval following a request for revisions/changes. The work unit record may be updated to specify the pending approval value for the approval state parameter. Specifying the pending approval value may cause the unit of work to be again reassigned back to the original assignee for “final” approval. The assignee may then select a value of the approval state (e.g., again requesting changes, marking as approval, rejecting, and/or other states).


In some implementations, the work unit component 112 may be configured to update the first work unit record by specifying the reject value for the approval state parameter of the first unit of work. Such update may be responsive to obtaining third user input characterizing the selection of the third user interface element on the first work unit page of the first unit of work. In some implementations, updating the first work unit record to specify the reject value for the approval state parameter may cause a value of the status parameter of a preexisting second work unit record of a (preexisting) second unit of work to be specified with a value of incomplete. The first work unit record may be subordinate to the preexisting second work unit record within the record hierarchy. The value of the status parameter of the preexisting second work unit record may have been previously specified with a value of complete. In some implementations, the preexisting second work unit record may automatically include an updated due date value. The updated due date value may be an amount of time prespecified by the administrative user and/or other users added to the due date and/or completion date of the first unit of work, and/or a current date. In some implementations, the preexisting second work unit record may not automatically include an updated due date value, rather the due date value requires user input or remains the same (i.e., the past due date).


In some implementations, user interface component 110 may be configured to update the first work unit page to include indicia showing the first unit of work has been rejected. Such update may be responsive to the first work unit record specifying the reject value for the approval state parameter of the first unit of work. For example, the indicia showing that the first unit of work has been rejected may include the third user interface element that corresponds to the reject value to be a solid red box instead of the red-outlined box. For example, the indicia showing that the first unit of work has been rejected may include a red “X” icon and text specifying the user who rejected the unit of work.


In some implementations, the user input information may convey user input characterizing the deselection of the individual user interface elements in the individual work unit pages. The deselection of an individual user interface element in an individual work unit page of an individual unit of work may cause the corresponding value of the approval state parameter to be unspecified for the individual unit of work and/or set to a default value (e.g., null value). For example, the first user may select the first user interface element and the approval state parameter of the first unit of work may specify the approve value and the first work unit page may include, for example, a green check icon. Subsequently, the first user may deselect the first user interface element and the value for the approval state parameter of the first unit of work may be unspecified. Accordingly, the first work unit page may no longer include the green check icon.


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, historical work information, and/or other information.



FIG. 3 illustrates a user interface 300, in accordance with one or more implementations. The user interface 300 may display a first unit of work. The user interface 300 may display different values of one or more work unit parameters of the first unit of work, and/or other information. By way of non-limiting illustration, a user interface element 302 may display a title of the first unit of work (e.g., Task X). A user interface element 304 may display an assignee of the first unit of work (e.g., User A). A user interface element 305 may display an assignor of the first unit of work (e.g., User B). A user interface element 306 may display a due date of the first unit of work. User interface elements 308a-308c may display approval states a user may select for the first unit of work. User interface element 308a may represent approval of the first unit of work. User interface element 308b may represent revise the first unit of work. User interface element 308c may represent rejection of the first unit of work. Upon the assignee, User A, selecting user interface element 308a, a user interface element 310 that shows the first unit of work has been completed may be displayed.



FIG. 4 illustrates user interface 400, in accordance with one or more implementations. The user interface 400 may display a second unit of work. The user interface 400 may display different values of one or more work unit parameters of the second unit of work, and/or other information. Simultaneously referring to FIG. 3, responsive to user selection of user interface element 308b to request revisions of the first unit of work (e.g., Task X), a second work unit record for the second unit of work may be generated and user interface 400 may be displayed as illustrated in user interface 400 of FIG. 4. By way of non-limiting illustration, user interface 400 may display a user interface element 402 that may display a title of the second unit of work (e.g., Task Y). A user interface element 406 may display a due date of the second unit of work. A user interface element 404 may display an assignee of the second unit of work. The second unit of work may be assigned to the assignor (i.e., User B) of the first unit of work, as displayed by user interface element 305 in FIG. 3 responsive to the selection of user interface element 308b. A user interface element 405 may display an assignor of the second unit of work (e.g., User A). The second unit of work may be assigned by the assignee of the first unit of work, as displayed by user interface element 304 in FIG. 3, responsive to the selection of user interface element 308b (i.e., responsive to User A requesting revisions). A user interface element 408 may display a description for the second unit of work. Revisions input by User A prior to or subsequent to selection of user interface element 308b may be displayed in user interface element 408.



FIG. 5 illustrates a user interface 500 and user interface 300, in accordance with one or more implementations. User interface 300 may be the same as or similar to user interface 300 in FIG. 3. User interface 300 may display the first unit of work. User interface 500 may display a preexisting third unit of work. The third unit of work may display different values of one or more work unit parameters of the third unit of work, and/or other information. By way of non-limiting illustration, user interface 500 may display a user interface element 502 that may display a title of the third unit of work (e.g., Task W). User interface element 504a and 504b may display a status (e.g., “Mark Complete”, “Complete”) of the third unit of work. Similar to FIG. 3, the first unit of work may display different values of one or more work unit parameters of the first unit of work, and/or other information. By way of non-limiting illustration, a user interface element 302 may display the title of the first unit of work (e.g., Task X). A user interface element 303 may display the title of the third unit of work (i.e., Task W) of which the first unit of work is subordinate to. Responsive to user selection of user interface element 308c to reject the first unit of work Task X, user interface element 504a of the third unit of work, “Completed”, may be updated to display user interface element 504b of the third unit of work, “Mark Complete”. In other words, a status of the third work unit record may be specified as incomplete and user interface 500 may display accordingly.


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


Referring back to 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, and/or 112, and/or other components. Processor(s) 130 may be configured to execute components 108, 110, and/or 112, 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, and/or 112 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, and/or 112 may be implemented remotely from the other components. The description of the functionality provided by the different components 108, 110, and/or 112 described below is for illustrative purposes, and is not intended to be limiting, as any of components 108, 110, and/or 112 may provide more or less functionality than is described. For example, one or more of components 108, 110, and/or 112 may be eliminated, and some or all of its functionality may be provided by other ones of components 108, 110, and/or 112. 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, and/or 112.



FIG. 2 illustrates a method 200 to facilitate user engagement with units of work assigned within a collaboration environment, 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 describing units of work assigned to individual users within the collaboration environment. The work unit records may include values of an approval state parameter. The values of the approval state parameter including an approve value, a revise value, and a reject value, the work unit records including a first work unit record for a first unit 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 effectuate presentation of a user interface (of the collaboration environment) displaying individual work unit pages that may include a set of user interface elements available for selection by the users. Individual user interface elements in the set may correspond to different ones of the values of the approval state parameter. 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 user interface component 110, in accordance with one or more implementations.


An operation 206 may obtain user input information conveying user input characterizing the selection of the individual user interface elements in the individual work unit pages. 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 work unit component 112, in accordance with one or more implementations.


An operation 208 may update the work unit records based on the user input information. Operation 208 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 work unit 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 facilitate user engagement with work unit records of a collaboration environment, the system comprising: one or more physical processors configured by machine-readable instructions to: manage, at a server, electronically stored environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by users with the collaboration environment, a first user interacting with the collaboration environment via a first remotely located client computing platform communicating with the server over an Internet connection, the environment state information including a first work unit record for a first unit of work involving review of a first digital content item, the first work unit record including a value of an approval state parameter, the approval state parameter characterizing approval of the first unit of work by the first user, values of the approval state parameter including an approve value, a revise value conveying a request to generate changes to the first digital content item, and a reject value;establish the Internet connection between the first remotely located client computing platform and the server;effectuate communication of information from the server to the first remotely located client computing platform so that the first remotely located client computing platform presents a user interface of the collaboration environment, the user interface displaying a first work unit page for the first unit of work, the first work unit page including a set of user interface elements available for selection, individual user interface elements in the set of user interface elements corresponding to different ones of the values of the approval state parameter;obtain, at the server, user input information conveying user input into the first remotely located client computing platform characterizing the selection of the individual user interface elements in the first work unit page, the selection of an individual user interface element causing a corresponding value of the approval state parameter to be specified for the first work unit record; andupdate, at the server, the first work unit record based on the user input information, such that: responsive to the user input information conveying a first selection of a first user interface element on the first work unit page, update the first work unit record by specifying the approve value as the value for the approval state parameter of the first work unit record;responsive to the user input information conveying a second selection of a second user interface element on the first work unit page, update the first work unit record by specifying the revise value as the value for the approval state parameter of the first work unit record, the revise value conveying a first request to generate one or more changes to the first digital content item; andresponsive to the user input information conveying a third selection of a third user interface element on the first work unit page, update the first work unit record by specifying the reject value as the value for the approval state parameter of the first work unit record.
  • 2. The system of claim 1, wherein updating the first work unit record to specify the approve value as the value for the approval state parameter causes a status value of a status parameter of the first work unit record to be specified with the status value of complete.
  • 3. The system of claim 1, wherein updating the first work unit record to specify the revise value as the value for the approval state parameter for the first work unit record causes: a second work unit record for a second unit of work to be generated, the second unit of work being assigned to an assignor of the first unit of work, and describing the one or more changes.
  • 4. The system of claim 3, wherein a description of the one or more changes are input by an assignee of the first unit of work.
  • 5. The system of claim 3, wherein the one or more physical processors are further configured by the machine-readable instructions to: responsive to obtaining the user input information conveying the second selection of the second user interface element, effectuate presentation of a set of recommended revision instructions on the first work unit page;obtain further user input including selection of one or more recommended revision instructions from the set of recommended revision instructions; andwherein the one or more changes as described in the second work unit record include the one or more recommended revision instructions.
  • 6. The system of claim 1, wherein updating the first work unit record to specify the reject value as the value for the approval state parameter causes: a status value of a status parameter of a preexisting second work unit record for a second unit of work to be specified with the status value of incomplete, wherein the first work unit record is subordinate to the second work unit record within a record hierarchy, and wherein the status value of the status parameter of the second work unit record was previously specified with the status value of complete.
  • 7. The system of claim 1, wherein the one or more physical processors are further configured by the machine-readable instructions to: update the user interface based on the update of the first work unit record, such that: responsive to the first work unit record specifying the approve value as the value for the approval state parameter of the first unit of work, update the first work unit page to include indicia showing that the first unit of work has been approved;responsive to the first work unit record specifying the revise value as the value for the approval state parameter of the first unit of work, update the first work unit page to include indicia showing that the first unit of work requires revision; andresponsive to the first work unit record specifying the reject value as the value for the approval state parameter of the first unit of work, update the first work unit page to include indicia showing the first unit of work has been rejected.
  • 8. The system of claim 1, wherein the first work unit page includes an instance of the first digital content item.
  • 9. The system of claim 8, wherein the first digital content item comprises one or more of an image, a video, an audio file, a PDF, or a word document.
  • 10. The system of claim 1, wherein the first work unit record is subordinate to a second work unit record.
  • 11. A method to facilitate user engagement with work unit records of a collaboration environment, the method comprising: managing, at a server, electronically stored environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by users with the collaboration environment, a first user interacting with the collaboration environment via a first remotely located client computing platform communicating with the server over an Internet connection, the environment state information including a first work unit record for a first unit of work involving review of a first digital content item, the first work unit record including a value of an approval state parameter, the approval state parameter characterizing approval of the first unit of work by the first user, values of the approval state parameter including an approve value, a revise value conveying a request to generate changes to the first digital content item, and a reject value;establishing the Internet connection between the first remotely located client computing platform and the server;effectuating communication of information from the server to the first remotely located client computing platform so that the first remotely located client computing platform presents a user interface of the collaboration environment, the user interface displaying a first work unit page for the first unit of work, the first work unit page including a set of user interface elements available for selection, individual user interface elements in the set of user interface elements corresponding to different ones of the values of the approval state parameter;obtaining, at the server, user input information conveying user input into the first remotely located client computing platform characterizing the selection of the individual user interface elements in the first work unit page, the selection of an individual user interface element causing a corresponding value of the approval state parameter to be specified for the first work unit record; andupdating, at the server, the first work unit record based on the user input information, including: responsive to the user input information conveying a first selection of a first user interface element on the first work unit page, updating the first work unit record by specifying the approve value as the value for the approval state parameter of the first work unit record;responsive to the user input information conveying a second selection of a second user interface element on the first work unit page, updating the first work unit record by specifying the revise value as the value for the approval state parameter of the first work unit record, the revise value conveying a first request to generate one or more changes to the first digital content item; andresponsive to the user input information conveying a third selection of a third user interface element on the first work unit page, updating the first work unit record by specifying the reject value as the value for the approval state parameter of the first work unit record.
  • 12. The method of claim 11, wherein the updating the first work unit record to specify the approve value as the value for the approval state parameter causes a status value of a status parameter of the first work unit record to be specified with the status value of complete.
  • 13. The method of claim 11, wherein the updating the first work unit record to specify the revise value as the value for the approval state parameter for the first work unit record causes the method to further perform: generating a second work unit record for a second unit of work, the second unit of work being assigned to an assignor of the first unit of work, and describing the one or more changes.
  • 14. The method of claim 13, wherein a description of the one or more changes are input by an assignee of the first unit of work.
  • 15. The method of claim 13, further comprising: responsive to obtaining the user input information conveying the second selection of the second user interface element, effectuating presentation of a set of recommended revision instructions on the first work unit page;obtaining further user input including selection of one or more recommended revision instructions from the set of recommended revision instructions; andwherein the one or more changes as described in the second work unit record include the one or more recommended revision instructions.
  • 16. The method of claim 11, wherein the updating the first work unit record to specify the reject value as the value for the approval state parameter causes the method to further perform: specifying a status value of a status parameter of a preexisting second work unit record for a second unit of work with the status value of incomplete, wherein the first work unit record is subordinate to the second work unit record within a record hierarchy, and wherein the status value of the status parameter of the second work unit record was previously specified with the status value of complete.
  • 17. The method of claim 11, further comprising: updating the user interface based on the update of the first work unit record, such that: responsive to the first work unit record specifying the approve value as the value for the approval state parameter of the first unit of work, updating the first work unit page to include indicia showing that the first unit of work has been approved;responsive to the first work unit record specifying the revise value as the value for the approval state parameter of the first unit of work, updating the first work unit page to include indicia showing that the first unit of work requires revision; andresponsive to the first work unit record specifying the reject value as the value for the approval state parameter of the first unit of work, updating the first work unit page to include indicia showing the first unit of work has been rejected.
  • 18. The method of claim 11, wherein the first work unit page includes an instance of the first digital content item.
  • 19. The method of claim 18, wherein the first digital content item comprises one or more of an image, a video, an audio file, a PDF, or a word document.
  • 20. The method of claim 11, wherein the first work unit record is subordinate to a second work unit record.
US Referenced Citations (496)
Number Name Date Kind
5233687 Henderson, Jr. Aug 1993 A
5524077 Faaland Jun 1996 A
5530861 Diamant Jun 1996 A
5548506 Srinivasan Aug 1996 A
5608898 Turpin Mar 1997 A
5611076 Durflinger Mar 1997 A
5623404 Collins Apr 1997 A
5721770 Kohler Feb 1998 A
5983277 Heile Nov 1999 A
6024093 Cron Feb 2000 A
6256651 Tuli Jul 2001 B1
6292830 Taylor Sep 2001 B1
6332147 Moran Dec 2001 B1
6385639 Togawa May 2002 B1
6578004 Cimral Jun 2003 B1
6621505 Beauchamp Sep 2003 B1
6629081 Cornelius Sep 2003 B1
6769013 Frees Jul 2004 B2
6859523 Jilk Feb 2005 B1
7020697 Goodman Mar 2006 B1
7039596 Lu May 2006 B1
7086062 Faour Aug 2006 B1
7349920 Feinberg Mar 2008 B1
7418482 Lusher Aug 2008 B1
7428723 Greene Sep 2008 B2
7640511 Keel Dec 2009 B1
7676542 Moser Mar 2010 B2
7779039 Weissman Aug 2010 B2
7805327 Schulz Sep 2010 B1
RE41848 Daniell Oct 2010 E
7917855 Satish Mar 2011 B1
7991632 Morris Aug 2011 B1
7996744 Ojala Aug 2011 B2
7996774 Sidenur Aug 2011 B1
8214747 Yankovich Jul 2012 B1
8314809 Grabowski Nov 2012 B1
8499300 Zimberg Jul 2013 B2
8522240 Merwarth Aug 2013 B1
8527287 Bhatia Sep 2013 B1
8554832 Moskovitz Oct 2013 B1
8572477 Moskovitz Oct 2013 B1
8627199 Handley Jan 2014 B1
8639552 Chen Jan 2014 B1
8768751 Jakowski Jul 2014 B2
8831879 Stamm Sep 2014 B2
8843832 Frields Sep 2014 B2
8863021 Bee Oct 2014 B1
9009096 Pinckney Apr 2015 B2
9024752 Tumayan May 2015 B2
9143839 Reisman Sep 2015 B2
9152668 Moskovitz Oct 2015 B1
9201952 Chau Dec 2015 B1
9208262 Bechtel Dec 2015 B2
9251484 Cantor Feb 2016 B2
9350560 Hupfer May 2016 B2
9383917 Mouton Jul 2016 B2
9405532 Sullivan Aug 2016 B1
9405810 Smith Aug 2016 B2
9454623 Kaptsan Sep 2016 B1
9514424 Kleinbart Dec 2016 B2
9600136 Yang Mar 2017 B1
9674361 Ristock Jun 2017 B2
9712576 Gill Jul 2017 B1
9785445 Mitsui Oct 2017 B2
9830398 Schneider Nov 2017 B2
9842312 Rosati Dec 2017 B1
9949681 Badenes Apr 2018 B2
9953282 Shaouy Apr 2018 B2
9959420 Kiang May 2018 B2
9978040 Lee May 2018 B2
9990636 Lewis Jun 2018 B1
10001911 Breedvelt-Schouten Jun 2018 B2
10003693 Wolthuis Jun 2018 B2
10083412 Suntinger Sep 2018 B2
10157355 Johnson Dec 2018 B2
10192181 Katkar Jan 2019 B2
10235156 Johnson Mar 2019 B2
10264067 Subramani Apr 2019 B2
10308992 Chauvin Jun 2019 B2
10373084 Kurjanowicz Aug 2019 B2
10373090 Holm Aug 2019 B2
10382501 Malatesha Aug 2019 B2
10455011 Kendall Oct 2019 B2
10496943 De Dec 2019 B2
10586211 Steplyk Mar 2020 B2
10594788 Larabie-Belanger Mar 2020 B2
10606859 Smith Mar 2020 B2
10613735 Karpe Apr 2020 B1
10616151 Cameron Apr 2020 B1
10623359 Rosenstein Apr 2020 B1
10671692 Koopman Jun 2020 B2
10684870 Sabo Jun 2020 B1
10706484 Murnock Jul 2020 B1
10785046 Raghavan Sep 2020 B1
10810222 Koch Oct 2020 B2
10846105 Granot Nov 2020 B2
10846297 Smith Nov 2020 B2
10922104 Sabo Feb 2021 B2
10956845 Sabo Mar 2021 B1
10970299 Smith Apr 2021 B2
10977434 Pelz Apr 2021 B2
10983685 Karpe Apr 2021 B2
11082281 Rosenstein Aug 2021 B2
11095468 Pandey Aug 2021 B1
11113667 Jiang Sep 2021 B1
11138021 Rosenstein Oct 2021 B1
11140174 Patel Oct 2021 B2
11204683 Sabo Dec 2021 B1
11212242 Cameron Dec 2021 B2
11263228 Koch Mar 2022 B2
11288081 Sabo Mar 2022 B2
11290296 Raghavan Mar 2022 B2
11327645 Karpe May 2022 B2
11341444 Sabo May 2022 B2
11341445 Cheng May 2022 B1
20020065798 Bostleman May 2002 A1
20020082889 Oliver Jun 2002 A1
20020143594 Kroeger Oct 2002 A1
20030028595 Vogt Feb 2003 A1
20030036934 Ouchi Feb 2003 A1
20030041317 Sokolov Feb 2003 A1
20030097406 Stafford May 2003 A1
20030097410 Atkins May 2003 A1
20030126001 Northcutt Jul 2003 A1
20030200223 Hack Oct 2003 A1
20030225598 Yu Dec 2003 A1
20030233265 Lee Dec 2003 A1
20030233268 Taqbeem Dec 2003 A1
20040083448 Schulz Apr 2004 A1
20040093290 Doss May 2004 A1
20040093351 Lee May 2004 A1
20040098291 Newburn May 2004 A1
20040122693 Hatscher Jun 2004 A1
20040125150 Adcock Jul 2004 A1
20040162833 Jones Aug 2004 A1
20040187089 Schulz Sep 2004 A1
20040207249 Baumgartner Oct 2004 A1
20040230447 Schwerin-Wenzel Nov 2004 A1
20040268451 Robbin Dec 2004 A1
20050027582 Chereau Feb 2005 A1
20050210394 Crandall Sep 2005 A1
20050216111 Ooshima Sep 2005 A1
20050222971 Cary Oct 2005 A1
20060028917 Wigginton Feb 2006 A1
20060047454 Tamaki Mar 2006 A1
20060085245 Takatsuka Apr 2006 A1
20060095859 Booking May 2006 A1
20060136441 Fujisaki Jun 2006 A1
20060143270 Wodtke Jun 2006 A1
20060167736 Weiss Jul 2006 A1
20060190391 Cullen, III Aug 2006 A1
20060200264 Kodama Sep 2006 A1
20060218551 Berstis Sep 2006 A1
20060224430 Butt Oct 2006 A1
20060277487 Poulsen Dec 2006 A1
20070016646 Tendjoukian Jan 2007 A1
20070025567 Fehr Feb 2007 A1
20070038494 Kreitzberg Feb 2007 A1
20070041542 Schramm Feb 2007 A1
20070050225 Leslie Mar 2007 A1
20070073575 Yomogida Mar 2007 A1
20070143169 Grant Jun 2007 A1
20070147178 Masuda Jun 2007 A1
20070150327 Dromgold Jun 2007 A1
20070232278 May Oct 2007 A1
20070255674 Mahoney Nov 2007 A1
20070255715 Li Nov 2007 A1
20070260499 Greef Nov 2007 A1
20070288283 Fitzpatrick Dec 2007 A1
20070294344 Mohan Dec 2007 A1
20080033777 Shukoor Feb 2008 A1
20080046471 Moore Feb 2008 A1
20080079730 Zhang Apr 2008 A1
20080082389 Gura Apr 2008 A1
20080082956 Gura Apr 2008 A1
20080091782 Jakobson Apr 2008 A1
20080120129 Seubert May 2008 A1
20080126930 Scott May 2008 A1
20080134069 Horvitz Jun 2008 A1
20080155547 Weber Jun 2008 A1
20080158023 Chung Jul 2008 A1
20080167937 Coughlin Jul 2008 A1
20080175104 Grieb Jul 2008 A1
20080195964 Randell Aug 2008 A1
20080221946 Balon Sep 2008 A1
20080222566 Daughtrey Sep 2008 A1
20080244582 Brown Oct 2008 A1
20080268876 Gelfand Oct 2008 A1
20080270198 Graves Oct 2008 A1
20080281665 Opaluch Nov 2008 A1
20080313004 Ryan Dec 2008 A1
20080313110 Kreamer Dec 2008 A1
20090048986 Anderson Feb 2009 A1
20090055796 Springborn Feb 2009 A1
20090076878 Woerner Mar 2009 A1
20090089133 Johnson Apr 2009 A1
20090094623 Chakra Apr 2009 A1
20090113310 Appleyard Apr 2009 A1
20090133027 Gunning May 2009 A1
20090167553 Hong Jul 2009 A1
20090187454 Khasin Jul 2009 A1
20090199113 McWhinnie Aug 2009 A1
20090199192 Laithwaite Aug 2009 A1
20090204463 Burnett Aug 2009 A1
20090204471 Elenbaas Aug 2009 A1
20090234699 Steinglass Sep 2009 A1
20090235182 Kagawa Sep 2009 A1
20090241053 Augustine Sep 2009 A1
20090260010 Burkhart Oct 2009 A1
20090287523 Lau Nov 2009 A1
20090296908 Lee Dec 2009 A1
20090299803 Lakritz Dec 2009 A1
20090307319 Dholakia Dec 2009 A1
20100005087 Basco Jan 2010 A1
20100070888 Watabe Mar 2010 A1
20100088137 Weiss Apr 2010 A1
20100106627 O'Sullivan Apr 2010 A1
20100114786 Aboujaoude May 2010 A1
20100115523 Kuschel May 2010 A1
20100122334 Stanzione May 2010 A1
20100131860 Dehaan May 2010 A1
20100145801 Chekuri Jun 2010 A1
20100169146 Hoyne Jul 2010 A1
20100169802 Goldstein Jul 2010 A1
20100180212 Gingras Jul 2010 A1
20100223575 Leukart Sep 2010 A1
20100269049 Fearon Oct 2010 A1
20100299171 Lau Nov 2010 A1
20100306007 Ganapathyraj Dec 2010 A1
20100312605 Mitchell Dec 2010 A1
20100313151 Wei Dec 2010 A1
20110015961 Chan Jan 2011 A1
20110022662 Barber-Mingo Jan 2011 A1
20110054968 Galaviz Mar 2011 A1
20110055177 Chakra Mar 2011 A1
20110060720 Devereux Mar 2011 A1
20110071878 Gingras Mar 2011 A1
20110071893 Malhotra Mar 2011 A1
20110072372 Fritzley Mar 2011 A1
20110093538 Weir Apr 2011 A1
20110093619 Nelson Apr 2011 A1
20110113365 Kimmerly May 2011 A1
20110154216 Aritsuka Jun 2011 A1
20110161128 Barney Jun 2011 A1
20110184768 Norton Jul 2011 A1
20110270644 Roncolato Nov 2011 A1
20110307100 Schmidtke Dec 2011 A1
20110307772 Lloyd Dec 2011 A1
20120030194 Jain Feb 2012 A1
20120035942 Graupner Feb 2012 A1
20120066030 Limpert Mar 2012 A1
20120066411 Jeide Mar 2012 A1
20120072251 Mircean Mar 2012 A1
20120079449 Sanderson Mar 2012 A1
20120110087 Culver May 2012 A1
20120117499 Mori May 2012 A1
20120123835 Chu May 2012 A1
20120131191 May May 2012 A1
20120158946 Shafiee Jun 2012 A1
20120192086 Ghods Jul 2012 A1
20120221963 Motoyama Aug 2012 A1
20120239451 Caligor Sep 2012 A1
20120254218 Ali Oct 2012 A1
20120266068 Ryman Oct 2012 A1
20120278388 Kleinbart Nov 2012 A1
20120296993 Heyman Nov 2012 A1
20120304187 Maresh Nov 2012 A1
20120317108 Okazaki Dec 2012 A1
20130007332 Teh Jan 2013 A1
20130013560 Goldberg Jan 2013 A1
20130014023 Lee Jan 2013 A1
20130018688 Nudd Jan 2013 A1
20130021629 Kurilin Jan 2013 A1
20130066944 Laredo Mar 2013 A1
20130067375 Kim Mar 2013 A1
20130067549 Caldwell Mar 2013 A1
20130073328 Ehrler Mar 2013 A1
20130080919 Kiang Mar 2013 A1
20130103412 Nudd Apr 2013 A1
20130124254 Jafri May 2013 A1
20130124638 Barreto May 2013 A1
20130151421 Van Der Ploeg Jun 2013 A1
20130151604 Ranade Jun 2013 A1
20130173486 Peters Jul 2013 A1
20130179208 Chung Jul 2013 A1
20130179799 Savage Jul 2013 A1
20130215116 Siddique Aug 2013 A1
20130227007 Savage Aug 2013 A1
20130246110 Nakhayi Ashtiani Sep 2013 A1
20130246399 Schneider Sep 2013 A1
20130275229 Moganti Oct 2013 A1
20130279685 Kohler Oct 2013 A1
20130317871 Kulkarni Nov 2013 A1
20130321467 Tappen Dec 2013 A1
20130339099 Aidroos Dec 2013 A1
20130339831 Gulanikar Dec 2013 A1
20140007005 Libin Jan 2014 A1
20140012603 Scanlon Jan 2014 A1
20140012616 Moshenek Jan 2014 A1
20140025767 De Kezel Jan 2014 A1
20140036639 Taber Feb 2014 A1
20140040780 Artzt Feb 2014 A1
20140040905 Tadanobu Feb 2014 A1
20140058801 Deodhar Feb 2014 A1
20140059910 Norton Mar 2014 A1
20140074536 Meushar Mar 2014 A1
20140089719 Daum Mar 2014 A1
20140101310 Savage Apr 2014 A1
20140156539 Brunet Jun 2014 A1
20140165001 Shapiro Jun 2014 A1
20140172478 Vadasz Jun 2014 A1
20140189017 Prakash Jul 2014 A1
20140200944 Henriksen Jul 2014 A1
20140208325 Chen Jul 2014 A1
20140215344 Ligman Jul 2014 A1
20140229609 Wong Aug 2014 A1
20140236663 Smith Aug 2014 A1
20140244334 De Aug 2014 A1
20140257894 Melahn Sep 2014 A1
20140279294 Field-Darragh Sep 2014 A1
20140288987 Liu Sep 2014 A1
20140310047 De Oct 2014 A1
20140310051 Meng Oct 2014 A1
20140350997 Holm Nov 2014 A1
20140364987 Shikano Dec 2014 A1
20150006448 Gupta Jan 2015 A1
20150007058 Wooten Jan 2015 A1
20150012330 Sugiura Jan 2015 A1
20150052437 Crawford Feb 2015 A1
20150058053 De Feb 2015 A1
20150113540 Rabinovici Apr 2015 A1
20150134393 De May 2015 A1
20150153906 Liao Jun 2015 A1
20150213411 Swanson Jul 2015 A1
20150215256 Ghafourifar Jul 2015 A1
20150262111 Yu Sep 2015 A1
20150312375 Valey Oct 2015 A1
20150317595 De Nov 2015 A1
20150339006 Chaland Nov 2015 A1
20150363092 Morton Dec 2015 A1
20150363733 Brown Dec 2015 A1
20150379472 Gilmour Dec 2015 A1
20160012368 O'Connell Jan 2016 A1
20160048408 Madhu Feb 2016 A1
20160048786 Fukuda Feb 2016 A1
20160063192 Johnson Mar 2016 A1
20160063449 Duggan Mar 2016 A1
20160072750 Kass Mar 2016 A1
20160110670 Chatterjee Apr 2016 A1
20160124775 Ashtiani May 2016 A1
20160140474 Vekker May 2016 A1
20160140501 Figlin May 2016 A1
20160147773 Smith May 2016 A1
20160147846 Smith May 2016 A1
20160148157 Walia May 2016 A1
20160180277 Skiba Jun 2016 A1
20160180298 McClement Jun 2016 A1
20160182311 Borna Jun 2016 A1
20160188145 Vida Jun 2016 A1
20160216854 McClellan Jul 2016 A1
20160224939 Chen Aug 2016 A1
20160234391 Wolthuis Aug 2016 A1
20160275436 Kurjanowicz Sep 2016 A1
20160307210 Agarwal Oct 2016 A1
20160313934 Isherwood Oct 2016 A1
20160328217 Hagerty Nov 2016 A1
20160342927 Reznik Nov 2016 A1
20170004213 Cunico Jan 2017 A1
20170009387 Ge Jan 2017 A1
20170017364 Kekki Jan 2017 A1
20170017924 Kashiwagi Jan 2017 A1
20170039503 Jones Feb 2017 A1
20170061341 Haas Mar 2017 A1
20170068933 Norton Mar 2017 A1
20170093874 Uthe Mar 2017 A1
20170099296 Fisher Apr 2017 A1
20170103369 Thompson Apr 2017 A1
20170116552 Deodhar Apr 2017 A1
20170132200 Noland May 2017 A1
20170147960 Jahagirdar May 2017 A1
20170153799 Hoyer Jun 2017 A1
20170154024 Subramanya Jun 2017 A1
20170177671 Allgaier Jun 2017 A1
20170185592 Frei Jun 2017 A1
20170192642 Fishman Jul 2017 A1
20170206217 Deshpande Jul 2017 A1
20170206501 Wang Jul 2017 A1
20170249577 Nishikawa Aug 2017 A1
20170316358 Candito Nov 2017 A1
20170316367 Candito Nov 2017 A1
20170317898 Candito Nov 2017 A1
20170323233 Bencke Nov 2017 A1
20170323267 Baek Nov 2017 A1
20170323350 Laderer Nov 2017 A1
20170337517 Defusco Nov 2017 A1
20170344754 Kumar Nov 2017 A1
20170346861 Pearl Nov 2017 A1
20170351385 Ertmann Dec 2017 A1
20170364214 Javed Dec 2017 A1
20180032524 Byron Feb 2018 A1
20180052943 Hui Feb 2018 A1
20180053127 Boileau Feb 2018 A1
20180059910 Wooten Mar 2018 A1
20180060785 Carnevale Mar 2018 A1
20180060818 Ishiyama Mar 2018 A1
20180063063 Yan Mar 2018 A1
20180068271 Abebe Mar 2018 A1
20180075387 Kulkarni Mar 2018 A1
20180082255 Rosati Mar 2018 A1
20180088754 Psenka Mar 2018 A1
20180089625 Rosati Mar 2018 A1
20180095938 Monte Apr 2018 A1
20180102989 Borsutsky Apr 2018 A1
20180131649 Ma May 2018 A1
20180157477 Johnson Jun 2018 A1
20180165610 Dumant Jun 2018 A1
20180173386 Adika Jun 2018 A1
20180189706 Newhouse Jul 2018 A1
20180189735 Lo Jul 2018 A1
20180189736 Guo Jul 2018 A1
20180225795 Napoli Aug 2018 A1
20180247352 Rogers Aug 2018 A1
20180260081 Beaudoin Sep 2018 A1
20180262620 Wolthuis Sep 2018 A1
20180285471 Hao Oct 2018 A1
20180300305 Lam Oct 2018 A1
20180316636 Kamat Nov 2018 A1
20180331842 Faulkner Nov 2018 A1
20180357049 Epstein Dec 2018 A1
20180367477 Hariram Dec 2018 A1
20180367483 Rodriguez Dec 2018 A1
20180373804 Zhang Dec 2018 A1
20190005048 Crivello Jan 2019 A1
20190014070 Mertvetsov Jan 2019 A1
20190018552 Bloy Jan 2019 A1
20190034057 Rudchenko Jan 2019 A1
20190068390 Gross Feb 2019 A1
20190079909 Purandare Mar 2019 A1
20190080289 Kreitler Mar 2019 A1
20190089581 Purandare Mar 2019 A1
20190095839 Itabayashi Mar 2019 A1
20190095846 Gupta Mar 2019 A1
20190102700 Babu Apr 2019 A1
20190138583 Silk May 2019 A1
20190138589 Udell May 2019 A1
20190138961 Santiago May 2019 A1
20190139004 Vukovic May 2019 A1
20190147386 Balakrishna May 2019 A1
20190187987 Fauchère Jun 2019 A1
20190213509 Burleson Jul 2019 A1
20190265821 Pearl Aug 2019 A1
20190340296 Cunico Nov 2019 A1
20190340554 Dotan-Cohen Nov 2019 A1
20190340574 Ekambaram Nov 2019 A1
20190347094 Sullivan Nov 2019 A1
20190347126 Bhandari Nov 2019 A1
20190370320 Kalra Dec 2019 A1
20200019907 Notani Jan 2020 A1
20200059539 Wang Feb 2020 A1
20200065736 Relangi Feb 2020 A1
20200145239 Ghods May 2020 A1
20200162315 Siddiqi May 2020 A1
20200192538 Karpe Jun 2020 A1
20200192908 Smith Jun 2020 A1
20200193556 Jin Jun 2020 A1
20200218551 Sabo Jul 2020 A1
20200228474 Cameron Jul 2020 A1
20200233879 Papanicolaou Jul 2020 A1
20200244611 Rosenstein Jul 2020 A1
20200328906 Raghavan Oct 2020 A1
20200344253 Kurup Oct 2020 A1
20210004380 Koch Jan 2021 A1
20210004381 Smith Jan 2021 A1
20210035069 Parikh Feb 2021 A1
20210049555 Shor Feb 2021 A1
20210073697 Paranjape Mar 2021 A1
20210097466 Sabo Apr 2021 A1
20210097490 Ratcliff Apr 2021 A1
20210103451 Sabo Apr 2021 A1
20210110347 Khalil Apr 2021 A1
20210136012 Barbitta May 2021 A1
20210149925 Mann May 2021 A1
20210182475 Pelz Jun 2021 A1
20210216562 Smith Jul 2021 A1
20210232282 Karpe Jul 2021 A1
20210320891 Rosenstein Oct 2021 A1
20210342361 Radzewsky Nov 2021 A1
20210342786 Jiang Nov 2021 A1
20210382734 Rosenstein Dec 2021 A1
20220019320 Sabo Jan 2022 A1
20220019959 Roy Jan 2022 A1
20220058548 Garg Feb 2022 A1
20220075792 Koch Mar 2022 A1
20220078142 Cameron Mar 2022 A1
20220158859 Raghavan May 2022 A1
20220215315 Sabo Jul 2022 A1
Foreign Referenced Citations (8)
Number Date Country
101305350 Nov 2008 CN
101563671 Oct 2009 CN
102378975 May 2015 CN
2008059035 Mar 2008 JP
2015036817 Mar 2015 WO
2015123751 Aug 2015 WO
2016115621 Jul 2016 WO
2020006634 Jan 2020 WO
Non-Patent Literature Citations (51)
Entry
N. C. Romano, Fang Chen and J. F. Nunamaker, “Collaborative Project Management Software,” Proceedings of the 35th Annual Hawaii International Conference on System Sciences, 2002, pp. 233-242, doi: 10.1109/HICSS.2002.993878.
“U.S. Appl. No. 14/584,750, Examiner Interview Summary dated Feb. 25, 2016”, 3 pgs.
“U.S. Appl. No. 14/584,750, Non Final Office Action dated Aug. 28, 2015”, 21 pgs.
“U.S. Appl. No. 14/584,750, Notice of Allowance dated Mar. 28, 2016”, 8 pgs.
“U.S. Appl. No. 14/584,750, Response filed Feb. 29, 2015 to Non Final Office Action dated Aug. 28, 2015”, 16 pgs.
“U.S. Appl. No. 14/584,850, Final Office Action dated Sep. 1, 2017”, 31 pgs.
“U.S. Appl. No. 14/584,850, Non Final Office Action dated Jan. 10, 2017”, 9 pgs.
“U.S. Appl. No. 14/584,850, Response filed Apr. 10, 2017 to Non Final Office Action dated Jan. 10, 2017”, 13 pgs.
“How to Asana: Inviting teammates to Asana.” YouTube, Asana, Mar. 21, 2017, https://www.youtube.com/watch?v=TLOruY1KyxU ( Year: 2017), 13 pages.
“Rules of Data Conversion from Document to Relational Databases”, published: 2014, publisher: Future-processing, pp. 1-8 (Year: 2014).
(Tiburca, Andrew) Best Team Calendar Applications for 2018—Toggl https://toggl.com/blog/best-team-calendar-applications-for-2018 (Year: 2017).
Asana Demo and Product Tour, you tube excerpt, Dec. 7, 2017 https://www.youtube.com/watch?v=IMAFWVLGFyw (Year: 2017) (16 pages).
Asana integrations, Asana tutorial, youtube, excerpt, Nov. 16, 2016 https://www.youtube.com/watch?v=hBiQ7DJNinE (Year: 2016) (21 pages).
Asana Workload and Portfolios,youtube,excerpt, Aug. 1, 2019 https://www.youtube.com/watch?v=7XkNcfFDG6M (Year: 2019) (20 pages).
Asana YouTube channel, list of all product videos, Nov 19, 2014-Aug. 19, 2019 https://www.youtube.com/user/AsanaTeam/videos?disable_polymer=1 (Year: 2019) (5 pages).
Asana, Task dependencies, archives org, Aug. 25, 2017 https://web.archive.org/web/20170825002141/https://asana.com/guide/help/tasks/dependencies (Year: 2017) (5 pages).
Asana, Manage your team capacity with Workload, youtube, excerpt, Aug. 1, 2019 https://www.youtube.com/watch?v=2ufXyZDzZnA&list=PLJFG93oi0wJAi UwyOhlGWHdtJzJrzylBv (Year: 2019) (1 page).
Assef, F., Cassius, T. S., & Maria, T. S. (2018). Confrontation between techniques of time measurement. Journal of Manufacturing Technology Management, 29(5), 789-810. (Year: 2018).
Biggs, “GateGuru Relaunches With New Ways to Streamline Your Travel Experience”, Techcrunch, (Apr. 26, 2013), 3 pgs.
Castaneda Samuel, Introduction Manual—Asana, Sep. 25, 2017 https://static1.squarespace.com/static/586d532ae58c6232db243a65/t/5c210c10f950b7fc7a8e3274/1545669658049/Asana+Manual.pdf (Year: 2017) (20 pages).
Command and control, Wikipedia, archives org, Mar. 16, 2018 https://web.archive.org/web/20180316193655/https://en.wikipedia.org/wiki/Command_and_control (Year: 2018), 6 pages.
Creating Tables with Fields from 2 Different Tables, published: 2009, publisher: StackOverflow, pp. 1-2. (Year: 2009).
Critical chain project management, Wikipedia, archives org, Dec. 17, 2016 https://web.archive.Org/web/20161217090326/https://en.wikipedia.org/wiki/Critical_chain_project_management (Year: 2016) 5 pages.
Critical Path Method, Wikipedia, archives org, Sep. 19, 2017 https://web.archive.Org/web/20170919223814/https://en.wikipedia.org/wiki/Critical_path_method (Year: 2017) 6 pages.
Dawei Li, “Deepcham: Collaborative Edge-Mediated Adaptive Deep Learning for Mobile Object Recognition”, 2016, IEEE/ACM, pp. 64-76 (Year: 2016).
Fruhlinger, Joshua. “The Best To-Do ListApps for Feeling Productive; With the right app, feeling productive can be just as gratifying as actually getting things done” Wall Street Journal (Online); New York, N.Y. [New York, N.Y]Nov. 8, 2013 (Year: 2013) 4 pages.
Hartmann, “TimeProjectscheduling with resource capacities and requests varying with time: a case study,” 2013, Flexible services and manufacturing journal, vol. 25, No. 1, pp. 74-93 (Year: 2013).
Helen Mongan-Rallis & Terrie Shannon, “Synchronous Chat,” Aug. 2016, Dept. of Education, Univ. of MN Duluth, web. archive.org/web/20160825183503/https://www.d.umn.edu/hrallis/professional/presentations/cotfsp06/indiv_tools/sync_chat.htm (Year: 2016) (2 pages).
How to Asana Asana time tracking, youtube, excerpt, May 24, 2017 https://www.youtube.com/watch?v=291qlex-TLc (Year: 2017) (1 page).
How to Asana, Asana project management, youtube, excerpt, Mar. 7, 2017 https://www.youtube.com/watch?v=qqANMTvVpE (Year: 2017) (28 pages).
How to Asana, Creating your first Asana project, youtube, excerpt, Jan. 31, 2017 https://www.youtube.com/watch?v=L04WmcUdsLo (Year: 2017) (1 page).
How to Asana, Getting Asana into your workflow, youtube, excerpt, Jul. 17, 2017 https://www.youtube.com/watch?v=7YLrNMdv3o (Year: 2017) (24 pages).
How to Asana, Planning with Asana calendar, youtube excerpt, Feb. 14, 2017 https://www.youtube.com/watch?v=w8t6KYiVPyc (Year: 2017) (19 pages).
How to Asana, Using Asana for task management, youtube, excerpt, Feb. 7, 2017 https://www.youtube.com/watch?v=vwvbgiejhQ (Year: 2017) (8 pages).
How to Asana, Visualizing work with Asana kanban boards, youtube, excerpt, Feb. 21, 2017 https://www.youtube.com/watch?v=jmZaZGydfPY (Year: 2017) (41 pages).
How to Asana, Workflow management, youtube, excerpt, May 30, 2017 https://www.youtube.com/watch?v=rk8nPWmXsRo (Year: 2017) (9 pages).
How to use Advanced Search in Asana, Asana tutorial, May 25, 2016 https://www.youtube.com/watch?v=5VyJ3toPfQM (Year: 2016) (28 pages).
Justin Rosenstein, Unveiling the Future of Asana, Mar. 28, 2018 https://www.youtube.com/watch?v=nRI?d_WM4Bc (Year: 2018) (2 pages).
Lauren Labrecque, “Fostering Consumer-Brand Relationships in Social Media Environments: The Role of Parasocial Interaction”, 2014, Journal of Interactive Markeing, 28 (2014), pp. 134-148 (Year: 2014).
Macro, computer science, Wikipedia, archives org, 6 pages, Feb. 11, 2020 http://web.archive.org/web/20200211082902/https://en.wikipedia.org/wiki/Macro_(computer_science) (Year: 2020).
Mauricio Aizawa, Zapier, How to Automate Asana Tasks creation using Evernote, youtube excerpts, Mar. 16, 2018 https://www.youtube.com/watch?v=BjDQ4Gny4WI (Year: 2018) (8 pages).
Paul Minors, How to automate your tasks, youtube excerpts, Oct. 18, 2019 https://www.youtube.com/watch?v=lwF9XyUQrzw (Year: 2019).
Prioritize My Tasks in Asana, Asana tutorial, youtube, excerpt, May 25, 2016 https://www.youtube.com/watch?v=UbCnMvw01nl (Year: 2016) (3 pages).
Project views, Asana tutorial, youtube, excerpt May 25, 2016 https://www.youtube.com/watch?v=FYjA8ZH3ceQ (Year: 2016) (5 pages).
Using Asana Premium, Asana tutorial, youtube, excerpt, Sep. 10, 2016 https://www.youtube.com/watch?v=vMgLtDDmyeo (Year: 2016) (4 pages).
Where does Asana fit in, archives org, Jul. 8, 2017 https://web.archive.org/web/20170708150928/https://asana.com/guide/resources/infosheets/where-does-asana-fit (Year: 2017) (5 pages).
Wix.com, How to Use Wix Code with Marketing Tools to Create Custom Events, Oct. 18, 2018, YouTube, https://www.youtube.com/watch?v=MTBVykOYGvO&feature=emb_title, 2 pages.
www.asana.com (as retrieved from https://web.archive.Org/web/20160101054536/https://asana.com/press and https://web.archive.org/web/20160101054527/https://asana.com/product) (Year: 2016) 15 pages.
www.cogmotive.com/blog/author/alan Alan Byrne: “Creating a company Shared Calendar in Office 365”; pp. 1-17; Sep. 10, 2013 (16 pages).
Klipfoliio. “What is a Project Management Dashboard?”. Jan. 18, 2021. <https://web.archive.org/web/20210128061955/https:// www.klipfolio.com/resources/articles/project-management-dashboard > (Year: 2021) 6 pages.
Shivakumar; Complete Guide to Digital Project Management; 2018; Apress; (https://doi.org/10.1007/978-1-4842-3417-4; last access Mar. 6, 2023).
Related Publications (1)
Number Date Country
20220343283 A1 Oct 2022 US
Continuations (1)
Number Date Country
Parent 16947160 Jul 2020 US
Child 17862701 US