Pattern

Keep one inbox for unassigned work

Loose tasks become expensive when each one invents its own storage place. Keep one small inbox for work that has no project yet, then review it often enough that the inbox remains a capture point rather than a second backlog nobody trusts.

About 2 min read

Before you use it

Use when
  • A useful task or idea appears before you know which project, owner or schedule it belongs to.

Keep this limit in mind

  • The inbox is temporary routing, not a reward system, priority engine or permanent project category. Do not store secrets or sensitive personal material merely for convenience.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Steps

  1. Capture the item in one agreed inbox with enough context to recognize it later.
  2. During review, either assign it to a real project or owner, schedule it, do it, or delete it.
  3. If the inbox keeps growing, fix the review or ownership problem instead of adding more labels.

What to look for

Loose tasks become expensive when each one invents its own storage place. Keep one small inbox for work that has no project yet, then review it often enough that the inbox remains a capture point rather than a second backlog nobody trusts.

Why it matters

Loose tasks become expensive when each one invents its own storage place. Keep one small inbox for work that has no project yet, then review it often enough that the inbox remains a capture point rather than a second backlog nobody trusts.

An example

A note such as ‘check export failures from Tuesday run’ belongs in the inbox until it is assigned. ‘Improve everything’ does not become useful merely because it has a checkbox.

Check your result

Every reviewed inbox item has a clearer home, owner, next action or explicit deletion decision.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingKeep one inbox for unassigned work

Evidence and sources
Provides context

First-party source of this practical exercise.

Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding.

This Container Is Your Personal Hub for Tasks That Don’t Belong to Any Specific) · data/life-os-content/unassigned-task-inbox.json

All sources (1)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-12

Read this idea as JSON · Release details