Multiple Third Place Environments

Faq green

Recently I received the following question on Third Place:

We planted our church in ’07. Currently, our Gospel Communities meet for a meal together and Bible discussion twice a month (every other week), and people meet in tripods (LTG’s) the other two weeks.

While our GC’s have certainly done “Third Place” gatherings, that is not something we have implemented into our DNA like the other two gatherings. Our GC’s are a diverse mix of college students, recent grads, young marrieds, and families with young kids. Finding a third space that is natural and regular for this group is difficult. I’d love any feedback you could give me on implementing a third place into GC’s where life rhythms are wide and diverse.

I’ve actually had a number of people ask this question, so I thought I would post a response.

First, I think this question is so often asked because we primarily conceive of community as an event we attend rather than relationships we have. By and large, the three kinds of gatherings are meant to serve the relationships you have by creating intentionality in what you are gathering for.

You don’t need to have everyone at every gathering all the time! In fact, I think you’ll be far more successful if you don’t have everyone all the time.  We’ve had a number of missional communities who bring 12 people to a particular location, only to have one other friend who doesn’t yet know Jesus join.  That’s a difficult social setting for anyone to walk into!

I’d highly recommend that you work on having multiple different “Third Places” for each Gospel Community. When you have a great diversity of people, focus on having a couple different places where two’s, three’s and four’s of people can gather and invite people they know that don’t know Jesus to spend time with them.

The place or the event is less important than intentionally creating overlap between your community and people who don’t know Christ.

What would you add?


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.