Design a Today view that reduces overwhelm

Give the Today view one job

The page should answer one practical question: what deserves attention now? It is not the complete workspace and it is not a permanent home for every open task. Projects, reference material, future work and finished history can remain connected without appearing in the daily decision surface.

This article’s framework is a design judgment rather than a claim that one layout guarantees productivity or treats anxiety. Its purpose is narrower: make the reasons for showing, ordering and removing work explicit so the reader spends less effort interpreting the dashboard.

Notion's official views, filters and sorts documentation describes how each database view can have its own visibility, filter and sort settings. Notion's guide to database-view types illustrates how teams can create different views of the same database to surface information for different needs. Those capabilities can implement a Today view, but its useful behavior still depends on the rules chosen by the person designing it.

Write the entry rule first

An item should appear because it meets a rule the user can explain. Common reasons include a confirmed due date of today, an overdue commitment, an intentional plan for today or a dependency that needs a decision. Avoid rules that simply include every unfinished item.

Write the rule in plain language before building the filter. For example: show incomplete items that are due today or earlier, plus incomplete items explicitly selected for today. This wording reveals two different reasons for visibility—commitment and deliberate focus—and makes it easier to investigate an unexpected result.

Check whether each required field is dependable. A filter based on due date cannot protect the user if meaningful deadlines are frequently blank or used as rough estimates. In that case, distinguish committed dates from planning dates or add a verification state before relying on them.

Separate Now, Next and Waiting

Three states are often enough to explain the page without turning every difference into a new section.

These labels describe the relationship between the user and the work, not the global importance of the project. A high-value task can remain in Waiting because another person must respond. A modest administrative task can sit in Now because it is due and actionable.

Keep supporting context close to the action but visually secondary. The task name, responsible person and meaningful date may be enough in the main view. Detailed notes, relationships and historical information can remain inside the record.

• Now contains work that can begin and deserves attention in the current period.
• Next contains a small queue that can follow when current work moves or finishes.
• Waiting contains visible dependencies that need monitoring but cannot be advanced directly.

Choose one ordering rule people can understand

Sorting cannot resolve every conflict between urgency, value, effort and dependency. A useful default chooses one or two signals and explains what they mean. For example, overdue commitments may appear first, followed by confirmed work due today, while a manually selected focus stays visually distinct.

Avoid adding several badges that restate the same conclusion. If an item’s position and date already show that it is overdue, another red priority badge may add noise without changing the decision. Visual signals become easier to trust when each one has a single meaning.

When priorities genuinely conflict, leave room for a human choice. A Today view should support judgment, not pretend that a formula has proved which responsibility matters most.

Define the exit rule

Every visible item needs a destination when the day changes. Completed work should leave the active view and remain available in appropriate history. Work that still matters can be rescheduled deliberately. Work that is blocked can move to Waiting. An overdue commitment may remain visible because its unresolved state is the important signal.

The dangerous outcome is silent accumulation. If unfinished items remain forever without a fresh decision, the Today view gradually becomes the complete backlog. A short review at the end of the day or start of the next one can make each carry-over intentional.

Use these exit questions:

• Is the item complete and correctly recorded?
• Is the date still a real commitment?
• Is another person or event blocking progress?
• Should the work return to its project rather than remain in daily focus?
• Does keeping it visible communicate a genuine exception?

Audit six messy records with the rules

Assume the entry rule is the one defined earlier: show incomplete items due today or earlier, plus incomplete items deliberately selected for today. Order actionable overdue commitments first, confirmed work due today second and manually selected work after those groups. Keep Waiting separate from actionable work. At review, completed work moves to history, rescheduling is deliberate, blocked work receives a monitoring decision and a valid overdue exception can remain visible.

The result is explainable: four actionable or queued records appear in Now or Next, the blocked record appears separately in Waiting and the completed record stays out. The example also exposes a rule choice: manually selected undated work can enter as Next, but an undated item that was not selected would remain in its project queue.

Then test the interface from a new user’s perspective. Can they tell why an item is visible? Can they distinguish action from waiting? Can they find the context needed to proceed? Can they complete or reschedule work without manually cleaning several views?

If the answer is unclear, fix the rule or label before adding more decoration. Predictability is the foundation: every visible item should have an understandable reason to be there and a clear next decision.

• Overdue record: Send signed contract is incomplete, actionable and due yesterday. Appears: yes, because it is overdue. Today state: Now. Ordering reason: first, ahead of work due today. Exit decision: keep it visible as a genuine overdue exception until it is completed or its commitment is deliberately renegotiated; do not silently change the date.
• Due-today record: Submit expense report is incomplete, actionable and due today. Appears: yes, because its confirmed due date is today. Today state: Now. Ordering reason: after overdue commitments. Exit decision: in this example it is completed during the day, so it leaves the active view and remains in history.
• Undated record: Outline the proposal has no committed date but was deliberately selected for today. Appears: yes, because manual selection satisfies the entry rule. Today state: Next. Ordering reason: after overdue and due-today work because it is intentional focus, not a dated commitment. Exit decision: if it is not started, remove today's selection and return it to the project queue unless a new deliberate plan is made.
• Blocked record: Approve launch copy is incomplete and due today, but it is waiting for legal feedback. Appears: yes, because it is due today. Today state: Waiting. Ordering reason: it is separated from actionable Now and Next work rather than ranked against them. Exit decision: keep it in Waiting only with an owner and next check date; remove it from Today when monitoring is no longer needed.
• Recurring record: Complete the weekly metrics review is incomplete and due today. Appears: yes, because the current occurrence is due today. Today state: Now. Ordering reason: it shares the due-today group; the rule does not manufacture a priority over the other due-today item. Exit decision: complete and archive this occurrence, then schedule the next occurrence for its real date instead of carrying the completed one forward.
• Completed record: Publish meeting notes is already complete. Appears: no, because the entry rule admits only incomplete work. Today state: none; completed is outside Now, Next and Waiting. Ordering reason: none, because it is excluded before sorting. Exit decision: leave it in history rather than returning it to the active view.