Building a System That Actually Works

Every productivity framework — GTD, time-blocking, priority triage, context-based execution — is really trying to solve the same problem: too much coming in, not enough clarity about what to do next. Principal Task is built around the best ideas from all of them. This article distills those principles and shows you how to apply them so your system works with how you actually think, not against it.

Capture Everything, Decide Later

The most important habit in any productivity system is capturing tasks the moment they appear — before they disappear into the mental pile you're already carrying. Capture first, organize later. A half-organized task in your list is worth more than a perfectly-formed task that never made it in.

Principal Task makes this easy. On web, the What needs to be done? field in the top header is always visible — type a title and press Enter. The + Create Task button in the sidebar opens the full task form when you want to add more detail. On mobile, a quick long-press on the green + button opens a minimal title-only form so you can capture without breaking your flow.

Give Every Task a Home

Captured tasks are just noise until they have a place. Principal Task gives you five dimensions to organize your work: folders, contexts, priorities, statuses, and stars. You don't need to use all five at once — start with what you'll actually maintain.

A task without a folder is still a task, but a folder gives it a home. A task without a priority is still actionable, but a priority tells you which one to do first. The system works as a whole when each dimension is earning its place.

Projects vs. Areas of Responsibility

A project has a finish line. An area of responsibility doesn't — it just continues as long as that part of your life or work is active.

A practical folder structure maps folders to areas of responsibility — Work, Personal, Finances, Family — and to active projects: Atwater Account, Q2 Planning. Use the Group field to cluster related folders together: assign the same group value to "Work" and all your active work projects, and they'll stay adjacent in folder lists. This keeps related folders visible together while the top-level list stays readable. When a project ends, delete or deactivate its folder. The area folders stay.

Using Contexts to Filter for Now

A context tag answers the question: what do I need to be able to do this task? @Computer means you need your laptop. @Phone means a phone call. @Errands means you're out of the house. @Home means you can only do it at home.

The payoff comes when you're in a specific situation and want to see only the tasks that are actionable right now. Pull up a context filter and your list collapses to exactly what you can act on. A dentist waiting room isn't the time to think about work tasks that require your computer — filter to @Phone and work through those instead.

Assign a context to any task that has a clear situational requirement. Leave it blank for tasks you can do anywhere, anytime. To filter by context in Principal Task, select a context from the Contexts section in the sidebar (web) or drawer (mobile).

Using Priorities with Restraint

Priority should reflect real urgency or consequence, not enthusiasm. If you assign High or Top to everything, you've only recreated chaos under a different label.

A useful rule of thumb: Top means doing this wrong or late has a meaningful cost. High means it needs to happen today or tomorrow. Medium is this week. Low is someday but real. Negative is captured but de-prioritized — it stays visible without demanding attention. Most tasks should have no priority set or a Low priority. Reserve Top for the one or two things that genuinely can't slip.

Using Status to Track Where Things Stand

Status answers a different question than folder or priority: not where this task belongs or how important it is, but what's happening with it right now. Next Action means it's ready to do. Waiting means it's blocked on someone else. Someday means it's real but not now. Delegated means you've handed it off but still own the outcome.

You don't need to use all eleven statuses — pick the handful that reflect real distinctions in your work and ignore the rest. The value is in the filter: when you're processing your list, filter to Waiting to see everything that needs a follow-up, or filter to Next Action to work only from what's genuinely ready. See Adding and Organizing Your Tasks for the full list of available statuses.

Review Your Work Regularly

Capturing keeps the inbox full. Reviewing keeps it honest. A weekly review — even fifteen minutes — is where you process everything that accumulated during the week: clarify vague task titles, reassign folders and contexts that have shifted, reschedule tasks that slipped, and close out anything that's no longer real.

The review also directly affects your Task Velocity score. Completing tasks, clearing backlog, and maintaining an accurate in-progress list are all inputs to the score. A stale list full of tasks you'll never do is a drag on your velocity even if you're being productive. See Task Velocity: Your Productivity Pulse for more on what the score measures.

The Dashboard is the natural place to anchor your weekly review. It shows task counts by week, month, and year, broken down by context, folder, and priority — enough to surface patterns that are hard to see task-by-task. If your velocity is dropping or your folder counts are climbing, the Dashboard shows you where to look. See Reading Your Dashboard for a guide to interpreting what you find there.

Work from a Committed Short List

One of the most effective practices in personal productivity is deciding before the day starts which three to five tasks you are actually committing to. Not hoping to get to — committing to. The rest of your list exists, but it's not your focus.

In Principal Task, use the star to mark those committed tasks. Tap or click the ☆ star icon on any task to set it. Then filter your task view to starred tasks using the filter controls — the star field is available as a filter option on both web and mobile. Work from that view and ignore everything else until those tasks are done.

Use Templates for Repeating Work

Any work you do more than twice in the same sequence is a candidate for a template. Some obvious examples: a weekly review checklist, a client onboarding sequence, a recurring project kickoff, a travel packing list, a content publishing workflow. Templates preserve the full subtask structure, so a five-step process becomes a single tap to instantiate. See Task Templates: Build Once, Use Every Time for how to create and use them.

How Principal Task Supports Each Principle