Design Thinking and Church Community: Step Two - Define!

This post is the third in a six-part series on building Digital Church Community with Design Thinking, a series responding to the challenges of building Christian community in a pandemic. Click here for the intro post, and here for thoughts on starting design thinking with empathy!

All church leaders want to build "community." If we weren't invested in community-building, we wouldn't have gone into such a difficult line of work! The key challenge in community-building isn't a challenge of motivation or volition. It's a challenge of specificity.

When we set out to build "community," we don't actually know what we're looking to build. So we set out to extract the concrete from an abstract, which is to say, we set out to take specific actions based on a concept that is vague at best.

During my time working at Pine Lake Camp in Waupaca, WI, I recall seeing a poster on the staff office wall promising "1,0001 ways to build an intentional community." While I enjoyed reading through the ideas, the very fact that one could place 1,001 ideas on such a poster attests to the fact that "community" is an important yet highly ambiguous concept for today's Christian public leader.

What exactly is community? What is community within a virtual Christian setting? And why is a particular expression of community meaningful within a given ministry context? These are the questions that the church leader sets out to answer in "Define," the second step of the design thinking process.

According to interaction-design.org, step two of design thinking begins when we realize that:

It’s time to accumulate the information gathered during the Empathize stage. You then analyze your observations and synthesize them to define the core problems you and your team have identified. These definitions are called problem statements.

So while our intentions to build community, and specifically build virtual community are high-minded and idealistic, we do not begin with the question of "how do I build community?" As designers, such a question wouldn't generate ideas with adequate specificity and feasibility. Instead, we must begin with a problem, the problem that was discovered while Empathizing.

The problem we define in this step is never a lack of "community." The problem we must define is situated in the observations of our context, and framed as a question worthy of further design efforts. To truly design a collaborative solution, we must start with a problem that was collaboratively defined. We, therefore, define this problem by carefully analyzing the data from the "Empathize" phase of design thinking. When we listened to our community, what did they say? What themes emerged multiple times?

Analyzing this data and synthesizing it into design thinking, we will arrive at two outputs from the "Define" phase:

• A problem statement derived from the Empathize process, explaining what a church needs and wants from its "community"

• A research question that will inspire us as a design thinking group to solve the problem.

Let me provide an example of a hypothetical problem statement that may be relevant to some church leaders, circa October 2020:

"Disconnected from in-person worship, our congregation dearly misses the grace-filled experience of a Sunday morning sanctuary, where they could unplug from the problems of their day-to-day."

This problem statement, likely derived from a congregation struggling to navigate the turbulent conditions of a simultaneous pandemic and an election season, is helpful in that it allows us to craft our research question:

How can our church create moments to come together and unplug during this tumultuous season, so that we can collectively experience moments of grace?

Having defined the problem we seek to solve through design thinking, and framed the problem in the form of a question, we can turn our attention to a powerful brainstorm: the Ideation phase of design thinking, the subject of our next post.

---

@ryanpanzer is the author of Grace and Gigabytes.

What Every Church Leader Should Know about Building Digital Community

This is the first post of a new series on using Design Thinking to build virtual church community. Click here for our second post, which details how to start the Design Thinking process!

“Worship attendance is fine, but it doesn’t feel like a community anymore.”

It’s a quote I continue to hear from church leaders navigating our new normal. Perhaps you’ve said something similar at one time or another. Sure, members are tuning in to watch live-streamed or recorded worship. Maybe your finances are even secure thanks to members stepping up their generosity in recent months.

But still, something’s missing. We miss that sense of community our church enjoyed prior to March 2020. We lament that it’s just not the same, we acknowledge that an entirely virtual church is often a poor substitute for the face to face community that brings so many of us to church in the first place.

It’s hard to build a digital church community in “normal” circumstances, let alone during a pandemic where many of our families are juggling working demanding jobs from home while homeschooling their kids. But as church leaders, we are nevertheless called to build community, even when such a task seems unachievable.

While tactics for building a digital church community will vary from one congregation to another, community building in these uncertain times begins with a clear awareness of the challenges and opportunities involved with building up our now-distributed communities.

With an understanding of why it’s so difficult to build this digital community and why it’s so important to do so, we can begin to find the small acts of community building that will bring us together in profound and powerful ways.

The challenges are often self-evident. Our communities are busier than they’ve ever been. Parents are trying to teach and motivate their students, who are often reluctant to learn virtually (four in ten students didn’t complete any virtual homework last spring).

They’re also burnt-out in digital connection. Zoom fatigue is very real. Google searches for the query “Zoom fatigue” increased 1,000% between April and May 2020. Some have even suggested that online calls lead to unhealthily low levels of respiration - we don’t breathe as we should while online. This observation, described as “Zoom Apnea,” may explain why distributed, virtual work is so exhausting. Those who are working from home have little energy for additional digital engagement after the workday ends, and hardly any appetite for more video calls. And of course, an election is taking place. 55% of Americans are currently “worn out” by political posts on social media, while 70% find online politics discussions “exhausting." So many of our assumptions on digital church community intersect with social media, yet social media has its own set of problems.

But just as there are many challenges, there are even greater opportunities. If we find a way to create a sense of virtual community within our church, we can provide a moment of Sabbath rest, where we can all pause together, breathe together, pray together. If we find a way to connect our flock during this time of social distancing, our church can provide a concrete taste of grace and forgiveness, often lacking in social media environments. Perhaps most importantly, if we find a way to create a digital community in these divided times, we can inspire hope in the promise that God is greater than any pandemic, that Christ is our salvation, and that these challenging times will end.

So how do we realize these opportunities? How do we build a digital community that promotes a sense of rest, connection, and hope? We begin with the acknowledgment that community building is highly contextual. What works for one congregation will not work for the church across the street. We also start with the tacknowledgmenthat not all digital community is synchronous. In an environment of Zoom fatigue, we need not log on together to find meaningful connection.

From this starting line, we must apply the design thinking process to craft meaningful community moments that resonate within our context.

What is design thinking? According to Interaction-Design.org,

"Design Thinking is an iterative process in which we seek to understand the user, challenge assumptions, and redefine problems in an attempt to identify alternative strategies and solutions that might not be instantly apparent with our initial level of understanding. At the same time, Design Thinking provides a solution-based approach to solving problems. It is a way of thinking and working as well as a collection of hands-on methods."

Design thinking can build community in these challenging times because it facilitates the identification of alternative strategies and solutions. As a process, it moves us well-beyond the proverbial box, revealing the best ideas for our ministry context.

In upcoming blog posts, we'll explore design thinking and what it means for the church. We'll dive into each specific step in the design thining process (from empathizing to testing and everywhere in between), and offer suggestions for using digital tools to support collaborative brainstorming. Many, if not all church leaders, have lamented the breakdown of community during the COVID-19 pandemic. It's time to start rebuilding. Let the designing begin!

---

@ryanpanzer is the author of Grace and Gigabytes.

What Every Church Leader Should Know about Google Analytics

This is the latest in an ongoing series on digital marketing for church leaders - be sure to check out the companion post on advertising with Google!

"You can't manage what you can't measure."

-Peter Drucker

If you're a church leader, you've likely grown accustomed to measuring some key numbers in your church. You likely know (approximately) how many attended a worship service, or more recently how many watched an online worship service. You might know how much money you have in your budget, and how much you received in tithes and offerings last Sunday. It's likely that somewhere in your career you were trained to think about the"butts and bucks" numbers as the key performance indicators for your congregation (for more on how to move past "butts and bucks," check out Katie Langston's blog on Faith+Lead).

Doing church online requires a new approach to measurement. What matters in the virtually distributed church is the effectiveness with which your church's digital presence (ie, its website and social media) connects with your community. We can measure this level of connection with free digital tools, the most insightful of which is Google Analytics.

Google Analytics is an application that automatically collects data on website traffic, instantly organizing that data into reports and dashboards. Fully customizable and completely free to use, Analytics is a must-use tool for determining whether digital efforts are achieving the intended results.

When you start using Google Analytics, you'll be able to measure how many visited your website, what they did there, whether they stayed and engaged or quickly "bounced," if they viewed multiple pages or just one, and if they eventually returned. This data helps church leaders to determine when, where, and how communities are coming together on the church website. All of this data, of course, is aggregated and anonymized to protect user privacy. In this post, we'll look at some of the first steps you'll want to take as a church leader during COVID.

To get started, you'll need to sign up for Google Analytics with a Gmail account. Once you've signed up for your website, find and add the Analytics "Tracking Code" to your church website. The code snippet is what sends website data to Google Analytics, enabling you to view important reports on site visits and user activity.

Installing the "Tracking Code" tends to be the most confusing implementation step for new Analytics users, so don't be alarmed if takes you a moment to complete the implementation.

Simply copy the code from Analytics and paste the tracking code beneath the <head> tag of your website.

What's a <head> tag, you might ask? It's the "header" of your website, appended to all pages on your domain. If you can find the HTML for your website, all you'll need to do is paste the code near the top. Google Analytics will do the rest.

Once the tracking code is added to your website, you'll start to see site data in Google Analytics, which will look something like this:

With the code properly installed and site data showing up in your Analytics accounts, it's time to start measuring. While Analytics offers millions of datapoints and segmentations for you to analyze, a beginner Analytics users should focus on users, session duration, and pages/session.

"Users" measures the number of unique visitors to your church website as determined by the date range in the upper-right corner of the Analytics UI. A key question for a church during COVID is the number of users relative to the size of your congregation. If your website is effectively connecting to your community, the number of users in a 30-day window should be similar to your unique monthly attendees. If a church saw an attendance of 350 on a typical pre-COVID Sunday, it should strive for 350 monthly website users.

"Session duration"is the average time spent on your webpages during a single visit to your site. If I visit your homepage for 60 seconds and then leave your website, my session duration is 60 seconds. If I visit five different pages on your website for 10 seconds each, my session duration is also 60 seconds. Since all churches and all websites are different, there isn't a benchmark "session duration" that we ought to strive for. Rather, session duration is a metric of directionality. A key question for today's church leader is whether session duration is trending upward or downward. When church communities find relevant, spiritually-edifying content on a site, session duration increases. As you build out your site and add new types of content like blogs and video pages, see if session duration increases.

"Pages/Session"is the average number of pages a site visitor views per each unique visit to your site. If I visit your site but remain on your homepage, my Pages/Session is 1. If I visit your site and view your Worship page, your blog, and your Contact page, my Pages/Session is 3. Pages/Session is a helpful metric in evaluating whether your website is efficiently funneling traffic to key pages within your site. As a church, you'll likely have a page for worship times/streaming, a blog/videos page, a giving page, and many other pages that are vital to your ministry. Your site should make it easy for a user to switch between pages. A key question for today's church leader is how to maintain a Pages/Session average of 1.5 or more, indicating that the average user connects to more than one resource during their session.

Google Analytics can be overwhelming to those without backgrounds in tech or marketing. If you're feeling like there's too much data and it's hard to know where to get started, take a step back and review some of Google's self-paced learning materials.

Then, identify two or three key performance indicators (KPIs) that you will commit to tracking over the course of four weeks. At the end of four weeks, consider what these numbers might tell you about the quality of your website.

What changes might you make based on this data? That's fundamentally what using Google Analytics is about - not numbers, not graphs, but deriving insight from data. With enough practice and sufficient patience, every church leader can use Google Analytics to strengthen their connections with the community, particularly in an era of disruption.