Notion Goal Setting - "Goal Outcome" & "Value Goals" Databases (Life OS)

The core idea is to connect “what matters” to “what gets done” by building two linked databases—Value Goals and Goal Outcomes—so measurable targets (outcomes) stay emotionally grounded (values) and can be executed through projects and tasks. In the Life OS structure, Goal Outcomes sit tightly between values and the project/task layers, acting as the mid-level connective tissue that turns aspirations into trackable work.

Value Goals represent what someone cares about—aspirations, identity, and long-term direction—but they aren’t inherently measurable. Goal Outcomes, by contrast, are specific, quantifiable results that make progress unambiguous: they can be counted, tracked, and marked complete without relying on vague self-judgment. The system separates the two on purpose. Starting with measurable outcomes alone can produce targets that feel cold or transactional and may not reflect what truly motivates action. Starting with values alone can leave work direction too fuzzy to plan projects and evaluate progress. The solution is a two-step design: define outcomes that are actionable and measurable, then tie them back to the values they serve so the work feels meaningful and sustainable.

The databases are linked so that every Value Goal must have at least one Goal Outcome (and sometimes multiple), and every Goal Outcome must connect back to one or more Value Goals—preventing “orphaned” goals that can’t be justified or executed. A Value Goal can persist over time even after individual outcomes are completed. Once a Goal Outcome hits its measurable target, it moves to a completed state, while the Value Goal remains active until the underlying value no longer holds. If a Value Goal only had a single outcome, the system would force the next outcome to raise the bar—requiring a bigger measurement or a new target that still advances the same underlying value.

Goal Outcomes also include progress tracking and status logic. The system uses an “underway” view (excluding completed items) and three statuses: Not started, Complete, and additional operational states such as Green (in motion/active), Pause (started but temporarily stopped), and Next in cue (important but not yet bandwidth-available). This supports week-to-week prioritization by making it clear what’s actively being worked on versus what’s waiting for future capacity.

To avoid treating outcomes as mere numbers, each Goal Outcome can be supported by either projects or routines/habits. Most outcomes are executed through projects, since projects naturally aggregate tasks into meaningful chunks of work. But some outcomes—like reading and summarizing books—can be driven by routines, with daily or weekly habits scheduled and tagged to the relevant “pillar” (e.g., learning). The system’s logic stays consistent: outcomes define the measurable target, projects/tasks or habits provide the execution mechanism.

A practical example ties “extraordinary knowledge” to two measurable outcomes: reading and summarizing 20 books and interviewing 15 experts for a podcast. Those outcomes are then linked upward to the Value Goal (knowledge that improves client insight and content quality) and downward to the projects and tasks that make the outcomes achievable. The result is a hierarchy where hourly and daily work is explicitly connected to long-term aspirations, and periodic cycle reviews (weekly/monthly/quarterly) can quickly identify what’s working, stalled, or misaligned—keeping the whole pyramid coherent over time.