How to manage projects, tasks, people, and yourself using the Obsidian app with Francisco Bricio

TL;DR

Use a minimal “Focus” home note to reduce decision fatigue and keep attention on a few core documents.

Briefing Cornell Notes

Briefing

A practical Obsidian-based system keeps projects moving by forcing a weekly rhythm: every active project must advance at least one “next step,” so momentum beats perfection. Francisco Bricio’s setup is designed for someone who gets distracted easily—so it narrows attention to a small set of decisions, tasks, and daily priorities while still connecting work to people, tools, and context.

Everything starts from a single “home” note called Focus. It’s intentionally minimal: a reference area containing only three key documents—Focus, Command, and To Do—so the interface doesn’t become another distraction. “Command” is the naming convention for projects and ideas, created quickly with a shortcut, and it acts as the entry point for ongoing work.

To decide whether an idea deserves time, Bricio uses a 7Ws filter: Who, What, Why, When, Where, Whom, and (implicitly) how it fits into life. “Who” maps to the roles he plays (husband, father, godfather, etc.), which determines whether a project belongs in that lane. “What” defines daily standards and “no negotiables”—the consistent actions that must happen to reach goals. “Why” ties projects to personal motivation, helping prevent drift when motivation fades. “Whom” identifies the people who provide support; each project should have a named person responsible for helping execute it. “Where” is about tools and environment, with a clear rule to avoid tool-hopping and only adopt new tools when they’re genuinely worth it.

The system then turns those decisions into an operating cadence. On the Command page, ongoing projects are grouped by business and personal categories. Each project displays a “next step” at the top—typically something small but concrete like a call or email—plus a “why,” a list of contacts, and a curated set of “next tasks” that won’t overwhelm him. Larger tasks are kept in an “oven” area—items that are important but not ready to surface constantly.

Obsidian’s linking and URL capabilities connect project notes to live external information. For the Attention project, clicking an email link opens Gmail already filtered for that project, pulling relevant messages in one action. Company research is fed in through Owler, and a journal section logs what’s been happening over time. A “today” view aggregates the day’s most important items—three priorities—using search across projects so daily planning stays grounded in real work.

Capturing ideas isn’t limited to Obsidian. Bricio uses Drafts as the initial capture tool on mobile and iPad, then routes items into Obsidian to build a master task list. A companion plugin moves completed tags to the bottom of the file, keeping the active list clean.

The through-line is simple: align projects to personal interests and principles, keep the interface small, and require weekly progress on every active project. The result is a workflow that reduces anxiety by making the next action obvious—and makes long-term goals survivable by turning them into repeatable weekly motion.

Cornell Notes

Francisco Bricio’s Obsidian workflow manages projects, tasks, people, and personal focus by combining a decision filter (7Ws) with a weekly execution rule: every active project must move forward at least one “next step” each week. His Focus home note stays minimal, linking to Command (projects/ideas), and To Do (a master task list). Each project note is structured around a top-level “next step,” a “why,” relevant contacts, and a small set of “next tasks,” while larger items sit in an “oven” area until they’re ready. Daily planning uses Obsidian search to surface the three most important tasks for today across all projects. Capture happens in Drafts first, then routes into Obsidian, keeping the system fast and low-friction.

How does the 7Ws framework prevent distractions from becoming “real projects”?

Bricio uses 7Ws as a gate before committing time. “Who” checks which life role the work belongs to (husband, father, godfather, etc.). “What” defines whether it matches daily standards and “no negotiables.” “Why” confirms the personal motivation behind the effort. “Whom” ensures there’s support—each project should have a named person who helps execute it. “Where” limits tool sprawl by discouraging constant adoption of new tools unless they’re truly worth it. “When” and the remaining Ws function as additional alignment checks so misaligned ideas don’t steal attention.

What does “progress not perfection” look like inside his project notes?

Every ongoing project shows a single “next step” at the top—small, concrete actions like one phone call or one email. The system requires that, regardless of project size, each active project advances at least one step per week. That weekly motion keeps projects alive without demanding perfect execution. The note also includes “next tasks” (curated so they don’t overwhelm) and an “oven” section for important items that should not constantly compete with immediate priorities.

How does Obsidian reduce the effort of staying up to date on a project?

Project notes link out to live sources. For example, in the Attention project, clicking an email link opens Gmail with a search already set for that project, pulling relevant messages in one click. Owler feeds company updates for companies tied to his work, and a journal section logs what’s been happening over time. These links keep context attached to the project rather than scattered across apps.

What keeps daily planning from turning into a giant, unmanageable checklist?

Bricio’s “today” view surfaces only the three most important tasks for the day. Instead of manually copying tasks, it uses Obsidian search across projects to pull each project’s “next step” or today-specific items. Meeting notes are written into an agenda-style section with timestamps (e.g., 10 a.m., 11 a.m., 2 p.m.), so the day stays structured without ballooning into hundreds of tasks.

Why does he avoid adding too many tools, and how is that rule implemented?

Because new tools create learning overhead and can become a distraction. In the 7Ws “Where” lens, he treats tool adoption as a deliberate choice and tries to minimize the number of tools he uses. Obsidian is the key exception he values enough to incorporate; otherwise, he avoids jumping between tools just to experiment.

How does he capture ideas quickly without losing them later?

Capture begins in Drafts on mobile or iPad. From there, he can save ideas or create to-dos that route into Obsidian. In Obsidian’s To Do list, items like “buy milk” appear at the top, and a plugin moves completed tags to the bottom so the active list stays readable and current.

Review Questions

How would you apply the 7Ws filter to decide whether a new idea deserves a dedicated project note?
In Bricio’s system, what belongs in “next tasks” versus the “oven,” and how does that distinction reduce overwhelm?
What mechanisms ensure that every active project gets at least one weekly action, and how would you replicate that cadence outside Obsidian?

Key Points

1
Use a minimal “Focus” home note to reduce decision fatigue and keep attention on a few core documents.
2
Apply the 7Ws filter to determine whether an idea aligns with roles, interests, standards, people, and tool constraints before committing time.
3
Structure each project note around a single top “next step” and require at least one weekly action per active project.
4
Keep task lists curated: show only immediate “next tasks,” while deferring larger items into an “oven” area until they’re ready.
5
Attach live context to projects using links (e.g., project-filtered Gmail) and ongoing research feeds (e.g., Owler).
6
Plan the day with a “today” view that aggregates only the three most important tasks using search across projects.
7
Capture quickly in Drafts, then route items into Obsidian and use a plugin to keep completed items from cluttering the active list.

Highlights

The system’s core execution rule is weekly: every active project must advance by at least one concrete “next step,” so momentum survives imperfect conditions.

A project note is built for clarity—“next step” at the top, “why” and contacts alongside it, and an “oven” area for important-but-not-now work.

Obsidian linking turns project notes into dashboards, including one-click access to project-specific Gmail searches and company updates via Owler.

Topics

Obsidian Workflow
Project Management
Task Systems
7Ws Framework
Daily Priorities

Mentioned

Francisco Bricio