Skip to main content

Research workflow

Research gets messy when every sub-question lives in the same transcript. NodePad works better when you split the work into clean branches, keep those branches visible, and pull the useful pieces together deliberately — usually through a at the end.

​
A pattern that works

Frame the question

Start with a framing branch that defines the scope of the question and names the sub-questions you need to answer.

Branch by topic

Create one branch per sub-question so each line of inquiry has its own context and output history.

Reference across branches selectively

When one branch uncovers a source that matters elsewhere, use an @ reference instead of summarizing it by hand.

Merge into a synthesis draft

Once the branches have enough signal, merge the important messages into a new draft and ask for a comparison or summary.

​
Why it works

Each branch stays focused on one topic instead of inheriting every tangent. You can see where a conclusion came from because the source branches stay on the canvas. The final summary draws from real source branches instead of from your memory of what happened in them.
Add a text note naming the research question and the standard for evidence you want to use. It helps when the workspace grows past a few branches.

​
Continue

Merging

Compose a synthesis draft from selected source messages.

References

Pull a single message back into another branch with @.