Skip to content
ADVERTISEMENT
Sign In
  • Sections
    • News
    • Advice
    • The Review
  • Topics
    • Data
    • Diversity, Equity, & Inclusion
    • Finance & Operations
    • International
    • Leadership & Governance
    • Teaching & Learning
    • Scholarship & Research
    • Student Success
    • Technology
    • Transitions
    • The Workplace
  • Magazine
    • Current Issue
    • Special Issues
    • Podcast: College Matters from The Chronicle
  • Newsletters
  • Events
    • Virtual Events
    • Chronicle On-The-Road
    • Professional Development
  • Ask Chron
  • Store
    • Featured Products
    • Reports
    • Data
    • Collections
    • Back Issues
  • Jobs
    • Find a Job
    • Post a Job
    • Professional Development
    • Career Resources
    • Virtual Career Fair
  • More
  • Sections
    • News
    • Advice
    • The Review
  • Topics
    • Data
    • Diversity, Equity, & Inclusion
    • Finance & Operations
    • International
    • Leadership & Governance
    • Teaching & Learning
    • Scholarship & Research
    • Student Success
    • Technology
    • Transitions
    • The Workplace
  • Magazine
    • Current Issue
    • Special Issues
    • Podcast: College Matters from The Chronicle
  • Newsletters
  • Events
    • Virtual Events
    • Chronicle On-The-Road
    • Professional Development
  • Ask Chron
  • Store
    • Featured Products
    • Reports
    • Data
    • Collections
    • Back Issues
  • Jobs
    • Find a Job
    • Post a Job
    • Professional Development
    • Career Resources
    • Virtual Career Fair
    Upcoming Events:
    Student Housing
    Serving Higher Ed
    Chronicle Festival 2025
Sign In
Profhacker Logo

ProfHacker

Teaching, tech, and productivity.

GTD Contexts and Academic Work

By Natalie Houston October 15, 2009

One of the central concepts of David Allen’s Getting Things Done methodology is that your lists of next actions should be organized by context. The most basic context of an action is the physical setting or tools required to perform the action. So, tasks that can only be performed at the office would go on the @Office list; errands to be run on @Errands; or calls on an @Calls list. (Allen’s book suggests prefixing the @ symbol to your action lists if you use digital list keepers (folders in your email, memos on your PDA or phone) as it will bump them to the top of an alphabetical list and make the physical context aspect of the list obvious to you every time you use it.)

Choosing your context lists depends upon the kinds of actions you frequently do, and the structures of your life. If you don’t make a lot of phone calls, then you might not need an @Calls list, preferring to take care of them as part of either @Home or @Work. If you do make a lot of calls and want to bundle them together when you are in situations that allow for easy use of your phone, then @Calls might work for you.

The use of context-dependent action lists is one of the most useful features of the GTD approach because it forces you to consider in a very concrete way what, exactly, you will need in order to complete the action you’re putting on your list: a phone? an internet connection? another person? a microfilm reader in the library?


Of course, in the (9?) years since GTD first was unleashed upon the world, we’ve continually developed more and more ways to stay connected and to make almost any task potentially mobile. But just because you could make a given context work for a group of actions, doesn’t mean that you should. Many of us are rarely without a phone, for example — but even so, the noise level of your environment, your companions, or your mental state are not always conducive to sitting down and working through a list of calls you have to make. Because technology makes the boundaries between work and life more fluid, you have to make more decisions about setting them for yourself.


There are basically two main kinds of contexts: those that are structurally imposed and those you create yourself. If you are required to be in your office at certain times of the week, then you can only work on actions that can be pursued within that context. That’s the easy part. But while you’re there, depending on the categories that make sense for you, you might be working through actions on @Office, @Online, or @Teaching. (I know, I know, many Profhacker folks are always online, so the idea of an @Online category makes no sense to you. But if you spend a lot of time in a car, in a library without wifi, or (gasp!) unplugged, then it might.)

Categories like @Teaching or @Writing modify Allen’s original discussion of context, because they’re not physical or tool-based environments. (GTD purists might want shield their delicate sensibilities at this point.) But they can be very helpful in tracking actions that you can and do actually pursue from multiple physical locations. For example, I grade both from home and while I’m at my office. Keeping an @Teaching list of all of my grading and prep tasks helps me keep track of what I need to do, but it’s up to me to decide when I’m working from home whether I want to be focusing on @Teaching or @Writing.

And that’s where it can get a little muddy. The beauty of the pure GTD system is that it helps simplify the decisions you have to make at any given moment about what to do next. If you’re working in an business environment in which your day is partly or largely scheduled by or around other people, and/or in which your contexts are determined by your job requirements, then the division between @Work and @Home is very clear. But many academics work from home, and much of our work (in the humanities anyway) can be done in a variety of locations: office, home, coffeeshop, etc.

What has helped me is to set in place some guidelines that limit some tasks to particular contexts: I will only work on administrative tasks (faculty reports, committee memos, etc) in my office; I prepare teaching notes in my office; and any serious writing for my research takes place at home or at a coffeeshop. The first is an attempt to quarantine the less exciting tasks of my job; the second is because I store my teaching materials at the office, and since I teach on campus, it makes sense to bundle the prep with my teaching days; and the third guideline is based on knowing where I focus best for writing.

In short: just because you could work on any of your many responsibilities almost anywhere, that doesn’t mean you should. But only you can decide how to divide things up.


See also: Nels’s Introduction to GTD.


(CC licensed image from flickr user Aine D)

How have GTD contexts helped you to be productive? How do you match your tasks to your location? or not? Let us know in the comments!

To continue reading for FREE, please sign in.

Sign In

Or subscribe now to read with unlimited access for as low as $10/month.

Don’t have an account? Sign up now.

A free account provides you access to a limited number of free articles each month, plus newsletters, job postings, salary data, and exclusive store discounts.

Sign Up

One of the central concepts of David Allen’s Getting Things Done methodology is that your lists of next actions should be organized by context. The most basic context of an action is the physical setting or tools required to perform the action. So, tasks that can only be performed at the office would go on the @Office list; errands to be run on @Errands; or calls on an @Calls list. (Allen’s book suggests prefixing the @ symbol to your action lists if you use digital list keepers (folders in your email, memos on your PDA or phone) as it will bump them to the top of an alphabetical list and make the physical context aspect of the list obvious to you every time you use it.)

Choosing your context lists depends upon the kinds of actions you frequently do, and the structures of your life. If you don’t make a lot of phone calls, then you might not need an @Calls list, preferring to take care of them as part of either @Home or @Work. If you do make a lot of calls and want to bundle them together when you are in situations that allow for easy use of your phone, then @Calls might work for you.

The use of context-dependent action lists is one of the most useful features of the GTD approach because it forces you to consider in a very concrete way what, exactly, you will need in order to complete the action you’re putting on your list: a phone? an internet connection? another person? a microfilm reader in the library?


Of course, in the (9?) years since GTD first was unleashed upon the world, we’ve continually developed more and more ways to stay connected and to make almost any task potentially mobile. But just because you could make a given context work for a group of actions, doesn’t mean that you should. Many of us are rarely without a phone, for example — but even so, the noise level of your environment, your companions, or your mental state are not always conducive to sitting down and working through a list of calls you have to make. Because technology makes the boundaries between work and life more fluid, you have to make more decisions about setting them for yourself.


There are basically two main kinds of contexts: those that are structurally imposed and those you create yourself. If you are required to be in your office at certain times of the week, then you can only work on actions that can be pursued within that context. That’s the easy part. But while you’re there, depending on the categories that make sense for you, you might be working through actions on @Office, @Online, or @Teaching. (I know, I know, many Profhacker folks are always online, so the idea of an @Online category makes no sense to you. But if you spend a lot of time in a car, in a library without wifi, or (gasp!) unplugged, then it might.)

Categories like @Teaching or @Writing modify Allen’s original discussion of context, because they’re not physical or tool-based environments. (GTD purists might want shield their delicate sensibilities at this point.) But they can be very helpful in tracking actions that you can and do actually pursue from multiple physical locations. For example, I grade both from home and while I’m at my office. Keeping an @Teaching list of all of my grading and prep tasks helps me keep track of what I need to do, but it’s up to me to decide when I’m working from home whether I want to be focusing on @Teaching or @Writing.

And that’s where it can get a little muddy. The beauty of the pure GTD system is that it helps simplify the decisions you have to make at any given moment about what to do next. If you’re working in an business environment in which your day is partly or largely scheduled by or around other people, and/or in which your contexts are determined by your job requirements, then the division between @Work and @Home is very clear. But many academics work from home, and much of our work (in the humanities anyway) can be done in a variety of locations: office, home, coffeeshop, etc.

What has helped me is to set in place some guidelines that limit some tasks to particular contexts: I will only work on administrative tasks (faculty reports, committee memos, etc) in my office; I prepare teaching notes in my office; and any serious writing for my research takes place at home or at a coffeeshop. The first is an attempt to quarantine the less exciting tasks of my job; the second is because I store my teaching materials at the office, and since I teach on campus, it makes sense to bundle the prep with my teaching days; and the third guideline is based on knowing where I focus best for writing.

In short: just because you could work on any of your many responsibilities almost anywhere, that doesn’t mean you should. But only you can decide how to divide things up.


See also: Nels’s Introduction to GTD.


(CC licensed image from flickr user Aine D)

How have GTD contexts helped you to be productive? How do you match your tasks to your location? or not? Let us know in the comments!

We welcome your thoughts and questions about this article. Please email the editors or submit a letter for publication.
Share
  • Twitter
  • LinkedIn
  • Facebook
  • Email
ADVERTISEMENT
ADVERTISEMENT

More News

UCLA students, researchers and demonstrators rally during a "Kill the Cuts" protest against the Trump administration's funding cuts on research, health and higher education at the University of California Los Angeles (UCLA) in Los Angeles on April 8, 2025.
Scholarship & Research
Trump Proposed Slashing the National Science Foundation’s Budget. A Key Senate Committee Just Refused.
Illustration of a steamroller rolling over a colorful road and leaving gray asphalt in its wake.
Newly Updated
Oregon State U. Will End a Renowned Program That Aimed to Reduce Bias in Hiring
Dr. Gregory Washington, president of George Mason University.
Another probe
George Mason President Discriminated Against White People After George Floyd Protests, Justice Dept. Says
Protesters gather outside the Department of Education headquarters in Washington, D.C., on Feb. 14, 2025 to protest the Trump administrations cuts at the agency.
An Uncertain Future
The Education Dept. Got a Green Light to Shrink. Here Are 3 Questions About What’s Next.

From The Review

Photo-based illustration with repeated images of a student walking, in the pattern of a graph trending down, then up.
The Review | Opinion
7 Ways Community Colleges Can Boost Enrollment
By Bob Levey
Illustration of an ocean tide shaped like Donald Trump about to wash away sandcastles shaped like a college campus.
The Review | Essay
Why Universities Are So Powerless in Their Fight Against Trump
By Jason Owen-Smith
Photo-based illustration of a closeup of a pencil meshed with a circuit bosrd
The Review | Essay
How Are Students Really Using AI?
By Derek O'Connell

Upcoming Events

07-31-Turbulent-Workday_assets v2_Plain.png
Keeping Your Institution Moving Forward in Turbulent Times
Ascendium_Housing_Plain.png
What It Really Takes to Serve Students’ Basic Needs: Housing
Lead With Insight
  • Explore Content
    • Latest News
    • Newsletters
    • Letters
    • Free Reports and Guides
    • Professional Development
    • Events
    • Chronicle Store
    • Chronicle Intelligence
    • Jobs in Higher Education
    • Post a Job
  • Know The Chronicle
    • About Us
    • Vision, Mission, Values
    • DEI at The Chronicle
    • Write for Us
    • Work at The Chronicle
    • Our Reporting Process
    • Advertise With Us
    • Brand Studio
    • Accessibility Statement
  • Account and Access
    • Manage Your Account
    • Manage Newsletters
    • Individual Subscriptions
    • Group and Institutional Access
    • Subscription & Account FAQ
  • Get Support
    • Contact Us
    • Reprints & Permissions
    • User Agreement
    • Terms and Conditions
    • Privacy Policy
    • California Privacy Policy
    • Do Not Sell My Personal Information
1255 23rd Street, N.W. Washington, D.C. 20037
© 2025 The Chronicle of Higher Education
The Chronicle of Higher Education is academe’s most trusted resource for independent journalism, career development, and forward-looking intelligence. Our readers lead, teach, learn, and innovate with insights from The Chronicle.
Follow Us
  • twitter
  • instagram
  • youtube
  • facebook
  • linkedin