Back to blog

What Today, Upcoming, Anytime, Someday Get Wrong

The most polished task app of the last decade gives you four views. Todoist gives you four priority levels. Every layer of structure becomes a decision you make per task. Ember works with two views and a binary choice instead.

Open the most polished task app of the last decade and you’ll find four views.

Today. Upcoming. Anytime. Someday.

The structure has been copied so many times it feels obvious now. Of course you need somewhere for today, somewhere for what’s scheduled, somewhere for the indefinite future, somewhere for the maybes. That’s how a real task management system works.

I used Things for years and built elaborate systems inside it. Eventually I noticed that every time I added a task, I was answering four questions instead of one:

  1. Is this for today?
  2. Is this scheduled for a specific day?
  3. Is this something I’ll do eventually?
  4. Is this a “maybe someday”?

The four views look like organization. They’re actually four micro-decisions per capture, and the friction adds up.

The seduction of more views

Things isn’t an outlier. It’s the cleanest expression of an industry-wide assumption: that more granular categorization gives you more control.

Todoist gives you four priority levels (P1-P4) and a project hierarchy and labels and filters. Asana gives you sections and assignees and custom fields. ClickUp gives you literally everything you can imagine, every dimension you might want, every way to slice the work.

The pitch is always the same. More structure means more clarity. Tag it precisely, and you’ll find it when you need it. Set the right priority, and the system will tell you what to do next.

And it works for a while. The first month with a new task app is always great. You set things up, get organized, feel like you’re finally in control.

Then the second month happens.

What actually happens at month two

Tasks start sitting in the wrong places. Something you tagged “P2” three weeks ago is more important than the “P1” thing you added today, but you don’t have time to reclassify everything. The Anytime view starts collecting items you’ll never get to, Someday quietly turns into a graveyard, and Today fills up with carryover from last week.

You’re not the problem. You’re not “doing it wrong.” The problem is that every dimension of structure you add is a dimension that has to be maintained. Tags grow stale. Priorities drift. Project hierarchies stop reflecting how you actually think about the work.

The cost isn’t theoretical. It’s the activation energy you spend every time you capture a task. Every “where does this go?” question is a tiny moment of friction. Multiply it by the dozens of tasks you capture in a week, and capture stops feeling free. It feels like work.

So you stop capturing. Or you dump everything into Inbox and ignore the structure. Or you start using a notes app for task-like things because at least notes don’t ask you to categorize.

This is how the most polished task management system on the market eventually loses people to plain text files.

The third category is always the trap

Here’s a more specific version of the problem. Look at any task app with three or more “future” categories.

Today vs Upcoming vs Anytime vs Someday. Today vs Backlog vs Icebox. P1 vs P2 vs P3 vs P4. The first category is always clear: whatever you’ve named “today” or “high priority” or “active” gets your attention. The second category is the one you check next.

The third category and beyond is where things go to disappear.

Items in “Someday” or “P4” or “Backlog” don’t come back unless you remember to look at them. And you don’t remember to look at them, because the system has trained you not to. The fourth-priority items are by definition the ones you’ve classified as less important than the ones you’re already not finishing.

So the third category becomes a graveyard with good intentions. You feel productive when you put something there, because you’ve made a decision. You’re not feeling productive months later when you realize you’ve forgotten about thirty things.

The math doesn’t work. Categorization only helps if you actually revisit the categories. Most people don’t.

Two views, one rule

Ember works differently. There are two priority views: Now and Next.

Now is what you’re actively working on. Next is what you’ve decided deserves daily attention. There’s no third priority view to act as a graveyard. No Someday, no P4, no “maybe later” bucket.

But priority is optional. New tasks go into a list (Work, Personal, Side Project, or the Inbox) and sit there with nothing attached. No badge, no deadline, no urgency. When you decide a task deserves attention, you promote it to Now or Next. Until then, it stays in a list.

This separates two things most task apps conflate. Capture is free. Prioritization is a deliberate choice you make when you’re ready to make it.

The choice itself is binary. Am I doing this today, or am I not? If yes, Now. If no, Next.

The choice for execution is simpler still. Now is what you do. Next is what you pull from when you’re ready for more. Lists hold everything you haven’t gotten to yet.

Why two and not three

People sometimes ask why I didn’t add a third priority view for “maybe later” or “this week.”

The honest answer: every category I tried adding turned into a graveyard within a week.

A “this week” view didn’t survive because there’s no consistent boundary between today’s work and this week’s work. A “someday” view didn’t survive because nothing went into it that ever came back out. The structure either collapsed back into the two-view model or created new triage work to maintain.

There was already a place for unprioritized tasks: the lists. A task you’re not ready to prioritize doesn’t need a third priority category to live in. It sits in Work or Personal or wherever it makes sense, with no urgency attached, until you decide what to do with it.

The right number of priority categories isn’t the highest one your app supports. It’s the lowest one that still gives you what you need. For prioritization, that’s two. Everything outside that decision belongs in a list, not in another priority view.

The pull mechanic

Two views aren’t enough on their own. What makes them work is how things move between them.

Most task apps push. Tasks roll forward from yesterday into today automatically. The app decides, every morning, that you should still be looking at the things you didn’t do yesterday. The Today view inherits everything you didn’t finish, plus everything new, plus everything scheduled for today.

Ember pulls. Every morning, your Now view resets. Unfinished items go to Next. Scheduled and repeating tasks land in Now automatically because you committed to them in advance. Everything else waits in Next until you decide to bring it forward.

The mechanical difference is small. The psychological difference is large.

A push system makes you the gatekeeper of your own list. You’re constantly evaluating whether something deserves to stay in your today view. You feel like you’re managing the app.

A pull system makes you the chooser. Next is right there, always. You scan it in the morning and pull in what matters. The app doesn’t decide for you. It keeps track until you do.

What you give up, and what you don’t

I should be honest about the tradeoffs.

If you’re running a team and need to assign tasks across people, Ember isn’t the right tool. If your work life requires project hierarchies five layers deep, the two-view system will feel constraining. If you live and die by priority levels because your role demands explicit triage, you’ll miss them.

What I argue is that most personal task management doesn’t actually require those features. We adopt them because the apps offer them, then we maintain them because we adopted them. The features become work in themselves.

Strip them out and you lose less than you’d expect. Most of what you actually need is preserved through other structure:

  • Lists are where capture goes by default. Brain dump into Work, Personal, Side Project, or the Inbox without making any priority decision. Items wait there until you promote them.
  • Subtasks break down complex items without nesting projects inside projects.
  • Repeating tasks appear in Now when they’re due, without you remembering them.
  • Scheduled tasks put things in Now on a specific date.

The structure exists. It lives in the shape of the system instead of in metadata attached to each task.

What Now and Next are supposed to feel like

A finishing thought, because this is the part you can only know by using the app.

Now should feel small. The number of items in Now is supposed to be a number you can hold in your head. Some days that’s three tasks. Some days it’s seven. It’s never twenty, because you’re never trying to do twenty things in one day, even when the app pretends you are.

Next should feel quiet. There’s no countdown on items in Next. No red badge. No “overdue” label. Things sit in Next because they’re supposed to. You pull them when you’re ready. Looking at Next should feel like reading a menu, not paying a debt.

Two views, one binary choice, and a morning reset that gives you a clean Now every day.

That’s the whole system. Smaller than what you’re used to, and that’s the point.

Ember is available on the App Store.