![]() ![]() The truth is, people don’t connect with numbers, lists or schedules. One of the most engaging ways to be specific? Share a story in your missionary newsletter. To them, you won’t be “a missionary I support doing stuff with African orphans.” You’ll be “someone I support who runs a skills training program for aged-out orphans in Zimbabwe. This not only gives them greater confidence as they invest in your ministry, but it also equips them to share your ministry with others. Your readers will never know all the details of your work, but they should be able to concretely explain what you do, how, where and why. Keeping a simple log as events happen and thoughts come to mind will help you jump into writing with ease. No more hemming and hawing at the beginning ( “It’s been so long time since I last wrote, and it’s hard to even know where to start. No more hastily throwing together updates because you put it off, because you didn’t have time, because you couldn’t think of what to write. ![]() This simple tip fixes a plethora of ministry newsletter hassles. Today, in hope of sparing you the awkwardness I once faced, we’re sharing our top ten. But in the world of missions and writing, there are a few time-tested tricks that can help your newsletter do both. Getting them to remember what they read can be even harder. Getting people to read your missionary newsletter can be tricky. Except that I’d been to Asia once, my missions organization didn’t send people to Africa and, as a home staff copywriter, I did all my work from a cubicle near Dallas. She’s been to Asia and Africa and all over the place! Then she took me to the church sanctuary and told her friend, You’ve got to meet Beth. It was the kind of moment every ministry worker on a support trip looks forward to: The woman shared how excited she always got to see my blue newsletter envelope in the mail. Read part two, “How to Design a Beautiful Missionary Newsletter,” here. This is part one of two-part series on missionary newsletters. ![]()
0 Comments
Leave a Reply. |