Manage a Full Project with LifeOS Pro

Project management is not about creating more folders. It is about keeping goals, tasks, references, and reviews connected under the same theme. In LifeOS Pro, that starts with a theme note.

Step 1: create a theme from the top-left form

In the LifeOS form at the top left of Obsidian, switch to the theme note form and enter a project theme tag, for example:

project/user-feedback-report

If the form is not visible, click the LifeOS icon with a + in the left sidebar. After creation, LifeOS opens the project theme index.

Theme note entry: create a project theme from the top-left form

Step 2: make the project index clear

Do not start with a long document. Fill in four blocks first:

# User Feedback Report

## Goal

Deliver a feedback analysis report before Friday's product review.

## Deliverables

- A feedback classification table
- One page of key findings
- Three product recommendations

## Milestones

- [ ] Collect feedback #project/user-feedback-report
- [ ] Categorize and count issues #project/user-feedback-report
- [ ] Write findings #project/user-feedback-report
- [ ] Share in product review #project/user-feedback-report

## Key references

The project index defines the project. Daily notes, meeting notes, and references can stay where they are and return through the same theme tag.

Step 3: move work through the task view

Open the task view and filter by the project tag. You will see project tasks even when they are scattered across different notes.

Use three decisions:

  1. Do today: schedule it today or place it on the calendar.
  2. Waiting: keep the task, but write who or what it is waiting for.
  3. Not now: remove it from the active project list.

Project task view: manage tasks under one theme

Step 4: tag meetings and references too

Project context usually gets lost in meetings, quick notes, and references. Do not copy everything into the project index. Keep the same theme tag instead.

## Product review notes

- Mobile feedback is more concentrated than desktop feedback. #project/user-feedback-report
- We need the latest one-week sample for new users. #project/user-feedback-report
- [ ] Ask ops for the latest two weeks of feedback #project/user-feedback-report

The project index stays clean while advanced lists keep the related content visible.

Step 5: protect delivery time on the calendar

As the deadline gets closer, turn project tasks into time blocks. Open Calendar Pro and schedule the critical work.

Avoid large tasks like "write report". Split them into 60-90 minute units:

  • Clean the raw feedback table
  • Merge duplicate issues
  • Write three findings
  • Prepare the product review version

Calendar Pro: schedule critical project tasks

Step 6: close with a short review

After the project ships, add a short review to the theme note:

## Review

- Result: the report shipped on time and two recommendations were accepted.
- Worked well: theme tags made source review fast.
- Blocker: metric definitions were unclear, causing one round of rework.
- Next time: add a "confirm metric definitions" task on day one.

This turns the project note into reusable experience, not just an archive.