Concept card

Second Brain (PARA)

As of 2026-10-10

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Second Brain (PARA)?

T. F.'s PARA sorts notes by actionability — Projects, Areas, Resources, Archives — not by topic, which is exactly why it scales from a handful of notes to 10,000 without collapsing into an unusable folder tree.

What it is

T. F.'s knowledge management system organizing notes by actionability (Projects, Areas, Resources, Archives), not by topic. Scales from 10 to 10,000 notes without collapsing.

Example: In a real Category M · Productivity & AI engagement, Second Brain (PARA) is used to align business ownership, data contracts, and delivery sequencing before solution build starts.

Counterexample: Teams jumping directly into dashboards without clarifying Second Brain (PARA) usually create rework, semantic drift, and sponsor distrust.

Decision tree: If the business question is stable and recurring, prioritize canonical modeling; if volatile, start with a constrained pilot and explicit assumptions; if data quality is low, run remediation before scale-out.

KPI exercise: define baseline and 90-day target for freshness, trust score, adoption rate, and decision latency; then attribute variance to one change at a time.

Case prompt: design a 2-sprint plan using Second Brain (PARA) for a cross-country SAP analytics program in Productivity & AI, with trade-offs, governance checkpoints, and executive narrative.

Why it matters

Sorting by actionability (is this active, ongoing, reference, or dead?) rather than by subject avoids the folder-taxonomy sprawl that kills most note systems past a few hundred entries.
The four-bucket structure is deliberately coarse, which is exactly why it survives the jump from 10 notes to 10,000 without a redesign.
For a consultant juggling multiple client engagements, the Project/Area split keeps live delivery material separate from durable reference material — the two get conflated in most ad hoc systems.

Key points

T. F.'s knowledge management system organizing notes by actionability (Projects, Areas, Resources, Archives), not by topic.
Scales from 10 to 10,000 notes without collapsing.
Archives exist to be searched under deadline pressure, not to be admired — if retrieving a closed engagement's ADR takes longer than re-deriving it, the Archive has failed its one job.
The PARA boundary must extend to any persistent AI workspace (a Joule for Consultants Expert, a custom GPT) — a 'Resource' that has ingested a client's raw documents is not inert like a template file.
Filing decisions happen at capture time, not during a quarterly cleanup — a note that sits unfiled for months has already cost more in re-finding time than filing it would have.
PARA fails silently, not loudly: nothing breaks when Projects and Resources blur, which is exactly why it needs a deliberate quarterly audit rather than being trusted to self-correct.
The system scales by staying coarse — resist the urge to add sub-categories under each of the four buckets; granularity is what killed the folder-tree systems PARA replaced.

Terms used on this page

Judgment layer: The part of the work that AI cannot do — prioritisation, trade-offs, client-context reading.
AI-first draft: Workflow where AI produces the first pass (code, memo, slide) and the consultant edits rather than writes from scratch.
Agent reliability: The consistency, cost, safety, and policy compliance of an agent across repeated runs.
Project (PARA): A short-term effort with a specific, defined outcome and an end date — the bucket every SAP mission's live deliverables belong in, archived rather than deleted when it closes.
Area (PARA): A standing responsibility with no end date — certification renewal, invoicing, personal-brand content — the bucket most often neglected because nothing in it demands attention urgently.
Actionability sort: T. F.'s filing rule: sort any note by whether it is currently actionable, never by the subject it happens to be about — the reason PARA scales where topic-based folders collapse.
Expert Workspace filing boundary: The discipline of treating a persistent AI tool's ingested context (a Joule for Consultants Expert, a custom GPT) as a Project artifact for the mission's duration, not a permanent fifth PARA bucket.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →