The advice you cannot tell is also the advice you most want to share. If you are a fractional operator, every NDA you've signed is a list of your best posts that can never get written.
The shortcut — fictionalize, anonymize, or genericize — works against you. Generic stories don't resonate, because the specificity is what made the original story instructive. So you end up writing a post about a "SaaS company I worked with" and it lands flat.
The fractional operators who write well around NDAs have developed a different craft. Here's how it works.
The compression-substitution test
Take the story you can't tell. Compress it into a single sentence that captures the operational lesson, not the situation. Then ask: could this sentence describe ten other companies you've never worked with?
If yes — you have a publishable lesson. Now substitute the original company with a generic-but-vivid stand-in, keep the operational details intact, and the post writes itself. The NDA protected the identity. The lesson is yours.
Worked example
Original (unpublishable): "At Acme Series-C, we shipped a re-onboarding flow that recovered 22% of churned users in the first 30 days."
Compressed lesson: "Re-onboarding flows recover churned users at much higher rates than most teams expect."
Republished as your post: keep the lesson, drop the identifier, add the detail that makes it land. "I've watched four teams ship a re-onboarding flow in the last two years. Average recovery rate: 20%+." Same insight. Zero NDA exposure.
Three substitution patterns that work
1. The composite client.
Combine three real client situations into one fictional one. Each detail is real; the combination is not. This is a long-running craft in journalism (the composite source) and works on LinkedIn for the same reason: nothing you said is false; the assembled story isn't identifiable.
2. The "I've seen this" frame.
Move from "At [Client], we did X" to "I've seen this play out at three companies in the last year". The frame change does two things: it strips identifying detail, and it gives the claim more credibility because you're now reporting a pattern.
3. The future-tense flip.
Turn a past engagement into a hypothetical. "If you're running a re-engagement program for a B2B SaaS with 2k+ accounts, here's what I'd recommend." The NDA covers what you did. It does not cover what you'd advise.
The thing nobody tells you about NDAs
Most NDAs do not prevent you from sharing what you learned. They prevent you from sharing what was shared with you. The distinction matters.
The frameworks you developed during an engagement, the heuristics you refined, the patterns you noticed — these are yours. The customer list, the specific revenue numbers, the unreleased product plans — these are not. Most fractional operators conflate the two and end up self-censoring far more than the contract actually requires.
Read the NDA. Then write the post.