Asana Workflow Specialist Certificate cheat sheet

A workflow is a repeatable sequence of stages from request to completion; each stage should map to exactly one section or status value, not both ambiguously.

Design order: define outcomes first, then stages, then the data each stage requires, then automation last - automation added before stages stabilize creates rework.

Every handoff point (one person or team finishing work that another begins) is a candidate for an assigned task, a rule trigger, and a notification.

A stage earns its own section only if work can sit there for a meaningful duration or needs distinct ownership; otherwise it is a subtask or checklist item.

Standardize on one progress model per project: sections for stages OR a status field for stages. Mixing both produces conflicting views and broken rules.

Map each workflow role to a permission level: requesters need comment/submit access, doers need edit, approvers need edit plus approval action, stakeholders need read.

Reversible stages (rework, blocked, on hold) should be modeled explicitly; without them, tasks get parked in the wrong stage and reporting skews.

A workflow is testable when a sample task can traverse every stage using only documented actions; any undocumented manual step is a design gap.

Hierarchy: workspace > team > project > section > task > subtask. Subtasks are not members of the parent project's sections and do not appear in project views.

A task can belong to multiple projects; each project membership carries its own section placement, custom field values, and completion state within that project.

Sections are ordered columns in board view and groupings in list view; moving a task between sections is the canonical stage-change action for rules.

Subtasks inherit nothing automatically from the parent task except association; assignee, due date, and custom fields must be set deliberately.

Multi-homing a task into a second project duplicates visibility but not the task itself - edits to name, description, and comments propagate to all homes.

Deleting a section does not delete its tasks; they move to the sectionless area of the project and must be re-filed.

Use one project per deliverable stream, not per team; team-level coordination belongs in portfolios or a shared intake project.

Task naming convention: verb + object + distinguishing attribute (e.g., 'Draft Q3 launch email v2') keeps search and filters reliable.

Field types include text, number, dropdown (single-select), multi-select, date, people, checkbox, and formula-style rollups; type choice determines which filters and rules can use the field.

Workspace-level fields are shared across projects and editable centrally; project-local fields exist only in one project and cannot be reused elsewhere.

Dropdown options should be a closed, governed list; every added option is a reporting dimension and a potential filter value forever.

A field added to a project's task list does not automatically populate existing tasks - values must be backfilled or set by rule.

Formulas and rollups read values; they cannot be manually edited, so never design a workflow that requires typing into a computed field.

People fields support 'is me' style filters, making them the standard mechanism for personal work queues and reviewer routing.

Use a single-select status field instead of free text for any value that drives automation; free text cannot be matched reliably by rules.

Field proliferation is the main metadata failure mode: audit quarterly and archive fields with no filter, rule, or view dependency.

Rule anatomy: trigger (event) + optional conditions (all must pass) + actions. Conditions are evaluated at trigger time, not continuously.

Common triggers: task added to project, section changed, field changed, due date approaching, task completed, comment added, form submitted.

Rules run as the rule creator's permission context in many configurations; if the creator loses access, automation can silently fail.

Branching logic lets one rule handle multiple paths; prefer several small single-purpose rules over one large branched rule for debuggability.

Loops are a real risk: a rule that changes a field which triggers another rule that changes it back will oscillate. Design field changes to be idempotent.

Rules cannot retroactively process tasks that already exist unless the rule is triggered by a new event on those tasks; use bulk edit for backfill.

Test in a sandbox project with a copy of the fields and sections; enable in production only after a sample task completes the full path.

Automation ownership: name rules with the outcome ('Set Review Date on Enter Review'), and record the owner so orphaned rules can be retired.

View types: list (grouped work), board (stage columns), calendar (dates), timeline (durations and dependencies), and dashboard (charts from a project or portfolio).

Filters combine field conditions with AND across different fields and OR within a multi-select field's values; saved filters become reusable views.

Sort and group are view-level settings and do not alter task data; two people can see the same project differently without conflict.

A dashboard chart requires a source (project or portfolio) and a measure (task count is default); grouping by a dropdown field yields one bar per option.

Reporting accuracy depends on complete field data: tasks with empty grouping fields fall into an 'unspecified' bucket that inflates totals.

Date-based views only show tasks with dates; tasks missing dates are invisible on calendar and timeline, a common cause of 'missing work'.

Portfolios aggregate projects for cross-project reporting; a portfolio dashboard reports on project-level status and custom fields, not task detail.

Use 'tasks I've completed this week' style filters (assignee is me + completion date) as the standard personal throughput report.

A form is attached to a project; each submission creates one task in that project, with form questions mapped to task name, description, and custom fields.

Form fields that map to custom fields must use the same field type; a text question cannot populate a dropdown field.

Forms can set a default section and default assignee, which is how intake routes work to the right stage and owner at creation.

Required questions and conditional question logic reduce incomplete submissions; unmapped answers land in the task description as text.

Templates create a project with predefined sections, tasks, subtasks, relative due dates, and sometimes rules and fields; relative dates anchor to the project start or end date.

Template governance: a small set of approved templates with owners beats a sprawl of ad hoc copies; lock or restrict template editing to admins.

Intake pattern: public form > project > rule assigns owner and due date > section change signals triage complete.

Duplicating a project copies tasks and sections but review custom field settings and rules, which may reference fields not present in the copy.

Project roles: owner/admin (settings, members, fields), editor (tasks and comments), commenter (comments only), viewer (read only); permissions are per project, not per task.

Workspace guests see only projects explicitly shared with them; membership is additive, so removing a guest from a project revokes that project's access.

Private-to-members projects are invisible to non-members including workspace admins unless they are added; this is the main confidentiality control.

@mentions add the mentioned person as a collaborator on the task and notify them; collaborators can comment even without project edit rights.

Approvals are a task type with approve/reject actions; the approver must have at least comment access, and the approval state is reportable.

Governance baseline: named project owner, documented field dictionary, archived (not deleted) completed projects, and a quarterly rules audit.

Deleting is destructive and cascades to tasks; archiving preserves history and removes the project from active views - prefer archive.

Audit trail: task stories record field changes, section moves, assignments, and rule-driven actions with timestamps and actor.

A workflow is a repeatable sequence of stages from request to completion; each stage should map to exactly one section or status value, not both ambiguously.

Design order: define outcomes first, then stages, then the data each stage requires, then automation last - automation added before stages stabilize creates rework.

Every handoff point (one person or team finishing work that another begins) is a candidate for an assigned task, a rule trigger, and a notification.

A stage earns its own section only if work can sit there for a meaningful duration or needs distinct ownership; otherwise it is a subtask or checklist item.

Standardize on one progress model per project: sections for stages OR a status field for stages. Mixing both produces conflicting views and broken rules.

Map each workflow role to a permission level: requesters need comment/submit access, doers need edit, approvers need edit plus approval action, stakeholders need read.

Reversible stages (rework, blocked, on hold) should be modeled explicitly; without them, tasks get parked in the wrong stage and reporting skews.

A workflow is testable when a sample task can traverse every stage using only documented actions; any undocumented manual step is a design gap.

Hierarchy: workspace > team > project > section > task > subtask. Subtasks are not members of the parent project's sections and do not appear in project views.

A task can belong to multiple projects; each project membership carries its own section placement, custom field values, and completion state within that project.

Sections are ordered columns in board view and groupings in list view; moving a task between sections is the canonical stage-change action for rules.

Subtasks inherit nothing automatically from the parent task except association; assignee, due date, and custom fields must be set deliberately.

Multi-homing a task into a second project duplicates visibility but not the task itself - edits to name, description, and comments propagate to all homes.

Deleting a section does not delete its tasks; they move to the sectionless area of the project and must be re-filed.

Use one project per deliverable stream, not per team; team-level coordination belongs in portfolios or a shared intake project.

Task naming convention: verb + object + distinguishing attribute (e.g., 'Draft Q3 launch email v2') keeps search and filters reliable.

Field types include text, number, dropdown (single-select), multi-select, date, people, checkbox, and formula-style rollups; type choice determines which filters and rules can use the field.

Workspace-level fields are shared across projects and editable centrally; project-local fields exist only in one project and cannot be reused elsewhere.

Dropdown options should be a closed, governed list; every added option is a reporting dimension and a potential filter value forever.

A field added to a project's task list does not automatically populate existing tasks - values must be backfilled or set by rule.

Formulas and rollups read values; they cannot be manually edited, so never design a workflow that requires typing into a computed field.

People fields support 'is me' style filters, making them the standard mechanism for personal work queues and reviewer routing.

Use a single-select status field instead of free text for any value that drives automation; free text cannot be matched reliably by rules.

Field proliferation is the main metadata failure mode: audit quarterly and archive fields with no filter, rule, or view dependency.

Rule anatomy: trigger (event) + optional conditions (all must pass) + actions. Conditions are evaluated at trigger time, not continuously.

Common triggers: task added to project, section changed, field changed, due date approaching, task completed, comment added, form submitted.

Rules run as the rule creator's permission context in many configurations; if the creator loses access, automation can silently fail.

Branching logic lets one rule handle multiple paths; prefer several small single-purpose rules over one large branched rule for debuggability.

Loops are a real risk: a rule that changes a field which triggers another rule that changes it back will oscillate. Design field changes to be idempotent.

Rules cannot retroactively process tasks that already exist unless the rule is triggered by a new event on those tasks; use bulk edit for backfill.

Test in a sandbox project with a copy of the fields and sections; enable in production only after a sample task completes the full path.

Automation ownership: name rules with the outcome ('Set Review Date on Enter Review'), and record the owner so orphaned rules can be retired.

View types: list (grouped work), board (stage columns), calendar (dates), timeline (durations and dependencies), and dashboard (charts from a project or portfolio).

Filters combine field conditions with AND across different fields and OR within a multi-select field's values; saved filters become reusable views.

Sort and group are view-level settings and do not alter task data; two people can see the same project differently without conflict.

A dashboard chart requires a source (project or portfolio) and a measure (task count is default); grouping by a dropdown field yields one bar per option.

Reporting accuracy depends on complete field data: tasks with empty grouping fields fall into an 'unspecified' bucket that inflates totals.

Date-based views only show tasks with dates; tasks missing dates are invisible on calendar and timeline, a common cause of 'missing work'.

Portfolios aggregate projects for cross-project reporting; a portfolio dashboard reports on project-level status and custom fields, not task detail.

Use 'tasks I've completed this week' style filters (assignee is me + completion date) as the standard personal throughput report.

A form is attached to a project; each submission creates one task in that project, with form questions mapped to task name, description, and custom fields.

Form fields that map to custom fields must use the same field type; a text question cannot populate a dropdown field.

Forms can set a default section and default assignee, which is how intake routes work to the right stage and owner at creation.

Required questions and conditional question logic reduce incomplete submissions; unmapped answers land in the task description as text.

Templates create a project with predefined sections, tasks, subtasks, relative due dates, and sometimes rules and fields; relative dates anchor to the project start or end date.

Template governance: a small set of approved templates with owners beats a sprawl of ad hoc copies; lock or restrict template editing to admins.

Intake pattern: public form > project > rule assigns owner and due date > section change signals triage complete.

Duplicating a project copies tasks and sections but review custom field settings and rules, which may reference fields not present in the copy.

Project roles: owner/admin (settings, members, fields), editor (tasks and comments), commenter (comments only), viewer (read only); permissions are per project, not per task.

Workspace guests see only projects explicitly shared with them; membership is additive, so removing a guest from a project revokes that project's access.

Private-to-members projects are invisible to non-members including workspace admins unless they are added; this is the main confidentiality control.

@mentions add the mentioned person as a collaborator on the task and notify them; collaborators can comment even without project edit rights.

Approvals are a task type with approve/reject actions; the approver must have at least comment access, and the approval state is reportable.

Governance baseline: named project owner, documented field dictionary, archived (not deleted) completed projects, and a quarterly rules audit.

Deleting is destructive and cascades to tasks; archiving preserves history and removes the project from active views - prefer archive.

Audit trail: task stories record field changes, section moves, assignments, and rule-driven actions with timestamps and actor.

A workflow is a repeatable sequence of stages from request to completion; each stage should map to exactly one section or status value, not both ambiguously.

Design order: define outcomes first, then stages, then the data each stage requires, then automation last - automation added before stages stabilize creates rework.

Every handoff point (one person or team finishing work that another begins) is a candidate for an assigned task, a rule trigger, and a notification.

A stage earns its own section only if work can sit there for a meaningful duration or needs distinct ownership; otherwise it is a subtask or checklist item.

Standardize on one progress model per project: sections for stages OR a status field for stages. Mixing both produces conflicting views and broken rules.

Map each workflow role to a permission level: requesters need comment/submit access, doers need edit, approvers need edit plus approval action, stakeholders need read.

Reversible stages (rework, blocked, on hold) should be modeled explicitly; without them, tasks get parked in the wrong stage and reporting skews.

A workflow is testable when a sample task can traverse every stage using only documented actions; any undocumented manual step is a design gap.

Hierarchy: workspace > team > project > section > task > subtask. Subtasks are not members of the parent project's sections and do not appear in project views.

A task can belong to multiple projects; each project membership carries its own section placement, custom field values, and completion state within that project.

Sections are ordered columns in board view and groupings in list view; moving a task between sections is the canonical stage-change action for rules.

Subtasks inherit nothing automatically from the parent task except association; assignee, due date, and custom fields must be set deliberately.

Multi-homing a task into a second project duplicates visibility but not the task itself - edits to name, description, and comments propagate to all homes.

Deleting a section does not delete its tasks; they move to the sectionless area of the project and must be re-filed.

Use one project per deliverable stream, not per team; team-level coordination belongs in portfolios or a shared intake project.

Task naming convention: verb + object + distinguishing attribute (e.g., 'Draft Q3 launch email v2') keeps search and filters reliable.

Field types include text, number, dropdown (single-select), multi-select, date, people, checkbox, and formula-style rollups; type choice determines which filters and rules can use the field.

Workspace-level fields are shared across projects and editable centrally; project-local fields exist only in one project and cannot be reused elsewhere.

Dropdown options should be a closed, governed list; every added option is a reporting dimension and a potential filter value forever.

A field added to a project's task list does not automatically populate existing tasks - values must be backfilled or set by rule.

Formulas and rollups read values; they cannot be manually edited, so never design a workflow that requires typing into a computed field.

People fields support 'is me' style filters, making them the standard mechanism for personal work queues and reviewer routing.

Use a single-select status field instead of free text for any value that drives automation; free text cannot be matched reliably by rules.

Field proliferation is the main metadata failure mode: audit quarterly and archive fields with no filter, rule, or view dependency.

Rule anatomy: trigger (event) + optional conditions (all must pass) + actions. Conditions are evaluated at trigger time, not continuously.

Common triggers: task added to project, section changed, field changed, due date approaching, task completed, comment added, form submitted.

Rules run as the rule creator's permission context in many configurations; if the creator loses access, automation can silently fail.

Branching logic lets one rule handle multiple paths; prefer several small single-purpose rules over one large branched rule for debuggability.

Loops are a real risk: a rule that changes a field which triggers another rule that changes it back will oscillate. Design field changes to be idempotent.

Rules cannot retroactively process tasks that already exist unless the rule is triggered by a new event on those tasks; use bulk edit for backfill.

Test in a sandbox project with a copy of the fields and sections; enable in production only after a sample task completes the full path.

Automation ownership: name rules with the outcome ('Set Review Date on Enter Review'), and record the owner so orphaned rules can be retired.

View types: list (grouped work), board (stage columns), calendar (dates), timeline (durations and dependencies), and dashboard (charts from a project or portfolio).

Filters combine field conditions with AND across different fields and OR within a multi-select field's values; saved filters become reusable views.

Sort and group are view-level settings and do not alter task data; two people can see the same project differently without conflict.

A dashboard chart requires a source (project or portfolio) and a measure (task count is default); grouping by a dropdown field yields one bar per option.

Reporting accuracy depends on complete field data: tasks with empty grouping fields fall into an 'unspecified' bucket that inflates totals.

Date-based views only show tasks with dates; tasks missing dates are invisible on calendar and timeline, a common cause of 'missing work'.

Portfolios aggregate projects for cross-project reporting; a portfolio dashboard reports on project-level status and custom fields, not task detail.

Use 'tasks I've completed this week' style filters (assignee is me + completion date) as the standard personal throughput report.

A form is attached to a project; each submission creates one task in that project, with form questions mapped to task name, description, and custom fields.

Form fields that map to custom fields must use the same field type; a text question cannot populate a dropdown field.

Forms can set a default section and default assignee, which is how intake routes work to the right stage and owner at creation.

Required questions and conditional question logic reduce incomplete submissions; unmapped answers land in the task description as text.

Templates create a project with predefined sections, tasks, subtasks, relative due dates, and sometimes rules and fields; relative dates anchor to the project start or end date.

Template governance: a small set of approved templates with owners beats a sprawl of ad hoc copies; lock or restrict template editing to admins.

Intake pattern: public form > project > rule assigns owner and due date > section change signals triage complete.

Duplicating a project copies tasks and sections but review custom field settings and rules, which may reference fields not present in the copy.

Project roles: owner/admin (settings, members, fields), editor (tasks and comments), commenter (comments only), viewer (read only); permissions are per project, not per task.

Workspace guests see only projects explicitly shared with them; membership is additive, so removing a guest from a project revokes that project's access.

Private-to-members projects are invisible to non-members including workspace admins unless they are added; this is the main confidentiality control.

@mentions add the mentioned person as a collaborator on the task and notify them; collaborators can comment even without project edit rights.

Approvals are a task type with approve/reject actions; the approver must have at least comment access, and the approval state is reportable.

Governance baseline: named project owner, documented field dictionary, archived (not deleted) completed projects, and a quarterly rules audit.

Deleting is destructive and cascades to tasks; archiving preserves history and removes the project from active views - prefer archive.

Audit trail: task stories record field changes, section moves, assignments, and rule-driven actions with timestamps and actor.

A workflow is a repeatable sequence of stages from request to completion; each stage should map to exactly one section or status value, not both ambiguously.

Design order: define outcomes first, then stages, then the data each stage requires, then automation last - automation added before stages stabilize creates rework.

Every handoff point (one person or team finishing work that another begins) is a candidate for an assigned task, a rule trigger, and a notification.

A stage earns its own section only if work can sit there for a meaningful duration or needs distinct ownership; otherwise it is a subtask or checklist item.

Standardize on one progress model per project: sections for stages OR a status field for stages. Mixing both produces conflicting views and broken rules.

Map each workflow role to a permission level: requesters need comment/submit access, doers need edit, approvers need edit plus approval action, stakeholders need read.

Reversible stages (rework, blocked, on hold) should be modeled explicitly; without them, tasks get parked in the wrong stage and reporting skews.

A workflow is testable when a sample task can traverse every stage using only documented actions; any undocumented manual step is a design gap.

Hierarchy: workspace > team > project > section > task > subtask. Subtasks are not members of the parent project's sections and do not appear in project views.

A task can belong to multiple projects; each project membership carries its own section placement, custom field values, and completion state within that project.

Sections are ordered columns in board view and groupings in list view; moving a task between sections is the canonical stage-change action for rules.

Subtasks inherit nothing automatically from the parent task except association; assignee, due date, and custom fields must be set deliberately.

Multi-homing a task into a second project duplicates visibility but not the task itself - edits to name, description, and comments propagate to all homes.

Deleting a section does not delete its tasks; they move to the sectionless area of the project and must be re-filed.

Use one project per deliverable stream, not per team; team-level coordination belongs in portfolios or a shared intake project.

Task naming convention: verb + object + distinguishing attribute (e.g., 'Draft Q3 launch email v2') keeps search and filters reliable.