01 Lead measures The work · targets I control
Below are my core output paths. The total number compounding over time, with my sprint target underneath.
Articles published
24
total since inception
Target: 8 per sprint
S1 8 · S2 8 · S3 8 per sprint
Newsletters written
5
total since inception
Target: 2 per sprint
S1 1 · S2 2 · S3 2 per sprint
Quora answered
21
total since inception
Target: 10 per sprint
S1 5 · S2 8 · S3 8 per sprint
Short form
0
total since inception
Target: 20 per sprint
S1 0 · S2 0 · S3 0 per sprint
02 Lag measures Reach · quarter view · Sprints 1–6
A collection of core metrics to see trends per sprint, so I can optimize my content engine sprint over sprint.
Total reach · current sprint
1,560touches
▼ 3.8% vs Sprint 2 · ▲ 52.8% vs Sprint 1
Time-boxed sum: Cloudflare visits + Substack views + Quora views + LinkedIn Feed impressions + GSC impressions. Same five sources every sprint.
LinkedIn Feed
Impressions
1,058
Gauges read on their own units. Cloudflare / Substack / Quora / GSC / LinkedIn Feed are time-boxed to the sprint. Medium is cumulative per-article. Not summed across each other except in the hero recipe above.
03 Ranking & citation Lag · 3 target terms
My #1 long-term goal is to increase my ranking in AI search (AEO). My theory: building a highly specific content engine designed directly for this goal yields maximum benefit over time.
Target term
SEO position (Google)
AI citation
brand story consultant
not ranking
not-cited (0/4)
constraint coaching
not ranking
not-cited (0/4)
leadership facilitation
not ranking
not-cited (0/4)
0 / 3 cited in AI search · current sprint · ChatGPT, Google AI, Perplexity, Claude · site-wide Google avg position —
04 Optimization log What changed, and why
Each sprint I look at what worked, what did not, and the one thing I want to change next sprint. Process, strategy, or just a fun idea — like this dashboard page.
Sprint 1
Batch writing one sprint ahead, so the cadence never feels behind.
Sprint 2
Built a template guide for Claude to layer in Q&A, correct H2s, and SEO/AEO formatting — prevents going back to edit posts after they're live.
Sprint 3
Optimized the image workflow to cut down on post-image capture and editing time.
Sprint 3
Made canonical URLs consistent across all platforms and updated the systems doc for a final article pass — prevents rework.