Section 1
Fatigue is an information problem, not a frequency problem
People tolerate high frequency from sources that teach them something. Nobody complains about a daily briefing that is useful. They disengage from a weekly message that repeats a claim they already accepted three months ago. That reframes the metric. The thing to track is not sends per month, it is new information per send. A second telling of the same case study with a different headline carries close to zero, even though it costs the same to produce and consumes the same slot in the reader's attention. It also explains why bigger audiences do not fix it. New reach buys you fresh people who have not heard the story yet, while the audience that matters most, the ones who have been paying attention longest, keeps decaying. The general error catalogue is in [Common Storytelling Mistakes Entrepreneurs Make](/blog/common-storytelling-mistakes-entrepreneurs-make).
Section 2
Telling fatigue from a targeting error
The two look identical in aggregate and need opposite fixes, so separate them before acting. Split the response by tenure. If long-standing subscribers are declining while new ones respond normally, it is fatigue and the content needs new material. If both cohorts are flat from the start, the audience was never the right one and no amount of freshness will help. Then check whether the decline is uniform across topics. Fatigue is usually topic-specific: the operations content still lands, the founder-journey content no longer does. Uniform decline points at a list problem, a deliverability problem, or a positioning problem rather than a story problem. Situational tailoring is covered in [The Intersection of Storytelling and Personalization in Business](/blog/the-intersection-of-storytelling-and-personalization-in-business).
Section 3
A rotation model
The workable fix is a rotation that guarantees new information rather than new phrasing. The table below sets out the evidence types available, customer, operational, market, contrarian and instructional, with how often each can be reused before it stops carrying anything.
Section 4
A ninety-day refresh
Start by retiring something. Choose the asset you have used most and stop using it entirely for one quarter. Retirement is a real tool and almost nobody uses it, because retiring a proven asset feels like discarding an asset that works. Next, change what you are counting. Replace open rate with reply rate, or reaction count with saves and forwards. Fatigue shows up in the effortful actions long before it shows up in the passive ones, which is why teams notice it two quarters late. Then commit to one new source of material per month. A new customer interview, a number from your own operations, a position you have not stated publicly before. One genuinely new input per month is enough to keep the rotation honest. Foundational definitions for adjacent topics are in [What Is AI Automation? A Plain-English Guide for Founders](/blog/what-is-ai-automation-a-plain-english-guide-for-founders).
Section 5
The wrong fixes
Redesigning is the most popular. New template, new format, same content. It buys one cycle of curiosity and then the decline resumes from a lower base. Increasing frequency is the most damaging, because it accelerates exposure to material that has already stopped working. Adding drama is the third. Escalating language to recover attention teaches the audience to discount your language, and there is no way back from that in the same channel. You are ready to fix fatigue if you can name three pieces of information your audience does not yet have and you have a way to get them. You are not ready if the plan is a redesign, a subject line test, and more sends.