<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on LB</title><link>https://lindsaybrunner.com/blog/</link><description>Recent posts from LB</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://lindsaybrunner.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Meet Workshop, My App for Other Apps</title><link>https://lindsaybrunner.com/blog/2026-08-17/workshop-launch/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2026-08-17/workshop-launch/</guid><description>&lt;p&gt;Small everyday tools have a predictable lifecycle.&lt;/p&gt;
&lt;p&gt;First, you build a tool, a script, a skill, something that solves one irritating problem. It lives in a terminal command, a generically named repo, a Google Doc, or a file somewhere on your local disk. You did a good job, so the tool becomes indispensable very quickly.&lt;/p&gt;
&lt;p&gt;Then something changes. You go on vacation or whatever and you don&amp;rsquo;t need that tool for a few days or weeks. So you forget it exists and end up frustrated one day, months later, when you half remember that some part of your workflow used to be easier. Where the heck did you save that dang script? Even Codex can&amp;rsquo;t find the skill you&amp;rsquo;re talking about&amp;hellip; Did you actually set it up in Claude?&lt;/p&gt;</description></item><item><title>The Problem Is Usually Not the Prompt</title><link>https://lindsaybrunner.com/blog/2026-04-21/the-problem-is-usually-not-the-prompt/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2026-04-21/the-problem-is-usually-not-the-prompt/</guid><description>&lt;p&gt;Spent any time on LinkedIn lately? My ENTIRE feed has been taken over by AI: predictions about the market, advice for using it better, moaning about human review and job stealing, etc. From what I&amp;rsquo;ve been exposed to, the advice is always some form of &amp;ldquo;prompt better,&amp;rdquo; in one of these disguises:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Choose the right phrases.&lt;/li&gt;
&lt;li&gt;Learn my secret perfect wording.&lt;/li&gt;
&lt;li&gt;Add more context.&lt;/li&gt;
&lt;li&gt;Add less context.&lt;/li&gt;
&lt;li&gt;Tell it to act like a senior engineer, a strategist, a copy chief, a therapist, a war criminal, whatever.&lt;/li&gt;
&lt;li&gt;Just keep fiddling with the prompt until the machine gives you something usable.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Some of that probably works, sometimes.&lt;/p&gt;</description></item><item><title>Notes From a Marketer Building a Real CLI With Codex</title><link>https://lindsaybrunner.com/blog/2026-04-11/building-a-cli-with-ai/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2026-04-11/building-a-cli-with-ai/</guid><description>&lt;p&gt;At no point in my ten years working in technology before now did I imagine ever building a CLI myself. Hell, for most of my &lt;em&gt;ahem&lt;/em&gt; years on this planet I didn&amp;rsquo;t know WHAT A CLI WAS. So, please believe me when I say that &amp;ldquo;build a CLI&amp;rdquo; is not my native solution to virtually any problem I&amp;rsquo;ve ever encountered. But, last week I found myself fed up with a recurring, deeply irritating problem, and as it turned out, a CLI was the solution to the problem: I wanted to save complete ChatGPT conversations in a format that did not make me want to fling my laptop forcefully into a decorative pond.&lt;/p&gt;</description></item><item><title>The Content Resonance Framework: Beyond Engagement Metrics</title><link>https://lindsaybrunner.com/blog/2026-03-05/content-resonance-framework-beyond-engagement-metrics/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2026-03-05/content-resonance-framework-beyond-engagement-metrics/</guid><description>&lt;p&gt;I&amp;rsquo;ve watched more than one team celebrate a content report like it was a victory parade.&lt;/p&gt;
&lt;p&gt;Spoiler: The pipeline didn&amp;rsquo;t get the memo.&lt;/p&gt;
&lt;p&gt;Traffic up. Time on page up. Engagement up. &amp;ldquo;Our SEO is really working.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Meanwhile, the pipeline is flat. Sales is still explaining the same thing on every call. Support is still answering the same questions. Product adoption looks like a sad little plateau. And leadership is doing that quiet thing where they stop asking for updates and start updating their mental org chart.&lt;/p&gt;</description></item><item><title>Brand Signals Decoded: When Quiet Marketing Outperforms</title><link>https://lindsaybrunner.com/blog/2026-02-23/brand-signals-decoded-quiet-vs-loud-marketing/</link><pubDate>Mon, 23 Feb 2026 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2026-02-23/brand-signals-decoded-quiet-vs-loud-marketing/</guid><description>&lt;p&gt;If you&amp;rsquo;re trying to understand quiet vs loud brand signals, you&amp;rsquo;re probably feeling a familiar tension: you want your brand to be memorable, but you don&amp;rsquo;t want it to feel… try-hard. You want attention, but you also want credibility. You want momentum, but you don&amp;rsquo;t want to sound like every other company shouting the same three adjectives into the same crowded feed.&lt;/p&gt;
&lt;p&gt;The tricky part is that &amp;ldquo;quiet&amp;rdquo; and &amp;ldquo;loud&amp;rdquo; aren&amp;rsquo;t just aesthetic choices. They&amp;rsquo;re signals. They tell your audience what kind of brand you are, what kind of work you do, and most importantly, whether you&amp;rsquo;re the kind of team they should trust.&lt;/p&gt;</description></item><item><title>Responsible AI Content Creation Is a Human Problem</title><link>https://lindsaybrunner.com/blog/2026-02-05/responsible-ai-content-creation/</link><pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2026-02-05/responsible-ai-content-creation/</guid><description>&lt;p&gt;Over the last two years, AI has quietly integrated itself into all of our content workflows. We use it to sketch outlines, smooth paragraphs, and quickly summarize concepts.&lt;/p&gt;
&lt;p&gt;And now it feels like AI is everywhere — shaping language, structure, and tone — while the systems around it have remained vague. Everyone has opinions on where it&amp;rsquo;s appropriate and how much review it needs. These opinions rarely agree, and no one is consistently holding the reins.&lt;/p&gt;</description></item><item><title>Technical Storytelling: Bridging Engineering and Narrative</title><link>https://lindsaybrunner.com/blog/2026-01-27/technical-storytelling-bridging-engineering-narrative/</link><pubDate>Tue, 27 Jan 2026 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2026-01-27/technical-storytelling-bridging-engineering-narrative/</guid><description>&lt;p&gt;When I was first getting started, I assumed technical content failed for fairly obvious reasons. Either the underlying technology wasn&amp;rsquo;t very good, or the explanation itself was wrong. Bad assumptions, incorrect diagrams, missing steps (classic technical failures).&lt;/p&gt;
&lt;p&gt;I was lucky enough in my early roles to be learning from incredibly talented technical storytellers, who taught me to recognize the more common failure mode: the explanation is technically correct, carefully reviewed, and still ineffective. Not because it&amp;rsquo;s inaccurate, but because the reader never quite makes it far enough (or deep enough) to understand what&amp;rsquo;s actually being said.&lt;/p&gt;</description></item><item><title>Why Alice's Restaurant Matters</title><link>https://lindsaybrunner.com/blog/2026-01-20/alices-restaurant-family-ritual/</link><pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2026-01-20/alices-restaurant-family-ritual/</guid><description>&lt;p&gt;I listen to &lt;em&gt;Alice&amp;rsquo;s Restaurant Massacree (Revisited)&lt;/em&gt; every Thanksgiving morning.&lt;/p&gt;
&lt;p&gt;I used to hear it on the radio when I was younger, one of those regional, seasonal things that felt inevitable rather than intentional. Later, when radio stopped being part of my life, I kept the ritual anyway, but now with Spotify instead of a DJ on an oldies station. Eventually, I started making my boyfriend, now my husband, listen to it too. Not as a discussion or a lesson. Just as this is what happens on Thanksgiving morning.&lt;/p&gt;</description></item><item><title>Content Systems: How You Move from Content Chaos to Content That Works</title><link>https://lindsaybrunner.com/blog/2025-12-09/content-systems-chaos-to-works/</link><pubDate>Tue, 09 Dec 2025 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2025-12-09/content-systems-chaos-to-works/</guid><description>&lt;p&gt;There&amp;rsquo;s a specific piece of understanding that is missing when teams are scaling content, and it&amp;rsquo;s dead-obvious on the surface, but often not clear when you dig in: &lt;strong&gt;A content system is not the same as your CMS&lt;/strong&gt;. In reality, a content system is the architecture and process built on top of your CMS. It&amp;rsquo;s the the invisible rails that make content production repeatable, sustainable, and actually useful.&lt;/p&gt;
&lt;p&gt;This distinction between tools and systems is subtle in conversation but catastrophic in practice. A content management system is not a content system. The former is software; the latter is an operating model. And confusing the two is why so many teams end up with publishing chaos, fragmented processes, and content that gets neither engagement nor clarity.&lt;/p&gt;</description></item><item><title>Category Creation Is Calling Your Shot, Not Manifesting Your Destiny</title><link>https://lindsaybrunner.com/blog/2025-11-17/category-creation-calling-shot/</link><pubDate>Mon, 17 Nov 2025 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2025-11-17/category-creation-calling-shot/</guid><description>&lt;p&gt;There&amp;rsquo;s a particular kind of room, especially in Silicon Valley, where someone eventually leans back, folds their hands like a prophet, and announces, &amp;ldquo;We&amp;rsquo;re going to be iconic. We&amp;rsquo;re going to define a category.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Maybe you&amp;rsquo;ve been in that room. Big dreams, big decks, &lt;a href="https://lindsaybrunner.com/blog/2026-02-23/brand-signals-decoded-quiet-vs-loud-marketing/"&gt;big adjectives&lt;/a&gt;. Someone name-drops Uber or Kleenex as if becoming a verb is a go-to-market motion instead of a weird historical accident.&lt;/p&gt;
&lt;p&gt;In my career I&amp;rsquo;ve gotten to be in a few rooms like that, all at companies that were developer-focused and convinced they were on the cusp of &amp;ldquo;creating a category.&amp;rdquo;&lt;/p&gt;</description></item><item><title>The MSV Equation in an AEO World</title><link>https://lindsaybrunner.com/blog/2025-11-15/msv-equation-aeo-world/</link><pubDate>Sat, 15 Nov 2025 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2025-11-15/msv-equation-aeo-world/</guid><description>&lt;p&gt;If you build your content strategy around monthly search volume, you are optimizing for a world that no longer exists.&lt;/p&gt;
&lt;p&gt;MSV used to be a rough proxy for opportunity. Big keyword, decent intent, top three ranking, some predictable flow of traffic and leads. You could mostly get away with planning around that. It was not perfect, but the errors were tolerable.&lt;/p&gt;
&lt;p&gt;Now AI Overviews and answer engines sit on top of those same keywords and quietly intercept attention. People still search. The volume line looks fine. The part that breaks is the click. The largest studies we have show that when an AI summary appears, users click traditional results roughly half as often as they do without it, and informational queries with AI Overviews see organic and paid CTR fall off a cliff. The demand is still there. Your line of sight to it is not.&lt;/p&gt;</description></item><item><title>Leadership Communication Skills Every Leader Needs</title><link>https://lindsaybrunner.com/blog/2025-10-14/leadership-communication-skills-every-leader-needs/</link><pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2025-10-14/leadership-communication-skills-every-leader-needs/</guid><description>&lt;p&gt;Effective leadership communication is how exec teams create shared understanding around direction, priorities, and decisions. It&amp;rsquo;s the difference between an organization that knows what&amp;rsquo;s happening and one that knows what actually matters.&lt;/p&gt;
&lt;p&gt;This is where leadership communication diverges from everyday communication. It isn&amp;rsquo;t just about conveying information or running meetings efficiently. It&amp;rsquo;s about helping people understand why decisions are being made, how their work connects to the bigger picture, and what&amp;rsquo;s expected of them next.&lt;/p&gt;</description></item><item><title>How to Manage Up When Your Founder Isn't a People Manager</title><link>https://lindsaybrunner.com/blog/2025-07-01/manage-up/</link><pubDate>Tue, 01 Jul 2025 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2025-07-01/manage-up/</guid><description>&lt;p&gt;Here&amp;rsquo;s the thing no one says out loud: if you&amp;rsquo;re reporting to a founder, you&amp;rsquo;re reporting to someone who loves your work but doesn&amp;rsquo;t have the bandwidth (or playbook) to actually enable you, or manage your growth. That&amp;rsquo;s where you have to show up for yourself. I&amp;rsquo;ve been reporting to CMOs, CEOs, and founders for most of my career, so managing up was mission critical early on for me.&lt;/p&gt;
&lt;p&gt;These aren&amp;rsquo;t vibes or high-level frameworks. These are tactics I&amp;rsquo;ve used, broken, and rebuilt across five startups.&lt;/p&gt;</description></item><item><title>What Is Developer Marketing? A Guide from the Trenches (2025)</title><link>https://lindsaybrunner.com/blog/2025-06-25/what-is-developer-marketing-guide/</link><pubDate>Wed, 25 Jun 2025 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2025-06-25/what-is-developer-marketing-guide/</guid><description>&lt;p&gt;&lt;em&gt;Or: A practitioner&amp;rsquo;s guide to winning the hearts (and wallets) of developers&lt;/em&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;: Developer marketing is the art, and frankly the street fight, of getting cynical, caffeine‑fueled engineers to notice your tool, try it, and recommend it to someone in Slack. If you think that sounds like regular marketing, kindly step away from the buzzwords and keep reading.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="why-another-what-is-developer-marketing-post"&gt;Why Another &amp;ldquo;What Is Developer Marketing&amp;rdquo; Post?&lt;/h2&gt;
&lt;p&gt;Because I&amp;rsquo;m a content marketer, and most of the top‑ranking answers are either (a) dictionary definitions wearing LinkedIn makeup, (b) listicles with the nutritional value of styrofoam, or (c) whitepapers that confuse word count with insight.&lt;/p&gt;</description></item><item><title>Good Developer Content Is a Conversation, Not a Broadcast</title><link>https://lindsaybrunner.com/blog/2025-06-14/developer-content-conversation-not-broadcast/</link><pubDate>Sat, 14 Jun 2025 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2025-06-14/developer-content-conversation-not-broadcast/</guid><description>&lt;!-- Start writing your post below this line --&gt;
&lt;p&gt;&lt;em&gt;Or: Why developer content that listens is way better than content that just talks&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve been doing developer marketing for almost a decade now, and one of the first things I learned, which still proves itself true every day, is that developers are smart and impatient. They&amp;rsquo;re quick to spot marketing fluff and even quicker to bounce if your content wastes their time. Respect that intelligence and impatience, reward their time with usefulness, and you&amp;rsquo;ll earn their attention.&lt;/p&gt;</description></item><item><title>Building Docs with an Arc-Reactor (and a Bit of AI)</title><link>https://lindsaybrunner.com/blog/2025-06-13/meet-guideforge/</link><pubDate>Fri, 13 Jun 2025 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2025-06-13/meet-guideforge/</guid><description>&lt;!-- Start writing your post below this line --&gt;
&lt;p&gt;&lt;em&gt;Or: How I distilled years of tech-writing muscle memory into two reusable playbooks — and turned them into an assistant called &lt;strong&gt;GuideForge&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I adore the smell of fresh Markdown in the morning, but there&amp;rsquo;s a &lt;strong&gt;hard limit to how many times a human can type &amp;ldquo;Step 1: Obtain an API key&amp;rdquo; before questioning their life choices&lt;/strong&gt;. Somewhere around iteration #73 I realised I wasn&amp;rsquo;t writing, just copy-pasting tribal knowledge and hoping I hadn&amp;rsquo;t missed the GDPR footnote.&lt;/p&gt;</description></item><item><title>I Built a Custom AI Assistant Because My Brain Refused to Use Notion</title><link>https://lindsaybrunner.com/blog/2025-06-12/meet-guppi/</link><pubDate>Thu, 12 Jun 2025 00:00:00 +0000</pubDate><guid>https://lindsaybrunner.com/blog/2025-06-12/meet-guppi/</guid><description>&lt;p&gt;&lt;em&gt;Or: The Only Organization System My ADHD Brain Hasn&amp;rsquo;t Mutinied Against&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Like many people with good intentions and executive dysfunction, I&amp;rsquo;ve been through the full spectrum of &amp;ldquo;productivity systems.&amp;rdquo; I&amp;rsquo;ve color-coded Trello boards. I&amp;rsquo;ve had beautifully themed Notion pages. I&amp;rsquo;ve even gaslit myself into believing Asana was changing my life.&lt;/p&gt;
&lt;p&gt;Spoiler: None of them actually kept me organized, they were busywork I could easily abandon.&lt;/p&gt;
&lt;p&gt;All of these productivity tools felt like trying to pilot a spaceship with mittens on. Too much structure, not enough intuition. Too many rules, not enough adaptability. My brain doesn&amp;rsquo;t want a system. It wants a conversation.&lt;/p&gt;</description></item></channel></rss>