Read the piece on ianmcallister.substack.com ↗
Every claim below was made in this piece, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.
Their wordsCo-authoring a doc is painful, and the Frankendocs that result are usually painful to read as well. Collaborate on the outline, perhaps, but either write it yourself or have your prospective co-author write it. Don't tag-team.
Their wordsBoil the entire doc down into a few bullets or a paragraph. Spill it. Your temptation will be to save the good stuff for the end of the doc to build suspense or get your excuses in ahead of time. Resist!
Their wordsJust like it is quicker to fix a software bug during unit testing than in production, it is much more efficient to iterate on the outline of a document than to rework a fully written doc.
Keep reading
The other pieces are the ones whose claims are worded most like this one's. That measures language, not agreement: they may argue the opposite.