If you’re writing stuff for Got Users, follow these guidelines, but don’t waste hours trying to be perfect.
This means giving examples and details (without oversharing).
Bad: “What is love? It’s a feeling that bonds people together.”
Good: “What is love? It’s what you feel when you look into your partner’s eyes or when you look at your newborn baby.”
Bad: “I want to make the most of this opportunity.”
Good: “I’ve set aside 10 hours a week on my calendar to make edits based on your feedback.”
Bad: “We cut through complexity.”
Good: “We hire smart people to audit your complicated accounting statements.”
If you can’t be specific, it’s a sign you don’t actually have something to say.
Unless there’s a really good reason — like you’re writing technical documentation or speechwriting for the Federal Reserve — avoid professional-sounding language.
Write like you’re speaking to a coworker or a friend. Use words they would understand.
Use contractions (can’t, won’t) instead of the full words (cannot, will not).
Bad: “I am reaching out because we share mutual interests and are part of each other’s professional network.”