Workflowy Second Brain: Turn an Outline Into Useful Knowledge

A Workflowy second brain starts with a small outline for active projects, reusable references, and material you have finished using. Give each project a readable summary and connect its supporting notes, so you can retrieve an answer without expanding your entire outline.

For work that continues across assistants, fenbs can hold selected summaries, decisions, and next steps outside Workflowy. This is a manual transfer of useful context; fenbs does not connect to Workflowy or synchronize its bullets.

How do you create an outline you will actually use?

1. Create three starting branches: Active projects, References, and Archive. Add a temporary Inbox only if you need somewhere to capture notes before sorting them.
2. Under Active projects, add one bullet per outcome. Use a meaningful name such as Library workshop proposal rather than a broad subject such as Work.
3. Give each project child bullets for Goal, Current position, Sources, Open questions, and Next action. Write a sentence under each before adding more structure.
4. Move reusable knowledge into References and point to it from the project. Keep the reasoning next to the source it interprets.
5. Review the active branch regularly. Update the current answer, clear the Inbox, and move finished projects into Archive.

Workflowy organizes content as a nested outline. You can focus on an individual bullet and its children, then return through the surrounding structure; its getting started guide↗ (opens in a new tab) explains that model. Use this ability to work inside one project at a time rather than making every project visible at once.

Keep your starting structure shallow. If a captured note needs seven decisions about where it belongs, you have made capture too expensive. A project branch and a few descriptive bullets are enough until actual retrieval problems show you what needs changing.

What makes a bullet useful months later?

Write enough context for the bullet to make sense outside the moment you captured it. “Ask about space” is ambiguous later. “Ask the library coordinator whether workshop tables can seat groups of four” preserves the subject, question, and person who can answer it.

For a source note, record its title, original location, and the particular claim or question it supports. Keep your interpretation separate from any quotation. When an important fact can change, add when you checked it so a future reader knows whether another check is needed.

For example, a library policy note could say that an official room-use page needs checking before the proposal is finalized. The project summary should not quietly turn that reminder into confirmed permission. An assistant working from your outline needs to see which facts are established and which are still questions.

The AI second brain guide explains how a reusable knowledge collection supports future work. Here the practical test is simpler: can you find the original evidence and explain why you kept it?

When should you use tags, links, or mirrors?

Use each feature for a specific relationship. A tag groups items that share a useful label. A link points to a separate item. A mirror displays the same underlying content in another place. Workflowy describes these distinctions in its organization guide↗ (opens in a new tab).

Be especially careful with mirrors: editing the mirrored content changes it in its other locations too, as the mirror documentation↗ (opens in a new tab) explains. Use that behavior for information that should remain identical. Use a separate historical note when you need to preserve what was true at an earlier meeting.

Avoid tagging every bullet. Choose a small vocabulary whose labels answer questions you actually ask. Two labels that mean nearly the same thing make search less reliable, and a long collection of tags does not compensate for unclear writing.

How can you turn an outline into accurate AI context?

Select the project summary and the few source notes needed for the current task. Write a short instruction stating the output, relevant constraints, and unanswered questions. You do not need to provide your complete outline for an assistant to help draft a workshop proposal.

Nested notes can lose meaning when taken out of their parents. Before sharing a small excerpt, check that it names the project, the source, and the status of the information. Replace an isolated “approved” with a sentence explaining what was approved, by whom, and where the evidence lives.

Ask the assistant to separate facts supported by the notes from suggested improvements. Then compare its important claims with the sources yourself. If it cannot tell whether the room is confirmed, that uncertainty should remain visible in the output rather than becoming a confident assumption.

An AI brain also needs the current work state; selected context can go into fenbs while the detailed outline remains your reference collection.

What should you check during a regular review?

Read each active project from the top as if someone else wrote it. Can you state its goal, identify the current decision, and find the next action? If those answers are scattered among dated notes, rewrite the summary and retain the supporting details below it.

Remove stale next actions after completing them. Identify questions waiting on a person. Move finished material out of the active branch while keeping its final summary and useful sources. Spend review time improving the answers you need, not decorating an outline you already understand.

How to do this with fenbs

1. Create a free account and add one active project from your outline.
2. Manually record its current goal, constraints, and open questions in AI context notes. Save selected references in Links and listings, checking their access requirements.
3. Record human-approved choices in Decisions and rules, then add tasks for the follow-up work you want an assistant to help complete.
4. Connect a supported AI app through Integrations. Ask it to read context first and save progress and the next starting point before it stops.

A private Workflowy link remains a private reference; saving it does not give an assistant access. Provide any approved excerpt it needs separately. fenbs is not the right fit when your whole workflow is personal outlining and you do not need a shared record for ongoing AI work.

Browse the second-brain guides for other formats, or the Craft setup if you prefer project documents to a large outline.