Depth you can brief your board on.
Publishing matches how I consult: map the system, name trade-offs, ship something you can use Monday — frameworks, case-style narratives, operator notes from real rooms. No listicles dressed as thought leadership.
Every format has a job
Match the lane to how you decide — long analysis, fast signal, proof from the field, or patterns you can reuse.
Blog
Long-form takes on delivery, culture, and tooling — written so a CTO and a team lead can share the same paragraph.
Open Blog → Signal, fastNews & briefings
What changed in the industry, what it means for your roadmap, and what to ignore.
Open News & briefings → EvidenceCase studies
Before/after narratives with constraints named — proof procurement and engineering both accept.
Open Case studies → Repeatable movesPlaybooks
Workshop-ready steps: refinement, incident habits, planning cadences — minus the certification slide deck.
Open Playbooks → Problem → approachSolutions
How I frame common bottlenecks (velocity theatre, platform tar pits, “Agile in name only”) and what good looks like.
Open Solutions → Executive scanVisual deck
Dense ideas in a format you skim between meetings — for leaders who live in calendars.
Open Visual deck →Want this level of clarity inside your company?
Send the messy context. I tell you what I see, what I would do first, and whether I am the right person — in one conversation.
Start with a discovery call