How to Organize Tasks by Context and Project in GTD: The Action-Context Alignment Matrix

In GTD, a project is any outcome requiring more than one action step, while a context defines the tool, location, or mindset needed to perform a task. The Action-Context Alignment Matrix separates the 'What' (Project) from the 'Where/How' (Context) to keep lists actionable. Use the Clarify workflow to determine if an item is a project or next action, then filter by your current context to execute. Trayzero enforces this strict, local-first GTD loop to prevent list bloat.

What Counts as a Project vs. a Single Action in GTD?

The Action-Context Alignment Matrix begins with a critical distinction: separating multi-step outcomes from single tasks. This prevents your project list from becoming a vague wish list. Effective organization requires separating the 'What' (Project) from the 'Where/How' (Context) to ensure lists remain actionable rather than aspirational.

1. Define the desired outcome. A project is any outcome requiring more than one physical action step to complete, not a large endeavor. "Finish quarterly report" is a project; "Email Sarah for sales data" is a next action.
2. Apply the Clarify decision tree. The Clarify workflow guides you through a decision tree to determine if an item is a project, a next action, or non-actionable. Ask: Is it actionable? If yes, does it require more than one step? If yes, it is a project.
3. Assign a validated next action. Every project must have at least one concrete next action. Trayzero provides next-action warnings to ensure no project is left without an active moving part, enforcing this rule automatically.
4. Filter by context. The final step is to assign that next action to a specific context, which we will set up next. This ensures you only see tasks you can actually do right now.

Setting Up Your Contexts: From @Phone to @Zombie Mode

Contexts are the filters that make your next-action lists immediately executable. They represent the specific tool, location, or person needed to perform a task. The key is to define contexts that match your real-world constraints.

Context Type	Example	Best For
Tool-Based	@phone, @computer	Tasks requiring a specific device.
Location-Based	@home, @office, @errands	Tasks tied to a physical place.
Person-Based	@boss, @partner	Tasks requiring a specific person.
Energy/Mode	@zombie-mode, @high-focus	Tasks matching your mental state.

Traditional GTD emphasizes physical locations like @Office or @Home. However, modern practitioners argue these are obsolete due to ubiquitous technology and prefer energy-based or mindset contexts. A common GTD failure is working directly from a project list rather than filtering by your current context to execute.

Trayzero includes seven default contexts: @phone, @computer, @errands, @home, @office, @anywhere, and @waiting. You can customize these to include modern adaptations like "Zombie Mode" for low-energy tasks. The goal is to have a context for every situation you find yourself in, so you can always pull up a relevant list.

Grouping Projects by Life Areas (Horizon 2)

Once you have projects and contexts, you need a higher-level layer to ensure alignment with your life. Areas of Responsibility (Horizon 2) are used to group projects by life roles like Health, Finance, or Career. This grouping helps ensure your projects align with your broader commitments and prevents overlooking key life areas.

Example: Applying Areas of Responsibility

Imagine you have the following projects:

• "Complete marathon training plan" (Project)
• "File taxes" (Project)
• "Prepare Q3 presentation" (Project)

You would group them under Areas of Responsibility:

• Health: Complete marathon training plan
• Finance: File taxes
• Career: Prepare Q3 presentation

This structure allows you to review all projects within a specific life role during your weekly review, ensuring nothing falls through the cracks. It answers the question, "Am I maintaining all my commitments?" rather than just "What's next on my list?"

The Brain Dump to Clarify Workflow

The entire system starts with a clean slate. The 'Brain Dump' (Capture) is the first step, collecting all open loops without judgment. Get everything out of your head and into an inbox.

1. Capture everything. Write down every task, idea, and commitment. Do not filter or organize yet.
2. Process the inbox. For each item, apply the Clarify workflow. The rule is: if an item takes more than 2 minutes and more than 1 step, it is a Project.
3. Determine actionability. Is it actionable? If not, trash it, file it for reference, or add it to a Someday/Maybe list.
4. Assign next action and context. For actionable items, define the very next physical action. Then, assign it to a context based on where or how you will do it.
5. Execute by context. When you are at your computer, look at your @computer list. When you have low energy, look at your @zombie-mode list. This process ensures you assign a Next Action and filter by the current Context to execute, maintaining actionable lists.

This workflow is the engine of the Action-Context Alignment Matrix. It transforms a chaotic brain dump into a structured, executable system.