guide
  • Introduction
  • Guiding Principles
    • Mission Statement
    • Conflict Resolution Process
  • Operating Model
    • Working Together
    • Holacracy
      • Meetings
      • Specific Roles
      • Terms and Definitions
      • Finer Points
      • Holacracy-Asana Key
    • Getting Things Done
      • Daily, Weekly, Monthly, and Annual Reviews
      • GTD-Asana Key
    • Transparency
    • Language
    • Budgeting
    • By Department
      • Engineering Operations
  • General Guidelines
  • Employment Policies
    • Equal Opportunity Employment
    • At-Will Employment
    • Code of Conduct in the Community
    • Complaint Policy
    • Drug and Alcohol Policy
    • Vacation, Holiday, and Paid Time Off (PTO) Policy
    • Supplemental Policies for Remote Employees and Contractors
    • Supplemental Policy for Bonus, Commissions, and other Performance-based Payments
    • Supplemental Policies for Hourly International Contractors or Workers
    • Supplemental Policies for Hourly International Contractors or Workers
    • Disputes and Arbitration
  • Benefits and Perks
    • Health Care
    • Vacation, Holiday and Paid Time Off (PTO) Policy
    • Holiday List
  • Hiring Documents
    • Acknowledgement of Receipt
    • Partner Proprietary Information and Inventions Agreement
  • Engineering Wiki
    • Code Snippets
      • Front End Code Snippets
    • Setup
      • 1: Overview of development using Audienti
      • 2: How to setup your dev environment on Docker
      • 2a: Setting up on our cloud your dev server
      • 3: Connect to Production using the VPN
      • 4: Import data into your development environment
    • Deployment
      • Docker based deployment of back end (manual)
    • Culture
      • How our development team works
      • Code Best Practices
    • Tips
      • Setting up a new development machine
      • Importing data to Development environment
      • GIT workflow and work tracking
      • Using Slack
      • Using Rubocop
      • Our Code Standards
      • General suggested best practices
      • Tracking your time
      • Naming Iterations
    • Migrations
      • Postgres
      • ElasticSearch
      • Redis
    • Database and System Maintenance
      • Redis Howtos
      • Elasticsearch HowTos
      • Postgres HowTos
      • Administration recipes
      • App maintenance crash course notes
    • Front End
      • 2016 Plan
      • Deploy
      • Assets
      • SearchLogic
      • How to create UI components
      • OMA Standard Tables
    • Monitoring and Alerting
      • Monitoring Systems
      • Monitoring individual controller actions
      • Get notified when a metric reaches a certain threshold
      • Instrumenting your models using Oma Stats
      • Configuring Graphite Charts
      • Tracking your results with StatsD
      • Logging Fields
      • Updating Kibana Filtering
    • Testing
      • Coverage
      • Elasticsearch mapping config synchronization
      • Testing Gotchas
      • Rspec Preloader
      • Test Best Practices
    • Models
      • Backlinks
    • Queueing and Worker System
      • Queueing and Job Overview
    • Processors
      • Rebuilding Spot Instances
      • Deploying processors
      • Running processors in development
      • Reverting to the previous build on a failed deployment
    • Processors / Opportunity Pipeline
      • Opportunity Pipeline
      • Diagram
    • Processors / Enrichment Pipeline
      • Diagram
      • Clustering
    • Processors / Backlink Pipeline
      • Diagram
      • Backlink Pipeline external APIs
      • Backlink pipeline logic
    • Processors / Automation Pipeline
      • Diagram
      • Automation Pipeline Overview
      • Agents
      • Running in development
    • Messaging and Social Accounts
      • Overview
    • API
      • Audienti API
    • Algorithms
    • Troubleshooting
      • Elasticsearch
    • Big Data Pipeline Stuff
      • Spark
    • Our Product
      • Feature synopsis of our product
    • Research
      • Backend framework comparison
      • Internet marketing Saas companies
    • Code snippets
      • Commonly Used
      • Not Used
    • Miscellaneous
      • Proxies and Bax
    • Legacy & Deprecated
      • Search criteria component
      • Classes list
      • Target Timeline
      • Twitter processor
      • Asset compilation
      • Test related information
      • Interface to EMR Hadoop jobs
      • Mongo Dex Indexes to be Built
      • Mongodb errors
      • Opportunity pipeline scoring
      • Graph Page
      • Lead scoring
      • Insights
      • Shard keys
      • Setting up OMA on local
      • Clone project to local machine
      • Getting around our servers in AWS
  • Acknowledgements
  • Documents That Receiving Your First Payment Triggers Acknowledgement and Acceptanace
Powered by GitBook
On this page
  1. Operating Model
  2. Getting Things Done

GTD-Asana Key

This key is a guide to how GTD concepts are translated and used in Asana. All LG partners will be using the same methodology.

Context == Tag Use tags for the contexts, i.e. the type of task or the context in which you need to get it done. We will be using standardized contexts across the organization:

  • Online: Needs to be done online, using smartphone or computer

  • Phone: It’s a phone call

  • Office: This needs to be done at the LG office

  • Errand: This needs to be run as an errand

  • Home: This needs to be done at home

  • Think: This is something that needs some thought, not immediate action

  • Read: Something that requires reading

  • Listen: Something that requires listening

  • Bug: An problem that is customer impacting and that requires someone to fix it

  • Frog: This is a big action, and will require concerted effort/time

  • Focus:This requires a high level of focus, you might want to reserve your most alert/productive time for these tasks

  • Avoiding: You know you have a habit/tendency to try and avoid tasks like this

  • Easy: This can be easily and quickly done without much focus, might want to reserve these for if you have some brief time to get some quick things done

  • Waiting: This is waiting on someone else to complete a task of their own first

  • Maybe later: This is a good idea worth keeping, but now’s not the time for it, you’ll look at this context every once in a while and see if anything needs to be moved to more immediate

  • High Pri: These are high priority tasks that needs immediate attention

  • Stale: These are tags that are auto-marked by the GTD bot that haven't been touched in over 4 weeks.

Project == Project

Due date == Due date

Timing == New tasks, Today, Upcoming and Later in Asana

  • New tasks: have not been sorted yet - This is your unprocessed inbox

  • Today: This is where you'll sort tasks that you've decided in your morning sorting that you'll be doing today. Generally keep this list short and manageable to avoid overwhelm or blockage

  • Upcoming: means that you will be getting to them soon, they are your next actions, and you'll be checking to see at the end of each day if you're going to move them to today

  • Later: means they do not need your immediate attention. You will check on these in your monthly review to see if anything needs to be moved to upcoming or today.

Items in front of a project name

  • _ (underscore) - is a non-actionable project or a project template

  • @ (ampersand) - is a context-based, non-actionable project

  • &ROLE - is an ongoing, role-based project. Things tha tare todos because they are in a particular role. Your ongoing work.

Note: These are different from those tagged “maybe later” which means that they’re future projects. Later just means they’re not immediate

PreviousDaily, Weekly, Monthly, and Annual ReviewsNextTransparency

Last updated 7 years ago