Bratha

Part 1.0 — The Productivity Stack

13 min read

This is Part 1 of 7 in the Productivity Enhancement Series

  • Part 1 — Foundation (2 sub-articles):
  • Part 2 — The Physical Layer:
  • Part 3 — The Workflow Engine (2 sub-articles):
  • Part 4 — The Knowledge System (3 sub-articles):
  • Part 5 — The Tactical Toolkit:
    • Part 5.0: The Tactical Toolkit (digital fluency, supercharged: inbox zero, Readwise, the anti-library, RAG)
  • Part 6 — JIT Project Management:
  • Part 7 — AI as a Worker (3 sub-articles):

Table of Contents

Why start with a stack and not a list of apps?

Because the problem with productivity was never the apps. It’s that people collect them like Pokémon cards with no map of what each one is for. They read that Notion is good and Todoist is good and an AI assistant is good, and they end up with six subscriptions, three half-built systems, and no theory. You cannot optimise a system you can't picture. So before a single tool, we build the picture: the six layers that turn your hours into output, what each layer is responsible for, and the order to build them in. Everything later in the series (the inbox-zero routine, the PARA vault, the agentic worker that runs overnight) is just one of these layers, turned into a protocol.

Where this series sits

The Productive section of this blog has a clean shape, and it’s the same shape as a computer. Cognitive Enhancement is the hardware: the brain’s raw processing power, focus, and recall, plus the chemistry that protects it. Learning and Skill Acquisition is the software: the skills you install onto that hardware and the practice that compiles them. This series is the third pillar, and it’s the one almost nobody treats as a discipline:

==Productivity Enhancement is the operating system: the layer that takes a capable brain running good skills and actually converts your hours into output.==

A fast CPU running great software still does nothing useful if there’s no OS scheduling the work, no file system to find anything, and no way to run a job while you sleep. That’s what most people are missing. They sharpen the brain (sleep, nootropics, deep work) and they learn the skills (courses, reps), and then they lose half of it to a chaotic desktop, a 4,000-item inbox, and a “system” that lives entirely in their own working memory. This series builds the OS.

A note on the source pyramid

The layered model here is adapted from Tiago Forte’s productivity pyramid (digital fluency → task management → habits → personal knowledge management → just-in-time project management).1 It’s a genuinely good map. I’ve kept the parts that are load-bearing (PARA, Progressive Summarisation, JIT project management) and renamed the rest to plainer terms, because some of the original labels were built to sell a course, not to describe a layer. I also added a layer below it (the physical machine) and a layer above it (AI as an autonomous worker), because in 2026 both of those are doing real work that the original pyramid never accounted for.

The thesis: you don’t buy productivity, you build a stack

Here is the through-line for all seven parts, and it’s the same shape as the Cognitive and Learning theses:

Productivity is not an app you install or a hack you copy. It's a stack of layers, built in order, where each layer only works if the one beneath it is solid.

This is the 90/10 rule again, applied to your workflow. The structural work (a machine that doesn’t fight you, a workflow that captures everything, a knowledge base you can actually retrieve from) is 90% of your output. The clever tool at the top is the 10% margin. And just like a stimulant can’t rescue a brain running on five hours of sleep, an AI agent can’t rescue a workflow where nothing is captured, nothing is organised, and every project lives as a vague feeling of dread. It will just let you generate slop faster.

The order is the strategy

The series is built bottom-up, in order of leverage: fix the machine and the room (Part 2) before the workflow; build the workflow (Part 3) before the knowledge base; organise what you know (Part 4) before you reach for tactics; learn the tactics (Part 5) before you try to automate them; and only once a process is solid do you hand it to an agent (Parts 6–7). Most people do this in reverse. They buy the AI subscription to fix a problem that a fixed capture habit and a second monitor would have solved for a quarter of the cost.

The fundamentals didn’t change; the multiplier did

If you look at the old pyramid, every layer still holds. You still need to capture tasks before they vanish. You still need somewhere to put what you learn. You still need to pull projects forward only when they’re due. None of that was invalidated by AI.

What changed is that every layer now has a multiplier sitting on top of it. The fundamental is the same; the ceiling moved.

LayerThe fundamental (unchanged)The AI multiplier (new)
Tactical toolkitInbox zero, fast retrieval, shortcutsAn assistant that reads, triages, and clears the inbox on a schedule
WorkflowCapture → clarify → organise → executeThe assistant drafts the clarify/organise step for you
KnowledgeNotes you can find laterRAG: ask your 1,000-book library a question and get the passage
ProjectsPull the next action when it’s dueAn agent that does the next action while you’re asleep

This is why the series isn’t “AI productivity tips.” The tips are worthless without the layer underneath them. Inbox zero with an AI assistant is trivial once you have a capture habit; it’s impossible if your “system” is leaving emails unread as a reminder. We build the fundamental first, then bolt on the multiplier. Every single time.

The stack, bottom to top

Six layers. Read it from the ground up, because that’s the order you build it in and the order this series is written in.

The six layers

  1. The Physical Layer — the machine and the room (Part 2.0). The computer, the monitors, the RAM, the desk, and the temperature of the room. The substrate everything else runs on. You cannot out-discipline a hot, cramped, single-screen setup.
  2. The Tactical Toolkit — digital fluency (Part 5.0). The literacy layer: keyboard shortcuts, browser, email, calendars, password management, speed reading. Unglamorous, and the highest hourly return of anything in the stack.
  3. The Workflow Engine — task management (Part 3.0). The loop that catches every commitment and moves it to done: Capture, Clarify, Organise, Reflect, Execute.
  4. The Knowledge System — PKM (Part 4.0). Where everything you learn and reference lives so you can retrieve it on demand: PARA, Progressive Summarisation, and the tools you build on top.
  5. JIT Project Management (Part 6.0). The discipline of pulling a project through the system only when it’s actually due, instead of carrying forty open loops at once.
  6. AI as a Worker — the harness (Part 7.0). The apex: once a process is solid and documented, you hand it to an agent that runs it on a schedule, on its own machine, while you do something else.

Notice the inversion from how people actually shop. The base of the stack (a second monitor, a capture habit, keyboard shortcuts) costs almost nothing and returns the most. The apex (an autonomous agent) is the most exciting and returns the least until everything below it is in place. Build the boring layers first.

Habits aren't a layer here, and that's deliberate

The original pyramid puts “habit formation and behaviour change” in the middle of the stack. It belongs in your life, but it doesn’t belong in this series, because it already has its own: see Where habits live below. Productivity systems fail for behavioural reasons far more than technical ones, so the habit work is a prerequisite, not a chapter.

Why “Operating System” and not “Second Brain”

The most popular name for the knowledge layer is “building a second brain.”2 It’s a memorable phrase and I’m dropping it, for one reason: ==a second brain that only stores things is just a nicer-looking pile.== The metaphor stops at memory. It tells you to capture and file, and then it leaves the value sitting in a vault you still have to manually dig through.

The more useful frame, and the one we used in the Behavioral Change series, is an operating system: a layer that doesn’t just hold state, it runs processes. An OS stores your files, yes, but it also schedules jobs, runs programs, and does work while you’re not looking.

A concrete example from my own setup: I don’t track supplement stock in my head or in a note. I built a small Retool app that holds the inventory, knows my daily doses, and forecasts the run-out date for each compound so I reorder from iHerb before anything lapses. That’s the difference in one object. A second brain would be a note titled “supplements” that I’d have to read and do mental arithmetic on. An operating system is a tool that tells me what to reorder and when, without my attention. The knowledge layer's job is not to remember things for you. It's to act on what it remembers. That’s why this series calls it the Operating System, and why Part 4 ends not with a note-taking method but with building tools.

Two motifs that run through everything

Two ideas show up in almost every article from here on, so they get introduced once, here.

1. The self-improving workflow. Every workflow you hand to an AI should get sharper every time you correct it, not stay the same. The mechanism is two plain text files: a skills.md (or a skill folder) that holds the reusable how-to for a task, and a project instruction that holds the standing context. When the output is wrong, you don’t just fix this one output, you have the assistant write the correction back into those files. Next time, it starts from the corrected version. Feedback you give once becomes feedback the system keeps. Done consistently, a task you fought with in January runs itself by March. This is the spine of Part 3.1, and it’s why this very blog improves: corrections get saved, not repeated.

2. The anti-library and RAG. Reading is the slowest way to get information into your head, and you will never read everything you own. So stop trying. Maintain an anti-library: the books you haven’t read but know you’ll want one day.3 Mine is a Google Sheet of 1,000+ titles, each tagged by topic, so I can pull “everything I have on negotiation” in a second. The upgrade is RAG (retrieval-augmented generation): point an AI at that library and ask it a question, and it retrieves the relevant passage and answers from it, without you reading the whole book first. Reading is good but slow; retrieval is the supercharger. Full build in Part 5.0.

Where habits live

This series will lean on habits constantly (a capture habit, a weekly review, a shutdown ritual) but it won’t teach them, because that’s a whole discipline of its own and it already has a home on this blog.

If a layer in this series keeps collapsing (you set up the perfect capture inbox and then never open it), the problem isn’t the system, it’s the behaviour, and the fix is in the Behavioral Change series: identity and the lane, friction and the 11 constraints, and the Regime that holds it all together. Treat that series as the prerequisite reading. A productivity stack is only as durable as the habits that run it.

Part 1 Takeaways

  • Productivity is the operating system of the Productive section: Cognitive is the hardware, Learning is the software, this converts hours into output.
  • You don’t buy productivity, you build a stack of six layers, bottom to top, where each layer needs the one beneath it.
  • The fundamentals didn’t change; AI added a multiplier on top of every layer. Build the fundamental first, then bolt on the multiplier.
  • Build the boring layers first. A second monitor and a capture habit beat an autonomous agent sitting on top of chaos.
  • The knowledge layer is an Operating System (it acts), not a Second Brain (it only stores).
  • Two motifs run throughout: the self-improving workflow (skills.md + project instructions) and the anti-library + RAG.
  • Habits are a prerequisite, not a chapter here. They live in the Behavioral Change series.

Your Productivity Stack Task List

Before Part 2

  • Name your current weakest layer. Be honest: is it the machine, the toolkit, the workflow, the knowledge base, your project load, or automation?
  • Resist starting at the top. If your instinct was “I need an AI agent,” that’s usually a sign a lower layer is broken.
  • Set up the two plain-text files you’ll use all series: one skills.md and one project-instructions note. Empty is fine; you’ll fill them as you go.
  • If you don’t already keep one, start an anti-library list (a single sheet, one row per book, a topic tag in column B).
  • If your systems keep collapsing for behavioural reasons, read Behavioral Change Part 1 before continuing here.

Sources & references

Footnotes

  1. Tiago Forte, “The Hierarchy of Productivity Systems” / Forte Labs productivity pyramid. The original five-tier model (digital fluency, task management, habit formation, personal knowledge management, just-in-time project management) is the basis adapted and renamed throughout this series. The roots of the task-management layer trace to David Allen, Getting Things Done (2001), whose capture–clarify–organise–reflect–engage loop this series renames “Execute” at the final step. ↩

  2. Tiago Forte, Building a Second Brain (2022). Source of the PARA method and Progressive Summarisation, both kept in this series (Part 4). The “second brain” framing itself is the one term deliberately replaced here with “Operating System.” ↩

  3. The “anti-library” comes from Nassim Nicholas Taleb, The Black Swan (2007), describing Umberto Eco’s unread-books collection as a research tool rather than a trophy shelf: the value of a library is in what it lets you reach for, not in what you’ve already read. ↩

Graph View

Backlinks