A Research Workflow with Obsidian LifeOS

Research work often breaks in two places: you save more and more references, but no conclusion emerges; or you write long notes, but nothing turns into action. LifeOS theme notes help keep sources, questions, conclusions, and tasks in one context.

Create a research theme

Use the LifeOS form at the top left to create a theme note, for example:

research/ai-note-taking

This does not have to be a project. A research theme can be a long-running area of interest. Projects have deliverables; research themes can keep accumulating context.

Theme note: create a long-term entry for a research topic

Capture references lightly

Do not summarize every source immediately. Capture the source, the useful points, and your own judgment.

## AI note-taking tools

Source: https://example.com/report

### Useful points

- Users care more about getting back to source material than about one-off summaries. #research/ai-note-taking
- Team workflows need shared context, while personal workflows depend on the local knowledge base. #research/ai-note-taking

### My judgment

- DeepAsk should be explained as "ask questions inside your Obsidian knowledge base", not as generic AI chat.

The same theme tag connects reference notes, daily thoughts, and tasks.

Turn questions into tasks

Research is not collecting. It is reducing uncertainty. When you see a question, turn it into an executable task.

- [ ] Compare local-context features in 3 Obsidian AI plugins #research/ai-note-taking
- [ ] List 5 beginner-friendly DeepAsk scenarios #research/ai-note-taking
- [ ] Draft a website article #research/ai-note-taking

Then filter this theme in the task view and move the research forward.

Use DeepAsk for the second pass

If you use DeepAsk, ask questions against the relevant notes instead of a blank chat.

Useful prompts:

"What user pains repeat across this theme?"
"Group these references by usage scenario, not by source."
"Which conclusions are supported by notes, and which are still assumptions?"

DeepAsk: ask questions against your Obsidian knowledge base

Treat AI output as a second index, not as the final conclusion. Go back to the original notes before making decisions.

Turn research into output

At some point, research should become an output:

Output	Best for
Project	There is a deliverable and deadline
Case study	You need to explain the workflow publicly
Decision record	You need to record why a choice was made
Long-term area	No deliverable yet, but the topic stays relevant

If it becomes a project, create a project/... theme and link the key findings from the research theme.

#A Research Workflow with Obsidian LifeOS

#Create a research theme

#Capture references lightly

#Turn questions into tasks

#Use DeepAsk for the second pass

#Turn research into output