How to Manage Projects with Four Intensities

The core takeaway is that “efforts” are a more workable way to manage real-world work than rigid “projects,” because efforts let people adapt as information changes—without losing momentum. In the Ace system (Atlas, Calendar, Efforts), efforts act as the action layer: a way to allocate energy across what’s active, what’s simmering in the background, and what’s temporarily sleeping. The payoff is practical—clearer prioritization, less guilt, and faster bandwidth adjustments when priorities shift.

Efforts are defined as exertions of energy where steps, deadlines, and outcomes may be unclear or change over time. Projects, by contrast, are sequences of tasks with a defined timeline aimed at a specific outcome—often “top-down,” with tightly specified steps. That difference matters because project-based productivity tends to break when steps aren’t clear or when they change too rapidly. The transcript frames this as a mismatch between how work actually unfolds (often with limited information) and how project plans demand linear certainty. Efforts are presented as the “bottom-up” counterpart: they provide enough structure to move forward while staying flexible enough to evolve.

To make efforts usable day-to-day, the system uses four “intensities” represented through a folder structure: **On** (turned on efforts), **Ongoing** (broader active efforts), **Simmering** (back-burner work still progressing in the background), and **Sleeping** (completed, cold-storage, or temporarily irrelevant efforts). The key operational idea is that these states are visible and movable. When someone feels overwhelmed, they can scan what’s truly turned on, then re-rank or drag items to simmering to reduce daily pressure—without deleting the work. The transcript emphasizes that moving an effort from on to simmering functions as a stress and guilt reducer because it removes the constant reminder of “unfinished” tasks while preserving the possibility of returning later.

The system also ties efforts to a unified “home note” dashboard and a consistent notation approach across both notes and folders. Each core headspace—Atlas (knowledge), Calendar (time), and Efforts (action)—has its own notes folder, keeping different kinds of work from blending together. Action-oriented effort notes live in an actions folder, time-oriented calendar notes in a calendar folder, and knowledge/idea-oriented notes in an ideas folder.

A concrete example shows how an effort’s intensity can change over a course of days: a UCLA course is tracked as it winds down, while a “Workshop 12” effort ramps up. Another example demonstrates dragging a “podcast” effort from turned on to simmering when it’s not the right time, then keeping it off the daily radar while it remains available for future use. The transcript also illustrates how ongoing efforts can spawn smaller, time-specific projects—like a targeted “Ideaverse launch” or “Light workshops”—so bandwidth estimates reflect reality rather than best-case planning.

Finally, the lesson positions Ace as a practical, unified way to orient attention across knowledge, time, and action—promising “clarity, calm, and control” by making effort intensity visible and tangible. The next step is expected to be “linking your thinking,” but the immediate value here is how to manage what to work on now, what to hold, and what to pause without losing control of intentions and actions.