Designing InterVarsity’s Web Strategy
The Challenge: A fragmented user experience created by a decade of building 42 disconnected, department-focused sites.
The Goal: Develop a simple, streamlined, web strategy that enhances ministry, leverages the unique capabilities of technology, matches what we can actually support, and has a demonstrable impact on the ministry.
My Role: Strategist & Research
Discover
The Data
First, we could see that sites with a variety of resources were increasing in usage compared to sites that had one type of resource.
Single Type Resource Site - Student Soul
Multi-resource Site – The Ministry Playbook
Only 25% of the 42 sites were getting quarterly updates.
Only 36% of site owners were satisfied with their site.
Only 36% of the 42 sites were being actively promoted.
The People
The Web Strategy Leadership and I conducted 60 interviews across every department and 4 listening sessions with users.
-
To know what opportunities were available to students and faculty through InterVarsity:
what was an InterVarsity is community like
how they could involved
how they could grow in faith
what conferences were happening, etc.
-
Learn how to and gather resources for:
Making compelling invitations
Sharing the gospel
Running a Bible study
Answering hard questions
etc.
-
With the barrage of non-profits asking people to give, occasionally I forget that alumni, family and friends of staff, and others deeply want to and in our current system they were working really hard to do so!
-
Help staff find information specific to them like:
What our HR policies are
How to resolve conflict
What our theology statements are
How to file an expense report
How to fundraise
etc.
“I wish there weren’t like 5 sites.”
“It’s crazy to me that I have to go to one site to give, another to get training for my volunteer work, and another to get resources for my bible study, and yet one more to find the gospel diagram.”
“I just want to do my job. Why should I use your system when I can jump into weebly and do in 15 minutes what takes me 15 hours in Drupal?”
At the risk of over-simplifying, the ‘jobs to be done’ fit into one of four functions.
-
When our users did a search, they were overwhelmed by all the results. Yet, when shown them sites we thought they might find useful, they were grateful for a new set of resources at their fingertips.
-
We had a typical set that a non-profit might use: donors, volunteers, staff, constituent, etc.
But when you have a person is a former leader, an alumni, giving to a their local chapter and is considering coming on staff, they needed to visit 7 different sites to make all those labels 'happen'. Oof.
-
As years passed, the grew increasingly more frustrated that the system they had to use was complex and confusing alongside in comparison to other platforms they used in other contexts (Weebly, Wix, etc.)
-
We were fairly certain coming in that we would be building some sort of web system that would churn out a website for every InterVarsity community.
It turns out we were too late and staff were pretty happy with a combination of Instagram and Linktree - why bother with domains and hosting?
You could sum up our audiences like this:
📖 Ministry Participants
Anyone participating in campus ministry – undergrad students, grad students, faculty, etc.
🙏 Ministry Leaders
Anyone leading campus ministry – student leaders, campus staff, faculty, volunteers, as well as college student pastors, youth pastors, etc
🧡 Ministry Partners
Anyone who financially partner with InterVarsity to advance the overall mission – donors, churches, etc.
INTRODUCING:
InterVarsity’s New Web Strategy
Share the Invitation
Tell God’s story of InterVarsity and share invitation into the new yew with God and with InterVarsity – whatever that may be.
Equip the Called
Equip God’s people – whoever they are – to do campus ministry with a best-in-class learning center.
Serve Staff
Equip those who need support with organization provided functions like finances, human resources, technology, fundraising, etc.
Define
I depicted the marketing + engagement cycle for each of our audiences and key segments ↓
From these, we could ideate about what our web experience could be like!
Taking the ideas, I worked with each audience representative to describe the before & after of what we envisioned our new web experience to be like.
Vision → Strategy → Structure
We had our vision: We envision a simple, streamlined, web strategy that enhances ministry, leverages the unique capabilities of technology, matches what we can actually support, and has a demonstrable impact on the ministry.
We had our strategy: to do that, we needed to share the invitation, equip the called, and serve staff.
With the strategy and journeys in place, we could design our web ecosystem’s architecture!
InterVarsity.org
Prospective Participants
Learn about InterVarsity experience
Find a Chapter
Campus Participants
Grow in faith
See national opportunities like global trips and conferences.
Ministry Partners
Give to their local IV community
See what’s happening in InterVarsity
Alumni & general public
Consider volunteering
Consider coming on staff
and other needs like PR, Campus ministry thought leadership, etc.
Equipping Center
Staff, Student Leaders, Volunteers
Take courses on core campus activities
Access ministry tools
Manage chapter information
Download Bible studies
Grow in their own discipleship
Download resources for navigating conflict, discipling others, etc.
Staff
New and recently piloted resources and courses
Staff submitted content & resourcing
Staff Hub
Organizational communications
HR policies, benefits
Spiritual resourcing for staff
Theology resourcing
Finance management
Chapter data
Fundraising resourcing
Staff support & services
Is it simple and streamlined? Yes! ✅
Will it enhance ministry? Yes! ✅
Does it leverage the capabilities of technology? Yes! ✅
Is it supportable by our team? Yes! ✅
Prioritizing your users first is always worth it.
It has been a difficult, but worthwhile journey to shift national leaders’ perspectives from their own personal desires to a partnership where we meet our user’s needs together.