Parthenon temple on the Athenian Acropolis, Attica, Greece.

No matter how dense the subject, complicated the field, or convoluted the material, every interested reader should be able to access and understand the argument in any nonfiction book.

For some authors, this can be a difficult imperative to accept. When we’ve spent years–decades, likely–gaining expertise and building arguments, we often bury the assumptions, connections, and relationships that make up the foundation of our work. When we then condense our work into a book, we often assume our readers will do the work of excavation.

Although very (very) few readers will do this, authors often resist directives to make their arguments more accessible because it feels like a directive to dumb things down or pander to casual passersby.

To get past the resistance, we can think of accessibility not as a tool for making an argument artificially simple but as a tool for for making it functional and usable. In this case, functional and usable mean readable. Making thinking accessible means making a book readable, and it’s an authorial responsibility.

Books are, in part, a medium for delivering an author’s thoughts to a reader’s understanding. Ensuring successful (that is, readable) delivery depends on the access granted when authors adopt the conventions by which their thinking can be shared. 

These conventions usually guide authors toward locating their argument’s foundation and exposing the scaffolding from which their claims have been built.

Although this seems like it should be easy for an authorial expert, it’s very often not. The foundations of our most complicated arguments tend to be buried so deeply that even their authors can’t always easily find them. Consequently, many authors meet a moment of despair during the drafting stage–deciding that if their reader can’t follow their thinking, it’s simply because their thinking is too complex.

It’s possible. But far more likely, this is just the story we tell ourselves to avoid the difficult but necessary work of making our thinking usable, functional…readable.

While it’s true that not every reader will be interested in evolutionary biology and the future of genetics, or in the philosophical foundations and future of AI, those who are interested and motivated are capable of following the author’s most complicated argument, as long as it’s accessible.

We write for these readers–interested, motivated readers–readers who have sought out our work and want to know more. Making our argument functional and usable for them simply means making it readable.

Feedback is an integral part of any big project. Ideally, we solicit feedback from functional experts, neutrally review their notes, and integrate their applicable suggestions. In practice, however, we often solicit feedback from our friends, review their notes somewhat defensively, and search in vain for usable insights.

Feedback is always helpful, but it’s not always helpful in the ways we expect. Though we typically use feedback as a tool for finding solutions to our project’s problems, it’s a lot more effective (and more reliable) to use feedback as a tool for verifying our project’s problems (and determining which require our attention). 

We do this by looking for the feedback behind the feedback. Readers’ suggestions are often motivated by the emotional friction they experienced when encountering our project. When we look in the background, to the feedback behind their feedback, we can identify this friction and deduce the problems that generated it.

Let’s take a comparative look. Here, a list of solutions from a reader of a working draft:

  • Take out chapter 3–it doesn’t really seem to fit.
  • Chapters 8 and 9 are long and repetitive–join them together in a shorter chapter.
  • Some of the chapters start with stories and others don’t–start them all the same.
  • There are so many citations that I’m not sure what’s yours and what’s not.
  • The story in the conclusion is really interesting–move it to earlier in the book.
  • The same examples are used too much–mix it up more. 

These might be helpful, but they might be arbitrary. Is deleting chapter 3 a good solution? It’s hard to say when we haven’t identified the problem beyond “fit.”

If we look behind the feedback, though, we find more generative feelings:

  • I’m confused, and I don’t know exactly why. Maybe chapter 3 is confusing me, or maybe it’s another chapter.
  • I’m confused. Maybe it’s because some chapters have different forms than others.
  • I’m confused. Maybe it’s because there are a lot of interruptions in the sentences. 
  • I’m having a hard time following this argument. I’m confused
  • I’m not interested in this argument until it’s too late.
  • If I’m totally honest, I find this a little boring.

What’s the friction motivating our reader? Confusion: They can’t find the argument’s throughline. They don’t find the argument interesting. They may not find the argument relevant.

The feedback behind the feedback can feel harsh (which is one reason readers don’t offer it, and one reason writers don’t seek it out), but it very often points the way to the underlying issues keeping our project from completion. Sometimes, the most useful solutions are in there, but in the background. We need to look behind the feedback behind to find them.

The most viscerally painful critique I received was from my PhD advisor in a high-stakes, high-reward meeting before my defense. She’d reviewed my 320-page, 466-footnote project. She had much to say.

I, of course, wanted to be showered with praise. I also wanted appreciation for the work I had put in. I wanted approval that would not only validate my efforts, but would also free me from this project, which felt more like a boulder than a millstone around my neck.

Given these hopes, it won’t be surprising to hear that I didn’t receive anything like the praise I sought. Instead, my advisor was outraged that I hadn’t adequately cited her influence. Then, she picked apart my argument, piece by piece, pointing out its every weakness, and theoretically dismantling its overarching structure.

I was annoyed. Then incensed. Then devastated. I was also embarrassed—embarrassed that my work hadn’t garnered her approval and embarrassed that I wanted that approval so badly.

Today, more than ten years on, a major part of my work includes participating in similarly high-stakes, high-rewards conversations about high-commitment projects. I’m frequently the critic, but my work is also often the object of judgment. I still wonder: Why is it so hard to hear critique?

I’ve come to feel that critique hurts for a variety of reasons: It hurts because it mimics our inner doubts and insecurities. It hurts because it indicates rejection from a group we seek to join. Critique also communicates a strong signal that we must return to something that we long to release. It’s a painful indication that despite our efforts we haven’t achieved our aims.

I haven’t learned to lessen the sting of critique, but I have learned to view it not as evidence of universal disappointment but as an invitation to collaboration. It may not be gentle, thoughtful, or even particularly well-meant, but a critique frequently offers ideas that can make my ideas better.

Luckily, learning to view critique as collaboration isn’t a perspective shift that requires ten years to make. I believe I learned it back then, after the hurt of my advisor’s words subsided. When I felt capable of opening up my document yet again, I applied many of her suggestions. I ripped apart the garment I had spent years weaving, then pieced it into something new. It actually didn’t take nearly as long as I had feared, and once I was finished, I experienced the relief of utter rightness. The project was not only in better shape, but it had finally, finally achieved the form I’d been aiming at all along. 

Since then, I’ve had the opportunity to feel the pain of critique many, many times. It still hurts, but now I consider it an invitation to collaboration. When I accept, my projects benefit.

When we’re faced with disappointments on a project to which we’ve committed time, effort, money, and emotion, it can be hard to know when to persist and when to quit.

On the one hand, grit can get us over the finish line, argues Angela Duckworth, even when our lungs are labored, our legs are heavy, and the race is too long. 

On the other, quitting the race can save us from overvaluing persistence for its own sake, claims Annie Duke. Why should we keep running, Duke asks, when we know we can’t win, and when a loss means more than just a hit to our pride?

To dig deep and show grit, or to pull up short and quit? It’s a timeless question many of us must ask about the commitments we care about, whether it’s a project, a job, a race, or a relationship.

It’s a hard question to answer because we often assess the costs and benefits of persistence versus abandonment only when things go wrong. Yet, when things go wrong, we’re not especially good at neutral assessment. The sunk-cost fallacy and other cognitive biases typically limit our thinking and confine our actions. We end up overvaluing our investments when they aren’t paying off, or blowing long-term equity in a short-term fit of pique.

Because life is uncertain and so many variables shape our experiences, there’s no easy way to decide when to show grit or when to quit. But we can get closer to the least-wrong answer by identifying the root of resistance. Ask yourself:

  1. Am I saying no (or, I don’t want to; I can’t: I don’t feel like it; I prefer not to; uggghhhhhh), more than I’m saying yes?
  2. What are my reasons for saying no?
  3. Are those reasons bounded by time and space, or are they existential and timeless?

The preceding exercise won’t tell you what to do, but it may give you enough clarity to make a plan. For example, if your resistance is rooted in overwhelm, take a break, or take steps to reduce contextual chaos.

If, on the other hand, your resistance is related to the possibility that we are mere drops in the swelling ocean of humanity, that there’s nothing new in its depths, and that nothing you say or do can really change the rhythm of the waves, well, quitting isn’t going to change that, so you might just need to make a plan to comfort yourself before keeping on keeping on.

Garden shears isolated on a white background

Producing quality writing depends on successfully wielding two opposing forces: creation and destruction (addition and subtraction; expansion and reduction). On the one hand, you have to make it. On the other, in the process of making it, you have to let go of some of what you’ve made.

Unsurprisingly, the letting-go part of the process seldom gets its due. Writers refer to it as “killing your darlings” or “the cutting room floor.” Though the pain of the effort is communicated through verbs like “kill” and “cut,” it is a fundamental part of producing quality writing.

In fact, journalist Kevin Sullivan, in conversation with journalist Chip Scanlon, cites it as the best writing advice he’s ever received: “Don Murray, my college journalism professor and friend, said you can always measure the quality of a piece of writing by the quality of what you cut.”

It’s hard to let go of our brilliant turns of phrase, or our tightly crafted paragraphs. It’s harder to let go of whole narrative arcs. But Sullivan confirms that quality writing requires us to recognize that what we’ve created will almost always benefit from what we can cut.

To make it easier, save your cuttings as clips. The benefit is practical—you can consult your clips to develop new darlings. It’s also emotional—you can keep what’s not currently required, saving it for another creation.  

Screen Shot 2022-07-28 at 11.12.17 AM

Books are big projects. They require time and effort and can be consequently quite difficult to complete. Many (many) writers have to work hard just to make the time that allows us to put forth the effort. 

So, when we finish a draft of a big-project book, we want to be done—done with the time-finding and done with the effort-expending. We want to be done done. Yet, despite the meaning of “finished,” a finished draft is never The End.

Instead, it’s usually the beginning of implementing the big changes that move a draft from finished to accepted. Big changes are often suggested by critical readers, developmental editors, or hands-on agents and often include the following:

  • Too long: The book needs to be significantly shortened
  • Too much: The book needs to be broken into two or more projects
  • Too general: A specific audience needs to be identified as the book’s target readers
  • Too oblique: The argument needs to be obvious and integrated
  • Too weak: The argument requires more, specific, primary, secondary, or other evidence
  • Too confusing: The argument needs to be positioned as the impetus of organization 

Suggestions like these can feel big—too big. It can be overwhelming and demoralizing for authors to realize that their manuscript requires even more time and effort for completion.

But big changes don’t always translate to big effort. Revision, even major revision, is far easier to complete than the hard labor of producing the draft.

In the same way that carving a stone is challenging, while mining stone is backbreaking, shaping a draft into manuscript form is part of the process of artistry. Once the backbreaking work of creation is finished, refinement often feels like relief.

Authors asked to implement big changes can take heart: The request is often a testament to the reader’s confidence in the author’s craft.

Although he may be better known for his “2nd 4th grade” illustration skills, Tim Urban’s essays can be energizing. Exhibit X: His recent NYT editorial, in which he offers advice on how to approach time in a (near) post-Covid future.

The editorial is based on his “depressing math” posts from 2014 and 2015. There, Urban reminds us that although we tend to think we have all the time in the world, we don’t. Even if we’re very lucky and live a very long time, the experiences that define our lives—visiting friends and family, eating pizza, reading books—are not limitless. In fact, they’re depressingly countable. 

It’s gloomy. But it’s also galvanizing. When we realize that the life we (perhaps) passively live can be easily broken down into countable experiences, we can activate our agency to make different choices. Different choices can change the math, making the sum a little less depressing. 

Elsewhere, in Exhibit XX, Urban makes a similarly gloomy-but-galvanizing point about procrastinators. Based on his own rich experience, Urban argues that procrastinators frequently forget that, “No one ‘builds a house.’ They lay one brick again and again and again and the end result is a house.”

Urban here echoes Epictetus; indeed, the stoics have enjoyed a popular renaissance in Oliver Burkeman‘s and James Clear’s arguments on habit formation. Part of their message is that transformation is not the result of epiphany but the product of mundane persistence. (And persistence is most efficiently executed through habits.)

Taken together, depressing math and the procrastinator’s faulty memory can help us think about the mediating role we can play in our own lives. By intervening in the parts—whether in terms of the experiences that add up to a life, or in terms of the small steps that result in a transformative project—we can change the whole. From the perspective of the present, this kind of intervention requires a persistence that tethers it to the mundane. It’s often only from the vantage point of the future that we can see its bigger meaning.

Mass isn’t just “‘stuff’ that things can be made out of,” according to University of Copenhagen particle physicist, Matt von Hippel. Rather, mass is what “a high energy of interaction looks like.” 

Von Hippel has a provocative way with words. His claim that mass is energy you haven’t met yet refers to the surprise that, in particle physics, mass is less “stuff” and more a consequence of energy. A proton’s mass, for example, far exceeds the weight of its component quarks. It’s the energy of interaction, according to Von Hippel, that accounts for the extra weight.

His argument should certainly be isolated to its applied field, but it’s too provocative for detainment. When broadly considered against the relationship between parts and wholes, it offers interesting insights. Take, for instance, a book. Intense interactive energy is required to transmute letters, pixels, papers, and ink, glue, and binding into something as weighty as a story. The book in our hands barely compares to the narrative it provokes in our heads.

As in the relationship between a proton and its quarks, the relationship between words and story is not commensurate. Word count accounts for neither a book’s mass nor a story’s heft. Perhaps this is because a book is less a product of the stuff out of which it’s made than a product of the energetic interactions that result in its story.

Elsewhere, writing about the relationship between synchronization and the speed of light, von Hippel points out that our knowledge of the world depends entirely on the models we build to bridge perceptions and our memories. Another name for these models? Stories. Here again, insights from particle physics are relevant, but we already know how much the mass of such stories matters.

Stars

(Image credit: ESA/Hubble & NASA)

Although the American myth of meritocracy continues to crumble to smithereens, some of its fragments are worthy of consideration.

For instance, what does it mean when people who cannot succeed by virtue of their demonstrated abilities and merit, nonetheless continue to achieve? In this context (which is ours), what does success—or failure—even mean?

Success is typically communicated by signifiers of wealth, respect, or fame. It denotes achievement—which itself connotes effort—both of which confer the legitimacy collectively extended to success.

But when wealth, respect, and fame are gained without effort’s exertion, success becomes a more fragile, fluid word. It no longer refers to a meaning relatively fixed by the collective, and depends instead on the relative interpretation of a powerful few.

Failure is, or maybe was, different. Failure, denoted by lack rather than plenitude has always been fluid. We see this in the concept of failing up, where failure must be modified and fixed by its direction. The collective agrees, relatively speaking, that failure is not fixed.

To whom does it really matter if success and failure are now both fluid, relative terms? Well, for the collective seeking to award success and punish failure, it’s a problem. When we become less capable of consensus on what constitutes effort and exertion, we can no longer agree on who has won, and what, or who has lost, and how.

For the individual, however—for you—the responsibility of relativity can be a gift. Determining success and failure according to your own criteria is harder than it sounds, but it allows you to set a standard that matters to you. This is self-help at its most autonomous. Rather than reaching for a collective sense of success that appears increasingly empty, we can extend our efforts toward the kind of success toward which we want to strive. Of course, we can still fail. But, then again, we always could.

After the Locking, instructs Vonnegut, comes winter.

Here in Minnesota, winter has—emphatically—returned. I marked the occasion with a frigid run, thinking about my slippery but well-worn route, the new-but-old year, and the old-but-new omicron variant.

As I ran, I listened to Slate’s Political Gabfest, in which David Plotz, Emily Bazelon, and John Dickerson discussed a provocative conundrum: When is it okay to critique a friend’s creative efforts?

The initial, unanimous response? Never! 

But as they talked over variations on the theme, their answers started to shift:

Well, probably never…if you want to retain your relationship.

Perhaps sometimes…if they’re  particularly successful or are particularly solicitous.

Probably yes…if you’re a partner responsible for heading off potential embarrassment.

Definitely yes…in fact, you’re obligated.

The move from “you can’t” to “you must” seems to depend on the creative effort and on the relationship between creator and critic: Ultimately, critique might be necessary when the effort is writing and the critic is an editor.

Writing, Plotz argued, requires a critical reader because writing is iterative

Iteration describes repetition, making iterative a felicitous adjective when applied to writing. Writing requires repetition on both abstract and practical levels. When we write, we not only reproduce what we know; we also engage in mechanical reproduction—writing, reading, rewriting, rereading, asking others to read, rewriting, rereading, asking others to reread, then rewriting again.

It’s challenging, sometimes agonizing work, but modern iteration differs from rote repetition by its invocation of forward momentum. Iteration isn’t only repetition; it’s repetition toward refinement, toward a “desired result.”

Iteration is consequently an apt word for the work of writing. It’s also, possibly, an appropriate word for the work ahead.

In 2022, we face the same virus, the same intractable government and community responses, the same political rigidity, the same individual and collective challenges to childcare, school, and work, not to mention healthcare and other basic needs. The repetition itself feels like an inescapable, isolating trap. 

The language of iteration might help us conceive of a way out.

The gentle onomatopoeia in iterative means the word requires repetition for its completion. Like winter, like running, like writing, iterative work is repetitious work. However—and also like winter, like running, like writing—the repetition can reach beyond equivalence. Though 2022 is already a repetitive year, it doesn’t have to be the same as what preceded it.