MemoFlow

English

简体中文

English

简体中文

Appearance

Recording Tips ​

Recording usually fails not because people cannot write, but because they treat every memo as a full article.
In MemoFlow, a more effective pattern is: capture with low friction, structure the content, then review with searchability.

1. Define one executable recording standard ​

Keep each memo in three layers:

  1. Facts: what happened (objective details).
  2. Judgment: what you think (conclusion or hypothesis).
  3. Action: what to do next (executable step).

Compared with long free-form text, this structure is easier to review, easier to search, and easier for AI summarization.

2. Recommended workflow: capture -> structure -> connect -> review ​

Capture (write first) ​

  • Quick input supports draft auto-save to reduce interruption loss.
  • Undo/redo is available, so input can stay fast and iterative.
  • When the input box is empty, submit can jump directly into recording flow and save as attachment.
  • Image/file attachments are supported, so evidence and conclusions can stay in one memo.

Structure (make content reusable) ​

  • Use a short title or opening sentence to define topic.
  • Add key metadata in edit mode, such as tags and visibility (PRIVATE / PROTECTED / PUBLIC).
  • For task-like content, use quick insert for todo (- [ ]) and code blocks.

Connect (form a memo network) ​

  • Use #tags to organize themes; tags are reused in filters and stats.
  • Add related memos in edit page to preserve context chain.
  • During search, combine keyword + tag filtering to reduce missed retrieval.

Review (turn records into output) ​

  • Use random review and daily review to revisit old notes.
  • Use monthly stats and heatmap to inspect recording rhythm.
  • In weekly review, collapse scattered notes into next-week action items.

3. Ready-to-use templates ​

Template A: event review ​

text
[Facts]
What happened today? (time, people, result)

[Judgment]
Where is the core problem or opportunity?

[Action]
Next 1-2 actions (executable and verifiable)

Template B: task progress ​

text
Goal: what state should be reached this week?
- [ ] Step 1
- [ ] Step 2
- [ ] Step 3

Blocker: what is the biggest blocker right now?

Template C: idea capture ​

text
Trigger: what caused this idea?
Core point: explain in one sentence
Validation: how will I verify it?

4. Tagging rules (critical for future retrieval) ​

Use a simple rule:

  • Keep 1-3 tags per memo, avoid over-tagging.
  • Keep naming stable, avoid synonym drift.
  • Prefer topic tags over stacking mood tags.

Examples:

  • #product-design #login-flow #version-probing
  • #writing #weekly-review #action-list

5. Three common mistakes ​

Mistake 1: trying to write everything at once ​

Fix: start with three lines (facts / judgment / action), then extend if needed.

Mistake 2: writing conclusion without context ​

Fix: add at least one line of trigger/background so it stays understandable later.

Fix: assign stable tags to important records; later filtering speed improves significantly.

6. 30-second pre-publish check ​

Before posting, quickly confirm:

  • Is there only one core topic in this memo?
  • Is there at least one actionable next step?
  • Are reusable tags added?
  • Are attachment/screenshots needed as evidence?
  • Is visibility set correctly?