2026-03-11 — Module outlines milestone complete
What shipped today
The entire six-module curriculum got its outlines written today, completing the backbone of the course. Each outline follows the module template exactly — thesis, 4-5 lessons with turns, anchor material from the book and consulting stories, a 75-minute live session design, application exercises, artifacts, and detailed instructor notes. The outlines were written sequentially because each module’s opening picks up from the prior module’s closing provocation, and each artifact feeds into the next.
The arc holds together as a single movement: Module 1 reframes AI as exposure rather than threat. Module 2 looks directly at what’s exposed — the machine-self. Module 3 names what remains (the three capacities) and serves as the pivot from demolition to construction. Modules 4-6 each deepen one capacity — discernment, courage, self-authorship — with Module 6 integrating everything into the capstone roadmap. The artifact chain is continuous: reframed understanding → honest self-recognition → framework reference → organizational diagnostic → change leadership approach → 90-day transformation roadmap.
All content is grounded in Paul’s book manuscript (The Work of Being), with specific chapters mapped to each module. The philosophical depth is there but stays in the background — executives encounter the ideas through consulting stories (the leader who read the room, the $12M trust failure, the two AI rollouts), not through academic attribution. The voice throughout is sharp, concrete, and direct.
Completed
- SYN-239 — Write Module 1 outline: The reckoning (done in prior session)
- SYN-240 — Write Module 2 outline: The machine-self (done in prior session)
- SYN-241 — Write Module 3 outline: The correction
- SYN-242 — Write Module 4 outline: Discernment
- SYN-243 — Write Module 5 outline: Courage
- SYN-244 — Write Module 6 outline: Self-authorship
Release progress
- Content: 6 open / 9 closed — module outlines done; case studies, exercises, and video scripts remain
- Production: 7 open / 0 closed — not started
- Platform: 7 open / 0 closed — not started
- Audience: 6 open / 2 closed — LinkedIn strategy done, posts and newsletter remain
- Launch: 8 open / 0 closed — not started
Carry-over
PRODUCT.mdandpaulos.project.tomlhave unstaged modifications from a prior sessionDECISIONS.md,DEPENDENCIES.md,RISKS.mdare untracked project docs — should be committed- The book manuscript (
the work of being ed2.txt) and the AI Era outline are untracked source files in the repo root - GitHub issue #8 (case study library) is labeled
needs-clarification— waiting on Paul’s list of consulting stories he’s willing to use
Risks
- Content templates exist but haven’t been tested against real content yet. The case study template (#43), video script template (#44), and exercise template (#45) are done but no instances have been produced from them. First real use may reveal gaps.
- Module outlines are structurally complete but voice needs Paul’s revision. The AI drafts match the intellectual framework closely, but Paul’s actual delivery voice — the specific cadence, the consulting anecdotes with real detail — can only come from him.
Flags and watch-outs
- Main branch is now 11 commits ahead and pushed. The untracked files (DECISIONS.md, RISKS.md, DEPENDENCIES.md, book manuscripts) should be dealt with — either committed or gitignored.
- Linear “Module outlines” milestone should be closeable now — all issues are Done.
Next session
- Close the Module Outlines milestone in Linear — all 6 issues are Done
- Commit project docs — DECISIONS.md, DEPENDENCIES.md, RISKS.md should be tracked
- Decide on source files — should
the work of being ed2.txtand the AI Era outline be in the repo or gitignored? - Start case studies or video scripts — the content milestone has case study library (#8, needs Paul’s story list), video scripts, and exercises remaining. Check which are unblocked.
- Consider production and platform milestones — these have zero progress and will need attention for launch
Why customer tools are organized wrong
This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.
Infrastructure shapes thought
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
Server-side dashboard architecture: Why moving data fetching off the browser changes everything
How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
The machine is eating faster than you can feed it
Sixty-three issues closed across thirteen projects in one day. Four milestones completed. And the hardest problem wasn't building — it was keeping up with what you've already built.
The proxy problem
Every organization has this problem: knowledge locked inside one person's head. Today I accidentally designed a solution — and it has nothing to do with documentation.
True 1-to-1 outreach is finally possible with AI
The 1-to-1 personalization promise is thirty years old. It never worked because understanding each person was too expensive. AI changed the economics.