Pushpay Hackathon

Building Resources For The Overwhelmed Pastor

Client
Resi by Pushpay

Duration
48hr Hackathon

Role
UI Designer + Product Marketing

Tools Used
Adobe Figma, Figjam

Introduction

Pushpay held their annual 3-day Hackathon in which I participated in a group of 6 individuals (Engineers, Product Managers, Implementation Specialists, and designers).

During the 3-days, my role become product marketer and UI/UX Designer in which I helped organize and document our projects scope, align our persona, and design the product with Pastors in-mind.

Goal

Our main objective going into this hackathon was “How do help assist Pastors and Leaders of the church build congregational connection, deepening conversations amongst members, and drive more engagement within the app?”

Through our conversations as a team and with Pastors, we were able to narrow down our scope to how we can support their ministry by providing tools to support resources generation from current accessible proprietary material such as their on-demand livestream content.

Inspiration

Validating our ideas

While we were ideating on our ideas of the product we wanted to develop, we scheduled some meetings with Pastors to hear their thoughts and feedback. Through a few meetings with them, we were able to gather important feedback that helped us consider possible scenarios of the functionality such as real-time scenarios, bullet-points, and turnaround time.

During this time, it allowed us to have conversations with the engineering team around processing accuracy and token limits within the AI models and what potential solutions they could use to effectively build the sermon/livestream summaries.

Wireframing & Mockups

“Recognizing the limitations of AI models, I designed mockups that grouped content by resource type (e.g., summaries, guides, reading plans) and demographic (e.g., youth, families, children). This structure made prompts more consistent while improving both cost-efficiency and output accuracy.”

  • Idea 1

  • Idea 2

  • Idea 3

  • Idea 4

  • Idea 5

Think it. Build it.

From my talks with the Engineering Team, we discussed the user interaction and how they should click specific touchpoints. We eventually landed on Idea 5 which allowed for a dropdown experience where the user can select one content type and one audience type.

From our testing, this made the most sense from an Admin perspective.

Generating resources made easy

From our discussion with Pastors, Senior Leadership and hearing from church attendees, we found that this idea resonated deeply. Our team won 3rd place in the Hackathon out of 16 teams and currently investigation and research is ongoing as the team continues to work on future development.