Another quarter, another CRM. This time it was a migration from Pipedrive to a more automation-heavy platform for the team. The usual rollout chaos ensued: Slack DMs pinging, "how do I..." emails, and the inevitable "this worked better in the old system" grumbles. Support ticket queue was looking like a Monday morning disaster.
I was about to write another long-winded training guide nobody would read when I remembered a PM friend's offhand advice. Instead, I spent an afternoon building a brutally simple, **hyper-specific FAQ doc**. Not a knowledge base. Not a video library. Just a single, living Google Doc.
The rules were simple:
* Only include questions we had *already been asked* more than twice.
* Answers were **only** step-by-step instructions or screenshots. No theory.
* The #1 most common question (how to log a call the new way) was at the very top in bold.
* We linked to it *everywhere*: in the rollout announcement, in the support ticket auto-responder, in Slack pins.
The magic wasn't in the doc itself, but in the enforced culture shift. When someone asked a basic question in Slack, the response was: "Check the Rollout FAQ, section 2. If it's not there, let me know and we'll add it." Within a week, the doc became the first port of call. Ticket volume dropped by about 60% because the repetitive stuff was deflected instantly.
The real lesson? Most resistance during rollout isn't about the tool's capabilities—it's about friction and learned helplessness. A good FAQ doesn't just answer questions; it trains people to fish. Now, if only the new CRM's API was as straightforward as that Google Doc.