# Brian Sierakowski - Founder at Changebot URL: https://www.changebot.ai/blog/authors/brian-sierakowski/ Description: Brian Sierakowski is Founder at Changebot and writes about changelogs, release notes, and product communication. ![Brian Sierakowski](/_astro/brian-sierakowski.CVzujm3w_1gel5M.webp) # Brian Sierakowski Founder, Changebot Brian Sierakowski is Founder at Changebot and writes about changelogs, release notes, and product communication. ## Posts by Brian Sierakowski [ ![AI agent icon with empty fuel gauge surrounded by disconnected data sources](/_astro/featured.SIA2wRub_Z8rzpT.webp) ## Introducing the Changebot Agent Changebot is becoming the agent-first changelog: write, edit, review, and publish product updates from the workflow you already use. Brian Sierakowski June 13, 2026 ](/blog/introducing-the-changebot-agent) [ ![Developer workflow with AI coding tools and release communication signals](/_astro/featured.KqEEKq0c_1iiJvF.webp) ## Publish Your Changelog From Claude Code A practical example of the Changebot MCP workflow: ask for an update, review the draft, and publish without leaving your agent surface. Brian Sierakowski June 13, 2026 ](/blog/publish-your-changelog-from-claude-code) [ ![A changelog sitting at the end of a long product workflow](/_astro/featured.pnGxyg_q_Z1Yu70o.webp) ## The Agent-First Changelog The next changelog is not a CMS you remember to update. It is a publishing layer your agents can write to. Brian Sierakowski June 13, 2026 ](/blog/the-agent-first-changelog) [ ![Illustration of a person tangled in vines growing from a process flowchart they originally created](/_astro/featured.B82ojyQQ_ZOls7D.webp) ## I created this process and now it's eating me alive You championed release notes when nobody else would. Now you're the permanent owner. Here's why the 'person who cares' always gets stuck. Brian Sierakowski March 9, 2026 ](/blog/i-created-this-process-and-now-its-eating-me-alive) [ ![Illustration of a rocket ship representing 10x development speed leaving behind a cyclist struggling with manual communication](/_astro/featured.B_5fYJ4c_Zenksk.webp) ## AI made you ship 10x faster. Your communication didn't keep up. AI coding tools have accelerated engineering output dramatically. But nobody built the communication layer to match. The gap is widening. Brian Sierakowski March 6, 2026 ](/blog/ai-made-you-ship-10x-faster) [ ![Illustration of a scale with AI misjudging a large dependency update as more important than a small key feature](/_astro/featured.CSim7ook_1ymztg.webp) ## AI can't tell your biggest feature from a dependency update Generic AI tools treat all code changes equally. They over-index on PR volume, can't distinguish customer impact from internal cleanup, and the output sounds like a robot wrote it. Brian Sierakowski March 3, 2026 ](/blog/ai-cant-tell-your-biggest-feature-from-a-dependency-update) [ ![Illustration of ephemeral chat messages fading away contrasted with a solid permanent changelog record](/_astro/featured.B9tC-QeF_2lqndB.webp) ## Your deploy message in Slack is not a changelog Developer posts 'released this morning' in Slack. A week later, nobody can find it. Here's why Slack-as-changelog fails and what to do instead. Brian Sierakowski February 28, 2026 ](/blog/your-deploy-message-in-slack-is-not-a-changelog) [ ![Illustration of a building bustling with activity inside but no visible signs of progress to people outside](/_astro/featured.BXBGPQ95_1jEVmG.webp) ## We are doing stuff. Trust us. Your team ships features every week. Your customers have no idea. When there's no single place to point people to, trust erodes even when the work is getting done. Brian Sierakowski February 25, 2026 ](/blog/we-are-doing-stuff-trust-us) [ ![Illustration of a single document splitting into five paths for different audiences](/_astro/featured.DJaXBpwi_2bAx0a.webp) ## The five rewrites problem Every release cycle, the same update gets rewritten five times for five audiences. Here's why that's killing your product team's bandwidth. Brian Sierakowski February 22, 2026 ](/blog/the-five-rewrites-problem) [ ![A boomerang arcing through the air, representing SaaS customers who leave and come back](/_astro/featured.xIUcbq20_daQKk.webp) ## The customer always comes back SaaS customers are canceling to vibe-code their own tools. They're also coming back a month later. Here's why the build-it-yourself era is a blip, not a trend. Brian Sierakowski February 20, 2026 ](/blog/the-customer-always-comes-back) [ ![Illustration of a stopwatch showing fifteen minutes with a hidden iceberg of context-gathering work beneath](/_astro/featured.BpK0x1Io_Z1u2DdI.webp) ## The fifteen-minute illusion Your changelog process only takes fifteen minutes. But that number is hiding the real cost of how your team communicates what shipped. Brian Sierakowski February 19, 2026 ](/blog/the-fifteen-minute-illusion) [ ![Two changelogs side by side: a vibrant stack of update cards with a verification badge versus a sparse faded timeline with cobwebs](/_astro/featured.BBaEHGWA_1EbBq1.webp) ## Proof of Shipping: The New Table Stakes for Vendor Evaluation Prospects check your changelog before they book a demo. Investors want evidence of velocity. A stale update history says 'abandoned' louder than any pitch deck can overcome. Brian Sierakowski February 17, 2026 ](/blog/proof-of-shipping) [ ![A grid of hackathon project demos showing various customer communication tools](/_astro/featured.BlOmFd8H_Z1luqYv.webp) ## What 15 hackathon apps taught us about the future of customer communication When 15 teams at an AI hackathon independently built customer success tools, it confirmed something we've believed for a while: customer communication is the next frontier for AI. Brian Sierakowski February 17, 2026 ](/blog/what-15-hackathon-apps-taught-us) [ ![Illustration of a priority stack with changelog at the bottom collecting dust](/_astro/featured.pnGxyg_q_Z1Yu70o.webp) ## The changelog is always the last thing you update Ship the code. Update the docs. Update the marketing page. Then, if there's time, update the changelog. Here's why 'afterthought' is the default and how to fix it. Brian Sierakowski February 16, 2026 ](/blog/the-changelog-is-always-the-last-thing-you-update) [ ![Illustration of a clunky workflow with screenshots being pasted between a changelog editor, a capture frame, and ticket comments](/_astro/featured.CgeNT2Li_Z1MiiNF.webp) ## Sharing screenshots of your changelog drafts is a red flag When your team reviews changelog entries by taking screenshots of drafts and pasting them into tickets, the tool has become the bottleneck. Brian Sierakowski February 13, 2026 ](/blog/sharing-screenshots-of-your-changelog-drafts-is-a-red-flag) [ ![Product content cards ascending a staircase into a spotlight while generic SEO blog posts fade below, with AI chat bubbles at the top](/_astro/featured.CzAQQKXs_ZnHJua.webp) ## Product Marketing Is the Ascendant Discipline in 2026 Top-of-funnel SEO content is dying. LLMs are the new discovery channel. The companies that win are the ones writing about what their product actually does, not chasing keywords. Brian Sierakowski February 12, 2026 ](/blog/product-marketing-is-the-ascendant-discipline) [ ![A crumbling marketing funnel contrasted with product update cards flowing into an AI chat bubble that connects to customers](/_astro/featured.cH0vstkd_ZrwjV1.webp) ## Top-of-Funnel Content Is Dead. Product Updates Are Your New Growth Channel. Traditional SEO blog posts won't save you. In a world where prospects ask LLMs for recommendations, the companies with the most detailed product content win. Brian Sierakowski February 7, 2026 ](/blog/top-of-funnel-is-dead) [ ![Clock split between productive coding and wasted status meetings, with a chain of figures passing information in a telephone game](/_astro/featured.KqEEKq0c_1iiJvF.webp) ## Developers Lose 10 Hours a Week to Status Theater Your engineering team spends 5-10 hours every week in meetings explaining what they built. Then you wonder why they're not shipping fast enough. Brian Sierakowski February 2, 2026 ](/blog/developers-lose-10-hours-a-week-to-status-theater) [ ![Terminal with raw commit messages transforming through gears into a polished customer announcement card](/_astro/featured.By65PXk2_1O2PkY.webp) ## Your Commit Messages Were Never Meant for Customers The gap between what developers write in commit messages and what customers need to hear about your product is wider than you think. Here's why that matters. Brian Sierakowski January 28, 2026 ](/blog/your-commit-messages-were-never-meant-for-customers) [ ![Split illustration showing engineering artifacts on one side and a polished newsletter on the other, with a figure bridging the gap](/_astro/featured.EnJOzac9_ZxUHyI.webp) ## The Non-Technical Founder's Update Problem You know your product is shipping. You just can't see it. When every customer update requires interrupting your engineering cofounder, most updates don't happen. Brian Sierakowski January 23, 2026 ](/blog/the-non-technical-founders-update-problem) [ ![Illustration contrasting chaotic year-end data excavation with organized curation, showing scattered documents becoming a clean summary report](/_astro/featured.DfA7R9PO_Z1X25K0.webp) ## The Year-End Review You're Dreading Every January, product teams face the same grueling ritual: sifting through months of work to compile what actually shipped. There's a better way to approach year-end retrospectives. Brian Sierakowski January 19, 2026 ](/blog/the-year-end-review-youre-dreading) [ ![Illustration showing a communication gap between a product team shipping features and customers unaware of them, with a changelog bridge spanning the gap](/_astro/featured.Zcxg6EH4_Z18mJ15.webp) ## "I Had No Idea This Exists": The Feature Awareness Problem Your team shipped the feature. You announced it. And customers still don't know it exists. Here's why the gap between shipping and awareness is bigger than you think. Brian Sierakowski January 15, 2026 ](/blog/i-had-no-idea-this-exists) [ ![Illustration showing multiple repository sources converging from fragmented views into one unified holistic dashboard](/_astro/featured.Bvanj-gv_2j9J3g.webp) ## Many Repositories, Many Products: The Holistic View Nobody Has When your product spans five repositories, three teams, and two technology stacks, no single person can see the full picture of what shipped. Here's why that's a communication crisis. Brian Sierakowski January 13, 2026 ](/blog/the-holistic-view-nobody-has) [ ![Single figure with radiating connections to many product icons showing coverage spreading thin](/_astro/featured.3_OAoZzT_IvMzE.webp) ## Product Marketing Across 20 Products Most PMM advice assumes you own one product. But what happens when you're responsible for 10, 20, or 100? The playbook breaks down. Here's how to scale without losing your mind. Brian Sierakowski January 11, 2026 ](/blog/product-marketing-across-20-products) [ ![Towering stack of documents with scattered papers versus a clean tablet showing a concise summary](/_astro/featured.Jw8Dybi8_1VToof.webp) ## The 100-Page Update Doc Nobody Reads Every quarter, product marketing teams assemble massive update documents for events and stakeholder reviews. They take weeks to compile, and nobody reads them end-to-end. There's a better way. Brian Sierakowski January 9, 2026 ](/blog/the-100-page-update-doc-nobody-reads) [ ![Calendar with meeting blocks contrasted with automatic notification feed](/_astro/featured.DB1UC68X_Z1mHNa7.webp) ## The Meeting You Shouldn't Have to Attend There's a difference between meetings where you contribute and meetings where you're just extracting information. Product marketers shouldn't have to join calls just to learn what shipped. Brian Sierakowski January 7, 2026 ](/blog/the-meeting-you-shouldnt-have-to-attend) [ ![AI agent icon with empty fuel gauge surrounded by disconnected data sources](/_astro/featured.SIA2wRub_Z8rzpT.webp) ## Feeding Your AI Agents: Why Product Updates Need Structure AI-forward companies are building internal agents for sales enablement, support, and more. But these agents are starving for reliable product change data. Here's how to fix that. Brian Sierakowski January 5, 2026 ](/blog/feeding-your-ai-agents-why-product-updates-need-structure) [ ![Transformation from dry technical changelog on the left to customer-friendly release notes on the right, connected by an arrow](/_astro/featured.MHF0C3j5_Z1eM9v8.webp) ## Why Your Release Notes Still Sound Like a Changelog Most teams list what changed. Few explain why customers should care. Here's how to transform technical changes into customer value. Brian Sierakowski January 4, 2026 ](/blog/why-your-release-notes-still-sound-like-a-changelog) [ ![Staged rollout progress bar with megaphone icons at varying opacity and a question mark over middle stages representing communication timing uncertainty](/_astro/featured.Bbll_nbw_1QIox3.webp) ## When Do You Announce a Feature That's Only 10% Rolled Out? Feature flags and staged rollouts create a communication timing problem. Traditional release notes assume binary shipped/not-shipped. CI/CD requires a new mental model. Brian Sierakowski January 2, 2026 ](/blog/when-do-you-announce-a-feature-thats-only-10-percent-rolled-out) [ ![Three-stage workflow showing automation generating a draft, a human refining it with editing marks, and the polished document flowing to multiple distribution channels](/_astro/featured.D20IvKdv_ZdCK6e.webp) ## The Draft-to-Publish Workflow That Actually Works PMs draft. Marketing refines. Here's how to automate the drafting without losing the positioning control that makes release notes effective. Brian Sierakowski December 31, 2025 ](/blog/the-draft-to-publish-workflow-that-actually-works) [ ![Cobbled-together system with tangled wires and broken connections falling apart, contrasted with a clean integrated system](/_astro/featured.DHYFSHki_kV9vM.webp) ## Why You Can't Vibe-Code Your Way to Good Release Communication Teams think they can cobble together ChatGPT + scripts + Slack bots for release updates. Here's why that approach falls apart, and what it's actually worth to solve this problem properly. Brian Sierakowski December 29, 2025 ](/blog/why-you-cant-vibe-code-release-communication) [ ![Document in center with distribution arrows branching to channel icons, some reaching destinations and others fading or breaking midway](/_astro/featured.BAgALkvy_Z1gLDCJ.webp) ## Writing the Update Is Only Half the Battle Most teams think the hard part is writing product updates. The real challenge? Getting them where they need to go. Brian Sierakowski December 27, 2025 ](/blog/writing-the-update-is-only-half-the-battle) [ ![Two figures meeting on a bridge representing vendor and buyer collaboration in security reviews, with documentation and checkpoints leading to a handshake](/_astro/featured.D2Gpveqm_Z2gacfK.webp) ## The Vendor Security Dance: How Both Sides Can Move Faster Security reviews don't have to stall deals for weeks. Here's how vendors and buyers can structure evaluations that work for security teams without killing momentum. Brian Sierakowski December 25, 2025 ](/blog/the-vendor-security-dance) [ ![Iceberg visualization showing a small visible tip above the waterline with a few feature cards, and a massive collection of code commits, bug fixes, and shipped work hidden below the surface](/_astro/featured.BbJqLC4p_sDNm9.webp) ## Getting Paid to Build Is Easy. Getting Credit for It? Hard. Your team is shipping features every week. Your customers think you haven't improved the product in months. Here's why the credit gap exists, and what it costs you. Brian Sierakowski December 23, 2025 ](/blog/getting-paid-to-build-is-easy) [ ![Illustration showing scattered Jira tickets, GitHub PRs and Slack messages flowing through a funnel into a clean summary dashboard, representing the transformation from chaotic manual recaps to streamlined automation](/_astro/featured.0eHPIBRu_Z2fRlXi.webp) ## Five Hours Down to Five Minutes: The Monthly Recap Problem Monthly product recaps shouldn't take days. Here's why they do, and how to reclaim that time. Brian Sierakowski December 22, 2025 ](/blog/from-five-hours-to-five-minutes) [ ![Illustration of a developer silhouette overwhelmed by form fields and checkboxes, representing Jira bureaucracy](/_astro/featured.zSOk5WaU_Zuz8Rs.webp) ## Why Every Engineer Hates Jira (And How We Made It Worse) Jira became the most hated tool in engineering because every team added their own fields and requirements. Here's how it happened and what to do instead. Brian Sierakowski December 22, 2025 ](/blog/why-every-engineer-hates-jira) [ ![A spiral vortex with calendar and meeting icons multiplying, representing the destructive cycle of meeting overload](/_astro/featured.B-yMVFGy_Ziwp4x.webp) ## The Release Communication Death Spiral: More Meetings Won't Fix It When teams don't know what's shipping, they add meetings, which leaves less time to document, which means even more meetings. Here's how to break the cycle. Brian Sierakowski December 21, 2025 ](/blog/the-release-communication-death-spiral) [ ![Bug being squashed with checkmark on one side, megaphone broadcasting the fix on the other](/_astro/featured.35EeLAp5_ZSOSqX.webp) ## Why Your Bug Fixes Deserve Their Own Announcements Most companies only announce new features. But your customers already saw the bug. Here's why you should tell them you fixed it. Brian Sierakowski December 20, 2025 ](/blog/why-bug-fixes-deserve-announcements) [ ![Support agent desk showing contrast between sparse official inbox and overflowing secret channel sidebar with sticky notes and chat messages about small fixes](/_astro/featured.BIG96wNS_hwOOd.webp) ## The Support Team's Secret Channel: When Your Own Team Doesn't Know What Shipped Support teams often create workarounds just to learn about small releases. This signals a systemic communication failure that affects everyone. Brian Sierakowski December 17, 2025 ](/blog/the-support-teams-secret-channel) [ ![A visual gap showing code and shipped features on one side, empty documents and waiting stakeholders on the other](/_astro/featured.DCbRX0f0_Z2oXN2c.webp) ## The PM Accountability Gap: Why Documentation Falls Through the Cracks Product managers hate documentation. They know it's important, but it's never urgent enough to rank highly. Here's why this gap exists and what to do about it. Brian Sierakowski December 16, 2025 ](/blog/the-pm-accountability-gap) [ ![Secure code repository connected by a gated pathway to an AI brain symbol with security checklist](/_astro/featured.CBC49yCi_Z2pLeJo.webp) ## What to Ask Before Giving an AI Tool Access to Your Code Security concerns about LLM access to your codebase are valid. Here's what smart teams ask before granting access to any AI-powered development tool. Brian Sierakowski December 14, 2025 ](/blog/what-to-ask-before-giving-ai-code-access) [ ![Faded spec document floating like a dream contrasted with solid grounded code blocks](/_astro/featured.BvadUFir_ZP8ntR.webp) ## Product Manager Fiction: Why Your PRDs Aren't the Source of Truth PRDs and specs describe a future that may never exist. The code that ships is your actual tether to reality. Here's why this disconnect matters. Brian Sierakowski December 10, 2025 ](/blog/product-manager-fiction) [ ![Globe with location pins connected by information streams, showing fragmented communication flowing into unified channels](/_astro/featured.DPkoJhbE_f6375.webp) ## The Hybrid Workplace's Hidden Product Challenge: Keeping Distributed Teams in Sync on What's Shipping Remote and hybrid work solved the location problem, but created a new one: how do you keep distributed teams informed about what's actually getting built? Brian Sierakowski December 10, 2025 ](/blog/the-hybrid-workplaces-hidden-product-challenge) [ ![Illustration of a filter separating a chaotic stream of technical items into two paths: a highlighted signal path with key updates flowing to customers, and a faded noise path with internal changes](/_astro/featured.CAUlgTrj_Z1NRQ7H.webp) ## Signal vs. Noise: What Customers Actually Care About Not every code change is worth announcing. Database indexes, infrastructure tweaks, and internal refactors are valuable work but noise to customers. Here's how to filter. Brian Sierakowski December 7, 2025 ](/blog/signal-vs-noise-what-customers-care-about) [ ![Illustration of changelog entries flowing toward a customer, with retention icons like circular arrows and a shield, representing changelogs as customer retention tools](/_astro/featured.nfffnZlS_ZeEl6h.webp) ## When changelogs Become Customer Retention Tools (Beyond Mere Obligations) Most companies treat changelogs as a checkbox. Smart companies use them to save at-risk accounts and prove ongoing value. Here's how. Brian Sierakowski December 5, 2025 ](/blog/changelogs-as-customer-retention-tools) [ ![Silhouette trapped in gears versus silhouette overseeing automated machinery](/_astro/featured.MRbH_XSJ_1AN4CC.webp) ## The PM as Automation: Why Product Managers Build Systems That Break PMs create bespoke spreadsheets and processes to track what's shipping. Then they become the automation themselves. Here's why that doesn't scale. Brian Sierakowski December 3, 2025 ](/blog/the-pm-as-automation) [ ![Disconnected tool icons unified by a central code node forming a knowledge graph](/_astro/featured.WuaH5QsV_zWm7f.webp) ## The Missing Knowledge Graph: Why No One Knows What Shipped Organizations have rich data in GitHub, Jira, Docs, and Slack. But none of it connects. Here's why the missing knowledge graph is your biggest communication problem. Brian Sierakowski December 1, 2025 ](/blog/the-missing-knowledge-graph) [ ![Product marketer watching a fast-moving launch train while sipping coffee](/_astro/featured.B6sNec3O_1cmXJt.webp) ## High-Velocity PMM Without More Meetings How product marketing can stay ahead of rapid engineering output without living in standups, Slack threads, or demo day. Brian Sierakowski November 25, 2025 ](/blog/high-velocity-pmm-without-more-meetings) [ ![Two paths from code to customer: raw commits vs product-aware summaries](/_astro/featured.jPjj9por_1t7ART.webp) ## CodeRabbit vs Product-Aware Summaries Why product framing beats commit-level blurbs when support and marketing need customer impact. Brian Sierakowski November 15, 2025 ](/blog/coderabbit-vs-product-aware-summaries) [ ![AI tailoring release notes to a brand's voice](/_astro/featured.DK4zUq--_EqyVp.webp) ## Brand-Voice-Aware AI How Changebot learns your company's voice so release updates sound like your team wrote them. Brian Sierakowski July 29, 2025 ](/blog/brand-voice-aware-ai) [ ![Five concise bullets emerging from a stream of code updates for investors](/_astro/featured.Cwez3cEd_1CUjj.webp) ## Investor Updates From Code How Changebot turns your shipped code into investor-ready updates that prove progress and build confidence. Brian Sierakowski July 22, 2025 ](/blog/investor-updates-from-code) [ ![B2C update dial controlling frequency with a support team in the loop](/_astro/featured.Dl8PtQNd_Z1MDKxB.webp) ## B2C Cadence Control Avoiding churn by right-sizing app updates for millions of users while keeping support fully briefed. Brian Sierakowski June 24, 2025 ](/blog/b2c-cadence-control) [ ![A spotlight shining on a changelog entry rising from a backlog pile](/_astro/featured.B3h1Juci_Z25VpNU.webp) ## Backlog to Spotlight How Changebot's Recaps and Spotlights turn buried product work into customer-ready updates. Brian Sierakowski June 3, 2025 ](/blog/from-backlog-to-spotlight) [ ![The Development Hell Death Spiral (and how to escape)](/_astro/featured.DvQdHFZo_1Pt8Pv.webp) ## The Development Hell Death Spiral (and how to escape it) When big dev projects stall your roadmap, the real danger is the communication death spiral that follows. Brian Sierakowski May 19, 2025 ](/blog/the-development-hell-death-spiral-and-how-to-escape) [ ![The Soul of Your Company](/_astro/featured.DEptH9Vf_1UbRzh.webp) ## The Soul of Your Company Your product announcements reveal the soul of your company—are you a slow turtle or a cool rabbit with sunglasses? Brian Sierakowski May 15, 2025 ](/blog/the-soul-of-your-company) [ ![How GitHub Squeezes The Juice From Their Updates](/_astro/featured.DhPnM86N_Mlc23.webp) ## How GitHub Squeezes The Juice From Their Updates GitHub publishes 29 updates per month—here's how they squeeze maximum value from their changelog with relentless consistency and smart distribution. Brian Sierakowski March 7, 2025 ](/blog/how-github-squeezes-the-juice-from-their-updates) [ ![How Linear uses product updates to create yell-from-the-rooftop fans](/_astro/featured.vTn5qUMc_g0iEK.webp) ## How Linear uses product updates to create yell-from-the-rooftop fans Linear's obsessive fans aren't an accident—discover how they use public updates, consistent frequency, and storytelling to create product evangelists. Brian Sierakowski March 7, 2025 ](/blog/how-linear-uses-product-updates-to-create-yell-from-the-rooftop-fans) [ ![Changelogs: The PM's Secret Weapon](/_astro/featured.BjQbr1-X_Z1TFCBk.webp) ## Changelogs: The PM's Secret Weapon Five ways product managers turn ordinary release notes into a customer magnet that prevents churn and drives expansion revenue. Brian Sierakowski December 20, 2024 ](/blog/changelogs-the-pms-secret-weapon) [ ![Here's how Github uses their developers to write better changelogs](/_astro/featured.Bg_Rsrbv_12IQ7i.webp) ## Here's how Github uses their developers to write better changelogs Getting customer quotes slows down your changelog—here's how GitHub uses developer quotes to maintain speed while building trust. Brian Sierakowski December 3, 2024 ](/blog/heres-how-github-uses-their-developers-to-write-better-changelogs) [ ![This to That](/_astro/featured.BpVLW6Lg_ZPjDg8.webp) ## This to That Watch us transform minimal commit messages into compelling customer updates that actually resonate. Brian Sierakowski September 2, 2024 ](/blog/this-to-that) [ ![How to Update Your Changelog Before a Price Increase](/_astro/featured.Cw1e1wEe_ZgXGKw.webp) ## How to Update Your Changelog Before a Price Increase Raising prices with an empty changelog is asking for churn—here's how to avoid that mistake. Brian Sierakowski August 19, 2024 ](/blog/how-to-update-your-changelog-before-a-price-increase) [ ![Who's responsible for customer updates?](/_astro/featured.BdhqYxGa_YAdge.webp) ## Who's responsible for customer updates? Your team isn't updating customers enough—here's how to figure out who should actually own this critical responsibility. Brian Sierakowski July 15, 2024 ](/blog/whos-responsible-for-customer-updates) [ ![Here's how Github uses their developers to write better changelogs](/_astro/featured.CJmKqClh_Z2cxQmf.webp) ## How Cringe Should Customer Updates Be? Finding the right balance between boring corporate speak and over-the-top enthusiasm in your customer updates. Brian Sierakowski June 3, 2024 ](/blog/how-cringe-should-customer-updates-be) [ ![The Art of the Update](/_astro/featured.R4nmcstn_sXp31.webp) ## The Art of the Update The complete guide to writing product updates that prevent churn, attract customers, and prove your value. Brian Sierakowski March 25, 2024 ](/blog/the-art-of-the-update)