Good documentation compounds. A user who understands your product from day one adopts more features. Raises fewer tickets. Renews. Refers others. The documentation they read in their first week shapes their entire relationship with your product.
Bad documentation also compounds. The user who hits a confusing article in their first week forms a judgment about your product's quality that is hard to reverse. The support team that answers the same question repeatedly builds processes around the gap instead of closing it. The documentation debt grows.
The compounding effect works in both directions. The only variable is which direction you choose to compound in.
It starts with the workflow. Not the writers.