Thoughts

Essays and observations

This section is for original writing on publishing, editorial operations, AI, and product work. The first essay is live. The rest are drafted for review before they go live, and the verified writing portfolio is the public reading list in the meantime.

Open the writing portfolio

Published essays

AI Is Changing Search. Content Leaders Need More Than Another SEO Checklist

Search is becoming an answers layer. The useful response isn’t more keywords. It’s clearer ownership of intent, accuracy and whether a topic is worth ...

Read more →

Selected writing already published elsewhere

Verified bylines from the publications. These replace an empty “coming soon” state.

Essays in development

Outlines only. Draft articles are not published until they have been reviewed.

Draft

What Nearly Two Decades in Digital Publishing Taught Me About Building Content Teams

A working editor’s view of recruiting contributors, teaching a point of view, and keeping quality intact after the founder is no longer the only writer.

  1. Why a single-author voice does not scale, and what has to become explicit.
  2. Hiring for judgment versus hiring for throughput.
  3. Briefs, review cycles, and the difference between a style guide and a point of view.
  4. How feedback actually improves writers — and when a contributor is not a fit.
  5. What I would keep, and what I would not repeat, in a corporate editorial organization.

Draft

Great Content Operations Are a System, Not a Content Factory

Calendars, briefs, editing, updates, and analytics are one loop. Treating them as separate departments is how quality and performance both drift.

  1. The loop: decide, assign, edit, publish, measure, update or stop.
  2. Why volume targets without lifecycle ownership produce decaying libraries.
  3. Governance as an editorial act: what no longer belongs.
  4. Remote operations only work when the workflow is visible.
  5. How this maps to in-house content teams that do not look like a media company.

Draft

What I Learned Building a SaaS Product With AI Coding Agents

Notes from directing PositionTracker with AI-assisted development: speed is real, and so is the need for product judgment, review, and honest scope.

  1. What I asked agents to do, and what I refused to delegate.
  2. Product definition still comes first: workflows, not features in a pile.
  3. Auth, data, billing, and deploy are the product, not chores after the UI.
  4. Testing and reading the diff are the job when generation is cheap.
  5. Why this experience is relevant to content and knowledge systems, not only software.

Draft

Why Technical Content Still Needs Human Editorial Judgment

AI can draft a plausible how-to. It cannot be accountable for a wrong step, a missing warning, or a publication’s point of view.

  1. The difference between fluent prose and a correct procedure.
  2. Voice is a series of refusals: what we will not oversimplify.
  3. Review systems that assume AI was in the draft, not that it was not.
  4. Accuracy, trust, and the reader who will follow the steps.
  5. A practical standard: humans own the claim; tools own the acceleration.