field notes

Launch diary

A lightweight diary format for the first weeks: what people search, where they stall, what they buy, and which words repeat.

Goal: not lose living observations in the stream of fixes.

what to ask first

Date.
One user quote.
One friction point.
One improvement shipped or planned.

Write one fact

Do not try to describe everything. One real fact per day beats ten foggy impressions.

  • Exact page or path.
  • What user tried to do.
  • What stopped them.

Spot repetition

Repeated client words reveal future buttons, FAQ, and pricing copy.

  • Same question repeated.
  • Same page abandoned.
  • Same support category.

Tie to action

Every entry should either become a task or be marked as an observation without action.

  • Task, FAQ, copy edit, macro, or no action.
  • Owner if action.
  • Review weekly.

reply templates

Daily diary card

Once daily.

Launch diary day ...

Signal: ... User words: ... Page: ... Friction: ... Decision: task / watch / ignore. Next small action: ...

Weekly pattern

End of week.

Weekly support pattern

Repeated issue: ... Affected pages: ... Evidence: ... Proposed change: ... Priority: low / medium / high.

red flags

  • Diary becomes a complaint graveyard with no owner.
  • Only vanity wins are recorded.
  • No one reviews entries weekly.

closed when

  • Daily entries completed during launch window.
  • Weekly top pattern selected.
  • One small improvement shipped from diary.

related doors