• strict warning: Declaration of FeedsImporter::copy() should be compatible with FeedsConfigurable::copy(FeedsConfigurable $configurable) in /home/writezil/public_html/sites/all/modules/feeds/includes/FeedsImporter.inc on line 94.
  • strict warning: Declaration of FeedsNodeProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsNodeProcessor.inc on line 319.
  • strict warning: Declaration of FeedsNodeProcessor::setTargetElement() should be compatible with FeedsProcessor::setTargetElement(&$target_item, $target_element, $value) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsNodeProcessor.inc on line 319.
  • strict warning: Declaration of FeedsFeedNodeProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsFeedNodeProcessor.inc on line 227.
  • strict warning: Declaration of FeedsFeedNodeProcessor::setTargetElement() should be compatible with FeedsProcessor::setTargetElement(&$target_item, $target_element, $value) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsFeedNodeProcessor.inc on line 227.
  • strict warning: Declaration of FeedsUserProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsUserProcessor.inc on line 195.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • You must include at least one positive keyword with 3 characters or more.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of views_plugin_display::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_display.inc on line 1877.
  • strict warning: Declaration of views_plugin_display_block::options_submit() should be compatible with views_plugin_display::options_submit(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_display_block.inc on line 193.
  • strict warning: Declaration of views_handler_field_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_field.inc on line 641.
  • strict warning: Declaration of views_handler_sort_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_sort.inc on line 82.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 585.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 585.
  • strict warning: Declaration of views_handler_filter_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 609.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 128.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_style_default.inc on line 25.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of content_handler_field::options() should be compatible with views_object::options() in /home/writezil/public_html/sites/all/modules/cck/includes/views/handlers/content_handler_field.inc on line 208.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Declaration of views_handler_argument_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 770.

Learning to Outsource and Then Let Go

http://writerunboxed.com/wp-content/uploads/2017/04/letting-go-300x207.jpg 300w, http://writerunboxed.com/wp-content/uploads/2017/04/letting-go-768x529.jpg 768w, http://writerunboxed.com/wp-content/uploads/2017/04/letting-go-800x551.jpg 800w, http://writerunboxed.com/wp-content/uploads/2017/04/letting-go-581x400.jpg 581w, http://writerunboxed.com/wp-content/uploads/2017/04/letting-go.jpg 1568w" sizes="(max-width: 525px) 100vw, 525px" />
In a few weeks I’ll be leading a session with independent editor Nicola Kraus at Grub Street’s annual Muse and the Marketplace writers conference, on “Outsourcing for Writers.”
When we first pitched the idea to Grub Street, the conference organizer confessed that the idea “freaked [him] out a bit.” After all, writing is such a solitary endeavor and as writers we like to think we can — and should — do everything ourselves, every step of the way.
Nothing else feels right. And after years of solitary drafting and revising, of silently dreaming and imagining what the pages will look like and what publishing this book will mean for your identity and your future, it’s hard not to feel anxious about getting help.
I get it. But the truth is, it’s becoming fairly standard in these busy, hyper competitive times for authors approaching publication to outsource a variety of tasks. Manuscript consultants and developmental editors like Nicola help get drafts into the best possible shape before submitting to agents. Research assistants check facts or make lists of conferences to attend. Social media pros help build up authors’ quintessential online presence. And with publishers’ resources squeezed, many authors opt to hire independent publicists to help get news and reviews once their book is out.
Still, chances are you’ll lose sleep wondering whether your manuscript consultant was right in suggesting you cut the scene you slaved over for months – and whether you should take his advice or ignore it. Or whether the independent publicist you hired is doing anything at all. So you enter your outsourcing arrangements determined to take what the pros you’ve hired say with a grain of salt and to keep a very close eye on them so they get it right.
As one who now sits on the “outsourced” side of this equation, I have seen that, paradoxically, this reluctance to let go is exactly where real disappointment begins. Because by definition, outsourcing means entrusting a project to somebody else, and letting go. Embedded in “entrusting” is trust.  Trusting the person or people you’ve hired empowers them to do their very best. On the flip side, trusting them will result in immense frustration on all sides. And frustration is not the ideal backdrop for success.
Let’s take website design for example. I am personally guilty of not having let go here, even after hiring an outstanding, reputable firm. Through the building of two separate sites, I proceeded to second guess every graphic and every color the designer chose. Rather than complete the job in three rounds of back-and-forth, the designer needed almost ten rounds to accommodate my changes and directives. Over time he grew frustrated with my onslaught of requests. After a while he stopped trying to convince me of why my choices weren’t working and just did what I asked. The project wound up costing nearly twice the initial estimate, and after barely 18 months of having the site up and running, I see that he was right and wish I could redo it.
As a provider myself, I understand his frustration. Going back and forth with authors in response to questions about why I’m reaching out to one particular reporter instead of another at, say, the Boston Globe, or being given to-do lists and asked to account for each item takes time and energy away from doing my job and doing it well. At times, I have found myself slipping into the same mode as my website designer: that is, doing what a client instructs me to do simply to keep the peace, even if I know the results won’t be as good as they would have been if I’d followed my gut. All the while feeling somewhat resigned to having my hands tied or having to explain my every move — thus somewhat disempowered, and less motivated to give it my all.
In contrast, the most successful campaigns I’ve led have been those where an author gives my team and me carte blanche to do our thing. In those cases, the pure joy and excitement of being able to exercise our creativity on the job almost always snowballs into amazing results – including some wonderful surprises. I’ve heard cover designers, independent editors and social media specialists say the same.
That’s why I’m convinced it’s incredibly important for writers to learn to let go. True, as writers we value our solitude and the control we have over our work. But for our work to have broader appeal, to speak broadly to readers and to transcend our immediate networks, we will have no choice but to outsource at least certain core tasks at some point.  After all, it takes a village to create a great book and bring it out into the world.
How, then, can we bridge the chasm between solitary creation and outsourcing? Here’s my take:
Hire people you trust. Vet the professionals you hire through word of mouth, references and work samples. Take the time you need to talk with them before signing the dotted line. This is something they should be willing to do. If not: red flag.
Trust the people you hire. Once you’ve made a choice, commit to trusting those whose help you’ve enlisted. You hired them for their knowledge and skills. If you’re feeling a lack of trust, ask yourself whether it is founded on something real –for example, their behavior — or whether in fact it may stem simply from anxiety.
Accept that no two providers are the same. Just as no two authors will write the same book, no two designers, copy editors, social media pros or publicists can possibly yield the same results. Having made a choice, accept that the person you have selected will bring his or her own unique gifts and perspective and will deliver results that reflect these.
Resist the urge to micromanage. Micromanaging suggests a lack of trust, will take your provider’s time away from other, more strategic tasks, will take your time away from the things you do best and will inevitably lead to frustration on both sides.
Remember: There is no such thing as perfect. Each and every provider you choose to work with WILL have flaws. But remember: each one will also be able to make something wonderful happen that nobody else could.
Having made these choices, let go and put your time to use doing what you do best. Then see where your provider’s talents take you.
Have you outsourced as a writer? If so, what tasks, and to whom?  How has the experience been and what have you learned?

About Sharon BiallySharon Bially (@SharonBially) is the founder and president of BookSavvy PR, a public relations firm devoted to authors and books. Author of the novel Veronica’s Nap, she’s an active member of Grub Street, Inc., the nation’s 2nd largest independent writing center, and writes for the Grub Street Daily.Web | Twitter | Facebook | LinkedIn | More Posts

"The role of a writer is not to say what we all can say, but what we are unable to say."
Anaïs Nin

Random picks

  • The skills needed to begin a sash window refurbishment company are very much the same as in any other business. During the current recession, many people have been trying to start their own business so that they do not have to depend on others for a job. There is a skill set that is particularly well suited to this endeavor. The most critical factor in this industry and in all others in general, is the entrepreneurial mental state. An investor must have the attitude of a business owner and leader. He should not be content to sit idly by and collect a weekly paycheck from a boss. The ideal...
  • The article provides aspiring writers sample plans for writing a fiction or a non-fiction book. It emphasizes the need for aspiring authors to create and to implement a realistic writing schedule.
  • Celebrating 35 years of continuous publishing, Calyx: A Journal of Art and Literature by Women Summer 2011 features the cover art "Adaptation" (acrylic on canvas, 36" x 48") by Amy Guidry. It can be viewed in a larger image in the Calyx website. More of Guidry's work is featured inside the magazine, along with that of Christine Wuenschel, Marie Le Glatin Keis, Alethea Norene, RoByn Thompson,
  • Like most writers, I keep a backlog of story ideas that I revisit from time to time, trying to decide what to write next. To help me with my choices, I analyze each idea, testing whether it has what I consider the essential components of a compelling book-length idea: a clear protagonist, strong primary conflict, high stakes, character transformation, etc. In doing so, I found an area where my ideas consistently fell short: most of the ideas did not have a clear antagonist. I know that’s not necessarily a dealbreaker – there are plenty of books that don’t have a specific...
  • I read “On the Conduct of Lord Tadanao” when I was thirteen or fourteen, and though I’ve not had an opportunity to reread it since, I still remember the plot some twenty years later. It’s a strangely poignant tale. A young feudal lord, an excellent swordsman, is in the habit of challenging his retainers to fencing matches. One night, after defeating all comers, he is strolling complacently through the garden when he overhears the following disconcerting words, ... Translated from Japanese by Ralph McCarthy

Recommended sites

Most recent titles

Fast fact about writing

It has been said that a monkey, randomly typing away on a typewriter (in the days when typewriters replaced the pen or plume as the preferred instrument of writing) could re-create Shakespeare-- but only if it lived long enough (this is known as the infinite monkey theorem).