Tithely

What Tithely is
At it's core, Tithely is a donation tool that supports churches and non-profits in collecting and processing online transactions via ACH transfer, Credit/Debit, Cash, or Check. The product suite has expanded over time to become an all-in-one solution for churches, including things like registration and ticketing, member tracking, and self-service website and app builder tools.

• 40,000+ organizations
• 240,000+ monthly active users
• $20m in ARR

💻 Online Collection: Create a custom donation form for your organization and collect donations online or via text-to-donate.

💳 Financial Tools: Track physical forms of payment,  set campaign goals, generate tax statements, and more.


📱 Apps & Engagement Tools:
Collect information, tag data, save reports, and streamline communications through email or sms.

Admin Dashboard for Giving
How I made it better
🎨 No design process? No problem.
Alongside the Product Operations team, the Director of Product, and the Director of Engineering, we established flexible and scalable processes that made sense for where the company was at in its growth. Creating UX-owned spaces in company tools like Atlassian and Slack created much needed transparency and helped teams understand and prioritize design needs.

🙋🏽‍♀️ Asking stupid questions
Does anybody really want to use this? Why did we do that? Is this necessary? I found myself asking at least one of these questions in any given meeting. Sometimes, the thing that is obvious to everyone in the room just needs to be said. Design is meant to advocate for real people, and sometimes that means popping the hive-mind bubble and forcing the team to see things from a different perspective.

📝 Defining the undefined
Before I joined, the company was made up of 7 completely independent products–data, styles, layouts, nomenclature, and navigation were incompatible. But even with a vision for an all-in-one solution, internal teams struggled to communicate effectively and define work because we had no source of truth for how we should be talking about users, products, or features. After workshopping over the course of several weeks with various stakeholders in Marketing, Sales. Revenue, and Finance, we were able to align on and document terminology which allowed us to operate more uniformly across each and every team.

🎓 Mentorship
The reason I showed up to work every day was not because I loved creating software for churches. Helping other designers grow in their roles and find their voice at the company has been the most rewarding part of my time there. I empowered our junior designers to run internal workshops, interview customers for discovery, and truly understand what it means to own the UX direction and how to create space for that ownership.

📣 Context and communication
The path to providing a great user experience starts with buy-in from the company; you need everyone to be as excited about the thing you're designing so that they sell it, market it, build it, and support it to the best of their ability. If they don't understand why what you're doing a good idea, it's going to show in all corners of the product and experience. Cross-department communication and storytelling was where I spent a lot of my time; I was recognized as Tithely's product person of the year for helping internal teams stay in alignment which contributed to the overall success of our product.
Donor Experience - Giving to an organization
Navigation Explorations on Mobile

A company of acquisitions: how we successfully merged 7 stand-alone products into 1
What went well
• Teams cared, a lot.
• Clarity isn't easy but along the way we were able to articulate and document gaps in validating and understanding the experience, which became an invaluable tool when working with users to shape the final product.
• Existing customers still in the legacy experience are chomping at the bit to be migrated into the new experience, with some willing to pay for two subscriptions until we are able to migrate them.
Where we struggled
• It took way too long to define measurable outcomes–we were vaguely chasing "unlock new revenue streams" or "increase average revenue per user" for the first half of the project.
• Major changes in leadership–VCs, VP of Product, CRO–led to a constant shift in goals and priorities.
• Product and Growth teams were working long hours, having repeat conversations, and sitting in meetings that often felt purposeless before we were able to align on what we were actually trying to accomplish.