Build a Second Brain with Notion for a Design Team’s Client Work

A design studio can build a second brain with notion so critique notes, handoff links, and client decisions sit on the project they belong to. This is a filing habit for design work, not a life-operating system and not a template shop. Tiago Forte’s PARA method, on his site, sorts notes into projects, areas, resources, and archives. Used here, those four labels cover studio work only. This page does not promise faster design, better memory, or finished goals.

Capture still starts in the getting things done method notes. Timed making still sits in the pomodoro technique deep dive. This page is where a kept note goes after you decide it belongs to a client job.

Four folders, aimed at design work

Forte’s PARA article defines projects as short-term efforts with a goal, areas as ongoing responsibilities, resources as topics you are learning, and archives as items from the other three that are no longer active. He describes four top-level folders. For a design team, translate them like this. A project ends: “Publish the October homepage” or “Send the revised hero for the launch review.” An area does not end: “Client: Northwind,” “Design system,” or “Proposals.” A resource is a topic you study: “type pairing” or “critique notes that are not tied to one job.” An archive is a shipped or paused job you may open later.

The same article’s test matters on a design board. A list that only says “brand” or “clients” is a list of areas. An area does not finish. Until you split it into projects with an outcome, you cannot see which delivery is actually in progress. If you cannot name the outcome and the moment the row is done, it is an area, not a project.

How to build a second brain with notion this afternoon

Create one Notion page for the studio, not a personal life wiki. Add one database with these properties and nothing else on day one:

• Name. The delivery you would say in standup.
• Category. A select with four options only: Project, Area, Resource, Archive.
• Done when. Text. Required for Project. Blank for Area and Resource.
• Link. URL to the file, the ticket, or the live page. Do not paste the design file into Notion.

That is the whole schema. If you add scores, owners, and review dates first, you will design the database instead of filing the critique notes you already have.

Forte’s article says to organize by the projects you are committed to now, not by school-style subjects. A homepage rewrite does not go under a page called “Ideas” or “Writing.” It goes on the project row whose Done when line says the new homepage is published. Child pages on that row hold the critique, the decision, and the link to the file.

File the work you already have

Open the shared drive, the chat pins, and the old Notion workspace. Do not write new strategy. For each existing note, ask one question: does this support a delivery that ends, a client or system that continues, a topic the team is learning, or a job that is already inactive? Set Category and move on. Cap the first pass at one sitting. A second brain that needs a weekend of setup is competing with the client work it was meant to hold.

When a delivery ships or is paused, change Category to Archive. Do not delete the row. Forte describes archives as completed or paused projects and inactive items you might reopen. Archived rows stay searchable and leave the active view.

After the first rows exist, make two views. One filter is Category is Project. The other hides Archive. Do not add a chart of note counts. The Project view should read like a list of design deliveries.

Rules that keep client notes findable

One note lives on one row. If a critique serves two deliveries, file it on the one you will open next and paste a link on the other. Duplicate pages drift apart, and a client will get two versions of the same decision.

“Learn Notion” is not a design project. “Replace the homepage hero before the launch review” is. If a project row has an empty Done when field, rename it or move it to Area.

Notion is not the system of record for contracts, invoices, or the design file itself. Those stay in the tool that already owns them. Link the file. Copying it into Notion creates two masters and no owner.

Once a week, open the Project view before critique. For each row, write the next design action in one line or move the row to Archive if nobody will touch it. This is a filing pass. If the row needs a decision, write that decision in the first line of the page and stop.

What not to add

You do not need a template marketplace, an AI filing add-on, or a second notes app to build a second brain with notion. Forte presents PARA as four folders in a drive or a notes app. If the studio already lives in a shared drive, use four folders there and skip Notion. The method does not require this product, and this page is not a recommendation to buy a plan.

Do not score how polished the workspace looks. The test is whether the designer opening a delivery finds the critique and the file link on that row, instead of hunting a subject page called Ideas.

Name rows as deliveries. “Client onboarding” is an area. “Send the October welcome screens” is a project. “Brand” is an area. If two designers would file the same critique on two different rows, the names are too vague.

Meeting notes are child pages of the delivery they serve. Put the date in the child title and the decision in the first line. A meeting with no decision and no next action does not need a page. The test in Forte’s PARA article is to put the note where you will use it.

Tomorrow: create the page, the four options, and file the notes already attached to live client work. Then return to the delivery you meant to design. That is how a studio can build a second brain with notion without turning the setup into the job.