founder

a trail for each part of the product. pin the decisions. write the board update from the pins.

a trail for each part of the product

shizumu
trails· 8
all trails
▼orbitdiscrete· 0
▼releasesdiscrete· 0
v0.4discrete· 23
v0.3discrete· 18
customersdiscrete· 16
marketingdiscrete· 11
designdiscrete· 7
north starcontinuous· 1
releases, customers, marketing, design. nest the versions under releases.

north star is one living document, the only one that keeps growing. every other page starts empty.

a working day

shizumu
↑ open memory orbit › releases › v0.4 ↗ pins 6
what matters now
settle the follow-up reminders

reminders one tap from a contact, not a module. do not build a calendar. the customers asked for this on → orbit:customers:call with the dental group, and pricing already assumes it: ↗ pricing: flat vs metered.

↗ pinned
reminders live on the contact
considered
•a reminders module
•our own calendar
•one tap from the contact
choseone tap from the contact. scheduling goes to the os calendar.
becausewe never want to own a calendar, and nobody asked for one.
/decision: considered, chose, because. the deliberation stays in memory. the decision is pinned.

the because line is the part worth keeping. three months on, the choice is obvious from the product. the reason is not.

the decision log

shizumu
pins · v0.4 · 6
alltextlistsstructurechartscodefiles
decisionreminders live on the contact↻ ↓ ×
a reminders module our own calendar one tap from the contact one tap from the…
tablepricing: flat vs metered↻ ↓ ×
option price contacts flat (chosen) $9/mo unlimited metered $0.10 ea per contact
tasksv0.4 scope↻ ↓ ×
reminders inline csv import onboarding polish write the changelog
listopen questions↻ ↓ ×
seats, or stay solo-first? price the self-host tier, or keep it free? mobile…
textcsv import only this cycle↻ ↓ ×
drop the gmail scraper. the oauth review is not worth one import path.
flowchartonboarding path↻ ↓ ×
open pins from the page and the trail's pins are in one list. open a pin and the whole table, list or chart is there.

every decision on this trail and why you made it, in one list. read it back when you write the changelog or the board update.

the way back

the two pins marked ↻ above carry forward. choose v0.4 for a new page and the scope and the open questions are already on it, as a working copy you can edit. a trail brings back the pins it owns, not its parent's: what you keep on releases stays on releases. it happens once, when the page first joins the trail, so you begin where you left off, not from your memory of it.

type @ and a page from any trail becomes a link, so the customer call that settled the reminders sits on the v0.4 page without being copied. the long version of any week is in memory: search finds the call notes you never pinned.

why not just keep everything

the usual way is to keep every note, and six months later there are two hundred pages nobody re-reads, including you. so the board update gets written from memory, which means it gets written from the last two weeks.

the pins on this trail are the other five months. none of them was written for the board. they were written to think, and the pinning was a judgement you made on the day, while you still remembered why you were choosing. that is the part memory loses first and the part a search box cannot recover, because you cannot search for a reason you have forgotten having.

every page starts empty, and that is what made the writing honest in the first place. a page that keeps everything is a page you write for posterity. the rest stays in memory, searchable, for the day you need the long version.