Product leaders
who want one defensible source of truth for every shipped decision.
§
Issue 03June 24, 2026A product memory journal
The product decision archive
Every decision.
Every voice.
On record.
Omofis Plan is a quiet, methodical archive for the conversations that shape your product. It listens to your stakeholder meetings, attributes every idea to the person who said it, and assembles a single, accepted specification per feature — versioned, sourced, and defensible.
In this issue
- — A live demonstration
- — The problem with prompts
- — Four steps to provenance
- — Who reads this journal
No. 01
The Archive at Work
A live demonstrationThree voices in one meeting. Three contributions. One accepted spec.
Meeting · Tue 23 June, 10:04Recording transcribed
MR
Maya ReyesHead of ProductIdea00:04:12
“Onboarding is too long. Five steps before users see real value — we should let them skip to the dashboard.”
JT
Jonah TanCustomer SuccessConcern00:11:48
“If we skip steps, we lose the data we need to personalize. Maybe defer them instead of removing.”
AK
Aisha KoneDesign LeadDecision00:19:30
“Agreed — collapse onboarding to two required steps, defer the rest to first session usage.”
↓ Attributed · synthesized · drafted ↓
Feature spec · v3 · accepted
Two-step onboarding with deferred personalization
Reduce required onboarding to account + workspace. Defer personalization prompts into the first three sessions, gated by meaningful actions.
Sourced from 3 contributions·Resolves 1 open question·Drafted from Meeting #128
No. 02
The Problem
An essay, brieflyMost product decisions arrive as orphans — disconnected from the meetings that birthed them, the trade-offs that shaped them, and the people who first voiced them. The Jira ticket says what. It rarely says why, almost never who, and when something has changed, the chain of reasoning is already gone.
Roadmaps drift. Stakeholders repeat themselves. A senior engineer quietly inherits a spec with no provenance. Six months later, no one can answer the simplest question: whose idea was this, and what did we agree to instead?
Pull quote
“Is a product decision a single prompt
— or the result of a hundred conversations?”
— Editor's note
No. 03
The Method
Four movementsI
Capture
Bring in meetings — Fireflies, uploads, or notes. Transcripts become source material.
II
Attribute
Each idea, concern, and decision is bound to a stakeholder and a moment in time.
III
Synthesize
Contributions flow into feature drafts. Conflicts surface as open questions.
IV
Accept
One accepted spec per feature, fully versioned, sourced back to the voices that shaped it.
No. 04
The Readership
Who this journal is forFounders
who run scrappy stakeholder calls and need the receipts later.
§
Design leads
tired of recovering rationale from screenshots and Slack threads.
§
Engineering managers
who inherit specs and need to know what was actually agreed.
§
No. 05
The Apparatus
What it actually does- 01
Stakeholder attribution
Every contribution carries a name, a role, and a timestamp from the meeting.
- 02
Meeting impact view
See exactly what each new meeting created, updated, or resolved across your features.
- 03
Versioned specifications
Drafts, revisions, and accepted versions kept in a single readable history.
- 04
Open question tracking
Disagreements surface as questions; later meetings auto-close them with a note.
- 05
Live processing indicator
Watch as the system imports, extracts, matches, and drafts in real time.
- 06
Handoff to Omofis Manage
Send accepted specs downstream to be broken into work, with provenance intact.
Colophon