Hello,

Thank you to all of you who replied to my brief survey on whether or not to create an audio version of Book Indexing: A Step-by-Step Guide. Your responses have been very helpful.

So far the response is overwhelmingly, though not quite 100%, against an audio version, and for many of the reasons that I’ve been hesitant so far. Specifically, that it can be difficult to focus and follow along when listening to nonfiction (compared to fiction), and that being able to see the indexing examples is crucial for understanding what is being taught, which would not be possible with audio. I agree, and I appreciate having your confirmation. I’m not an audiobook person myself, though I know people who are, so I want to make sure I am hearing from you and not simply making decisions based on my own preferences. For the time being, I think an audio version will not be a priority.

If you haven’t responded yet, I am still open to hearing what you think, especially if you would like an audio version. I am open to changing my mind. The survey link is here.

Learning to Say No

Before I begin another mini-series, I want to touch on a topic that has been on my mind again recently, which is turning down projects that I don’t want.

This has been a persistent struggle for me throughout my freelancing career. As a new freelancer, FOMO, or the fear of missing out, was very real. Job offers could be far and few between, and I was inclined to accept any offer that came my way, regardless of how good a fit the project actually was. Now being more established, I typically receive more offers than I have room in my schedule, and yet I still struggle to say no to projects I don’t actually want.

I find it easier to say no when there is an obvious, objective reason that I can clearly explain to the client: My schedule is already full. The subject matter is too far out of my knowledge base. The budget is too low. But what about when there is no objective reason? Can I simply say no? Do I need to explain myself?

For example,

• I don’t like the client. Maybe I previously worked with them and had a bad experience. Or maybe I’m seeing red flags in my correspondence with them.
• I am not interested in the subject of the book. Am I capable of writing the index? Yes. Have I indexed similar books in the past? Probably. Do I need to be passionate about every book I index? No. But the work is more enjoyable when I am excited about the subject.
• I am not comfortable with the subject or with the author’s point of view. This is a little different than whether or not I find the subject interesting. Sometimes books go against my beliefs and values, though this is not always obvious until I start reading. Have I indexed books that I disagreed with? Yes. Do I expect to agree with everything I index? No. As a professional, I also strongly believe in my responsibility to remain neutral and to index the text that is in front of me. And yet, if I can tell upfront that I’m going to strongly disagree with the author, do I really need to put up with that? At what point is it okay for me to say no?
• I don’t like the budget. Sure, it is not a terrible budget and a pay check is money in my pocket. But I also know that other clients are willing to pay more.
• I want to hold out for something better. Maybe the subject and/or the budget are acceptable, but not great. Am I allowed to wait for something better? The absolute worse case scenario is that nothing else comes along and I end up with a hole in my schedule, with no work and no pay check. The more likely worse case scenario is that nothing better comes along and I eventually agree to a different project that is also kind of meh.

Re-reading this list, I feel guilty. I am very much a people pleaser, for better or worse, and I feel like I should be able to say yes, regardless of how I feel. And yet I also know, though painful experience, as a one-person freelance enterprise, that I do not have time for every project that comes along. Being more selective is both a privilege and a necessity, so that I don’t feel overwhelmed, so that I don’t burn out, and so that I can give my best to the work that I do accept.

And so I come back to this question of how to say no.

Part of my struggle saying no is that I believe that I need to justify my decision. And while I do need to clear on the reasons for myself, I don’t actually need to justify it to the client. This may seem obvious to you, but it has taken me several years to come to this realization.

All of this came together recently when I received an offer from someone I previously worked with several years ago. My previous experience working with the client was fine, but it was for a book I wasn’t comfortable with. This time, again, I had mixed feelings about the subject matter. And so even though I had room in my schedule, I declined, writing, “I’m afraid I am not available to index this book.”

That was it! The client accepted what I wrote, I recommended a few other indexers the client might try, and we moved on.

For all of the work and anxiety that went into writing that reply, saying no felt so liberating. I’m not stuck indexing a book I’m ambivalent about and my schedule is free for a better fit to come along. And, I now have a response ready for when I simply want to say no, with no explanation.

I hope you have an easier time saying no than I do. As I am learning, it is a helpful skill to have. If you are a newer freelancer, I understand that it can be hard to say no, and that sometimes the only way to learn which books are a good fit is to learn through experience. Long term, though, not every book is going to be a good fit, and I think part of being a successful freelancer—both financially and in the enjoyment of the work—is learning when to accept and when to turn down.

Yours in freelancing,

Stephen