Concepts & methods

Pillars, Pipelines and Vaults: the Notion life OS, honestly costed

August Bradley's PPV is the most complete life-OS methodology ever built in Notion, and the most demanding. A reference entry on what the three layers do, who thrives on it, and the maintenance bill nobody skips.

Aleem O'BalogunBy Aleem O'Balogun|Updated |4 min read

The short answer

Pillars, Pipelines and Vaults (PPV) is August Bradley's Notion-native methodology for a personal life operating system: Pillars hold your life areas and values, Pipelines move goals and projects through stages, and Vaults store knowledge. It is the most complete framework of the Notion life-OS movement, with real review cadences built in, and it demands more upkeep than any other system in this library.

What it is, and who made it

PPV is the methodology August Bradley (with Jane Bradley) built and began teaching in 2020, the system that effectively started the Notion life-OS movement; the official home is notionlifedesign.com. The architecture has three layers. Pillars are your life areas and the values behind them, the why that everything else hangs from. Pipelines are databases that move things through stages: goals from someday to done, projects through their phases. Vaults hold knowledge, linked back to the work it serves. Threaded through all three is the part most template buyers miss: a built-in cadence of daily, weekly, monthly, and quarterly reviews that connects the layers, so goals are supposed to be looked at, not just stored.

What it actually offers

PPV's honest distinction is completeness. Where most Notion setups are a dashboard with aspirations, PPV specifies the whole chain from values to pillars to goals to projects to this week's tasks, with linked databases making the chain navigable in both directions; you can genuinely ask what this Tuesday task serves and follow the links to an answer. And unlike the storage-only systems, it has an operating rhythm: the review cadences are the method, not an accessory, which makes PPV the rare framework in this library that takes running seriously rather than just organising.

Where it breaks

The bill is upkeep, and Bradley is upfront about it, which is to his credit. Every moving part is a database you maintain by hand: statuses to update, links to set, reviews to actually hold. Practitioners describe hours a week of system tending, and the failure pattern is well documented across the template graveyards: a magnificent three-weekend build, a month of dutiful updating, then quiet abandonment when a busy fortnight breaks the habit chain. The system's completeness is also its fragility, because a chain from values to tasks only navigates if every link stays current. PPV thrives with people who genuinely enjoy systems as a craft; it punishes everyone else in proportion to their ambition.

How it maps to the notice loop

On the notice loop, PPV is the closest thing the canon has to the full six verbs on paper: capture into inboxes, review cadences that force noticing, weekly shaping against pillars, and a learn step in the quarterly look-back. What it lacks is a runner. Every verb executes only when you do; the noticing is you opening the weekly template, the shaping is you dragging database rows, and on the week you skip it, nothing happens at all. PPV is the strongest argument in the life-OS category that the loop's design is right, and the clearest demonstration that a loop without an engine is a rota pinned to a wall.

Sources

Primary sources for the method as described; the assessment of maintenance cost reflects the method's own positioning and widely documented practitioner experience.

  • Jane and August Bradley, Notion Life Design (the official PPV course site) and August Bradley's Notion systems videos. The three layers, the review cadences, and the system's own upkeep framing.
← All guides