Distinguishing Sub-Areas in Things

A pet peeve of mine in Things is the inability to have sub-areas. In my eyes, you’re forced into categorizing your tasks into one of two ways – neither of which work all that great:

  • Option 1: Areas for all the things!
    Pro: You’re actually using areas and projects as Culture Code intended
    Con: In order to pull this off, you’ll likely have lots of areas which becomes overwhelming to look at, especially on iOS.
  • Option 2: Areas for higher level things, and projects for sub areas.
    Pro: Less visual clutter
    Pro: By using projects for sub-areas, you can take advantage of project-only features like headers
    Con: You’re not using the app as intended so you lose the distinction between actual projects and sub areas

While I’ve settled with Option 2 as the better option for my use cases, I’ve never been fully satisfied with my projects and sub areas being indistinguishable from one another.

Over the past several months of using Things, I’ve played around with a few characters to differentiate the two. The two that have stood out in my mind are the checkbox symbol (☑︎) and what Apple’s character palette considers a “Parenthesis Extension” (⎜). ( They actually have separate characters for both left and right extensions, but I can’t seem to find any visual difference between the two.)

I eventually settled with prefixing my sub-areas the parenthesis extension rather than prefixing each project with the checkbox.  The extension seemed to introduce the least amount of visual clutter, and I find the divide also visually indents the sub-areas nicely under their main areas which helps to further the idea of it being nested under the area.

I still wish Cultured Code would just allow us to selectively disable the “progress pies” for sub-areas, but until then, this is a nice way of quickly distinguishing sub-areas from projects.

4 thoughts on “Distinguishing Sub-Areas in Things

  1. Mau says:

    Thanks for another great post.!

    Maybe this is a dumb question but, does a sub-area then get segmented into virtual projects using headers? Or is the content of a sub-area made up of loose tasks?

    I agree that an official sub-area feature would be ideal. I wish the glacial speed at which Cultured Code adds features would speed up a bit.

    • Andrea says:

      Whether I use headings really depends on the sub-area. For example, my “Pets” sub-area under Home doesn’t have any special break down, but my “Chores” sub-area is broken up into headings for Daily, Weekly, Monthly, and Seasonal. Anytime I’m breaking something down with headings, it’s purely to help my brain visually rather than to create virtual projects. Projects always get their own dedicated project.

  2. Mark says:

    I’m trying to solve the same challenge, which brought me to your excellent blog.

    The interesting thing about Headings is that they function like sub-Projects. Within each heading are Anytime, Upcoming, and Someday tasks. So a project with 3 heading could have 3 separate Anytime, Upcoming, and Someday lists all on the same “page”. Unfortunately, they’re all mashed together, so clicking the “Hide later items” button is the only way to visually distinguish them.

    My best solution (wish list) would be to add “Groups”, basically a dumb folder; it’s only functions to contain and collapse/expand areas (like a folder in Wunderlist). In your example, that would look like:

    Work (group)
    – Management (area)
    – Support (area)
    — Project 1
    — Project 2
    — Project 3

    Of course, that doesn’t exist (and probably never will). After using your system outlined here from July 2019, have you improved upon it at all?

    • Andrea says:

      Hi Mark,

      Thanks for stopping by. Yes, I am still using this method. While I’d much rather have the option for a desperately needed third level between areas and projects, distinguishing areas in this way does work for me. It’s not ideal, but until Cultured Code reconsiders, if they ever do, I’m forced to work with what we currently have.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.