Created
July 16, 2018 22:28
-
-
Save noahgibbs/f006364c3b335046314d9cdcbaa5c4d6 to your computer and use it in GitHub Desktop.
Robert Pozen writing advice, very abbreviated notes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Make an Outline: | |
| * Brainstorm | |
| * Categorize (arrange into categories and subcategories) | |
| * Outline | |
| Introduction: | |
| * Provide the Reader with Context | |
| * State the main theme | |
| * Explain the organization (what you'll get, how you'll get it) | |
| Summaries: | |
| * For longer documents, summarize up-top. | |
| Conclusions: | |
| * Restate the article, like a summary | |
| * Draw further conclusions, or lessons for other subjects | |
| * Explore implications | |
| * Recommend further research | |
| Body: | |
| * Each section gets a heading or subtitle | |
| * Start each body paragraph with a topic sentence, in effect for skimming | |
| Sentences: | |
| * Short (or varied short/long w/o filler) sentences | |
| * Show connection to previous sentences (e.g. "Soon after" beats "in addition") | |
| * Active voice, nouns and verbs that convey imagery | |
| * Simple is good. Less clever is good. | |
| Write regularly; Edit after a delay |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment