Archive - July, 2009

Fervr looking for a digital media intern

I like Fevr.

It’s a website for young (in age, rather than maturity, although the two aren’t mutually exclusive!) Christians. The website is well-designed and is using new media (Twitter, Facebook, videos, etc) to communicate with a generation that is as familiar with this mode of communication as Tiger Woods is with his 5-iron.

They are currently advertising for a digital media intern. I gather ‘intern’ is code for ‘volunteer’ (i.e. unpaid position), but as they point out in the job advertisement, it’s a great opportunity for experience and resume building.

Know anyone who’d be up for this?

P.S. – does anyone remember the Zed magazine, produced by Matthias Media in the 90′s? This was a resource for young people that served me well (in magazine format) as a Christian, dealing with issues that were relevant to me. I’m encouraged to see a similar concept, using more accessible media.

Resources for pursuing sexual purity

How many people at your church struggle with pornography? We may not like to admit it, but pornography (sexually explicit material), and increasingly pornography addiction, is an epidemic that is doing more damage to this country than swine flu.

Here are some shocking facts and figures:

  • The average age a person first views pornography online is11 years old.
  • 90% of 8-16 year-olds have viewed pornography online.
  • The pornography industry generates a global annual revenue of $52 billion.
  • 25% of total internet search requests are porn related.
  • 20% of men admit to looking at pornography at work.
  • 10% of adults admit having internet sexual addiction.
  • 34% of pornographic website activity is by women.
  • 100,000 websites offer illegal child pornography.
  • Every second, $2,075 is being spent on pornography.
  • Every second, 28,258 internet users are viewing pornography.
  • Every 39 minutes, a new pornographic video is being created in the US.
  • An anonymous survey of those in Christian ministry revealed that 53% of respondents had viewed pornography in the past 90 days.

This isn’t a small problem. This is a problem affecting Christians – ministers and congregation members, and the rest of our world. We need to act.

This week, Church by the Bridge held a men’s night to discuss pornography, and how Christian men should respond to it, and keep themselves pure. Paul Dale (Senior Minister) spoke about the Bible’s commands for sexual purity and how God designed sex to be used. Derek Higgo (a counsellor) spoke of the horrifying scope of the problem, and the psychological, relational and societal damage caused by pornography. I finished up by sharing some tips for pursuing purity.

This is a problem that our churches need to face up to – to help those struggling with this sin – not just in our churches, but in our communities. Not to mention the victims caught up in the production of these materials. Also, consider the cost to our world when $52 billion is spent on pornography each year – how many people could be fed for that amount of money?!

Resources for pursuing sexual purity

  • The seminar (minus the discussion which is obviously confidential) is available to listen or download from the Church by the Bridge website. I am in the process of turning the tips I shared into a short fact sheet – let me know if you’d like a copy once it’s completed.
  • Also available on the website is a list of resources for pursuing sexual purity.  This list includes links to books, articles, filters and accountability software, Scripture to memorise and more. If you have come across other resources that you have found helpful, I’d love to hear from you.

What is your church going to do to help people struggling with this? Please feel free to contact me if you’d like advice in organising a seminar at your church.

Search for the ideal church database (part 4)

I’ve now written out the requirements (and some optional extras) for the database for my church. I’d encourage you to do the same for your church. As I’ve been pondering requirements, I’ve also been contacting different database providers to arrange for demos/trials, and some of them have been contacting me with details of their databases.

Stafftool

My church has been using Stafftool for the past 18 months. The best thing about Stafftool is Toby – his support and (very) prompt replies and help, plus his willingness to implement changes and suggestions has been a breath of fresh air. Unfortunately, my church’s requirements are exceeding what Stafftool can currently provide, but I would recommend it to other churches, and certainly consider it again in the future.

Ascribe

At first glance (i.e. looking at the website) Ascribe doesn’t look promising. I’m easily turned off by cheesy images and the one on this homepage is right up there! However, I pushed on and requested a demo. I’m pleased I did, as I have been very impressed. The interface is nothing like the website – it’s well designed, the functionality is excellent and the support I’ve received has been first class. Truman has patiently answered my many questions and has been both friendly and helpful.

Jethro

Jethro is a database developed by Tom – on the staff at Christ Church Inner West. Tom has just released the latest version and I’ve just received the link – I’m taking a look now, and it looks promising. You can explore the demo too, here. I’d love to hear your thoughts, and Tom is keen for feedback too.

PAM

PAM is the online database developed by the Sydney Anglican Diocese. This is the first version, and it’s been developed in conjuction with a number of Parish administrators. I’m encouraged to see the Diocese developing these tools to assist Parishes (one of the benefits of being a part of a denomination!), and to see the Anglicans making use of web technologies. They also have a great road-map for future developments, based on feedback from current users. You can check out the demo using the details below, and again, I’d love to hear your thoughts.

https://secure.anglican.asn.au/Demo

user name: demo
password: parish01

A couple of extras…

Thanks to Truman from Ascribe, I’ve discovered a great series of posts written last year, documenting the search the a new church database. Here’s the summary of the search. I’m coming to different conclusions (at least for my church), but the series is well worth a look. It also includes details of some databases that I hadn’t come across previously. I’ve included these below, along with a couple of others I found since posting The List.

Search for the ideal church database (part 3)

I’ve been doing some thinking about my church’s requirements for a database. There are some things that we need in a database. There are other things that we would like in a database, but can live without.

Different churches have different needs, but I think that a lot of these requirements would be common to many churches. This isn’t a final list – is there something that you think most churches would need that I haven’t included?

What we need (i.e. non-negotiable)

  • Access the database online. Why? To enable group leaders (e.g. Connect Leaders, leaders of Welcome Teams) to take ownership of their groups. To enable church members to access and edit their own information (e.g. when they change address). To access the database regardless of platform (Mac or PC). The online database option is a fairly new strategy – only made available by new technologies in recent years. However, I’m keen to explore this option for the reasons above.
  • Ability to easily print out a directory of members. Why? Because not everyone wants to view the directory of church members online, and we want to give multiple options for our members to contact each other.
  • Ability to track attendance (people, not just number of attendees). Why? To keep track of who came to church on the weekend in order to care for people who haven’t been for a couple of weeks. Most databases contain an ‘attendance’ facility, e.g. to note that 54 people attended the morning service on Sunday. We require the capacity to track if John Smith attended the service on Sunday morning, and how regular his attendance has been.
  • Ability to email groups (e.g. men, 6.30pm congregation). Why? Sending email directly from the database to pre-existing groups saves a lot of time (e.g. avoids the need to import email addresses into my email software, create a new group, and then send the email).
  • Excellent support. Why? I want to be confident that if the system goes down, they will be on top of it quickly. I’d like to know that if I have requests for how the database might be improved, they will be responsive to the feedback. I’d like to know that if I’m stuck or need help, the will be keen to help.  The expectations for support are much greater for online databases than a software-based database, because a) the costs are higher, but also b) the capacity to roll-out continual improvements is also greater.
  • Easily get data out of the database. Why? Because we won’t necessarily keep using the same database forever and because there are times when we need to take information from the database to use in another format (e.g. name badges or labels for a mail merge).
  • Identify gifts, passions and abilities. Why? As the church grows, it becomes harder for all staff to know all the people in the church and therefore be aware of who is gifted, passionate and able in particular ways/areas. Tagging members with gifts, passions and abilities (e.g. passionate about interior design, gifted in reading the Bible) enables faster identification of people who might be able to serve in current and potential ministries.
  • Varied access levels. Why? Different staff and lay leaders require different access to information on the database. We want to give members access to basic information of other members (with their permission of course), without listing all the details about all members.
  • Detail ministry involvement. Why? To keep track of who is involved in particular ministries (e.g. is a Kids Church leader, plays piano in the Saturday Night band). There is also potential (i.e. this would be an optional extra) to list who has been approached about serving in a particular ministry (e.g. “asked John to join welcoming team – busy with uni until October, follow up in November”).
  • Detail who has done child protection training, and when. Why? To remain above reproach, adhere to legislative/Diocesan requirements and to care for the children and leaders.
  • Create basic workflows. Why? To care for people. For example, a basic workflow might involve a reminder to call someone within four weeks of their first visit, to ask how they are finding church, and if there’s anything they would like to know, or get help with.

What we would like (desirable but optional)

  • Support for Australian (international) date, phone and address formats. Why? Whilst not essential, it can be frustrating adding data to the database in a different format to how this is normally entered.
  • A planned path of growth. Why? It would be encouraging to see that the developer of the database has a plan for its growth and a road-map for how these improvements will be implemented and when.
  • Support for internet-enabled devices (e.g. iphone). Why? As more and more people (staff and members) use these devices, the capacity to access the database (either via a designated app, or a mobile-friendly site) would be useful.
  • Track important dates. Why? Again, to care for people. e.g. date first attended the church, date baptised, etc. This could be followed up by a phone call – “you joined our church 6 months ago…”
  • Set reminders. Why?  e.g. a reminder to call John in November to follow-up request to serve at Kids Church.
  • List previous involvement in a ministry. Why? Someone who is new to the church might have been involved in men’s ministry at their previous church, but you would like to give them time to settle (and observe their Christian life) before inviting them to get involved. If this information is noted, you can return to it once they have become a member of the church.
  • Track who has completed training. Why? Running a training event doesn’t guarantee that everyone who needs to be trained actually attends! Tracking this information enables follow-up of people who should have been trained, but haven’t been trained yet.

What have I left off these lists that you think should be included?

5 (useful) links #13

Five websites and online resources to inspire, inform and enthuse.

  1. 25 things I’ve learned in my life. What would be on your list? Courtesy of Prodigal Magazine – an online ‘magazine’ for Christian men.
  2. Weegy. “Weegy is an online artificial being, powered by an advanced search engine and live experts. If you need the right answer, fast, go to weegy.com first.”
  3. 13 free Adobe AIR apps that can make your lives easier. I use Tweetdeck (sometimes), testing out Dukt, and keen to try out Focus Booster.
  4. Ref.ly. Quickly and easily turns Bible verses into ‘Tweetable’ URLs.
  5. 17 Ways You Can Use Twitter. “A guide for beginners, marketers and business owners”.

10 situations to avoid email communication

When I proposed to my girlfriend several weeks ago, I chose to ask her that important question in person. When I discovered the Rocks Aroma Festival, I chose to send her an email with the link, asking if she’d like to go along. For my sister’s birthday on Saturday, I chose to phone her and wish her all the best. Each day we make choices as to how we will communicate particular things to particular people.

The same is true of ministry, but I feel in this context, email is too quickly selected as the best means of communication. It’s understandable – email communication is just so convenient. It doesn’t take long to write an email – and in fact, it takes the same time to send an email to one person as it does to send to your whole congregation. There are lots of efficiency gains to be had.

However, I think we need to be more discerning with when we use email to communicate. Not necessarily because of the disadvantages of email (though there are many!), but because of the advantages of personal (face-to-face or voice-to-voice) communication.

I’ve put together some guiding principles for when email should be avoided (based on my own observations and mistakes) – what do you think?

1. Avoid email…when you are asking someone to serve.
Inviting someone to participate in ministry is a special interaction. You are recognising that they have gifts and abilities that make them suitable to serve, and you are inviting them to use these gifts to serve the Body. It’s easy to think of asking someone to serve as simply filling a gap, but by making this a personal conversation (phone or face-to-face) you have the opportunity to encourage them (by noting the gifts you’ve seen that God has given them), and by painting a picture of the vision you have for the ministry, with their involvement.

2. Avoid email…when you need a quick response.
If you need to confirm that Suzie can read the Bible at church on Sunday, if it’s less than four days out, a phone call is the best way to confirm. A phone call enables instant confirmation (rather than waiting for a response, or wondering if they even got the email!), and if they are unable to serve, you’ve still got time to find a replacement.

3. Avoid email…when you want to encourage someone.
Think of the difference if you were to receive an email encouraging you for the good job you did praying at church on Sunday, or if you received a phone call to communicate the same encouragement. The effort taken to make the phone call, plus the personal nature of the conversation, makes email the lesser option.

4. Avoid email…when you are upset.
I’ve sent emails when I’ve been upset, and this was foolish. I’ve said things that I would never have said in person. I’ve reacted to things that would have easily been clarified if I’d picked up the phone or met up in person. It’s easy to fire off an email when upset, but it’s a foolish option.

5. Avoid email…if there’s any chance your email might be misunderstood.
The written word is easily misunderstood – either because the writer may not have written clearly, or because the reader may have read with his or her own bias. Regardless, if there’s a chance that a misunderstanding might occur, the potential time spent in damage control dealing with the mis-communication will soon overtake the time you should have spent making the original phone call.

6. Avoid email…when you are canceling or apologising.
It’s not easy to tell someone that you can no longer come along to an event, or can no longer (or would no longer like to) be involved in a particular ministry. Email is an easy way to communicate this, but I think it’s a cop-out. I think this is a simple issue of courtesy (and the same goes for cancelling via SMS!). Similarly, it’s much easier to apologise over email than in person. To apologise in person displays humility, plus you have the advantage of being able to ask for forgiveness, and for the other person to offer forgiveness, thus restoring the relationship.

7. Avoid email…when you have a suggestion on how to do something better (i.e. constructive criticism!).
When you send an email, you don’t know how the recipient is going. They could be having a terrible day/week/month. Your feedback could be the straw that breaks the camel’s back! Giving feedback in person allows you to see how the other person is going, read the visual cues, and communicate gently where necessary!

8. Avoid email…when you are rebuking.
Similar to the example above, delivering (and receiving) a rebuke isn’t easy at the best of times. In personal interactions, facial expressions and body language count for a lot (this video gives a good explanation of non-verbal cues). When rebuking, responding to these cues is important. Therefore, I would go the further step to suggest that the best way to rebuke is face-to-face, not even over the phone.

9. Avoid email…when the interaction will be back and forth.
Email isn’t the forum to converse – it takes time, it’s prone to misunderstandings and it’s not immediate. If you want to have a conversation with someone, have a conversation.

10. Avoid email…to share private information.
When you are sending an email, like it or not, there is the potential that the contents of the email may be shared with others. This isn’t always a bad thing (e.g. you can forward an email with prayer points), but private information that would be harmful if distributed beyond the recipients of the email should be discussed in person. Therefore it’s safe to assume that the contents of an email may be made public, and communicate in person where necessary.

This is just a start based on my own experience – what would you add or subtract from this list?

Page 2 of 5«12345»