Skip to content

Worklogs

Worklogs track what we are doing day-to-day — decisions made, priorities shifted, and relationships stewarded.

Why We Keep Worklogs

  • Transparency: Anyone can follow the project's progress and understand the reasoning behind decisions.
  • Continuity: When picking up work after a break, the most recent entry provides context.
  • Accountability: Time and effort are tracked in a lightweight, human-readable format.

Who Keeps Worklogs

StartMeUp.nz (SMUNZ) — worklogs around the fiscal host, governance, and strategy. What it takes to host collectives.

OpsDev.nz — a collective hosted by SMUNZ. Worklogs around the engineering delivery, tooling, and platform work. Different focus, shared kaupapa.

See the OpsDev.nz worklogs for the engineering-side activity (tooling, token burn, platform work).

What Goes In a Worklog

Worklogs are high-level and brief — they tell the story of the day, not the step-by-step. Aim for a reader skimming entries weeks later to understand what we were focused on and roughly how far we got.

Include:

  • What we set out to do (focus)
  • What we finished or moved forward (outcomes, not details)
  • Decisions or reasoning worth capturing (notes)
  • Links to issues, MRs, or docs for deeper context

Skip:

  • Step-by-step technical detail — that belongs in runbooks or commit messages
  • Minor housekeeping (.gitignore updates, lint fixes, etc.)
  • Financial reconciliation details — those go on the reporting page