This lesson is still being designed and assembled (Pre-Alpha version)

Introduction to Asana

Overview

Teaching: 30 min
Exercises: 0 min
Questions
  • What is the purpose of Asana?

  • How can the Field Team use Asana?

Objectives

OTN’s Asana

At OTN, Asana is used for internal record keeping and collaborative action item tracking.

Asana allows us to be accountable, thorough, and comprehensive in our processes. This is essential for smooth communication and acts as a searchable archive of OTN’s institutional memory. Asana has replaced Podio and GitLab for the Field Team.

Why Asana?

OTN has several relevant Asana Teams, beyond Field Operations (described below), that you will need to interact with.

Field Operations Team

As the Field team has grown, job descriptions have expanded, and remote work has become more common it is now important to start using some of the lessons learned by the Data team to improve Field Ops communications. For this reason, there is now a Field Team Asana - https://app.asana.com/0/1201938039482799/overview.

Each OTN Field team member should have an Asana account created - please contact Project Management.

FieldOps Asana Home Page

This Field Ops Asana has been created as a place to track complex / important / outstanding issues so that they can be contributed to collaboratively and archived for future reference. This will be used in addition to Slack to make sure all Field Team members are communicating and information does not slip between the cracks of our busy schedules.

Asana projects include:

You will likely use the Field Shipping, Mission Planning, Found Gear Reporting and TOIL projects most often.

Exploring Projects

Each Project in Field Operations should include information in an Overview tab. This will detail exactly how to use this project, and how to complete the Tasks within it. This will differ for each project and therefore will not be covered in this curriculum.

Current members of this Asana Project include: all Field staff and members of the Project Management Office. Please tag them in any tasks (using the @ symbol) to prompt them for input.

Project Overview

Tasks

Within each project there are Tasks - these are the action items, and often contain subtasks with deadlines for completion. A Task may be defined differently in different projects - Ex: in Found Gear Reporting each task is one “washup”. In Receiver Inventory it’s a specific model of receiver.

Often, there is automation built into the creation of Tasks or Subtasks in a project. This helps us remember when we can complete each step of our action item. A great example is the Field Shipping project. Once a shipment’s status is changed to Active shipment then additional subtasks are populated for the assignee to follow. Similarly, if the shipment is labelled as Incoming vs. Outgoing there are different subtasks automatically created and so forth.

Tasks can be reassigned when needed to ensure they’re not forgotten when a staff member goes on vacation or on a field mission.

You can see all Tasks and Subtasks assigned to you, with their due dates, in the left-hand menu option My Tasks. You need to check these every day to ensure you are not missing tasks assigned to you by Project Management or other teams.

Asana Structure

More Information

The Field Ops Asana has a Onboarding Powerpoint with all the details needed to learn how to navigate Asana!

Key Points

  • Asana helps organize and archive tasks

  • There are several ways Asana is used by the Field Team