memo-culture
Make decisions and run meetings on memos, not docs and decks. One rule (Write A Memo) and two laws (no memo, no decision; no memo, no meeting).
What it does
Section titled “What it does”memo-culture installs a simple, AI-native way of deciding things. You brain-dump the situation; your assistant structures it into a clear six-section memo; you decide. Memos are plain markdown: no docs to format, no decks to build, no threads to lose. Decided memos pile up into your team’s institutional memory: onboarding becomes “read the last twenty memos” instead of a slide deck.
It is built on one rule and two laws:
- WAM: Write A Memo.
- No memo, no decision.
- No memo, no meeting.
When to use it
Section titled “When to use it”- Any real decision: capture it as a memo so the reasoning survives.
- Any meeting: it gets an agenda memo to pre-read, so the meeting is for deciding, not catching up.
- Onboarding: hand someone the decided memos.
What you get
Section titled “What you get”| Piece | What it gives you |
|---|---|
| Charter | The rules, the four-step decision framework, and the meeting protocol |
| Memo template | The six-section form: Story So Far → Issue → Recommendation → Risks → Open Questions → Ask |
| Shared store | A drafts → review → decided lifecycle plus a BOARD showing the next agenda, pre-reads, and recent decisions |
| Patterns | Write a memo, decision memo, review memo, run a memo meeting, update the board, onboarding digest |
How to use it
Section titled “How to use it”Say “write a memo” to start, or ask your assistant to route you to the right pattern.
Memos live in one shared place your whole team and their assistants can reach (a NAS,
S3, Drive, or a folder), set at install time; the default is a memos/ folder in
your workshop. To adjust the culture itself, edit the charter and template.